Skip to content

Instantly share code, notes, and snippets.

@randallb
Last active February 14, 2026 17:31
Show Gist options
  • Select an option

  • Save randallb/ac0fd027276665c846cf1b13c0218604 to your computer and use it in GitHub Desktop.

Select an option

Save randallb/ac0fd027276665c846cf1b13c0218604 to your computer and use it in GitHub Desktop.

After Action Review (AAR) Template

Use this structure whenever you close a time-bound project or incident. Copy the sections into your project folder (e.g., memos/cross-company/projects/<project>/AAR.md).

# After Action Review (AAR)

## 1. Context
Briefly describe the situation *as it existed at the time decisions were made*.
- What was happening?
- What constraints or pressures were present?
- What information was available / missing?

(1-3 paragraphs max)

---

## 2. Intent (What Was Supposed to Happen)
Restate the **active commander's intent** verbatim or link to it.

- Purpose:
- End State:
- Constraints / Tradeoffs:
- Phase (if applicable):

> This anchors evaluation to intent, not hindsight.

---

## 3. What Actually Happened (Facts Only)
Describe events in order, without judgment.

- Key actions taken
- Notable deviations from plan
- Environmental changes
- Outcomes observed

No analysis yet. No "why".

---

## 4. Delta Analysis (Why It Was Different)
Explain **why reality diverged from intent or expectations**.

Consider:
- Assumptions that were wrong
- Constraints that were unclear or incomplete
- Signals that arrived late or were misinterpreted
- Where the plan no longer fit reality

Focus on **system behavior**, not people.

---

## 5. Initiative Assessment
Document where initiative occurred.

For each instance:
- What changed that justified acting without orders?
- How did the action align with intent?
- Were constraints respected?
- Was the outcome reversible?

Classify (if useful):
- Disciplined initiative (inside intent)
- Undisciplined initiative (outside intent)
- No initiative (plan held)

---

## 6. Weaknesses in Intent (If Any)
Call out flaws *in the intent itself* that were visible at the time or became
apparent during execution. This is about **decision quality**, not blame.

Prompts:
- Ambiguities or missing success criteria
- Conflicting incentives or unclear tradeoffs
- Assumptions that should have been validated up front
- Scope or phase boundaries that were too broad

If none, write: "No material weaknesses identified."

---

## 7. What We Will Sustain
List behaviors, decisions, or structures that worked and should be preserved.

Examples:
- Clear intent wording
- Effective phase boundaries
- Tooling or signals that helped

---

## 8. What We Will Improve
Concrete changes for next time.

Examples:
- Clarify a constraint in intent
- Add or remove a signal
- Adjust phase transition criteria
- Update policy or templates

Each item should answer:
> "What will we do differently *next time*?"

---

## 9. Ownership & Follow-Up
Who owns the follow-up, and by when?

- Owner:
- Action:
- Target date:

(Keep this short. This is not a task tracker.)

---

## Notes
- This AAR is about **learning**, not blame.
- Outcome quality does not determine decision quality.
- If an action was reasonable given intent and context, it is protected.

INTENT Template

Use this template to create new INTENT.md files. Copy the sections into the appropriate scope.

Purpose

  • < Why this scope exists. >

End State

  • < Conditions that define success; not feature lists. >

Constraints

  • < What must not happen. >

Tradeoffs

  • < Decisions already made (this over that). >

Risk tolerance

  • < How bold we can be. >

Escalation conditions

  • < When to pause or escalate. >

Verification steps

  • < Signals/metrics/commands that prove success. >

Activation / revalidation

  • < When should this intent start governing decisions? What must be true? >
  • < When should this intent stop governing decisions? What condition ends or supersedes it? >
  • < What should trigger a deliberate review/revalidation of this intent? >

Appendix

Inputs

  • < Upstream intents, policies, or resources that informed this intent. >

Related

  • < Nearby projects or docs worth linking. >
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment