At a web-startup there is a tendency to start building stuff with screens and mock-ups. While it seems so obvious and tempting to jump at a program and create a mock-up and wire-frames; it’s not a wise idea. Of course your service / product are online and has screens and is a site but it’s not just a series of screens.
It’s a flow of processes. Usually one integrated in other. Start with flow charts of how these things flow.
That ways, not only you will know what’s more important (how it works and not how it looks) but you will get the user experience thing right (yea that is where it begins).
Refine your flow charts to make it simpler. Can you describe whole function of your website in simple chart? What’s the central thing? Is it user? Their bio? Their conversation? What can you make easier? What do you need to make more complex?
It gives you a very clear mindset about where you are headed. Now make the screens that come in a flow one after another. The more time you spend on earlier stages, the more refined the product and the more control you will have over it.
And if you are working with designers / developers – involve them in the process (but take the advice with pinch of salt). Use common sense. It’s a good idea to include a non-techie to involve in the process… just a random person off the street who uses web will do.
Photo by chego101
Got a reaction? Got something to say? You can praise / bash / discuss this post on twitter, mail me or just do a reaction on your blog. Here are some people who tweeted about it:
{ 2 comments }
I don’t know how you know so much about all this stuff, King… I guess it’s common sense ;).
Contradiction!
If it’s common, why’d you wonder how I know? If you wonder, why’d it be common? You know what I mean?
I’ve been guiding and building some of these startups / web-apps lately. So I post what to you & me seem obvious – but somehow “they” miss it. :P