Downloaded 25 times
Uploaded byTheFamily
Fighting complexity by Rémi Guyot, VP Product @BlaBlaCar
Rémi Guyot, a VP product, discusses managing complexity in product design and development. He emphasizes the importance of simplicity, prioritization through the two-list method, and the need to accept and address complexity rather than avoiding it. The talk covers strategies like fanatic focus, simplification reviews, and testing to improve usability and reduce unnecessary complications.
More Related Content
Similar to Fighting complexity by Rémi Guyot, VP Product @BlaBlaCar
Fighting complexity by Rémi Guyot, VP Product @BlaBlaCar
- 1. Rémi Guyot -VP Product Fighting Complexity
- 2. A. You workin a startup. B. You are product manager/owner/designer. C. You have anxiety issues and you hope that this talk will reveal the secret of life. WHAT DESCRIBES YOU BEST?
- 3. A. 10.000 km B.20.000 km C. 40.000 km D. I already regret coming tonight WHAT IS THE DISTANCE BETWEEN FRANCE AND NEW ZEALAND?
- 7. If the captaindies or falls in the water: 1. Turn off the engine (yellow button) 2. Pick up the red phone 3. Wait for instructions
- 9. If the captaindies or falls in the water: 1. XXXXXXXXXXXXXX 2. Turn off the engine (yellow button) 3. Pick up the red phone 4. Wait for instructions
- 10. 3 years atSécurité Solaire 7 years at PayPal 3 years at BlaBlaCar
- 11.
- 12.
- 13.
- 15. Your obsession hasvalue. Go deeper. Spread it. Uris Dacosta
- 17.
- 18. If the captaindies or falls in the water: 1. XXXXXXXXXXXXXX 2. Turn off the engine (yellow button) 3. Pick up the red phone 4. Wait for instructions
- 19. If the captaindies or falls in the water: 1. Accept the situation 2. Turn off the engine (yellow button) 3. Pick up the red phone 4. Wait for instructions
- 20.
- 21.
- 22. Things are complex Fromthe start
- 23. KEEP IT SIMPLE STUPID. Hasn’t accepted thesituation Has accepted the situation
- 24.
- 25.
- 26.
- 29. COMPLEXITY ANTIBODIES Roadmap requests FanaticFocus Interface design Simplification Reviews User feedback Absence Testing RISKY SITUATION
- 30.
- 31.
- 32.
- 33. Goal A Goal B GoalC Goal D Goal E Goal F Goal G Goal H Goal I Goal J
- 34. Goal A Goal B GoalC Goal D Goal E Goal F Goal G Goal H Goal I Goal J
- 35. First List Goal A Goal C GoalH Second List Goal B Goal D Goal E Goal F Goal G Goal I Goal J
- 36. Company Priorities Goal A Goal C GoalH ?? Goal B Goal D Goal E Goal F Goal G Goal I Goal J
- 37. Company Priorities Goal A Goal C GoalH Avoid At All Cost Goal B Goal D Goal E Goal F Goal G Goal I Goal J
- 38. Company Priorities Point-to-Point Multipass Pro Avoid At All Cost GoalB Goal D Trust Goal F Goal G Goal I Goal J
- 39.
- 40. Yes, it isimportant. And we have decided not to focus on it for now.
- 41. Level 0 =No priorities Level 1 = Clear priorities Level 2 = Level 1 + Everyone knows priorities by heart Level 3 = Level 2 + No one works on other topics
- 42.
- 44. A camel isa horse designed by a committee.
- 45.
- 46.
- 47.
- 51.
- 52.
- 54.
- 55. USABILITY TESTING No regularuser noticed. FLOW CONVERSION
- 56. USABILITY TESTING No regularuser noticed. FLOW CONVERSION 2-10% uplift. (depending on platform and countries)
- 57. Accept that thingsare complex from the start. Don’t avoid complexity — fight it! Develop complexity antibodies: - Fanatic Focus (two-list prioritization) - Simplification Reviews (H.O.R.S.E) - Absence Testing (qualitative / quantitative)
- 60. Accept that thingsare complex from the start. Don’t avoid complexity — fight it! Develop complexity antibodies: - Fanatic Focus (two-list prioritization) - Simplification Reviews (H.O.R.S.E) - Absence Testing (qualitative / quantitative)