1. How to prototype to
understand your clients
antti.tarvainen@leonidasoy.fi harri.lammi@leonidasoy.fi
@tarvaina @harri_lammi
2. Talk in one slide
Understand the context
1. of your system.
Build prototypes to validate
2. your understanding of the
context and the design.
Different situations call for
3. different kinds of prototypes.
4. Case: Lausuntopalvelu
Demo
http://youtu.be/jVlYofasZnI
http://lausuntopalvelu.fi
https://github.com/leonidas/lausuntopalvelu-prototyyppi
but look at it on your own risk — it really is throwaway code.
5. Schedule:
Understand the problem
Start shop 1 day
Iterate with paper protos
Design & Design user interface
5 days
Development Develop functionality
Demo 2 hours Deliver to the customer
Team:
Proxy product owner
2 IX/UI designers
2 software developers
6.
7.
8.
9.
10. Startshop Tips
DO have a schedule
DO let the client tell their story
DON’T try to come up with a solution before
you understand the problem
DON’T delegate design responsibility to the
client
11. From context to
the solution
Context
Personas
We need to
understand the Scenarios
context before
Paper prototypes
we can
implement the Wireframes
solution.
Layouts
Solution
12. From context to
the solution
Context
Personas
We use
Scenarios
different tools
to move from Paper prototypes
context towards
Wireframes
solutions.
Layouts
Solution
13. From context to
the solution
Context
We verify our Personas
understanding
Scenarios
at each level
with the client Paper prototypes
and by
Wireframes
comparing to
the other levels. Layouts
Solution
16. Development Tips
DO have small tasks (< 2h)
DO commit and deploy all the time
DO have product owner test the prototype all
the time
DON’T write anything extra
DON’T spend time in polishing
17. Internals in this case
jQuery, Transparency, Spine, Undescore, ...
CoffeeScript
Node.js
MongoDB
Github
Linode
YouTube
27. when you are
Example.
just a few bored and need
minutes of time entertainment
you can stop
whenever
you want
always
with you
etc. etc.
you don’t
want to learn
anything difficult
28. when you are
Example.
just a few bored and need
minutes of time entertainment
you can stop
whenever
you want
always
with you
etc. etc.
you don’t
want to learn
anything difficult
29. when you are
Example.
just a few bored and need
minutes of time entertainment
you can stop
whenever
you want
always
with you
etc. etc.
you want to learn
something useful
30. when you are
Example.
bored and need
social entertainment
situation
you can stop
whenever
you want
always
with you
etc. etc.
you want to learn
something useful
42. But a few things are unclear
1. How do you find the context?
2. How does the context result in a backlog?
43. user needs
User needs are the most
fundamental part of the context.
44. architecture
user interface
user needs
? requirements
data model
feature list
What is the most logical next step?
Why?
45. architecture
user interface
user needs requirements
data model
feature list
User interface is, because it
can be tested against user needs.
46. architecture
user interface
user needs requirements
data model
feature list
You cannot tell from e.g. data model
alone if it will match the user needs.
60. We use mostly paper prototypes
and functional prototypes.
61. The length of a paper prototype
feedback loop is minutes.
62. The length of a functional prototype
feedback loop is days.
63. Paper prototype is good for
finding out and validating
the use cases and the design.
64. A functional prototype is good for
communicating the vision of the product,
selling it and validating the market.
65. Talk in one slide
Understand the context
1. of your system.
Build prototypes to validate
2. your understanding of the
context and the design.
Different situations call for
3. different kinds of prototypes.