Working with PMs
Defending craft without slowing the train.
- Explain craft in terms of user and business outcomes
- Offer options with costs instead of a yes or no
- Plan polish so it doesn't land as a late surprise
Product managers own what gets built and when. UX engineers care about how it feels. The two goals rarely conflict, but they need translating to each other, and that translation is a big part of the job.
Speak in outcomes
"The easing is wrong" is taste. "This panel feels slow, so people will think the app is laggy" is an outcome a PM can weigh. Tie craft to things they care about: conversion, support tickets, retention, trust in a sensitive flow.
Offer options, not vetoes
Instead of "we can't ship this", offer a menu:
- Ship as specified — and accept the known rough edges
- Small fix — half a day, covers the most common case
- Proper fix — two days, covers the edge cases too
Options turn a disagreement into a decision you make together.
Plan polish early
Polish added at the end looks like scope creep. Polish planned at the start is part of the estimate. When a feature kicks off, name the few details that will matter most (loading states, the error path, a key transition) and include them in the plan.
Show, don't argue
A quick coded prototype or a before/after recording settles most debates about feel faster than a discussion. Let people feel the difference.
Pick your battles
Not every detail is worth a fight. Save your influence for the moments where users are most affected, and let the small things go when the deadline is real.
For the next feature you build, write a short note to your PM listing two or three craft details you want to include, what each costs in time, and what users would notice if it were cut. Agree on them before you start.