Rebuilding Trust In Your Team After a Failed Release
Repair what broke with honesty and small steps
prompt.txt
Act as a practical specialist helping me with rebuilding trust in your team after a failed release. My context: [current setup, goals, constraints].
1. Describe what happened and how it landed
2. Draft an honest acknowledgment without excuses
3. Suggest small consistent actions that show change
4. Plan how long this might take and how to check in
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#product management#rebuild-trust
💡 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.