← Writing

A Practical Checklist to Assess Your PM–Design Relationship

September 7, 2024 · PM × Design

A Practical Checklist to Assess Your PM–Design Relationship

Hook

If your PM–design relationship feels “fine” until it suddenly isn’t, you probably don’t have a diagnosis tool. You have vibes.

Thesis

A simple checklist—used monthly—will surface misalignment early and prevent the “big blowup” that costs weeks.

The checklist (score 0–2 each)

0 = not true, 1 = sometimes, 2 = consistently true

1) Shared problem clarity

  • We can both state the user problem and success criteria in one paragraph.
  • We agree on the top constraints (time, tech, legal, brand, etc.).

2) Decision rights

  • We know who decides what for this project.
  • We rarely re-open decisions without new information.

3) Workflow health

  • Design work starts with enough context to avoid thrash.
  • PM feedback is timely and specific (not “I don’t like it”).
  • Engineering joins early enough to prevent “design–dev divorce.”

4) Crit quality

  • Reviews focus on goals and tradeoffs, not personal preferences.
  • We discuss risks (usability, edge cases, accessibility) openly.

5) Trust and respect

  • Disagreements do not feel like power struggles.
  • We protect each other from random stakeholder drive-bys.

6) Customer evidence loop

  • We regularly anchor decisions in user evidence.
  • We share research learnings and don’t weaponize anecdotes.

How to interpret the score

  • 0–8: high risk. You’re operating on luck.
  • 9–16: functional. You can ship, but you’ll hit periodic friction.
  • 17–24: strong. You’ll move fast without sacrificing quality.

The absolute number matters less than the trend. If your score is dropping, fix it before the roadmap suffers.

The “one hour reset” playbook

If your score is low, do this in a single hour:

  1. Pick the lowest-scoring category.
  2. Name the behavior, not the person (“we re-open decisions late”).
  3. Agree on one change for 2 weeks.
  4. Re-score after 2 weeks.

Examples of two-week fixes:

  • Add a 15-minute weekly pre-brief.
  • Write problem statements before mocks.
  • Define ship criteria together (quality + scope + metrics).

Counterpoint: “This feels like process overhead”

The overhead is smaller than the alternative: unplanned rework, escalating conflict, and stakeholder confusion. The checklist is a rework prevention tool, not bureaucracy.

Actionable takeaways

  • Run this checklist monthly with your design partner.
  • Don’t debate the score—debate the examples behind the score.
  • Pick one fix at a time; consistency beats big process changes.
  • Track trend lines. A relationship that’s getting worse is a product risk.