RE: [IxDA] Wireframes and prototypes: a waste of time?

3 Aug 2010 - 11:07am
4 years ago
1 reply
668 reads
Alex Hogan
2009

What is the level of experience that the programmer has?  I ask because it sounds to me like a statement that would come from a programmer that has enough experience to not be considered entry level but not enough to be considered senior.  They are extremely comfortable in their understanding of what they do but don't have the knowledge or experience to understand the "bigger picture" and how the process was established or why.

I'm not trying to be derogatory.., I have a development background and can identify with their statement remembering where I was when I was saying things like that.

They have to understand that by the time you get to wireframes there have been a series of documentation that led up to the decisions and layout that you present in the wireframes.  There were considerations from the initiative as it was initially presented and your previous deliverables from analysis may have either supported or refined that initiative.

Creative should give back what you present in the wireframes.  If they are deviating greatly from them then they may be taking too much liberties and run the risk of prolonging the project.

Bottom line is that if development  doesn't have a clear and concise set of wireframes that are clearly annotated, referencing the requirements where applicable, and visually explain any non standard functionality (with accompanying flows), then it is going to take them a lot longer to develop the project.  Why?  All the interpretation from the requirements and business rules have been done for them.

Thanks,


alexhogan

Information Architect
linkedin: http://www.linkedin.com/in/alexhogan
twitter: http://www.twitter.com/hogana


Comments

3 Aug 2010 - 9:16pm
Nancy Roberts
2008

Thanks, everyone...

These are very useful insights. I think there are bits and pieces of my situation in most of them! Yes, I do have a political issue more than a process issue, and I agree, the same exact process isn't going to work for every project - each one needs an approach that suits the requirements, the client, even the feel of the project (within reason!). 

While I'm pretty sure that the wireframes and lo- medium-fidelity clickable prototypes are ffrequently the way to go, ultimately it might make sense to crawl before we walk. I am intrigued by the idea of clickable lists or "word" diagrams. This might feel like less of a threat to a creative than a symbolic diagram, however rudimentary. Then maybe laterI can sneak in a box or two... desensitization training?

Hey, as long as I can do - and document -  the necessary thought process that makes the site or application interactivity usable and intelligible, then we're heading in the right direction.

You've all given me a lot to think about. Brilliant, thank you! (And don't stop... any and all ideas continue to be welcome!)

Syndicate content Get the feed