Part of the inspiration for lean is to eliminate as much unnecessary work as possible to arrive at a valuable end-product. Methodologies such as Lean UX aim to design the best customer experience in the shortest cycle possible, but how do these approaches apply when it comes to executing and shipping a functional Minimum Viable Product? In this talk, designer Jono Mallanyk and software engineer Ben Burton delve into the hands-on approach they've taken to cross-functional pairing to design and build products quickly and effectively. They'll detail how and when to involve execution in the lean process and tools and techniques they've found useful for developers and designers working together. At Neo Innovation Labs, Jono and Ben have spent the past 12 months pairing as designer and developer, learning from each other, and honing their cross-functional process to arrive at a truly lean approach to software creation.

1. #twoburgerteam
Photo credit: http://www.flickr.com/photos/snekse/2500327895/

2. #twoburgerteam
Jono
@jonomallanyk
Ben
@bjburton

3. VALUES
PROCESS & CASE STUDY
+

4. "
If a tm c’t be f wh
two pi, ’s o big.
Jeff Bezos

5. "
If yr MVP execu
tm c’t be f wh two
burgs, ’s o big.
Jono Mallanyk

6. MVP?

7. An MVP   smat g
y c do  make 
r  dictly msu
some fm  val 
ng.

9. AN EVOLUTION OF PAIRING

10. AN EVOLUTION OF PAIRING

11. AN EVOLUTION OF PAIRING

12. GENERALISTS

13. PROXIMITY

14. WORK IN PARALLEL

15. Ga a sd
ustg, n get 
al  sn  psib.

16. TWO BURGER VALUES

17. BE CURIOUS
EVERYONE SHOULD

18. GET OUT OF THE BUILDING
EVERYONE SHOULD

19. SKETCH
EVERYONE SHOULD

20. UNDERSTAND THE
BUSINESS GOALS
EVERYONE SHOULD

21. OPTIMIZE FOR LEARNING
EVERYONE SHOULD

22. DESIGNERS SHOULD
DEMYSTIFY THE PROCESS
SHOW DESIGNS EARLY AND OFTEN

23. WRITE HTML & CSS
(AT THE VERY LEAST)
DESIGNERS SHOULD

24. DEPLOY TO PRODUCTION
DESIGNERS SHOULD

25. NOT OVER-DESIGN
DESIGNERS SHOULD

26. CARE ABOUT DESIGN:
ASK WHY?
DEVELOPERS SHOULD

27. NOT OVER-ENGINEER
DEVELOPERS SHOULD

28. THROW OUT CODE
DEVELOPERS SHOULD

29. INVOLVE YOUR TEAM EARLY
PRODUCT MANAGERS SHOULD

30. FIND A WAY TO BE HANDS ON
PRODUCT MANAGERS SHOULD

31. BUY BURGERS
PRODUCT MANAGERS SHOULD

32. OUR MVP PROCESS

34. Probm: C we improve
ships by lpg
cps be crde
ir sd
spsibili?

35. INCEPTIONPhoto credit: http://muted.com/inception-totem/

36. FULL TEAM INCEPTION

37. Problem, vision & MVP idea

38. ASSUMPTIONS

39. DESIGN STUDIO

40. A “Wizard of Oz” MVP

45. BUILDING TOGETHER

51. CUSTOMER DEVELOPMENT

52. BURGERS

53. TWO BURGERS OF YOUR OWN
WHAT’S NEXT?

54. #twoburgerteam
Jono
@jonomallanyk
Ben
@bjburton