| Common Mistakes: Specifiying Fucntional Web Specification |
|
|
Page 3 of 3 Not enough visual supports or purely text based: Textual description of Web applications can be interpreted subjectively and hence leading to wrong expectations. To avoid setting wrong expectations, which may are only discovered during development or at worst at launch time, functional specification need to be complemented by visual supports (e.g. screenshots or at best HTML prototypes for home pages or any major navigation pages like sub-home pages for the major sections of the site such as for human resources, business units, finance, etc.). This allows reducing subjective interpretation and taking into account the users' feedback prior development. Such an approach helps setting the right expectations and to avoid any disappointments at the end once the new application is online. We have observed these common mistakes, independently if companies have developed their Web applications internally or subcontracted them to an external service provider. Benefit from our freely availabe Web publications. Subscribe to our FREE monthly newsletter on Web design, usability and strategic Web marketing. Subscribe to our FREE Webinars providing you pragmatic advise on how to boost your Web sites. Article by Nicolas Burki Nicolas Bürki is the founder of effinfo.com, a European based usability and Strategic Web Marketing company providing you actionnable and pragmatic publications on online marketing, usability, Web strategy, Web Goverance. Our consulting engagements are delivered in English, French and German language. |
| Next > |
|---|