Neil Turner's 2012 Guide to Scenario Mapping
•Download as PPTX, PDF•
26 likes•11,272 views
A quick guide to scenario mapping. Covers what it is; how to carry it out and why to use it.
Recommended
Recommended
More Related Content
More from Neil Turner
More from Neil Turner (20)
Recently uploaded
Recently uploaded (20)
Neil Turner's 2012 Guide to Scenario Mapping
- 1. Neil Turner, April 2012
- 2. What will I be covering?
- 3. What’s a scenario anyway?
- 4. Starfire – a vision of future computing
- 5. So what’s a scenario map?
- 6. A bit of background…
- 7. Not just about personas then!
- 8. How does one go about scenario mapping?
- 9. Find a good size space
- 10. Get loads of post-it notes
- 11. Get the project team together
- 12. Take a key user goal / task
- 13. Start mapping…
- 14. What to map…
- 15. Why use scenario mapping?
- 16. A great research tool
- 17. A great early design tool
- 18. Just don’t over do it…
Editor's Notes
- - Stories about people.- Fictional but grounded in reality.- Usually task / goal orientated i.e. doing something.- Usually outline the ‘to be’ but could equally outline how things currently happen
- - Famous ‘vision of the future video’ Created by Sun MicrosystemsIn 1992 (now part of Oracle).- Attempted to predict and guide the future of computing – set in 2004!.- Drew together the talents of more than 100 engineers, designers, futurists, and filmakers
- - Maps out steps a user (e.g. persona) would take to complete a task or goal in the context of a scenario.- Might map out end to end user journey, or part of the user journey.- Captures steps together with comments, questions and ideas
- - Nothing new.People have been breaking down complex tasks for hundreds of years.- From Fredrick Taylor’s time and motion studies at the turn of the 19th century. - To more modern Ergonomics derived task analysis. - Scenario mapping just a different spin
- - 1st encountered scenario mapping at Nielsen Norman seminar by Tamara Adlin and John Pruitt. - Referred to as both scenario and design mapping in the book (scenario for ‘as is’, design for ‘to be’)
- - Need a decent amount of wall or table space. - Good idea to stick up some brown paper so that you can easily take down the scenarios afterwards.- Can also take a photo afterwards
- - Ideally want 4 different colours. - Super sticky post-its can be useful (if you can find them) as they are more likely to stay stuck
- - Ideally want designers, developers and domain experts. - Can be done individually but works best with a small group (e.g. 2 – 5). - Too big a group makes agreeing a scenario more difficult.- Make sure that people are prepared for the session e.g. know the personas and the scenarios that will be worked through
- - Focus on primary scenarios – what are the key goals and tasks?.- What absolutely has to work well for the product to succeed? E.g. Finding & booking a holiday on the Thomson website. - Focus on sunny day scenarios first – i.e. when things go right.- Danger is that otherwise easy to get tied up in knots
- Try to focus on the ‘what’ not the ‘how’ and keep it reasonably high level.For each step note down- What the user does - remember to focus on what happens, not necessarily how it happen- Any comments or information that you feel is important at this step- Any questions or assumptions that arise are this step that you'll want to resolve- Any ideas or good suggestions that people have
- - Don’t worry about capturing too much detail – that’s not what scenario maps are for- Will also want to provide the context for the scenario e.g. What? Who? Where? Why? When? How often?
- - Quick, simple & fun way to build scenarios- Aids collaboration & encourages discussion-Stops you getting lost in the detail- Forces you to consider the context in which a design is likely to be used
- - During the research phase to analyse a current process e.g. a customer enquiry in a shop- Can be a useful way to capture observed tasks and to walk through a task with domain experts- Remember that what people say they do is often very different from what they actually do!
- - Early in the design phase to establish the user interaction- You can start defining, discussing and evaluating the user journey without expending too much design effort- Likely to be iterative in nature – can revisit scenario maps and map out parts of a map in more detail
- - Key is to capture enough to move on with the design – the aim is not to capture everything- Generally looking to map out the key usage scenarios i.e. 80 / 20 rule- Focus on sunny day scenarios – although a good idea to cover problems if they could be quite common- Don’t need to map out every conceivable scenario