Japanese KMI ➡️ KPI ➡️ KAI in Practice
In many OpEx programs, performance management quickly becomes a jungle of disconnected numbers. Japanese management philosophy offers a very simple and powerful cascade that solves this: KMI ➡️ KPI ➡️ KAI
🧭 KMI (Key Management Indicator): The “WHY”
KMIs are the few strategic indicators owned by top management. They describe what really matters for business over the term such as:
- Safety, Health & Environment
- Customer Engagement & Quality
- People & Culture
- Asset Utilization
- Cost & Profitability
Think of KMIs as the North Stars on your dashboard – there should be only a few.
📊 KPI (Key Performance Indicator): The “WHAT”
KPIs translate each KMI into a measurable process metric. One KMI is usually supported by several KPIs, but the total set should still be lean (10–12 max for a site). Examples:
- Safety, Health & Environment: TRIR, Days Without Incident, Emissions
- Asset Utilization: OEE, Throughput, Capacity Utilization
- Customer Engagement & Quality: RFT, Claims, OTIF
- Cost & Productivity: Unit Cost, Inventory Turnover, COPQ, Energy Consumption
- People & Culture: eNPS, Absenteeism, Turnover, Suggestions
⚙️ KAI (Key Activity Indicator): The “HOW”
KAIs are specific actions at the shop-floor level that move the KPIs. They are concrete and small enough to be owned by a team.
Goal 1: To improve OEE, KAIs could be:
- 🔻 Decrease setup time
- 🔻 Decrease # of Breakdowns
- 🔺 Increase MTBF
- 🔻 Decrease # of Short stops
Goal 2: To improve TRIR, KAIs could be:
- 🔺 Increase # of Observations
- 🔺 Increase # of Safety audits
- 🔺 Increase PPE compliance %
Goal 3: To improve Suggestions, KAIs could be:
- 🔺 Increase Ideas/FTE
- 🔺 Increase Implementation %
- 🔻 Decrease Idea cycle days
The KAI key is ‘Activity’, not a lagging result.
🔗 Why KMI ➡️ KPI ➡️ KAI Cascade?
- Aligns strategy to Gemba: Everyone can see how today’s kaizen, suggestion, or project contributes all the way up to Safety, Customer, Cost, or People objectives.
- Clarifies target setting: You start with a few KMIs, translate them into focused KPIs, then define KAIs that teams can influence every day.
- Enables performance management, not just reporting: Reviews can follow a simple logic: KMI trend ↓ 📉 ➡️ which KPI is off? ➡️ which KAI needs to improve/change?
- Drives Continuous Improvement: KAIs become a natural funnel for Kaizens. If a KPI is red, teams propose and track more Kaizens until it turns green.
🛠️ How to Implement
- Step 1: Start by agreeing on 4–5 KMIs that truly define success for your site.
- Step 2: Limit yourself to 10–15 KPIs, clearly owned, each mapped to one KMI.
- Step 3: For each KPI, define 2–3 KAIs, specific activities you want teams to execute.
- Step 4: Review regularly KMI ➡️ KPI ➡️ KAI on the same page, as in a visual, so everyone sees the connection.
When you get this right, you create a clear line of sight: KAI improves KPI ➡️ KPI improves KMI ➡️ Every team, every shift, every individual, every improvement contributes directly to the company’s success.
