First-principles UX for product teams that ship weekly

Most product teams do not need more frameworks. They need a smaller set of habits that survive a noisy week — and a willingness to put the product back down when those habits say to stop.

These are the heuristics we keep returning to. They are not novel. They are the ones we have not been able to argue our way out of after shipping for a decade.

Design at the speed of decisions, not pixels

A weekly shipping cadence rewards designers who reduce the number of decisions a product manager has to make on Monday. Mockups are a side effect. The real artifact is the resolved question.

Heuristics that pay rent

• If a screen needs a tooltip to be understandable, the screen is not finished.
• If a feature requires onboarding, scope the onboarding before scoping the feature.
• A "small UX fix" that touches three flows is not small.
• Default states matter more than empty states. Most users never empty anything.
• When in doubt, make the destructive action one more click and the constructive action one less.

The best product designers I have worked with are not the fastest at Figma. They are the fastest at deciding that a thing does not need to be designed at all this week.

Rituals that keep the product quiet

Three rituals have survived every team change we have made. A weekly walk-through of the live product on a real device. A monthly audit of the five most-used screens, with one micro-improvement shipped from each. A quarterly review of what we removed, not what we added.

None of this requires new tooling, and most of it is uncomfortable for the team in the short term. The compounding effect — on retention, on support load, on the kind of feedback users send — is the only durable case for working this way.