How Mapquest Builds Products

Transcript

1. How MapQuest Builds Products - The Spotify Way Presented by Natty Zola Senior Director of Product & Design @ MapQuest #MapQuestDSW @NattyZ
2. Lets Get Warmed Up 1. Think of a product you’ve built, worked on or contributed to that was NOT successful and why 1 min
3. Title Sponsors
4. Tech Track Sponsor
5. Partner Sponsors
6. Member Sponsors
7. Lets Get Warmed Up 1. Think of a product you’ve built, worked on or contributed to that was NOT successful and why 1 min 2. Turn to the person next to you, introduce yourself and create a secret handshake 3. Describe the product and insight you thought about earlier to your new friend 2 min
8. Hello! I’m Natty Zola
9. Hello! I’m MapQuest
10. Common Challenges 1. How does an organization go from idea to successful product launch 2. How does an organization structure itself and how do individuals identify themselves 3. How do you maximize day-to-day productivity, coordination and happiness
11. Why Is This Important • Everyone faces these challenges • Failing to address these challenges is costly • Answers are the building blocks of culture • Answers provide the best opportunity for success
12. playbook influenced by
13. playbook 1. Strategy: Think It, Build It, Ship It, Tweak It 2. Teams: The power of Tribes, Squads and Guilds 3. Process: MapQuest Modified SCRUM + a Disclaimer
14. Challenge #1 How does an organization go from idea to successful product launch
15. Everlater Photobooks
16. MapQuest Vibe
17. Photobooks and Vibe • Great ideas, but ended up not being what users wanted • Over-built and expensive • Wasted resources, killed motivation
18. Think It, Build It, Ship It, Tweak It
23. TBST Key Benefits • Capabilities and success defined up front • Users on the product long before launch • Promotes minimal development • Checkpoints force critical thought/decision making
24. Challenge #2 How does an organization structure itself and how do individuals identify themselves
25. Traditional Org. Structure by Function Identity is with function Functional priorities trump product priorities
26. Tribes, Squads & Guilds
27. Squads
28. Tribes
29. Guilds
30. @ MapQuest *note: this is just an example
31. Tribes, Squads & Guilds Key Benefits • Collaboration: “I’m on the Android App team” • Scale • Shared definition of success + a note about HR
32. Challenge #3 How do you maximize day-to- day productivity, coordination and happiness
33. Things We Knew • We wanted to be agile, but not unfocused • Product and Engineering collaboration is key • Engineers want to write code • We wanted to plan a roadmap and be able to assess the impact of changes in priority
34. modified SCRUM
35. Backlog Hard Sprint boundaries 1 Everything in the Backlog is pointed and is official SOR 2 Shared accountability for Sprint completion 4 Company wide Sprint reviews 3
36. It’s a Wrap! 1. How does an organization go from idea to successful product launch 2. How does an organization structure itself and how do individuals identify themselves 3. How do you maximize day-to-day productivity, coordination and happiness Think It, Build It, Ship It, Tweak It Tribes, Squads & Guilds Strategies from MQ Modified SCRUM
37. @NattyZ natty.zola@mapquest.com Thanks! We’re Hiring!
38. Q&A
39. Title Sponsors
40. Tech Track Sponsor
41. Partner Sponsors
42. Member Sponsors