Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Bringing Projects to Life Through Rapid Prototyping

1,585 views

Published on

Design and build projects are often difficult to kick-off, especially when you're strugglilng to convey your ideas and understand the solutions being suggested. This can lead to delays, confusion and potential rework.

Sound familar?

Rapid prototyping provides a quick and visual solution to identifying, documenting and validating project requirements in an interactive way.

In this session Jamie will take you through examples of rapid prototypes and show you how this approach can bring your projects to life and reduce development time, costs and help to maintain your relationship with your clients.

GET IN TOUCH WITH SIGMA

This presentation is from Camp Digital, a free, one-day event in Manchester exploring some of the most important and emerging themes in the digital industry. To see more presentations and videos from the day visit: http://campdigital.wearesigma.com/2013/.

Camp Digital was brought to you by Sigma. We are a leading specialist in User Experience consulting and design, information management, and web technologies. We provide research, analysis, design, development and support services, with specific expertise in usability, accessibility, content and document management, websites, intranets and online applications.

If you think we can help you call us on 01625 427718 or email hello@wearesigma.com.

Published in: Technology
  • Be the first to comment

Bringing Projects to Life Through Rapid Prototyping

  1. 1. BRINGING PROJECTS TO LIFEThrough Rapid Prototyping Jamie Clouting Technical Consultant Sigma UK
  2. 2. Agenda What is a prototype? Why do we need prototypes What options are available for your project? Examples of a real project The benefits A example timeline example
  3. 3. What is prototyping“ A prototype is an early sample or model built to test a concept or process or to act as a thing to be replicated or learned from ~ Wikipedia“ Interaction Design (IxD) defines the structure and behaviour of interactive systems ~ IxDA
  4. 4. WHY DOWE NEEDPROTOTYPES?
  5. 5. WHY DOWE NEEDPROTOTYPES? This may be familiar…
  6. 6. What the client wants…
  7. 7. What the developers think the clientneeds…
  8. 8. Building happens behind closed doors
  9. 9. Building happens behind closed doorsExcitement builds…
  10. 10. What gets delivered..!
  11. 11. HOW CANPROTOTYPINGHELP?
  12. 12. How can prototypes help Identify Validate Document
  13. 13. WHERE DO WE START?
  14. 14. Where do we start? Horizontal (pages & navigation)Vertical (functionality)
  15. 15. Low-fidelity Horizontal (pages & navigation) LowVertical (functionality)
  16. 16. Sketches
  17. 17. Rough concepts
  18. 18. Gives you a layout guide
  19. 19. Low-fidelity Horizontal (pages & navigation) Low + Layout + Expectation settingVertical (functionality)
  20. 20. Medium-fidelity Horizontal (pages & navigation) Low + Layout + Expectation setting MediumVertical (functionality)
  21. 21. Launch Prototype
  22. 22. Medium-fidelity Horizontal (pages & navigation) Low + Layout + Expectation setting Medium + Flow design + Simple interactionsVertical (functionality) + Internal buy-in
  23. 23. High-fidelity Horizontal (pages & navigation) Low + Layout + Expectation setting Medium + Flow design + Simple interactionsVertical (functionality) + Internal buy-in High
  24. 24. Launch Prototype
  25. 25. High-fidelity Horizontal (pages & navigation) Low + Layout + Expectation setting Medium + Flow design + Simple interactionsVertical (functionality) + Internal buy-in + Complex interaction + Animation + Look & feel High + Functionality
  26. 26. Audience Horizontal (pages & navigation) Internal Low + Layout project + Expectation setting team Medium + Flow design + Simple interactionsVertical (functionality) + Internal buy-in + Complex interaction + Animation + Look & feel High + Functionality
  27. 27. Audience Horizontal (pages & navigation) Internal Low + Layout project + Expectation setting team Other Medium + Flow design members of + Simple interactionsVertical (functionality) the business + Internal buy-in + Complex interaction + Animation + Look & feel High + Functionality
  28. 28. Audience Horizontal (pages & navigation) Internal Low + Layout project + Expectation setting team Other Medium + Flow design members of + Simple interactionsVertical (functionality) the business + Internal buy-in External stakeholders + Complex and users interaction + Animation + Look & feel High + Functionality
  29. 29. Story telling Horizontal (pages & navigation) Internal Low + Layout project + Expectation setting team Other Medium + Flow design members of + Simple interactionsVertical (functionality) the business + Internal buy-in External stakeholders + Complex and users interaction + Animation + Look & feel High + Functionality
  30. 30. Quality expectation Horizontal (pages & navigation) Internal Low Forgiving + Layout project + Expectation setting team Other Medium + Flow design members of + Simple interactionsVertical (functionality) the business + Internal buy-in External stakeholders + Complex and users interaction + Animation + Look & feel High + Functionality
  31. 31. Quality expectation Horizontal (pages & navigation) Internal Low Forgiving + Layout project + Expectation setting team Other Medium + Flow design members of + Simple interactionsVertical (functionality) the business + Internal buy-in External Expect stakeholders polish + Complex and users interaction + Animation + Look & feel High + Functionality
  32. 32. Project timelineWk 1- Client brief- Sketches- Wireframes Day 0 Day 90
  33. 33. Project timelineWk 1- Client brief- Sketches- Wireframes Wk 2 - 3 - Design workshop - Creative - Look and feel Day 0 Day 90
  34. 34. Project timelineWk 1 Wk 4- Client brief - 2 day- Sketches workshop with- Wireframes Stakeholders, Devs & Users Wk 2 - 3 - Design workshop - Creative - Look and feel Day 0 Day 90
  35. 35. Project timelineWk 1 Wk 4- Client brief - 2 day- Sketches workshop with- Wireframes Stakeholders, Devs & Users Wk 2 - 3 Wk 5 - 13 - Design workshop - Working up flows - Creative and user tasks - Look and feel - Polishing design Day 0 Day 90
  36. 36. Project timelineWk 1 Wk 4 Wk 11 - 12- Client brief - 2 day User testing- Sketches workshop with with 10 users- Wireframes Stakeholders, and analysis Devs & Users Wk 2 - 3 Wk 5 - 10 - Design workshop - Working up flows - Creative and user tasks - Look and feel - Polishing design Day 0 Day 90
  37. 37. Conclusion Prototyping can have real benefits to your project, no matter what the budget Prototyping can lead to increased buy-in from internal stakeholders and users Prototyping can save you money by reducing the amount of time it takes you to get consensus on your project Prototyping can highlights issues that are easier to fix before any code is written
  38. 38. THANKS, QUESTIONS?jamie.clouting@sigma.sewearesigma.com@wearesigma / #CampDigital
  39. 39. UX Training at SigmaSigma is launching a range of new User Experience trainingservices over the next few months, including courses in: Rapid prototyping and solution design with Axure Writing for the web Intro to UX – tools and techniques Tree testing with TreejackIf you’re interested in finding out more about these courses pleasevisit the Sigma stand over by the registration desk.

×