Smart Analysis Intelligently select and apply the most appropriate Kaizen analysis technique based on what you're analyzing. Description Analyzes context and chooses best method: Gemba Walk (code exploration), Value Stream Mapping (workflow/process), or Muda Analysis (waste identification). Guides you through the selected technique. Usage /analyse [target description] Examples: /analyse authentication implementation /analyse deployment workflow /analyse codebase for inefficiencies Variables TARGET: What to analyze (default: prompt for input) METHOD: Override auto selection (gemba, vsm, muda) Method Selection Logic Gemba Walk → When analyzing: Code implementation (how feature actually works) Gap between documentation and reality Understanding unfamiliar codebase areas Actual vs. assumed architecture Value Stream Mapping → When analyzing: Workflows and processes (CI/CD, deployment, development) Bottlenecks in multi stage pipelines Handoffs between teams/systems Time spent in each process stage Muda (Waste Analysis) → When analyzing: Code quality and efficiency Technical debt Over engineering or duplication Resource utilization Steps 1. Understand what's being analyzed 2. Determine best method (or use specified method) 3. Explain why this method fits 4. Guide through the analysis 5. Present findings with actionable insights Method 1: Gemba Walk "Go and see" the actual code to understand reality vs. assumptions. When to Use Understanding how feature actually works Code archaeology (legacy systems) Finding gaps between docs and implementation Exploring unfamiliar areas before changes Process 1. Define scope : What code area to explore 2. State assumptions : What you think it does 3. Observe reality : Read actual code 4. Document findings : Entry points Actual data flow Surprises (differs from assumptions) Hidden dependencies Undocumented behavior 5. Identify gaps : Documentation vs. reality 6. Recommend : Update docs, refactor, or accept Example: Authentication System Gemba Walk Example: CI/CD Pipeline Gemba Walk Method 2: Value Stream Mapping Map workflow stages, measure time/waste, identify bottlenecks. When to Use Process optimization (CI/CD, deployment, code review) Understanding multi stage workflows Finding delays and handoffs Improving cycle time Process 1. Identify start and end : Where process begins and ends 2. Map all steps : Including waiting/handoff time 3. Measure each step : Processing time (work happening) Waiting time (idle, blocked) Who/what performs step 4. Calculate metrics : Total lead time Value add time vs. waste time % efficiency (value add / total time) 5. Identify bottlenecks : Longest steps, most waiting 6. Design future state : Optimized flow 7. Plan improvements : How to achieve future state Example: Feature Development Value Stream Map Example: Incident Response Value Stream Map Method 3: Muda (Waste Analysis) Identify seven types of waste in code and development processes. When to Use Code quality audits Technical debt assessment Process efficiency improvements Identifying over engineering The 7 Types of Waste (Applied to Software) 1. Overproduction : Building more than needed Features no one uses Overly complex solutions Premature optimization Unnecessary abstractions 2. Waiting : Idle time Build/test/deploy time Code review delays Waiting for dependencies Blocked by other teams 3. Transportation : Moving things around Unnecessary data transformations API layers with no value add Copying data between systems Repeated serialization/deserialization 4. Over processing : Doing more than necessary Excessive logging Redundant validations Over normalized databases Unnecessary computation 5. Inventory : Work in progress Unmerged branches Half finished features Untriaged bugs Undeployed code 6. Motion : Unnecessary movement Context switching Meetings without purpose Manual deployments Repetitive tasks 7. Defects : Rework and bugs Production bugs Technical debt Flaky tests Incomplete features Process 1. Define scope : Codebase area or process 2. Examine for each waste type 3. Quantify impact (time, complexity, cost) 4. Prioritize by impact 5. Propose elimination strategies Example: API Codebase Waste Analysis Notes Method selection is contextual—choose what fits best Can combine methods (Gemba Walk → Muda Analysis) Start with Gemba Walk when unfamiliar with area Use VSM for process optimization Use Muda for efficiency and cleanup All methods should lead to actionable improvements Document findings for organizational learning Consider using /analyse problem (A3) for comprehensive documentation of findings