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
17. scrap•py
/‘skrapē/ • adj
seemingly small and unthreatening,
but shockingly able to kick your ass
Source: Urban Dictionary
“A scrappy Design Program Manager”
29. 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
30. 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
31. Playbook Contents: A Compelling Direction
Pandora
Digital Product
Development
Product
Design
Vision, Mission, Purpose, Principles
Vision, Goals, Strategies, Metrics
Goals, Team Principles, Experience Principles
34. 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
51. “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
53. 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
63. 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