So you’ve got a pretty good feel for what kind of new site you want.  Here’s some advice for efficiently building a site of great value.

1. Start with the content.

• gather all content together in one place
• content = words, photos, video, contact info, graphic art/logos…ANYTHING that will be visible by anyone who uses your site.
• organize it into acceptable file formats for the web (check with your web developer)

This is required work for any web project to be successful. Have it before you need it, or you risk wasting resources during your later project stages…because so many design/development decisions depend on what the final content is.

Too many website projects go awry because no one bothered to organize or produce the REAL content they needed for their REAL site. Everybody said “oh, that will be a demo” or “image area”, or “two or three paragraphs of content” and then assumed it would appear out of thin air. Content is the second-most important thing on your site, second only in importance to having users to appreciate it!  You don’t want to mess this up. Organize, write, edit, or produce the content yourself (or see to it that someone else does) now, not as an afterthought.

This is also a great exercise for you to be sure you will actually “say what you mean and mean what you say.”

2. Consider your users.

• put yourself in the shoes of your best customer
• what does he or she really want to do on your site?
• what do you really want them to do on your site?

Understand that the average web user is in a hurry and does not want to hunt for what he/she wants.  Don’t over think it.  Concentrate on user actions and clarity of information.

3. Assess the ‘minimum viable product’.

• what’s the simplest way to achieve your goals in a timely and efficient manner?
• think goals, not features
• separate the “would be nice to have” stuff from your bottom line “must have” stuff.  Prioritize both lists.

Understand that you can always add more stuff later (and you will want to), the important thing is to have a great foundation to build from.

4. Have a defined decision making process

• commit to being an active collaborator throughout the project.
• when it’s time to give feedback, be clear, be specific, and be engaged.
• when it’s time to decide A or B, be confident and be quick.

You should accommodate for change that will certainly occur during the lifespan of your project.  Building a website is an iterative process.  Sometimes the original vision doesn’t hold up under scrutiny.  That’s okay.  It’s not a failure or a setback…it’s an opportunity to improve and get things right.

Be ready to deal with important decisions in short order so you can keep your project momentum going strong and build a site of lasting value.

A great collection of interviews from the illuminating Jeffery Zeldman starting with the past, present, and future of web standards (and then on to the history of blogging, open source collaboration, and more).

Building a website is thought of mainly as a design and development challenge. And it certainly is. That’s indisputably the bulk of our business…ninety percent or more of our leads come to us seeking “web design” or “web development”, or both. Now those broad terms can mean all kinds of things when we start asking our questions. Every project is different. But ultimately that’s where the demand is, and that’s what our business supplies: web design and web development.

However, at some point (earlier the better) the client, the designer, the developer, or (oops?) the end user will each have to stare down the words on the page, and evaluate the message they comprise (or the damage they cause). There is nowhere to hide when it comes to content. If it stinks, the user will give up on you. So you work on it too make sure you don’t waste your time and money on a fancy website that speaks gibberish to the customer.

Would you believe that very often, almost always, the content strategy task of building a website can be just as involved with and urgently important to your ROI as any aspect of design or development? If that is overstating the case, it’s not by much.

What is “content strategy”, you ask?

In this excellent article published recently on one of our favorite websites, A List Apart, Kristina Halverson writes eloquently on “the Discipline of Content Strategy”:

Content strategy plans for the creation, publication, and governance of useful, usable content.

Necessarily, the content strategist must work to define not only which content will be published, but why we’re publishing it in the first place.

Otherwise, content strategy isn’t strategy at all: it’s just a glorified production line for content nobody really needs or wants. (See: your company’s CMS.)

Content strategy is also—surprise—a key deliverable for which the content strategist is responsible. Its development is necessarily preceded by a detailed audit and analysis of existing content—a critically important process that’s often glossed over or even skipped by project teams.

At its best, a content strategy defines:

• key themes and messages,
• recommended topics,
• content purpose (i.e., how content will bridge the space between audience needs and business requirements),
• content gap analysis,
• metadata frameworks and related content attributes,
• search engine optimization (SEO), and
• implications of strategic recommendations on content creation, publication, and governance.

There’s a lot more to digest in this very enlightening article, plus many others on the subject of writing for the web you should really check out.  We can’t recommend A List Apart enough if you really want to know what goes into building a better website.