Templates
26 templates for product teams — each builds a real workspace. Browse all templates.
Product templates in short
A Now / Next / Later roadmap that flows discovery to ship, with initiative-level grouping and release notes at the end of the pipe.
Now / Next / Later board out of the box
Move specs from draft to approved with explicit review gates, so engineering never starts on a half-baked PRD.
Explicit review and approval gates before build starts
A single intake list for customer feature asks, deduped and labeled, so the loudest request isn't the only one you hear.
One intake list for every channel of feedback
Plan studies, track interviews, and turn findings into linked product issues — research that ends in action, not a slide deck.
Study lifecycle from recruiting through synthesis
A backlog of growth bets scored and run as experiments, with a learnings log so wins and losses both compound.
ICE-scored backlog so the next experiment is obvious
An intake-to-delivery board for data and analytics requests, so dashboards, metrics, and ad-hoc analyses get triaged, scoped, and shipped instead of lost in DMs.
One intake queue so data requests stop living in chat
Run continuous discovery as an opportunity-solution tree — opportunities, assumptions, and experiments tracked before anything reaches the roadmap.
Opportunity-solution tree keeps solutions tied to real problems
Run a private or public beta end to end — recruit testers, gate access, collect feedback, and decide on general availability with evidence.
Tester lifecycle from recruiting through GA decision
A repeatable readiness checklist for shipping a feature — docs, support enablement, metrics, and rollout plan — so launches don't forget the unglamorous parts.
One readiness checklist every feature must clear
Connect product objectives to the bets meant to move them, with confidence states and weekly updates so the team always knows if a KR is on track.
Key results link directly to the bets meant to move them
A living tracker for competitor moves, win/loss notes, and feature gaps — so product and sales decisions are informed by the market, not vibes.
One home for competitor signals, win/loss, and feature gaps
A rigorous experiment register — hypothesis, metric, sample size, and result — so every A/B test ends in a documented, shareable decision.
Pre-registered hypothesis and metric on every test
Run a pricing or packaging change as a cross-functional project — research, modeling, and a careful rollout — so monetization moves don't ship half-considered.
Research and modeling before a single price changes
Coordinate translation and locale rollout — string extraction, translation, in-context review, and QA — so going multi-language stays organized.
Per-locale labels keep parallel languages from colliding
Track WCAG audit findings and accessibility fixes by impact, so a11y is a continuous practice with a clear queue — not a pre-launch scramble.
Audit findings tagged by WCAG level and impact
Turn shipped work into clear, customer-facing release notes — draft, edit for the customer, and publish — so launches are communicated, not silently merged.
Shipped work that needs a note never falls through
Test packaging and price points with rigour — design the experiment, ship it to a cohort, read the revenue impact, and only then roll the winner out.
Revenue-impact framing, not just conversion-rate vanity
Intervene before accounts churn — catch at-risk signals, run the right save play, and track which interventions actually retain revenue.
Risk signals routed to the right save play, not generic outreach
Run NPS as a closed loop, not a number — survey, segment the verbatims, follow up with detractors, and ship the themes that move the score.
Detractor follow-up is a tracked task, not a good intention
Learn why deals close or slip away — interview the buyer, code the reason, and feed patterns back to product, pricing, and sales enablement.
Buyer interviews triggered automatically on material deals
Give sales one structured front door to product — capture the deal context behind each ask, weight by revenue at stake, and close the loop when it ships.
One structured intake instead of scattered Slack pings
Retire features customers no longer need — measure usage, warn the few who depend on it, offer a migration path, and remove it cleanly.
Usage data gates the decision, not gut feel
Build evidence-backed personas — recruit representative users, interview for goals and pains, and keep each persona a living artifact the whole team uses.
Personas backed by interviews, not stock-photo guesswork
Map the jobs your customers hire the product for — capture the job, the current workaround, and the gap, then prioritise the jobs you under-serve.
Importance-vs-satisfaction scoring finds the real opportunities
Stand up product integrations as a pipeline — scope the use case, build and certify the connector, list it, and drive adoption together with the partner.
A full lifecycle from request to certified listing
Systematically remove friction from first-run — map the activation funnel, attack the biggest drop-off, and measure the lift to the aha moment.
The funnel's biggest leak is always the next thing you fix