Session Builder

Establish practice

Define cadence, owner, participation, and success signals for a recurring team practice.

Practice CharterweeklyOperating practice

Establish the practice

Define cadence, owner, participation, and success signals so the method works as a recurring team practice.

Derived automatically

Variant for Operating practice. The plan is derived from method form, method steps, and runsheet.

Runsheet

Cadence logic

Rhythm before scope

An operating practice works through repetition. The cadence should be small enough to hold reliably.

Iteration flow

One run, reusable each time

The steps describe one repetition and are adjusted after review.

1
0-5 min
5 min
State the intended outcome and the scope of the event or phase. Agree on what is in and out of the review.
OwnerIf the goal is still fuzzy, the review will drift. Start with the concrete result that should have happened.
2
5-12 min
7 min
Describe the actual sequence of events in order. Use evidence, not memory alone.
TeamIf people start explaining early, bring them back to the timeline first. Sequence comes before judgment.
3
12-20 min
8 min
Compare intent and reality and explain the largest deviations or surprises.
TeamDo not jump from deviation to blame. Name the gap clearly and keep the explanation mechanism-focused.
4
20-30 min
10 min
Collect lessons and patterns that are reusable beyond this one event.
TeamIf the lessons stay too general, ask what the team would repeat, avoid, or measure differently next time.
5
30-45 min
15 min
Turn the lessons into concrete actions with owner and follow-up date, then close the review.
TeamIf no action is owned, the learning will vanish. Keep the number of actions small and specific.

Usable artifact

Practice Charter

Copyable charter with purpose, cadence, owner, participation, flow, success signals, and review.

practice-charter.md

Practice Charter: After-Action Review

Purpose

The method helps clarify workflows, data, causes, and improvements concretely. It identifies patterns, causes, bottlenecks, and weaknesses and derives actions. The outcome is captured as lessons learned, action items, and event summary.

Cadence

weekly

Owner and Participation

Owner: open
Participants: 3-12
Mode: synchronous

Flow per Iteration

0-5 min (5 min) State the intended outcome and the scope of the event or phase. Agree on what is in and out of the review.
5-12 min (7 min) Describe the actual sequence of events in order. Use evidence, not memory alone.
12-20 min (8 min) Compare intent and reality and explain the largest deviations or surprises.
20-30 min (10 min) Collect lessons and patterns that are reusable beyond this one event.
30-45 min (15 min) Turn the lessons into concrete actions with owner and follow-up date, then close the review.

Success Signals

Lessons learned, Action items, Event summary

Review

4 weeks