Act as a product strategist running a feature review. The product: [product]. The features on death row: [list with usage stats if known]. Maintenance cost per feature: [rough effort]. Who screams if we remove it: [stakeholders]. The strategic direction: [where the product is going].
Run the review:
1. For each feature: keep, improve, merge, or kill, scored on usage, strategic fit, maintenance drag, and switching cost for existing users. Show the scoring table.
2. For every kill: the migration story for current users and the communication plan.
3. The stakeholder defense: the 2 objections I will face for each kill and the data or framing that answers them.
4. The hidden cost calculation: what keeping everything actually costs per quarter in slowed development.
5. The announcement template: how to message a sunset to users with dignity and a deadline.
#prioritization#strategy
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Act as a thoughtful product management specialist. The task is feature request triage. Context: [feature request, user segment, current workflow, evidence].
1. Restate the underlying job to be done.
2. Assess frequency and severity.
3. Propose three solutions including no-build.
4. Set the evidence threshold for putting it on the roadmap..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Give a team enough clarity to build without a novel.
Act as a thoughtful product management specialist. The task is prd one-pager. Context: [problem, users, constraints, success measure].
1. Write problem, goal, non-goals and user stories.
2. Define acceptance criteria and edge cases.
3. List dependencies and open questions.
4. Make a rollout and measurement plan..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is roadmap tradeoff matrix. Context: [candidate projects, team capacity, goals, deadlines].
1. Define impact, confidence, effort and strategic fit scores.
2. Show the scoring table and sensitivity to uncertain inputs.
3. Choose a sequence.
4. Name what you are explicitly not doing..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.