Once you can write a basic value prop, the hard part is using it under time pressure and politics. Here are advanced tactics I'd actually use.
Trade off against time
A perfect value prop that ships next year loses to a sharp one that guides this quarter. I'd timebox:
- Enough clarity to prioritize
- Explicit assumptions to revisit
- A date to re-validate with customers
Let the value prop kill features
If a request doesn't advance the prop, it needs an exceptional reason. This is how good props create roadmap courage.
| Ask | Filter |
|---|---|
| Sales one-off | Does it expand the ICP value prop or fragment it? |
| Exec pet feature | Which customer job does it serve? |
| Competitor parity | Do customers choose us for that axis? |
"Surprise and delight" isn't always desirable
Delight that distracts from the core job can burn eng capacity and confuse positioning. I'd rather nail the promised outcome reliably than sprinkle confetti on a broken workflow.
Practical moves
- Put the value prop at the top of every roadmap review
- Score initiatives against it in writing
- Retire props that no longer match the business
- Teach PMs and POs to argue from the prop, not vibes
This is product craft more than copywriting. Strengthen it with a PM Certification and real prioritization reps. More in the newsletter.