The “Decider vs Shaper” Model: Stop Arguing About Ownership

Hook

When PMs and designers fight about “ownership,” they’re usually fighting about a missing concept: shaping the decision vs making the decision.

Thesis

You can stop most PM–design friction by separating two roles that often get blurred:

• Shaper: influences the decision by improving the options and reasoning.
• Decider: makes the call when tradeoffs remain.

The decider vs shaper model

Shapers do this

• Expand options (not just “Option A vs Option B,” but reframing the problem).
• Clarify constraints and user needs.
• Stress-test assumptions with evidence or prototypes.
• Improve the decision quality before a decision exists.

Deciders do this

• Choose a direction when options are “good but different.”
• Own the consequences: timelines, metrics, stakeholder expectations.
• Prevent churn: “we decided X because Y; we’ll revisit when Z is true.”

Design is often the best shaper for interaction decisions. PM is often the final decider for scope and sequencing. But both roles can shape—and sometimes decide—depending on the topic.

Why this matters: the hidden failure mode

Without this separation:

• Designers feel disrespected (“PM overrode craft”).
• PMs feel blocked (“design won’t converge”).
• Engineering gets whiplash (“requirements keep changing”).

The real issue is that the team never agreed on who is shaping vs deciding at which moment.

A practical rule of thumb (use this tomorrow)

For every project, list the key decisions and assign roles:

Decision	Shaper (primary)	Decider (final)
Target user + job-to-be-done	PM + Design	PM
Interaction approach	Design	Design (unless huge business risk)
Scope for v1	PM	PM
Quality bar for ship	Design + Eng	PM + Design together
Success metrics	PM	PM

If you don’t like tables, write it as bullets. The point is explicitness.

How to run meetings with this model

Start with: “We’re shaping today, not deciding.”

• Shaping meeting output: 2–3 viable options, tradeoffs, evidence needed.
• Deciding meeting output: one direction, the “because,” and what would change it.

If you skip the shaping phase, decisions become personality contests.

Counterpoint: “Isn’t this too rigid?”

It’s only rigid if you treat it as a legal contract. Think of it as a traffic signal:

• Green = decide
• Yellow = shape more
• Red = not enough clarity to decide

Actionable takeaways

• Put “Shaping” or “Deciding” in the calendar invite title.
• Assign a decider for each decision, not for the whole project.
• When disagreeing, ask: “Are we shaping or deciding?”
• If you’re the decider, require at least two shaped options before calling it.

---