Being involved in over 20 startups (web and mobile) I finally decided to expose my thoughts on Lean UX (LUX) at Slide Share. Happy reading!

1. leanUX
ERIK LÜDECKER - FIRST DEGREE EXPERIENCE OFFICER

2. CUT THE CRAP. YOU NEED TO MAKE MORE
MONEY IN ORDER TO SURVIVE. AND IM HERE
TO TELL YOU HOW. PERIOD.
PLEASE

3. BEFORE WE GO INTO THE CONCEPT AND
REALITY OF LUX. LET US UNDERSTAND WHY
ITS THERE IN THE FIRST PLACE.
THINK

4. MONEY IS WHAT KEEPS YOU GOING. PEOPLE
GIVE YOU THEIR HARD EARNED MONEY AND
TIME FOR A PRODUCT OR SERVICE.
BUSINESS

5. IS IT A NEED. A HABIT OR PURE LOVE. IN
ORDER TO REALLY IMPROVE. WE NEED TO
UNDERSTAND PEOPLE.
REASON

6. THE FIRST STEP YOU NEED TO TAKE.
UNDERSTAND THE NEED FOR LUX AND
REORGANIZE. TOP-DOWN.
UNDERSTAND

7. INNOVATION IS A LIVING CREATURE.
ORGANISMS FLOURISH WHEN THE
SURROUNDING HABITAT IS FAVOURABLE.
ENVIRONMENT

8. BUILD A CROSS-FUNCTIONAL TEAM OF SEVEN.
ITS ABOUT FOCUS. COMMUNICATION. AND
SIMPLY CAMARADERIE.
SETUP

9. THE PURPOSE OF LUX IS NOT OUTPUT. ITS
OUTCOME. IMPLEMENTING BUSINESS VALUE
NOW. NOT TOMORROW.
VALUE

10. THE OUTCOME IS SOLVING A BUSINESS
PROBLEM WITH OUTPUTS FROM A FOCUSED
AND SMALL CROSS-FUNCTIONAL TEAM.
SOLVE

11. AN OUTPUT THAT DOES NOT SOLVE A PROBLEM
IS GARBAGE. NEW DESIGNS AND FEATURES
LACKING OUTCOME LIVE IN THE BIN.
WASTE

12. GOING FROM A TO B MUST NOT BE STALLED.
CREATIVE IDEAS THAT INTERUPT THAT PATH
ARE STORED IN THE BACKGROUND.
ASYNC

13. INVITE COLLEGUES AND USERS EVERY FRIDAY.
GIVE THEM A SANDWICH AND A SODA AND LET
THEM PLAY.
DISCOVERY

14. GET OUT OF THE BUILDING. YOUR USERS ARE
NOT IN THE OFFICE. THE SOONER YOU LEARN
THE FASTER YOU PRODUCE GOOD STUFF.
GOOB

15. COLLECTIVE CROSS COMPREHENSION. YOUR
LUX TEAM NEED TO UNDERSTAND EACH OTHER
AS A SINGLE MULTIFACETED UNIT.
CCC

16. AVOID NINJAS. GURUS AND ROCKSTARS IN
YOUR LUX TEAM. THEY WILL KILL YOUR
BUSINESS WITH THEIR EGO.
EGOISM

17. GET IT OUT OF YOUR HEAD AND COMPUTER
NOW. YOUR LUX TEAM NEED A BIG BOARD IN
THE HEART OF THE COMPANY.
EXPOSE

18. OVER ANALYZING IS BUSINESS POISON. GET
THE IDEA OUT THERE AND STOP DISCUSSING
ITS PROS AND CONS BEHIND A DESK.
OA

19. LEARN FIRST. SCALE SECOND. LEARN FROM
NEW FEATURES AND DESIGNS BEFORE YOU
SCALE THEM TO YOUR ENTIRE USER BASE.
SCALING

20. FAILING IS GOOD. MOST OF THE OUTPUTS
FROM YOUR LUX TEAM WILL FAIL. THE FEAR OF
FAILING KILLS CREATIVITY.
FIG

21. DOCUMENTS AND PRESENTATIONS DONT
SOLVE USER PROBLEMS. GOOD PRODUCTS DO.
SO SKETCH. PROTOTYPE AND TEST.
FOCUS

22. CORE OF LUX

23. MVP
FEEDBACK
ASSUMPTIONS
EXPERIMENT

24. DECLARING ASSUMPTIONS REQUIRES PRIOR FACT. REPORTS
AND HISTORICAL INFO. ANALYSIS OF PROBLEM SOLVING
RESULT. COMPETITOR ANALYSIS. ASSUMPTIONS ARE PROBLEM
RELATED. PROBLEMS ARE RELATED TO OUTCOMES NOT
OUTPUTS. PROBLEMS CAN BE OF FACTUAL OR HYPOTHETICAL
NATURE. YOUR SERVICE Z WAS DESIGNED TO MEET CERTAIN
GOALS X WHEN X IS NOT MET PROBLEM Y RISES. HOW CAN
YOU IMPROVE Z TO REACH X. THAT IMPLIES AN ASSUMPTION
RELATED TO Z.

25. PRODUCT
Z
GOALS
X
Y Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

