Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Real Talk: Proving Value through a Scrappy Playbook (Dianne Que at DesignOps Summit 2019)

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige

Hier ansehen

1 von 65 Anzeige

Real Talk: Proving Value through a Scrappy Playbook (Dianne Que at DesignOps Summit 2019)

Herunterladen, um offline zu lesen

Dianne Que: “Real Talk: Proving Value through a Scrappy Playbook”
DesignOps Summit 2019 • October 23-24, 2019 • New York, NY, USA
http://www.designopssummit.com

Dianne Que: “Real Talk: Proving Value through a Scrappy Playbook”
DesignOps Summit 2019 • October 23-24, 2019 • New York, NY, USA
http://www.designopssummit.com

Anzeige
Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Ähnlich wie Real Talk: Proving Value through a Scrappy Playbook (Dianne Que at DesignOps Summit 2019) (20)

Anzeige

Weitere von Rosenfeld Media (18)

Aktuellste (20)

Anzeige

Real Talk: Proving Value through a Scrappy Playbook (Dianne Que at DesignOps Summit 2019)

  1. 1. Real Talk: 
 Proving Value through 
 a Scrappy Playbook Dianne Que @dianneque DesignOps Summit 2019
  2. 2. Hi, I’m Dianne !
  3. 3. Does this sound familiar?
  4. 4. Re-Orgs Leadership Changes Attrition New Hires
  5. 5. Ambiguity Instability
 Uncertainty
  6. 6. Evolving Grounding Rebuilding
  7. 7. "
  8. 8. # #
  9. 9. What we’ll cover today…
  10. 10. BEING SCRAPPY CREATING A PLAYBOOK PROVING VALUE MEASURING OUTCOMES
  11. 11. REAL TALK
  12. 12. What do I mean by “scrappy?”
  13. 13. scrap•py
 /‘skrapē/ • adj
 
 consisting of disorganized, untidy, or incomplete parts. Source: Oxford “A scrappy pile of notes”
  14. 14. scrap•py
 /‘skrapē/ • adj
 
 determined, argumentative, or quarrelsome Source: Oxford “A scrappy New Yorker”
  15. 15. scrap•py
 /‘skrapē/ • adj
 
 seemingly small and unthreatening, 
 but shockingly able to kick your ass Source: Urban Dictionary “A scrappy Design Program Manager”
  16. 16. Source: Me scrap•py
 /‘skrapē/ • adj determined to get shit done 
 without letting perfect 
 get in the way of better
  17. 17. What were some of our
 team’s challenges?
  18. 18. “The team doesn’t understand 
 who is responsible for what.” –VP Challenges
  19. 19. “What’s the difference between a Design Manager and Design Lead?” –Product Designer Challenges
  20. 20. “How do we prioritize projects that aren’t committed on our roadmap?” –Product Designer Challenges
  21. 21. “People don’t follow our workflow…
 because nobody reads our Wiki.” –Design Program Manager Challenges
  22. 22. “Nobody knows what DesignOps is.” –Design Program Manager Challenges
  23. 23. Clarity
  24. 24. To prove value, know 
 what your audience values.
  25. 25. The Playbook
  26. 26. The Playbook A Deck
  27. 27. 1. Being a Real Team 2. A Compelling Direction 3. An Enabling Structure 4. A Supportive Context 5. Expert Coaching Playbook: Contents Source: Richard Hackman’s Five Factor Model
  28. 28. 1. Being a Real Team 2. A Compelling Direction 3. An Enabling Structure 4. A Supportive Context 5. Expert Coaching Playbook: Contents Source: Richard Hackman’s Five Factor Model A Compelling Direction An Enabling Structure
  29. 29. Playbook Contents: A Compelling Direction Pandora Digital Product Development Product 
 Design Vision, Mission, Purpose, Principles Vision, Goals, Strategies, Metrics Goals, Team Principles, Experience Principles
  30. 30. REAL TALK Our Product Design goals and principles weren’t buttoned-up.
  31. 31. REAL TALK Our first deck wasn’t this pretty.
  32. 32. Design Ops 101: Objectives, Values, Core Areas of Design Ops 
 How We’re Organized: Product Groups and Feature Areas
 Org Design North Star
 Roles & Responsibilities
 Core Capabilities & Expectations
 Decision-Making Frameworks: Horizons & DACI
 Workflow & Process
 Meetings
 Systems & Tools  
 Playbook Contents: An Enabling Structure
  33. 33. Playbook Contents: An Enabling Structure
  34. 34. Playbook Contents: An Enabling Structure
  35. 35. Playbook Contents: An Enabling Structure
  36. 36. Playbook Contents: An Enabling Structure
  37. 37. Playbook Contents: An Enabling Structure
  38. 38. Playbook Contents: An Enabling Structure
  39. 39. Provide visibility, visualization, and vocabulary.
  40. 40. Initial Value
  41. 41. Initial Value The playbook became 
 a springboard.
  42. 42. Initial Value The project was a 
 forcing function.
  43. 43. Initial Value It made our team 
 feel better.
  44. 44. We’re not always proving value upwards, but also across and down.
  45. 45. REAL TALK We rolled out the playbook without our manager's approval.
  46. 46. Measuring Impact 
 and Outcomes
  47. 47. Intentional Unintentional Measuring Impact and Outcomes
  48. 48. Clarity Measuring Impact and Outcomes
  49. 49. “Without clarity, organizations quickly come unglued and little bumps—like an angry client or misinformed employee—turn into mountains.” Measuring Impact and Outcomes Source: Chris Myers, Forbes
  50. 50. After 4.6 Before 3.1Clarity Measuring Impact and Outcomes
  51. 51. Measuring Impact and Outcomes This makes me realize how much I take for granted. It’s so useful to have a source of truth for all this stuff, especially 
 when we get lost. 
 
 - Product Designer You guys have your shit together. - Sirius XM partner A lot of people want to
 move toward this type of org design, but you illustrated it in a way that’s easy to digest and understand. 
 
 - Engineering partner
  52. 52. Turn feelings into data
  53. 53. Extensibility Playbook content used in: • Onboarding: 
 Sirius XM, partners, new hires • Cross-functional product kick-offs • Executive shareouts • Other people’s random decks Measuring Impact and Outcomes
  54. 54. Extensibility Measuring Impact and Outcomes Amplification Acceleration Collaboration
  55. 55. Outcomes emerge over time. Measure baselines.
  56. 56. REAL TALK This isn’t really about a playbook. It's about a process.
  57. 57. REAL TALK We re-orged one month after rolling out the playbook.
  58. 58. There is no end-state 
 in DesignOps.
  59. 59. What’s Next?
  60. 60. 1. Evolve & Improve Content 2. Continue Roadshow 3. Define DesignOps Metrics What’s Next?
  61. 61. 1. To prove value, know what your audience values. 2. Provide visibility, visualization, and vocabulary. 3. We're not always proving value upwards, but also across and down. 4. Turn feelings into data. 5. Outcomes emerge over time. Measure baselines. 6. There is no end-state in DesignOps. Key Takeaways
  62. 62. REAL TALK We’re all in this together.
  63. 63. Thanks $ Dianne Que @dianneque

×