Ignore site maps, create functionality ones instead
How many CMS sites have you worked on last year?
OK, maybe not many. Maybe you still work in the Jurassic era and do all changes for your clients in the code. The majority of sites these days require some form of a CMS systems though. And that means their owners have full control over their content. Also, they now decide what goes where. Very often your expertise in that field is no longer required.
Web design has definitely changed and you can either cop on or extinct. Not a great prospect, eh? Two years ago you could have shown off how great you are by your knowledge of creating the sites structure, today the client knows better. And very often doesn’t want to listen to you.
Good news! There is something new though they need your help with.
Functionality. Content management is no longer a problem but how the site works is. And it’s often your call how that gallery works, how contact form processes the information or how product catalog indexes all items. It’s also your job now to communicate those ideas to clients in a clear and
understandable way.
Therefore from now on, ignore site maps. They are a massive waste of time. Focus your energy on functionality maps.
Here’s how to make one.
List all pages with a list of functionality beside each page. If necessary draw a quick step by step sketch of how certain functionality will work. Think of it as a functionality story board.
Help your client understand what you are suggesting to them. And remember, the main rule of functionality is that it has to be easy to operate and easy to understand for the visitor.
Last thing, consult your developer before you pass your functionality map to the client. These days you can develop practically any system with time and cost being the only things that may stand on the way.
And they very often do.
–> Something extra to think about: <–
- when was the last time you checked how your desired functionality works? Do you visit scripts producers sites and view demos of their systems? Do you ask your developers for advice on what are the best solutions for what you want to achieve? Or do you just play smart?
- which web development blogs are you subscribed to? Do you follow new technologies and issues with the existing ones?
Good stuff … thanks.
Cool tips, thanks!