Turn messy project feedback into team habits

Convert retrospective complaints and scattered project notes into concrete team working agreements and actionable habits.

You getRoot Friction Points, proposed Team Working Agreements and habit Rollout Script

Prompt

Prompt
You are an agile coach and team systems specialist helping a lead transform retro notes into team habits.

- Extract the core operational breakdowns from the provided project feedback.
- Convert vague complaints into specific, binary working agreements (actions the team either did or did not do).
- Keep habits realistic to enforce, with a designated trigger and clear verification check.

Output format:
- Root Friction Points (3-4 bullet points identifying the recurring operational issue)
- Proposed Team Working Agreements (Table: Trigger Event | Required Team Action | Who Checks It)
- Habit Rollout Script (a short paragraph to present these changes in the next team sync without assigning blame)

The raw retrospective feedback is below:

Example output

Example for: retro notes following a rushed quarterly client product launch

Root Friction Points
  • Scope was added in Slack messages without adjusting agreed deadlines.
  • Pull requests sat without review for days, causing an end-of-sprint testing crunch.
  • Design assets arrived incomplete during the development sprint rather than during refinement.
Proposed Team Working Agreements
Trigger EventRequired Team ActionWho Checks It
Client or stakeholder requests new scopeLog in backlog; do not assign to active sprint without dropping an equal point itemProduct Owner
PR opened in repositoryAssign 2 reviewers immediately; reviews completed within 24 business hoursDaily Standup Lead
Sprint Planning kickoffStories must have final design links and acceptance criteria 24 hours before meetingTech Lead
Habit Rollout Script

"Thanks everyone for the clear retro feedback. Looking back at our launch, the friction wasn't our engineering quality; it was how work entered the sprint mid-flight and stalled in review queues. To protect our focus and prevent end-of-cycle crunch, we are testing three simple rules starting this sprint: no scope swaps without an equal trade, 24-hour code review turnarounds, and designs fully finalized before planning. We will review how these felt in two weeks."

Written by AI from this prompt. Your results will vary.

Paste your unfiltered retrospective notes or post-mortem bullet points into ChatGPT, Claude, or Gemini. If some agreements seem too demanding, ask the model to simplify them into lightweight checklist items.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management