Oh, technical requirements documentation. So fun to read and so fun to write! All kidding aside, it seems to be a necessary evil. Otherwise, how do you know what to build?
Well, what if I told you that there is an alternate option? Interested? Good, then let’s talk about User Stories!
As information architects, we sometimes take wireframes for granted. We work with them every day. We live and breathe boxes and lorem ipsum placeholder text. What we don't often realize is that many people that we work with don't really grasp the concept of wireframing as it relates to web design. Often times, clients would just like to see a page mocked up in Photoshop and sink their teeth into a full-fledged design.
My lasttwo posts have centered around prototyping methods. Since I talked a bit about techniques, I thought it would be helpful to show an example in practice that we have used for a project I'm currently working on.
Wireframes have been an indispensable tool for information architects to present and communicate the web page layouts and content placement to clients and developers. In revisiting our wireframes templates, I wanted to tackle a couple of issues that have been brought up across the years since I last wrote anything on the matter:
A reader of my last post, Prototyping for the Masses, brought to my attention an online tool used to create simulations of web applications called Simunication. I thought it would be good to add these kinds of tools to my list of prototyping resources.
In a previous post, I talked about the notion of "looking before you leap" as it relates to designing a website. Part of this "looking," or exploration stage, can be enhanced by prototyping.