← Writing

When a PM Should Push Back on Craft—and When to Let It Go

May 3, 2025 · PM × Design

When a PM Should Push Back on Craft—and When to Let It Go

Design craft matters. But not every craft improvement is worth delaying the release. The PM’s job isn’t to lower the bar; it’s to choose where the bar is non-negotiable.

A practical rule: push back on craft only when craft affects one of these three things:

1) Clarity: can users understand what to do?

If the UI hierarchy is muddy, labels are confusing, or the primary action doesn’t stand out, craft isn’t “polish.” It’s correctness.

Push back if:

  • users can’t find the next step quickly
  • the page feels visually noisy
  • key information isn’t scannable

2) Trust: will users believe the system?

In many products, trust is the feature. If design undermines confidence, adoption dies.

Push back if:

  • results look “magical” without explanation
  • error states feel scary or blamey
  • automation can’t be previewed or undone
  • data feels suspicious (no context, no source, no freshness)

3) Friction: does poor craft create drop-off?

Sometimes “small” details cause huge funnel losses.

Push back if:

  • onboarding steps feel heavier than the value
  • empty states don’t guide users
  • microcopy is unclear at decision points (“Save” vs “Publish”)

Now: when should you let craft go?

Let it go when the change:

  • improves aesthetics but doesn’t improve comprehension or trust
  • is a “nice-to-have” animation, spacing, or styling pass
  • increases build complexity without moving outcomes
  • can be shipped as a follow-on iteration without harming the experience

The best way to handle craft tension is to make it explicit:

“Let’s separate bar vs better. What must be true for launch (bar), and what would make it great (better)?”

Then agree on a plan:

  • Launch with the bar met (clarity, trust, control)
  • Put “better” items in a fast follow-up sprint
  • Track a metric that proves whether “better” is needed

In interviews, a clean line is:

“I respect craft deeply. I push back only when craft changes clarity, trust, or friction. Otherwise, I protect the timeline and commit to iteration.”

That signals taste and discipline at the same time.