Hoshin Kanri
Hoshin Kanri depends on honest feasibility answers and quick countermeasures. With aangine, catchball and reviews work from a live plan of team capacity and budget, so each level can test what it can really commit to.
The planning gap
Hoshin Kanri asks for very few breakthrough objectives, chosen to close the gap between where the organization is and where it needs to be. That discipline is its strength. The pressure comes one level down. Breakthrough objectives become annual objectives, annual objectives become improvement priorities with owners, and the same engineering, quality and IT teams start to appear under every one of them.
Catchball is meant to test that. A draft objective goes down a level, the team asks whether it can be done, with what and by when, and the answer goes back up. Without a shared view of capacity, that answer rests on judgment alone. Teams say they are stretched, and nobody can say how stretched, or what would have to give.
Reviews meet the same gap. When rows on the bowling chart stay red, PDCA says act, and a countermeasure usually needs people or money already committed elsewhere. The X-matrix shows which priority serves which objective, but not time and load. Reworking the plan to test a countermeasure can take until the next review.
How aangine helps
Breakthrough objectives, annual objectives and improvement priorities can map onto aangine’s strategy hierarchy, above the projects that deliver them. Your X-matrix, A3s and bowling charts stay where they are; aangine doesn’t draw them. It plans what sits behind them.
Put each draft annual objective and its improvement projects into the plan, with effort by team or skill. Every level throws and catches against the same live plan, and each team sees its own load, so the answer that comes back up rests on facts.
Operations work is planned next to improvement projects for every team and every period. Leaders see early whether the breakthroughs really fit alongside the work that keeps the business running, before the hoshin is agreed rather than after.
Model alternative drafts of the hoshin as scenarios and compare them side by side on capacity, budget and timing. Ask why an objective doesn’t fit and see the constraint. Lock what is agreed, so later changes don’t quietly move it.
Test a countermeasure during the review: add effort, move a team or pull a project forward, and replan in one click. Dependencies, deadlines and locked work hold, and the drill-down shows which objective lost out and why.
In practice
Some rows on the bowling chart have stayed red for consecutive reviews. The review surfaced the gap early, as it should. The next question is what closing it would cost.
Actuals come from your PPM tool, so the plan-versus-actual view is current rather than reconstructed, and shows where effort really went.
Add the extra effort the red rows need, move a team toward them or pull an improvement project forward in the plan.
The plan honors dependencies, deadlines and locked commitments, and shows which projects moved to make room and which team ran out.
Leaders agree on the countermeasure in the same review. The approved plan goes back to the tools where teams work, ready for the next PDCA cycle.
How aangine works
aangine is the decision layer above the tools you already use. No rip & replace: it imports your plans, replans them in one click and pushes the approved plan back.
The result: faster, clearer decisions when it matters most.
What our customers report in their case studies. Read the customer results
Keep exploring
Framework and method names are used to identify them only. aangine and Continuous Software are not affiliated with, or endorsed by, the owners of these frameworks and methods.
Book a demo
Book a demo and bring your current hoshin: breakthrough objectives, annual objectives and improvement priorities. We’ll talk through your next catchball round and test it against real capacity.
