Create beginner Works with: Any AI

Retrospective Action Follow-Through System

Before after Has example

Make improvements actually happen.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Design a system for retrospective actions. Past retrospectives and what happened to the actions: [PAST_ACTIONS]. Team size: [TEAM_SIZE]. Tools: [TOOLS].

Diagnose why actions fail (too many, vague, no owner, no time allocated, not reviewed). Produce: rules (maximum two or three actions per retro, each with an owner, due date, and a definition of done); a visible action board; a time allowance in the sprint plan for improvement work (for example 10 percent of capacity, with arithmetic); a review routine at the start of each retro (done, in progress, dropped, with reasons); and a metric (action completion rate).

Rewrite five vague actions from my list into concrete ones. Example: Before "Communicate better". After "Post blockers in the team channel by 10 am; owner: Sam; review in two weeks; measure: blockers older than one day". Include a template and a plan for escalating actions that need management help. Use my details.

Include a one-page action board layout, the exact wording of the review question at the start of each retrospective, and a rule that an action unfinished twice is either dropped with a reason or escalated.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Diagnosis: last three retros produced 14 actions; 3 were done (21 percent).
Rules: at most two actions per retro; each has an owner, due date, and definition of done; 10 percent of sprint capacity reserved: 5 people x 10 days x 0.10 = 5 person-days.
Before: "Communicate better." After: "Post blockers in the team channel by 10 am; owner Sam; review in two weeks; measure: blockers older than one day."
Before: "Improve testing." After: "Add two automated checks for the checkout flow; owner Lin; done by sprint 12; measure: escaped defects."
Board columns: proposed, doing, done, dropped (with reason).
Start each retro with a five-minute review of last actions. Action completion rate = done / set; target 80 percent.

• retro-actions