![Scenario [element names]
Peter explores bike profiles on the CHOOSE BIKE PAGE
Sees info about what he can do here [Content box]
Sees multiple bike images w/ basic info & price [Carousel]
Uses controls to pan through them [Carousel]
Chooses a bike to see in more detail [Carousel]
Peter sees the bike he picked on the CONFIGURE BIKE PAGE
Sees large image of bike he chose [Bike config picture]
Sees list of parts with info and prices [Bike config list]
Sees the total price [Bike config list]
etc...](https://image.slidesharecdn.com/2012-04-12-leanuxnyc-wkshp-130416190633-phpapp01/85/Conversation-Cadence-Culture-34-320.jpg)
Uploaded byLane Goldstone
Conversation, Cadence & Culture
The document outlines strategies for fostering collaboration within teams, emphasizing the importance of trust, communication, and shared vision throughout the product lifecycle. It provides specific recipes for engaging conversations, defining MVPs, and conducting design experiments, while illustrating these concepts through a custom bike web application example. The focus is on iterative development using lean methodologies to enhance creativity and ensure team alignment.
More Related Content
Similar to Conversation, Cadence & Culture
Conversation, Cadence & Culture
- 1. Conversation, Cadence & Culture Recipesto inspire collaborative teams
- 2.
- 3. Agenda Today you willlearn how to: • Stimulate necessary conversations between team members • Advance with a shared vision and • Maintain a culture of invested team members Throughout the lifecycle of your product
- 4.
- 5. What are thequalities of happy productive teams?
- 6. Good work comesfrom good teams Trust Ownership Empathy Communication Fun Flow Empowerment Creativity Productivity
- 7. Culture Our work atCarbon Five
- 8.
- 9. Design + Agile+ Lean Startup Design Thinking empathy, creativity and rationality Agile Development self-organizing teams, quality code, iterative & incremental delivery Lean Startup products people want, learning experiments
- 10. Developer Designer Product Owner
- 11.
- 12. Conversation Recipes to unlockcreativity and collaboration
- 13. Recipes for conversation Question Recipe What’s the vision? Opportunity Statement, Persona 4x4, Project Brief What might we do? Six-ups, Scenarios How will it look and Thumbnails, behave? Wireframe Walkthrough
- 14. Recipes for conversation Question Recipe Where do we start? Define MVPs & Experiments How do we build it? User Stories Does it work? Five on Friday
- 15. Recipes are nota process Use whatever helps your team: •Focus on a shared goal •Minimize handoffs •Have the right conversations
- 17. Let’s see howthis works!
- 18. wheel nice guys wheel nice guys
- 19. Create a sharedvision opportunity statement persona 4x4 six ups
- 20. Opportunity statement Problem: Custombike shoppers find it difficult to learn about, configure and purchase bikes. Solution: A Web application that lets custom bike shoppers explore different components, envision different combinations and understand price.
- 21.
- 22.
- 23. Try it! Six-ups Based onthe opportunity statement, what could we create for Peter?
- 24. What could wecreate? Problem: Peter finds it difficult to learn about, configure and purchase a new commuter bike. Solution: A Web application that lets Peter explore different components, envision different combinations and understand price.
- 25. Show and tell(six-ups)
- 26. six-up demo: six-up conversation
- 27. Define an MVP dotvoting project brief
- 28. Try it! Dot voting Basedon the conversation you observed, where are areas of risk & opportunity?
- 29. six-up Where’s your dot?
- 30. dot voting demo: MVP conversation
- 31. project brief last updated opportunity persona(s) scenarios metrics
- 32. Just in timedesign scenario UI elements and layouts thumbnails living style guides & visual assets
- 33. Scenario demo: scenario Peter explores bike profiles conversation Sees info about what he can do here Sees multiple bike images w/ basic info & price Uses controls to pan through them Chooses a bike to see in more detail Peter sees the bike he picked Sees large image of bike he chose Sees list of parts with info and prices Sees the total price etc...
- 34. Scenario [element names] Peterexplores bike profiles on the CHOOSE BIKE PAGE Sees info about what he can do here [Content box] Sees multiple bike images w/ basic info & price [Carousel] Uses controls to pan through them [Carousel] Chooses a bike to see in more detail [Carousel] Peter sees the bike he picked on the CONFIGURE BIKE PAGE Sees large image of bike he chose [Bike config picture] Sees list of parts with info and prices [Bike config list] Sees the total price [Bike config list] etc...
- 35. UI elements Header Talk to us Marketing message(s) Bike images Bike config picture Bike config list Footer
- 36.
- 37. page layouts thumbnails
- 38. Living style guide &visual assets
- 39. Define an experiment wireframe walkthrough user stories
- 40.
- 41. Try it! 1-week experiment Whatcan we build and validate in the first week?
- 43. Try it! User story Asa.... I want to...so that... Acceptance criteria?
- 44.
- 45. Cadence Establishing your continuous,iterative cycles
- 46. How much time? project start kickoff - 2 days to 2 weeks regular cadence Monday - reflect & define Tuesday - specify Wednesday & Thursday - build & refine Friday - customer feedback
- 47. How can youuse these recipes on your projects?
- 48.
- 49. Thank you! Carbon Five LeanUX & Agile Development for Web and mobile products www.carbonfive.com