prototyping
DESCRIPTION
My presentation for WXG (Web Expo Guildford)TRANSCRIPT
This talk is a prototype.
Thank you to :: Keith Turner, Nathan Verrill, Mathias Crawford, Ollie Kavanagh, Natalie Fletcher
Kat Kavanagh@kassy4
http://thisiscapra.com
Sunday, 27 October 13
Hello!
Sunday, 27 October 13
Hello!
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Defined.A prototype is an early sample, model or release of a product built to test a concept or process or to act as a thing to be replicated or learned from. It is a term used in a variety of contexts,
including semantics, design, electronics, and software programming.
-wikipedia
Sunday, 27 October 13
In cognitive science Cognitively we reason using imagination, past
experiences to define how we view the world. We use prototypes to help us define how we
think about things. But that means that the view the world is inherently distorted by prototypes.
Sunday, 27 October 13
A good design is better than you
think.-Rex Heftman
“Sunday, 27 October 13
Prototypes efficiently answer designers’* most important questions in the least
amount of time.
My definition
Sunday, 27 October 13
A prototype is not...
Sunday, 27 October 13
Sunday, 27 October 13
Product centric.
Sunday, 27 October 13
The Role
Look & Feel
Implementation
Houde & Hill
Sunday, 27 October 13
Vis
ual F
idel
ity
Functional Fidelity
Sketches
Paper wireframes
Paper design comps
Image mapped comps
Rich comp prototype
Production ready ‘prototype’
Interactive wireframes
Rich interactive wireframesProof of
concept prototype
Image mapped sketches
Sunday, 27 October 13
There is no such thing as high or low
fidelity, only appropriate fidelity.
- Bill Buxton
“Sunday, 27 October 13
But why?
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Scale
ClayWire
Paper
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
The Role
Look & Feel
Implementation
Houde & Hill Sunday, 27 October 13
Mathias Crawford, Game designerTheorist, game nerd
Nathan Verrill, DirectorBig dreamer, user experience junkie
Kat Kavanagh, Interface designerPixel pusher, product champion and mediator
Mark Borcherding, DeveloperDevil’s advocate, perfectionist
Keith Turner, DeveloperLogical master, method maker
The ‘other devs’
Sunday, 27 October 13
Mathias Crawford, Game designerTheorist, game nerd
Nathan Verrill, DirectorBig dreamer, user experience junkie
Kat Kavanagh, Interface designerPixel pusher, product champion and mediator
Mark Borcherding, DeveloperDevil’s advocate, perfectionist
Keith Turner, DeveloperLogical master, method maker
The ‘other devs’
Sunday, 27 October 13
Mathias Crawford, Game designerTheorist, game nerd
Nathan Verrill, DirectorBig dreamer, user experience junkie
Kat Kavanagh, Interface designerPixel pusher, product champion and mediator
Mark Borcherding, DeveloperDevil’s advocate, perfectionist
Keith Turner, DeveloperLogical master, method maker
The ‘other devs’
Sunday, 27 October 13
Mathias Crawford, Game designerTheorist, game nerd
Nathan Verrill, DirectorBig dreamer, user experience junkie
Kat Kavanagh, Interface designerPixel pusher, product champion and mediator
Mark Borcherding, DeveloperDevil’s advocate, perfectionist
Keith Turner, DeveloperLogical master, method maker
The ‘other devs’
Sunday, 27 October 13
Mathias Crawford, Game designerTheorist, game nerd
Nathan Verrill, DirectorBig dreamer, user experience junkie
Kat Kavanagh, Interface designerPixel pusher, product champion and mediator
Mark Borcherding, DeveloperDevil’s advocate, perfectionist
Keith Turner, DeveloperLogical master, method maker
Rol
e
The ‘other devs’
Sunday, 27 October 13
Mathias Crawford, Game designerTheorist, game nerd
Nathan Verrill, DirectorBig dreamer, user experience junkie
Kat Kavanagh, Interface designerPixel pusher, product champion and mediator
Mark Borcherding, DeveloperDevil’s advocate, perfectionist
Keith Turner, DeveloperLogical master, method maker
Rol
eLo
ok
The ‘other devs’
Sunday, 27 October 13
Mathias Crawford, Game designerTheorist, game nerd
Nathan Verrill, DirectorBig dreamer, user experience junkie
Kat Kavanagh, Interface designerPixel pusher, product champion and mediator
Mark Borcherding, DeveloperDevil’s advocate, perfectionist
Keith Turner, DeveloperLogical master, method maker
Rol
eLo
okIm
plem
enta
tion
The ‘other devs’
Sunday, 27 October 13
Remote team
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
PLAYTEST
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Why different typesof prototypes?
Sunday, 27 October 13
By prototyping isolated interactions at a high functional fidelity and
testing them with users, I can get really good data about whether that interaction works before I base an
application around it….
-Fred Beecher
“Sunday, 27 October 13
The Role
Look & Feel
Implementation
Integrated
Houde & Hill Sunday, 27 October 13
Remote prototyping• It is HARD.
• Try out new tools
• Maintain excellent communication
• Have project owners
• Assign roles, and swap them when appropriate
Sunday, 27 October 13
We’re convinced already!
Sunday, 27 October 13
Iteration is actually expensive
• Can’t necessarily reuse code
• End up with a messy disjointed product
• If over 50% of your code is for your interface, then...
Sunday, 27 October 13
dev + design + business
Sunday, 27 October 13
Do you have a methodology?
Sunday, 27 October 13
Scientific method
Sunday, 27 October 13
Desired Outcome Model1. Who wants it?
2. What’s wanted?
3. What does it get them?
4. How will they know when they have it?
5. What stops them from having it?
6. What problems could having it cause?
7. What must they do to achieve their desired outcome?
Sunday, 27 October 13
BackplanStart with the desired outcome.
Milestone 3Milestone 2Milestone 1
Sunday, 27 October 13
Wing it! But...
Sunday, 27 October 13
Wing it! But...
• Timebox tasks
Sunday, 27 October 13
Wing it! But...
• Timebox tasks
• Discuss take-away points
Sunday, 27 October 13
Wing it! But...
• Timebox tasks
• Discuss take-away points
• Have a curator
Sunday, 27 October 13
Wing it! But...
• Timebox tasks
• Discuss take-away points
• Have a curator
• Icebox most of the ideas
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
ON ICE.
Sunday, 27 October 13
Requests & Agreements
Making Requests
Clarify the wantWho wants it?What is wanted?What does it get them?How will they know when they have it?
Make the requestWho is asking?Who is being asked?What do I want you to do?How will I know it is done?By when?
Responding to Requests
Consider the requestAre you clear what is being asked?Do you know the criteria for satisfaction?(What is the minimum required (demanded), what is the ideal (desired)?What context got us here?When does it need to be done by?
Make the requestPromise, Decline, CounterofferCommit to commit (When I get more info, I’ll get back to you by x date), Renegotiate
Sunday, 27 October 13
Are you AGILE?
Sunday, 27 October 13
Sunday, 27 October 13
Tools should make everything easy.
Sunday, 27 October 13
When does prototyping fail?
Sunday, 27 October 13
Sunday, 27 October 13
Fail.
Sunday, 27 October 13
Fail.• Trying to do too much
Sunday, 27 October 13
Fail.• Trying to do too much
• Fidelity is wrong for what you’re testing
Sunday, 27 October 13
Fail.• Trying to do too much
• Fidelity is wrong for what you’re testing
• Too many assumptions
Sunday, 27 October 13
Fail.• Trying to do too much
• Fidelity is wrong for what you’re testing
• Too many assumptions
• Prototype things too late
Sunday, 27 October 13
Fail.• Trying to do too much
• Fidelity is wrong for what you’re testing
• Too many assumptions
• Prototype things too late
• Inability to let go of preconceived ideas
Sunday, 27 October 13
Fail.• Trying to do too much
• Fidelity is wrong for what you’re testing
• Too many assumptions
• Prototype things too late
• Inability to let go of preconceived ideas
• Test only experts or new users
Sunday, 27 October 13
Doing, not seeing!It’s your turn...
Sunday, 27 October 13
Sunday, 27 October 13
The Role
Look & Feel
Implementation
Houde & Hill Sunday, 27 October 13
Keep in mind• Test one thing: the issue you think is the
most complex
• Keep fidelity low
• Let go of preconceived ideas
• Test ‘in-context’
• Test with both expert and new users in mind
Sunday, 27 October 13
Okay... Go!
Sunday, 27 October 13
Presenting...
Sunday, 27 October 13
Dan + Anna + Me
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
I think we all agree prototyping should
be part of your plan.
Sunday, 27 October 13
But, how to sell prototyping time to your boss as part of your work process?
Sunday, 27 October 13
Boss cheat sheet
Sunday, 27 October 13
1. Best way to get complete logical interaction loops that make sense (especially for complex interactions)
Boss cheat sheet
Sunday, 27 October 13
1. Best way to get complete logical interaction loops that make sense (especially for complex interactions)
2. Whittles out shit ideas
Boss cheat sheet
Sunday, 27 October 13
1. Best way to get complete logical interaction loops that make sense (especially for complex interactions)
2. Whittles out shit ideas
3. Gets everyone on board and understanding what will be happening early on (I see! with testing to confirm it!)
Boss cheat sheet
Sunday, 27 October 13
1. Best way to get complete logical interaction loops that make sense (especially for complex interactions)
2. Whittles out shit ideas
3. Gets everyone on board and understanding what will be happening early on (I see! with testing to confirm it!)
4. Can iterate through 10 concepts in a week
Boss cheat sheet
Sunday, 27 October 13
1. Best way to get complete logical interaction loops that make sense (especially for complex interactions)
2. Whittles out shit ideas
3. Gets everyone on board and understanding what will be happening early on (I see! with testing to confirm it!)
4. Can iterate through 10 concepts in a week
5. Can address risks and problems early on before they become dangerous for the business
Boss cheat sheet
Sunday, 27 October 13
Sunday, 27 October 13
Sunday, 27 October 13
Go forth and Prototype!
Iteration is expensive....
Sunday, 27 October 13
@kassy4http://thisiscapra.comThank you.
Sunday, 27 October 13