A3 Problem Analysis Apply A3 problem solving format for comprehensive, single page problem documentation and resolution planning. Description Structured one page analysis format covering: Background, Current Condition, Goal, Root Cause Analysis, Countermeasures, Implementation Plan, and Follow up. Named after A3 paper size; emphasizes concise, complete documentation. Usage /analyse problem [problem description] Variables PROBLEM: Issue to analyze (default: prompt for input) OUTPUT FORMAT: markdown or text (default: markdown) Steps 1. Background : Why this problem matters (context, business impact) 2. Current Condition : What's happening now (data, metrics, examples) 3. Goal/Target : What success looks like (specific, measurable) 4. Root Cause Analysis : Why problem exists (use 5 Whys or Fishbone) 5. Countermeasures : Proposed solutions addressing root causes 6. Implementation Plan : Who, what, when, how 7. Follow up : How to verify success and prevent recurrence A3 Template Examples Example 1: Database Connection Pool Exhaustion Example 2: Security Vulnerability in Production Notes A3 forces concise, complete thinking (fits on one page) Use data and facts, not opinions or blame Root cause analysis is critical—use /why or /cause and effect Countermeasures must address root causes, not symptoms Implementation plan needs clear ownership and timelines Follow up ensures sustainable improvement A3 becomes historical record for organizational learning Update A3 as situation evolves (living document until closed) Consider A3 for: incidents, recurring issues, major improvements Overkill for: small bugs, one line fixes, trivial issues

analyse-problem