Many nonprofit organizations that are beginning to adopt Web 2.0 technologies consider them the “cool” part of their online communication. They look at them as a way to engage younger or larger audiences or to project an image of hipness.

But the reason social tools such as Twitter, Facebook and Flickr have become so popular is that they make it incredibly easy for people to work together. Yet, if you look at the internal structure of many organizations, you’ll see that they communicate with one another through phone calls, printed notes and in-person meetings. True, there’s no substitue for face-to-face communication, but social tools can make it much easier to share information among your workmates.

For example, every time we have a meeting at Talance HQ, we have our intranet chat open to facilitate sending links or snippets of documents back and forth. We open a bulletin board for every project so the whole team can communicate about it, and we have a record of everything that was said. Our wiki keeps track of standard procedures and methodologies so we can access them any time, and make revisions when necessary. We use these tools in the office and with our team members who live across the country, and we do it because it’s entirely practical.

The majority of our social tools are built into our website (you do have a CMS, don’t you?). It’s the perfect place to build out a business, because everybody knows your web address, and it’s all centrally stored and accessible online.

Think about what you can do to make it easier for your employees to communicate with one another, and then give them the tools they need. You’ll very well find your organization runs better just by opening up new avenues of communication.

[Photo credit: AVP Volunteer 2 by yuan2003, on Flickr]

As any charitable organization knows, volunteers are superstars. They give love and expertise and don’t ask for a dime in return. They can be especially helpful if your organization has a website. Bearing in mind that an entire Web development project is long-term and requires dedicated knowledge and commitment that you’re better off hiring someone to do (upshot: it’s easier to fire someone whose work you’re not happy with), there are still plenty of other tasks you can assign out to people who want to help. Here are a few.

1. Social networking cheerleader
2. Add comments to blogs
3. Contribute blog entries
4. Participate in discussion on bulletin boards
5. Data entry (i.e., cutting and pasting info into a new site)
6. Website promotion
7. Adding your website to directories
8. Writing news updates about events
9. Website literacy workshops
10. Checking for dead links
11. Updating old content
12. Convert press releases for websites
13. Usability testing (i.e., make sure everything works in a logical way)
14. Bug reporting (i.e., look for and report errors or problems)
15. Identify requirements for new development
16. Browser testing
17. Taking pictures for the website
18. Formatting and uploading pictures
19. Making videos for the site
20. Uploading videos onto a service like YouTube or Vimeo, and adding them to site
21. Help manage wiki

Anything we missed? Add your ideas below.

This little gem has been hidden on the main Talance website, but we thought we’d bring it to wider attention. Use this checklist every three months or so to make sure your website is still up to date and healthy.

Site Content

• All links work
• All downloads work
• All forms work
• Contact information on homepage and accessible on every other page
• Addresses organization’s goals
• Has a favicon

Usability

• All images have ALT tags
• Custom 404/page not found page
• Each menu has no more than seven choices
• Home link in navigation
• User-friendly page titles

Readability

• Font size not too small
• Wide margins
• Good use of bullets, subheadings and bold
• No underlines except for hyperlinks
• High contrast text and images

Operation

• Looks OK in most common Web browsers (IE, Firefox, Safari, Opera)
• Uses limited Flash to comply with iPhone and iTouch
• Images are sized correctly (i.e., big image not squeezed into small box)
• Colors and images are consistent
• Loads quickly
• Looks OK in different screen resolutions
• Looks OK with various screen color settings
• URLs work without “www”

Security

• Pages requiring SSL access are accessible only via SSL
• No one has access to restricted areas that they shouldn’t have

Twitter updates come as fast as you can draw a sharp breath, but they may not be as spontaneous as they seem. Thanks to a selection of scheduling services, you can create tweets ahead of time and post them in the future, while you’re busy with something else.

Delayed tweeting isn’t the best strategy for building relationships with your followers (can you imagine having your half of a conversation an hour before you meet a friend for lunch?), but it can help when you want to deliver a message but aren’t able to.

For instance, if you want to notify everyone about a new project you’re launching on a set day. You can schedule the announcement to go out while you’re busy setting up said project. Or say you’re at a conference getting ready to speak. You want to tell your followers you’re about to step on stage so they’d better bustle down to the conference room, but you need to give the live audience your full attention.

Here are some tools you can use to set your tweets into the future:

• Hootsuite
• FutureTweets
• TweetLater
• Twuffer
• Calendar Tweet

At home, the flower beds are clean, the trees are pruned and the windows are sparklingly clear. I, probably like most of you, have been doing spring cleaning, and working my way down a list of home maintenance and improvement tasks. It’s satisfying to check those items off and look at the polished result.

