User Stories Template for New PMs on Startup Campaigns
A short user stories template for new PMs running their first startup campaign — light, fast, and structured to catch silent disagreement before launch.
Five fields, ten minutes per story, agreement that holds to launch
On startup campaigns, the team agrees in the kickoff and disagrees in the launch retrospective. The five fields below close most of the gap.
New PMs running their first startup campaign often discover that 'agreement' at the kickoff doesn't survive to launch. The team nodded along, then went and built different things. The silent disagreement pattern is structural — the kickoff format doesn't surface where people are interpreting the same words differently.
This template is light: five fields per story, about ten minutes per story to complete. It's calibrated specifically to startup campaign work, where the team is small and cross-functional, and where the cost of silent disagreement is high but the time available for thorough story workshops is low.
Five fields, in order
0 / 5- The story. What the campaign needs to communicate or accomplish, in one sentence. Don't use the formal 'as a user' template if it doesn't fit campaign work; one clear sentence is better than a forced template.
- Who specifically. Which audience segment, named specifically. 'Customers' is too vague; 'enterprise IT buyers in the $50M+ revenue segment' is specific enough to test interpretations against.
- What success looks like. 1-3 measurable outcomes. Engagement rate, conversion rate, brand recall — whatever the campaign is being measured against. Force specificity: 'increase awareness' isn't measurable; 'increase aided brand awareness from 20% to 30% in the target segment' is.
- What it's not. 1-3 things this story explicitly doesn't cover. The 'not' field surfaces silent disagreement most reliably — most disagreements live at the edges of scope.
- Open questions. Anything not yet resolved. The list should shrink as the story matures.
“The 'what it's not' field saved my second campaign. We had a story about 'launching the new product line.' Three of us put different things in the 'what it's not' field — different launch markets, different audience segments, different timing. We hadn't agreed at all. We'd just used the same words.”
- Day 1Draft stories1-2 hours, alone or with the senior PM. Get the first three fields written for each story.
- Day 2Team workshop1 hour, full team. Walk through each story; fill 'what it's not' and 'open questions' collectively. The conversation is the point.
- Day 3-5Resolve open questionsEach open question gets an owner and a date. Stories aren't signed off until their open questions are resolved.
- Day 5Sign-offEach story signed off individually, not as a batch. Each stakeholder confirms in writing that they've read it and agree.
The template is deliberately light — five fields, ten minutes per story. Its leverage comes from the 'what it's not' field, which catches most silent disagreement by making the team explicit about scope boundaries. For longer-format work on bigger projects, see the delivery lead implementation template; for the software-specific equivalent on startups, see the new-PM software template; for retrospective work after launch, see the user stories retrospective checklist.