Explanation of User Experience principles related to operating in a lean product development environment.

1. Creating Outcomes
Move from creating deliverables based on
requirements to outcomes based on
change.

4. Collaboration & Teaming

5. Collaboration & Teaming
Limited Documentation

6. Collaboration & Teaming
Communicate across
teams & modules
Shared resources
& tools
Daily or weekly
coordination
UX is still a UX team

7. Collaboration & Teaming
Principles

9. How do you design a house
one room at a time?

10. Everyone has to keep
the bigger picture in mind

11. The challenge is in keeping
a cohesive user experience
across teams and elements

12. UI Frameworks can help
Established
design patterns
Styled elements Consistent
behaviors

13. Guidelines are imperative for
cohesion, but also empower
teams to quickly iterate

14. Style guide should:
Be Accessible Be Continually
Improved
Be Actionable

15. Prototyping is a huge
piece of the puzzle

16. Choose the right tool and
the right fidelity

18. Individuals & interactions
over process & tools
Engage the entire team

19. Individuals & interactions
over process & tools
Replace constraints
with conversation

20. Build working software sooner
then assess for market fit & viability
Working software over
comprehensive documentation

21. Consensus built into the process
brings speed & agility
Collaboration with team &
users is mandatory

22. The user must be included & all team
members are required to validate
learnings through experimentation
Collaboration with team &
users is mandatory

23. The user must be included & all team
members are required to validate
learnings through experimentation
Responding to change
over following a plan

24. The goal is to figure out what’s
wrong & fix it
Responding to change
over following a plan

25. Build. Measure. Learn.
Responding to change
over following a plan

26. Test the hypothesis
Each design is a proposed
business solution

27. Test the hypothesis
The goal is to validate the
proposed solution efficiently
using customer feedback

28. Test the hypothesis
The smallest thing you can build to
test each hypothesis is your MVP
(Minimal Viable Product)

29. Test the hypothesis
Put the MVP in front of users &
find out what works & what doesn’t

30. BUILD. MEASURE. LEARN