Though it’s often overlooked, one of the best things about using Prototyping techniques is its responsiveness to change – no long-winded change approvals process; no complex recompilation; lower technological barriers to implementation.

All of these things mean that when the customer decides that page A should look a bit less like page B and a bit more like page D, the obstacles in your way are few and you can deliver that change with a very quick turnaround.  If you’d skipped prototyping and straight to the build phase, such change would be long-winded and slow to implement.

Responsiveness keeps people happy, and happy customers are repeat customers!

About John Clark

My name is John Clark and I previously ran a software house called Reynard Thomson, from which this blog originally grew. In the meantime, we launched a video-based user testing service (Kupima) which didn't really take off, and I have since moved into a new field specialising on software-based research & development consultancy. I'm active on LinkedIn, and would love to connect to anyone who has an interest in software prototyping or R&D:
This entry was posted in Prototyping and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>