At work, I’m also doing spring cleaning, and I hope some of you are too. I like to take some time every six months or so (call the second session fall clean-up) to tidy up some of the messiness that has worked its way into our website over the winter months. It’s also a good time to stand back and make some critical decisions about the functionality of your website and evaluate the direction you’re headed. Websites should never sit stagnant, and putting some time on the calendar at least twice a year to evaluate your strategy should be a given.

This week, we’ll guide you through a clean-up and revitalizing process that you can follow on your own website. Today we’ve got three things you can do to prep for your week of good housekeeping.

Put together a clean team. You’re about to do a major clean-up and make some big decisions. It’s not something one person should do alone, so put together a task force. If you are an army of one, just make sure to pace yourself. Here’s a good model for putting together a team:

• You should have someone at a high level who can either make these decisions or who has the power to put them on the schedule for evaluation.
• Also appoint someone to act as project manager. The person to put together a schedule, arrange meeting times and generally make sure everyone is moving along.
• Finally, have one or more people to do the busy work: someone to update copy, remove dead links, make little changes. Volunteers can be a big help here.

Dedicate half an hour every day. Consistency is the key to spring cleaning – not killing yourself with work. Just set aside half an hour or an hour every day for a week to evaluate what needs to be done. Your task may take longer than half an hour, but you’ll be able to budget how much time you’ll need to do it in half an hour.

Set up a place to submit comments/ideas. While you’re cleaning up the website you have, you’re going to have ideas about the website you wish you had. Establish a place for you and your team to submit ideas or discoveries so you can decide if you want to add new functionality to your website. Check out this earlier post Make a Better Website with a User Survey for ideas of how to collect ideas and responses.

Good luck setting up today. Tune in tomorrow for the next step in your polished-up website, and click here to see all stories about spring cleaning.

Many people start a web project by deciding they need a website. OK, good start, but that’s not where the project should end. Unfortunately, often it does, without any real thought given to what the website should do, what it should be used for and who should use it.

So the next step in starting a web project is to ask some questions, and who better to ask than the people who currently visit your website? Set up a questionnaire survey to find out what your audience thinks is most important. Take their comments into consideration for your needs assessment process (which I talked about here).

What those survey questions will be largely depend on your own organization’s directives. But a question like this might help you get started. I find Likkert-type questions to be the most useful in gauging opinion.

Please rate the value of each of these features, with 1 being extremely important and 4 being extremely unimportant.

- Ability to log on to access premium material
- A blog
- Video clips that demonstrate how we work

Make sure to leave a comments space so people can add features they think might be valuable. This is also a good time to evaluate some of your current processes, like asking people how long it took them to receive feedback or how easy it is to make a donation or pay for an item.

There are plenty of free survey tools out there you can use to collect responses, and just include a link to your survey online. But also send your survey out to your mailing list and include a line about it at the foot of outgoing e-mails or inserts in your paper newsletter.

Remember to not only use this exercise as building a route to a website that better serves your audiences, but add another survey in six months to make sure you’re meeting your users’ needs.

A publisher asked me the other day for advice on how to pare down the number of programs, software and tools his company uses. He is using a graphics program, a workflow program, a listserv and websites – that’s just what I know about. There’s probably more, including programs that handle subscriber databases, mailing lists, invoicing, purchasing and heaven knows what else. He’s desperately looking for a way to streamline the number of programs he has to deal with in a day.

It’s a problem that we’re seeing more and more often with our clients: there are so many free and useful tools out there that it’s easy to be sold on every one of them. Before you know it, you’ve got a million little programs with a million different users and one big mess.

Three things you can do to streamline your system:

Get yourself a CMS. A content management system (go, Drupal!) is the first step anybody should take when trying to figure out how to streamline. Imagine building a house out of Legos, but without the flat foundation piece to stick the bricks to. I always try to tell people to stop thinking of CMSs as websites and to start thinking of them as company platforms. It’s the thing you build from.

Get a whiteboard and markers to sketch out a production flow. And then reproduce that flow in your CMS. CMSs are master of ushering content where it needs to be, that’s why they’re called content management systems. These things are made for you to move pages from writer to editor to publisher in a regulated way. Once you figure out how your content should travel, you can come up with a production/editorial flow and permission settings that can bypass any outside software that does this. This also goes for CRM systems, where you might be tracking how people donate or subscribe or attend events. It should all fold into the CMS.

