Real Talk: Proving Value through a Scrappy Playbook

Key Insights

• •

  Organizational ambiguity post-acquisition creates anxiety and low morale which design ops can directly address.

• •

  A scrappy approach—prioritizing progress over perfection—enables design ops teams to deliver impactful solutions quickly.

• •

  Lack of role clarity and inaccessible documentation often cause confusion and inefficiency within design teams.

• •

  Consolidating dispersed knowledge into a simple, shareable playbook improves team alignment and understanding of vision and goals.

• •

  Grounding team guidance in frameworks like Hackman’s Five Factor Model can structure design ops efforts effectively.

• •

  Introducing a common vocabulary (e.g., McKinsey’s Horizon model) helps teams discuss work consistently and facilitates cross-team collaboration.

• •

  Measuring qualitative factors, such as team sentiment and clarity, can provide valid metrics of design ops impact.

• •

  Design ops value must be proven not only upward to leadership but also sideways and downward to teammates and partners.

• •

  Design ops documentation should be visual, high-level, and conversational to encourage engagement beyond wiki deep dives.

• •

  Continuous evolution and iteration in design ops are essential; there is no fixed end state, so regular updates and roadshows sustain momentum.

Notable Quotes