Skip to content
GanttPal
Log in Get started

What Is Design Operations? A Practical Guide from Philip Rowe

Design operations sits where product, engineering and UX meet. In this episode, Philip Rowe, a UX program manager at Google, explains the role to Brett Harned and shows how it helps design teams deliver inside a larger product system.

The role in one sentence

Design operations is best understood as program management for design teams. It is tactical and strategic at once: it applies project-management discipline while using design thinking to connect business goals with the way design work actually happens. The role therefore sits between product, engineering and UX, translating needs across those groups so creative work can move forward without losing sight of what can be built and shipped.

Three legs, one product team

A useful mental model is a three-legged stool. Product, engineering and UX each support the others; if one leg is missing or ignored, the work becomes unstable. Design operations helps keep all three connected. Cross-functional design sprints are part of that balance: the team first opens up options, then narrows them down until they converge on a buildable solution.

Sprints inside a release frame

At Google, as described in the episode, design activity is fitted into engineering's release schedule. Think of the outer structure as mostly sequential, with agile iteration inside it. That distinction matters: the release date and delivery frame are fixed by the wider engineering plan, while design can still explore, test and refine within the time available.

Skills that matter most

Strong program-management skills matter more than deep design craft. You still need to be comfortable with creative work and with ambiguity, because design problems rarely arrive fully defined. Rowe's own background in project management and UX design illustrates the blend: enough design literacy to understand the work, and enough operational skill to plan, track and unblock it.

Keeping creative teams supported

Good design operations protects creative time. Tracking should stay simple, wins should be recognised, and unknowns should be reduced before design reviews. When people walk into a review with fewer surprises, they can spend their attention on the work itself rather than on logistics, missing context or unresolved questions.

Using OKRs to protect focus

Quarterly OKRs agreed with leadership give the role a clear basis for prioritisation. When a new request arrives, it can be judged against those agreed goals instead of being accepted by default. That shared agreement makes it easier to say no, defer, or redirect effort without turning every decision into a fresh negotiation.

A practical checklist

Use this checklist when deciding whether a design-operations approach fits your team:

  • Confirm product, engineering and UX all have a voice in planning, not just in review.
  • Map design sprints to the engineering release schedule before work begins.
  • Agree quarterly OKRs with leadership so priorities are settled in advance.
  • Keep tracking light and remove unknowns before design reviews.
  • Celebrate completed work so progress stays visible to creative teams.
  • Test every new request against the agreed OKRs before accepting it.

About the episode

The episode runs 31 minutes 57 seconds and covers how design operations works at Google, how other teams interact with design-operations staff, design thinking and related processes, team culture, and the use of OKRs. Resources mentioned include Rowe's Digital PM Summit 2019 presentation on scaling design teams, an article on what great listeners do, a book on saying no constructively, and Google's guide to setting goals with OKRs.

Frequently asked questions

What is design operations in practice?

It is program management applied to design teams, positioned between product, engineering and UX. The emphasis is on coordination, process and priorities rather than producing design work directly.

Do you need to be a designer to do design operations?

Program-management ability comes first. Comfort with creative work and ambiguity matters, while deep design expertise is less central than the ability to organise people, schedules and decisions.

How do product, engineering and UX fit together?

Product, engineering and UX are treated as three interdependent legs. Cross-functional sprints move through divergence and convergence so the team can settle on solutions that can actually be built.

How do design sprints fit a release schedule?

Design work is placed inside engineering's release cadence. The outer frame is largely sequential, with iterative work happening within it.

How do quarterly OKRs help with saying no?

Agree quarterly OKRs with leadership in advance. New requests can then be tested against those agreed priorities, which makes it easier to decline work that does not fit.