[Photo credit: Mind Map covering the issues of Owning a Cat by MyThoughtsMindMaps, on Flickr]

Think about what happened the last time you really considered what should be on your website. Ideas and thoughts probably flowed in on your stream of conscious in no particular order, but rapidly:

• “We need to update the contact information.”
• “Oh, and Chris at the front desk needs to be added to the staff page.”
• “Didn’t someone say the other day they wanted a place to put articles about us?”

That’s a good thing. When you’re starting to plan a Web site, you want to consider every little thought or suggestion that’s come at you since the last time you updated your site. Your chief job should be to get everything down so you can process the information and make reasonable decisions when it comes to organizing the information on the site.

Here at Talance HQ, the best tool we’ve found to capture these early ideas is a mind map. “A mind map is a diagram used to represent words, ideas, tasks, or other items linked to and arranged around a central key word or idea. Mind maps are used to generate, visualize, structure, and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing,” says Wikipedia.

We’re very un-technical about it too. We take a big sheet of paper, or several scraps of paper, and write down everything we think of, drawing lines to connect ideas, or grouping the scraps of paper together.

The process is pure catharsis for website planning, and remarkably effective at helping you organize what seems like idea-chaos. Plus, since it requires no technical prowess, it’s a good activity for even the most technically challenged in your organization.

Request for proposals rarely fill me with joy. More often than not they’re a source of confusion, business-speak and unfinished thoughts, which we have to sort through and make sense of so we can send a reasonable bid to an organization that wants a website.

But last week I received an RFP from a non-profit that may have performed a Vulcan mind-meld on Talance. It was as if they had seen our new-client questionnaire and had preemptively answered all the questions I have at this early stage of a project. It filled me with delight (because I’m sad that way), and I know that it will make the project run smoothly, no matter who they choose to build the site.

What made it so great? Here are a few stand-outs that you can incorporate in your next RFP to help your project move smoothly from inception to completion:

1. Think it through.

The clearest RFPs benefit from discussion and planning beforehand. Make sure you talk with your team to form clear ideas of what you want your website to be, and then communicate your wishes through the RFP.

2. Write clearly.

Some people think “RFP” and pull out their cryptic businessese thesaurus so they can load it with fancy words nobody really gets. Pretend you’re explaining what you want to an idiot. Trust us, we Web developers get more out of it that way.

3. Plan your objectives.

You cannot hope for a site that reaches your goals unless you know what they are before you begin. If you want to be the go-to guide for volunteering opportunities, write it down and make sure that every decision you make from that point forward feeds back into that goal.

4. Order your objectives.

Some objectives are must-haves, others are nice-to-haves. Rank yours.

5. Go window shopping.

Everyone has seen sites they love, whether they be your competition or a mega-commercial site like Amazon. Start keeping track of sites you like, and make notes on what you like about them.

6. Know your branding.

Unless they’re new, most organizations have gone through some kind of branding exercise in the past, where colors, logos and other standards were developed. If you’re not aware of what these standards are, start asking around. We just had to redesign a website whose colors and logo were completely wrong in an earlier version, because no one checked. Translation: expensive.

7. Name your widgets.

If you want any special functionality, like slideshows, animations, photo galleries – anything – write it down.

8. Technical needs.

If you’re bound to maintain your website in a particular format, you like a CMS like Drupal or you don’t have the staff bandwidth to do updates, cite these constraints. Also note if you need Web hosting.

9. Name your budget.

I know, I know. You don’t want to come right out and say how much you want to spend, but your Web developer really needs at least a ballpark. We receive calls from clients who have $400 to spend, and those who have $40,000 to spend. We can’t help everyone, but it saves everybody a lot of time if I can tell them up front whether we can or not.

10. Make a schedule.

Decide when you’ll accept RFP questions, submissions and make decisions. Also note any ideal launch dates.

11. Contact information.

Sounds elementary, but make sure your prospects know how to reach you if they have questions. We received a bizarre system-generated RFP a couple weeks ago that had no personal contact information and was so hard to read we couldn’t even consider responding.

Laying this groundwork is incredibly useful for Web development companies like ours, but your staff will also thank you if you take the time to plan. Bonus: your funders will love you for eliminating money-wasting mistakes early on.

Someone wrote me yesterday looking for details on how I work with clients. I was saying on an N-TEN blog that it’s important to perform an internal needs assessment before you really begin to work with a website developer.

People generally know when they need a new site, but many tend not to start by asking what purpose the site should serve, what kinds of issues it should resolve and how it should look. Of course, this step is important in all companies, but I find it an absolute necessity with nonprofits that are governed by a board or committee.

So the first step we take with a new client is to encourage them to have these conversations together internally before talking to the website developer. That’s the idea behind a questionnaire we developed and hand out to our new clients before beginning on a project. I encourage our clients to send out copies to everyone on the team (from receptionist to CEO), have them fill it out independently and decide together what the final version should look like. Then they come to me with a filled out copy, and we talk through it together.

Everyone’s always really glad of this exercise, because people at organizations often don’t realize how different their thoughts are about their website. And it saves a lot of time and money when it comes to making a solid decision and putting together a reliable schedule.

Make sure to read through this blog posting on how to go about asking for a new website. It’s about what to expect from the company you hire. This is very important, because I find increasingly more often that a designer or a web developer will offer to build a website, but a designer lacks understanding of the underlying architecture, and web developers lack an understanding of how to bring it all together aesthetically.

We work with a project manager, a web developer who is an expert in human factors (meaning the way people naturally interact with technology) and a designer. All of us are able to address many questions before they’re asked and we consider our chief role as that of advisor. Inevitably, with expectations set early on, everyone is always happy with the final outcome.

You can find more info on our site on the kinds of sites we build. Oh, and we also have a deal with N-TEN members, so we can offer a discounts there, depending on what you need.