Rapid Prototyping as part of user-centred design
A Rapid Prototype is a functional Website model with working navigation, images, graphics, text and even Meta information for Search Engines like Google. Prototypes offer many advantages over Wireframes, which are static non-functional outlines of Web pages.
Why Develop a Rapid Prototype?
Here are 10 good reasons why Rapid Prototypes provide a logical route for planning, scoping, accurately costing and building a Website:
- A prototype can be built in a fraction of the time it takes to build Web pages from a static Wireframe
- Prototypes allow you to test different page layouts and quickly agree on the most effective version
- Prototyping throws up details that are often “assumed” in Wireframing, and allows teams to remove these potentially costly assumptions in favour of agreed functional requirements
- Prototypes have working navigation so UX (User Experience) teams can test versions and agree on the most customer friendly navigation routes and interactive elements
- Prototypes confirm functional requirements in great detail and make it easy to favour or dismiss CMS platforms based on technical merit. Great if you’ve got a designer who claims he can build your multi-template, interactive booking Website with integrated checkout and sophisticated client area in WordPress!
- Some Prototyping programs print a detailed technical specification and this allows you to secure design & build quotes on an accurate like-for-like basis with zero assumption or potentially fatal interpretation
- Changes to designs are quick to establish in a Rapid Prototype so you can remove potentially costly reworks down the line
- Unlike Wireframes, which can scare people off because you have to think quite hard about how the concept will work in a real site, Rapid Prototypes are customer friendly, even for the most technophobic of clients
- Most Prototype programs are Web based so multiple team members can access the content, add notes or directions, then monitor the results
- Prototyping at the front end of a project will guarantee to save you time and money down the line
Prototyping typically goes through 4 stages, and this is duplicated when creating Responsive Design versions of the main Website that are intended for Smart Phones:
Some experienced UX Designers will plan the main pages of a Website as a hand drawn sketch first.
These people are experienced enough to get layouts on paper, backed up by supporting materials such as audience profiling, persona creation, focus groups, hypercard stacking and experience maps.
The Low-Fi (Low-Fidelity) version of the Prototype has the navigation set up and templates for the main pages. These pages are usually made up of grey blocks and subtle notes to indicate what is going where.
The Low-Fi version will be created in full scale, with working navigation, and will cater for the requirements of Responsive Design if specified.
Straight away, client and agency team members can begin collaborating.
The Low-Fi version is duplicated in a flash and we now start to add graphical elements using stencils and widgets.
Complex features such as pop-up interactions can be added so clients can start to get a real feel for how design and functional elements will play out.
The Hi-Fi (High Fidelity) version is as real as the proposed Website.
Ideas are shared and discussed, feedback can be pinpointed and incorporated, buy-in can be approved from stakeholders and the best news of all is that everything is available from a single login protected repository, so there’s no trying to keep track of Email threads and attachments across several different locations.
Below: Comparison between Med-Fi and Hi-Fi version of a smart phone plan
So Why Bother With Rapid Prototyping? Isn’t This Just Adding To the Cost?
Unless you are planning a very simple Website with basic functionality, Rapid Prototyping can save you a fortune and even protect your project from potential failure in a number of areas.
- Prototyping represents about 15%-20% of project cost but here are 5 top ways in which Rapid Prototyping will save you time, stress and money in the end:
- A specification derived from a Rapid Prototype will help you rule out a CMS platform that might not be powerful enough or scalable enough to manage your life cycle requirements
- Use the specification as part of your RFP (Request for Proposal) and benchmark vendor quotes accurately – none of this one price of £5k, one of £20k and one of £50k, all for supposedly the same service. Help your vendors quote on known factors with assumption taken out of the equation
- Helps you agree on changes before the system goes to production, so you can cut out Feature Creep and Change Requests. These beauties drive more projects into financial dispute and relationship breakdown than any other event
- Speeds up the planning and development process so you actually save money overall
- Removes the headache and stress that is commonplace in projects that don’t use Rapid Prototyping.
About the author:
Philip Allen is the Studio Director at D. and a UX and Drupal Design Consultant. He works hands-on with every project that comes through the agency and champions the case for discovering the truth behind the way users need to interact with Websites.
If you’d like to talk to Phil, get in touch via the Contact Us page or give him a ring on UK: 0844 544 9553 or INTL: +44 (1) 202 546762.
Follow us on:
- RT @drewallenmusic: Seen @ArticMonkeysBR & @bobdylan play @BournemouthIC now I am supporting @JamesBlunt - epic!!! http://t.co/uryO0o6UUz — 7 months 1 week ago
- RT @dorsetpolice: It's almost time! #boscombepolicebox http://t.co/K5cUrDeKLd — 1 year 2 weeks ago
- RT @WestBeachBmouth: Retweet this & be in to win a table for 2 at our legendary lobster and burger night next Thursday from 6pm... http://t… — 1 year 1 month ago
- Very pleased with the new site for #CaraDillon and best of luck @CaraDillonSings with the new album — 1 year 1 month ago
- @WildGreenBean Both! — 1 year 3 months ago