26. MAP YOUR ASSUMPTIONS ACCORDING TO RISK AND
KNOWLEDGE. CONVERT YOUR ASSUMPTIONS INTO
HYPOTHESIS. WE BELIEVE X IS TRUE. WE WILL KNOW X IS TRUE
OR FALSE WHEN WE GET QUALITY, QUANTITY OR KPI METRICS.
BRAKE DOWN YOUR HYPOTHESIS INTO SUBPARTS WHEN
NEEDED FOR A MORE FINE TUNED RESULT.

27. HIGH RISK
LOW RISK
KNOWN UNKNOWN

28. ASSUME PERSONAS ON THE FLY WITH THE WHOLE TEAM
CONTRIBUTING AND MAKE IT SIMPLE. ALSO KNOWN AS PROTO
PERSONAS OR PP. CREATE MANY OF THEM IN AN HOUR.
ANALYZE YOUR PP WITH THE REAL WORLD.

29. BEHAVIOUR
NEEDS
SKETCH
SOLUTIONS

30. WHAT FEATURE MAKES THE PP CLICK AND THUS GIVE RISE TO
THE DESIRED OUTCOME. ITS LIKE SAYING X + Y = OUTCOME.
CREATE MANY OF THEM IN AN HOUR ON POST IT NOTES. PUT
THEM ON THE BOARD. ARRANGE INTO THEMES. DISCUSS.

31. FEATURE PP OUTCOME

32. COLLABORATIVE DESIGN. BRING EVERYONE TO THE TABLE.
LISTEN EARLY. DESIGNERS ARE EQUAL TO NON DESIGNERS AT
THIS STAGE. DITCH HERO DESIGN. THIS IS OPEN SOURCE
DESIGNING. BUILD A DESIGN STUDIO WITH STYLE GUIDES.
GRAPHICAL PROFILE AND ITEM LIBRARY. THINK LOW FIDELITY.
AND LETS GET DOWN TO BUSINESS.

33. MVP. THE MINIMAL VIABLE PRODUCT IS NOT A CRAPPY
VERSION. ITS A GOOD LOOKING VERSION WITH NO COMPLEXITY
INVOLVED. TEST YOUR ASSUMPTIONS WITH THE MVP. MAKE IT
A CALL TO ACTION. A COMMENT FUNCTION CAN BE TESTED BY
ADDING A COMMENT BUTTON. THATS IT. NO COMPLEX LOGIC.
THE MVP IS THERE TO GIVE YOU FEEDBACK TO UNDERSTAND
VALUE AND POSSIBLE OUTCOME.

34. PROTOYPING. YOUR MVP SHOULD BE A NON PROTOTYPE MVP
AT FIRST GLANCE. USE SOLIDIFY. INVISION OR ANY OTHER
SUITABLE ONLINE TOOL. FOR PROTOTYPING. IF THE RESPONSE
IF GOOD. TAKE THE MVP TO THE NEXT LEVEL AND INTEGRATE
THE DUMMY. TEST AND LEARN. ALWAYS KEEP YOUR EYES AT
THE OUTCOME.

35. AB TESTING. ARRANGE SIMILAR FEATURES AND DESIGNS.
DIVIDE USER GROUPS. INVESTIGATE IF A IS BETTER OR WORSE
THAN B. THEN PROCEED. THIS IS CRUICAL. SOMETIMES OR
MANY TIMES A SMALL CHANGE CAN MAKE A HUGE
DIFFERENCE. PRESENTING ONLY A TO TEST YOUR ASSUMPTION
IS NOT GOOD ENOUGH.

36. RESEARCH AND FEEDBACK. THIS IS CONTINOUS. YOU DONT
PLAN TO DO IT. YOU SHOULD DO IT ALL THE TIME. THERE IS NO
WAITING IN LUX. WHILE THE FEEDBACK OF X IS COMING YOU
ARE WORKING ON PUSHING THE MVP OF Y. AND SO ON.
REMEMBER THAT THIS IS COLLABORATIVE DISCOVERY.

37. GET THE WHOLE ORG INVOLVED. EVERYONE AT YOUR COMPANY
IS GETTING PAYED BY THAT COMPANY. THE RECEPTIONISTS
SALARY DEPENDS ON YOUR OUTCOMES. SO CALL EVERYONE IN
ALL THE TIME AND MAKE THEM PLAY. CHAT AND EXPRESS
THEIR THOUGHTS AND FEELINGS. R&D IS NOT THE BRAIN IN
YOUR COMPANY. NOR ARE THE EXECUTIVE LEAGUE AT THE TOP
FLOOR. THE WHOLE COMPANY IS A BRAIN.

38. SCRUM. THIS WHOLE THING IS SCRUM BASED. WITH SLIGHT
MODIFICATIONS IN ORDER TO IMPROVE DESIGN-NON-DESIGN
INTEGRATION AND COLLABORATION. SHORT MEETINGS OFTEN.
TIMEFRAMING. SPRINTS. ITERATION PLANNING MEETINGS. USE
KANBAN. IT HELPS. THIS IS A TEAM SPORT. EVERY PLAYER IS
CRUCIAL.

39. UNDERSTAND THE VALUE OF LUX. REORGANIZE
TOP DOWN. SOLIDIFY THE LUX TEAM. GET
EVERYONE INVOLVED.
THATS IT.