Presentation from a talk I gave at UX Brighton. There were a bunch of other folks talking on the same night about other aspects of meshing / mashing UX into Agile projects, so this one focusses a bit more on how you can do Lean UX (a little).

1. lean ux
what that means for us…
for UX Brighton, 8 March 2011

2. hello…
i used to work in an
“advertising” agency
§ off-site
§ creative first or
§ ux first
now, I help build
software for finance
§ on-site
§ delivery driven
2

3. just enough / good enough
§ good enough
§ generically across the project
§ just enough
§ personas (and their use in stories)
§ sketching and documentation
§ design
§ the end product
3

4. good enough
define your quality
very satisfied
standards
§ what does done look
performance
like? excitement
§ does
the kano model
have some answers? fail win
hygiene
very dissatisfied
4

5. good enough
development quality
is easy(ish) to define
§ what
are the coding
standards
§ what
is acceptable
(bug wise)
5

6. good enough
creative quality?
§ whatcreative standard
are we striving to
achieve (chevrolet,
toyota, porsche, audi
ferrari…)
6

7. good enough
interaction quality?
§ what
level of
“usability” is good
enough
7

8. just enough / good enough
§ good enough
§ generically across the project
§ just enough
§ personas (and their use in stories)
§ sketching and documentation
§ design
§ the end product
8

9. Personas
what is appropriate
§ generic library
§ “sketch”
§ primary / secondary
FX ONLY
:: LAB49 IN
TERNAL DI
STRIBUTIO
N ONLY
City Perso
nas EDITION 1
9

10. personas
then use them!
§ as[persona…], I want
to [goal…], so that
[reason] FX ONLY
:: LAB49 IN
TERNAL DI
STRIBUTIO
N ONLY
§ mostuse:
“as a user I…”
City Perso
nas
§ use
your personas EDITION 1
“as bob jones, I…”
“as bob, mary or fred,
I…”
10

11. just enough / good enough
§ good enough
§ generically across the project
§ just enough
§ personas (and their use in stories)
§ sketching and documentation
§ design
§ the end product
11

12. interface states and event-based user actions. Through a few simple and standardized rules, what the user
sees (drawn in greys and blacks) and does (drawn in red) are unified into a coherent sketching system. This
unification of both interface and use, intends to enable designers to tell more powerful stories of interaction.
sketching and documentation
Events
Events are initiated when users perform Unspecified Event. A simple arrow that
Event Binding
To Element. A rounded
various actions on an interface. Think of represents a CLICK action by default. starting point denotes
events as causes and screens as effects. For an event bound to a par-
does anyone like the purpose of this notation, some relevant
events could include: Specific Event. To represent a user
action with an event, note it above the
ticular drawn element.
CLICK FOCUS arrow. To Anywhere. An event
producing documents DBLCLICK
RCLICK
BLUR
KEY: X Combined Events. Sometimes users
is attached to the full
window.
MOUSEOVER KEYUP: X perform more complex actions such as
that don’t get read? MOUSEOUT
MOUSEMOVE
KEYDOWN: X
LOAD
holding a key and clicking.
To Area. An event is
MOUSEUP UNLOAD Real World Actions. User actions can also bound to a specific area
§ canyou get away with
MOUSEDOWN SCROLL happen outside of an interface. on the screen.
CHANGE SUBMIT
just sketches…
Transitions Emphasis Techniques Page Organization
Unspecified Transition. A default Emphasis. Indicating Concept Title. Each page
transition is instant without delay. an important element can contain a title in the
with a 10% grey. top left. For multi-page
Delay. The time it takes before a concepts, use roman
transition starts. numerals as a suffix.
Selected State. Variations. Each concept
Duration. The time it takes for a Showing a selected can have multiple varia-
transition to complete. item with a 30% grey. tions which are referred
to alphabetically.
Effect. Two possible effects
include: FADE, and SLIDE.
Advanced Notations Rapid Tactics
Basic Condition. If something is to Drag&Drop. Quickly Delta Box. Only draw items
be met before the next screen. show a drag and drop which changed, suggesting
interaction. that previous screen ele-
Automatic Sequence. Use a black ments will also appear.
arrow(s) if there is a sequence of
screens that are shown automati- Multi Clicks. Use the Zooming. Draw atlinowski
least 12

13. sketching and documentation
§ we
have, but only
under in certain
conditions
§ whensketches don’t
work we spike
prototypes -
sometimes within the
app!
§ requirements
are
“acceptance tests”
13

14. just enough / good enough
§ good enough
§ generically across the project
§ just enough
§ personas (and their use in stories)
§ sketching and documentation
§ design
§ the end product
14

15. design
a beautiful photoshop
file…
15

16. design
but, the application…
16

17. finally…
§ if
phase 2 happens, how much of your detailed
ux work will actually get used, or (realistically)
will it all be changed again based on new
things you’ve learnt - if so - why do it?
§ thank you
mark@found.me.uk
@uxplant
17