Ditch the listserv/newsletter service. Look at getting a newsletter plug-in for your site. That way you can build up a web archive of content, do some site-specific branding on your missives and eliminate one tool from the arsenal. The newsletter tool we use lets you do unlimited newsletters with unlimited issues, so you can have a quarterly update, a weekly blast and a monthly newsletter and they can all look different or the same. It also synchs up your site visitors with subscriptions, which is useful. (If you want to see it in action, sign up for the Talance newsletter, and you can see flexible it is.)

Lemme know how your streamlining goes. Use the comments form below to ask questions and report back.

Small businesses and nonprofits are in the unusual position of being executive staff, mail room clerk and chief technologist all at the same time. Everyone can lick an envelope, but not everyone feels comfortable taking the role of CTO with no tech background. Yet that’s just what happens when you embark on a website project. Here are a few things you can do make sure the development of your website goes smoothly.

1. Decide what you need. This is a good time to start polling the people you work with, because people at your organization may have different ideas about how the site should work than you do. Start with a needs assessment, and put all the feedback and ideas into a big list.
2. Prioritize. The needs assessment will help you compile a wish list of what you want on your website, but now prioritize. If you don’t define scope, your project could go on forever and cost more than you have. Divide your list into three sections: Must Have, Will Need, Nice to Have. Be prepared to take out a clean sheet of paper for any additional items you think of during the project. We advise our clients to set aside an additional 15% of the budget for these unforeseen issues. Anything else you can get to these items during round two. Six months from launch is a good time to think of scheduling this round two.
3. Appoint a traffic cop. During your project development, you need someone to be the central command between your organization and the development team. This traffic cop doesn’t need to know about technology, but they should be organized, good at delivering information and have the ability to call the shots when needed.
4. Create a feedback forum for employees. It’s nice to have a web form or survey somewhere where people can drop comments and ideas during development and beyond. Websites should always be in motion, so use feedback as way to make sure your site does what you want it to as your organization evolves.

Which would be the smarter way to run a project:

1. Leave all decisions-making power and creative control to a single person with a genius IQ, or
2. Share decisions and idea-making among a team of interested people?

There may be some power-hungry geniuses who could effectively argue the first choice, but my money is on a shared responsibility. No matter how well I know something, I can’t honestly believe I’ll think of every angle, and that’s why it’s important to gather feedback.

Yet many organizations – very often nonprofits with limited staffs – will leave construction and maintenance of a website to a single person. What a mistake!

When we work through projects with clients, we encourage them to discuss ideas together before coming to us. They’re usually surprised at how much their ideas about the site differ. This is one of the key reasons why you should assemble a reliable tech team to guide your organization through the process. I believe this is doubly true if your nonprofit is a church or synagogue or otherwise serves a large community.

Why build a tech team?

• It helps solicit feedback from your audience/congregation in an organized way
• Helps draw out other’s talents to achieve organizational goals
• It works!

When creating your tech team, make sure you have all areas of your organization represented, and make sure you know who’s in charge. Everyone has to have a voice, but it’s imperative for successful projects to have one person who can give the nod on development, and then have one person who can give the nod on an ongoing basis.

Once you’ve got your prospects for a tech team, run this checklist by yourself:

• Does your tech team adequately represent everyone in your audience/congregation?
• Is there a single person in charge who’s good at leadership?
• Have you decided who’s in charge on an ongoing basis?

Now you’ve got your dream team, you can put them to work on discovering what should go into your site. Best place to start? A needs assessment.

Volunteers are a gift to a nonprofit website. The problem is, well, they’re volunteers. You’re counting on them to help out, but you’ve got respect their time and other limitations. A salary is a powerful incentive you can’t use with a volunteer.

It’s a chronic limitation for synagogue websites. The webmaster for a New York-based synagogue was talking about this with me the other day. She said, “One of the biggest challenges, of course, is that the site is managed on a fully volunteer basis and there is only so much time I can devote to it.”

We effectively face the same challenge with Talance’s company website – we squeeze in enhancements between other client projects. But knowing that anyone who comes to our website forms judgments on the quality of work we do based on what they see there, we also know it’s vitally important to keep performing upgrades.

My solution is to set up what equates to a project management checklist with a priority number next to each task and put it in a central location. Whenever a team member (including myself) has a bit of free time, we just pick something off the list and do it. It seems easier to attack in bite-sized bits, and things do eventually get done.

We have our own project management software we use, but you might look at Google Calendars and Docs & Spreadsheets for hosting a centrally accessible spreadsheet you can use for a tasklist. I think simpler is always better when it comes to tracking a project.