Christopher Reep | LEAN Culture Advisory

  Step 11: Build a review cadence A real X-Matrix lives in management review. Typical cadence: monthly: review annual objectives, initiative progress, KPI movement quarterly: assess strategic risks and adjust priorities annually: reflect, close gaps, reset next-year Hoshin During reviews, ask: Are the metrics moving? Are initiatives on track? Are assumptions still valid? Do we need countermeasures?

  Step 10: Break the X-Matrix into deployment plans The X-Matrix is not the detailed plan. It is the strategic map. Each initiative should now translate into: milestones owners due dates department plans monthly review points PDCA cycles Think of the X-Matrix as the control tower, not the airplane.

  Step 9: Run catchball Do not finalize the X-Matrix in a conference room and hand it down. Use catchball : leadership proposes the objectives departments respond with reality, constraints, and ideas revisions are made ownership becomes negotiated and real Questions to ask during catchball: Can this target actually be achieved? What support is needed? What conflicts with other priorities? What is missing? What initiative would truly move this metric? This is how the matrix becomes operational instead of ceremonial.

  Step 8: Review the matrix for overload A bad X-Matrix is crowded, bloated, and politically negotiated. Signs of overload: more than 5 breakthrough objectives more than 8 annual objectives too many initiatives every box connected to every other box vague wording no clear ownership metrics that cannot be measured monthly A good X-Matrix feels selective. You should be able to look at it and say: These are the few things that matter most this year.

  Step 7: Draw the relationship lines or symbols Now the matrix becomes useful. You connect the elements to show alignment: Which annual objectives support which breakthrough objectives Which initiatives support which annual objectives Which metrics evaluate which initiatives/objectives Most teams use symbols such as: strong relationship = filled circle medium relationship = open circle weak relationship = triangle Use whatever notation your team understands, but be consistent. This step is where hard conversations happen. Example: If an initiative does not clearly support an annual objective, ask: Why is it here? If an annual objective does not support a breakthrough objective, ask: Should it really be a Hoshin priority?

  Step 6: Assign owners Ownership is often shown along the bottom section too, or adjacent to the metrics and initiatives depending on the format. Every annual objective and every major initiative should have a named owner. Not: Operations Maintenance Leadership team But: Plant Manager CI Manager Maintenance Manager Value Stream Leader If ownership is shared by everyone, it usually belongs to no one.

  Step 5: Define the success metrics These usually go at the bottom of the X-Matrix. These answer: How will we know whether the objectives and initiatives are working? Examples: Lead time OEE Changeover time OTIF Scrap rate First pass yield Schedule attainment PM completion rate Safety incident rate Each metric should have: a definition current baseline target review frequency Try to avoid vanity metrics. Use measures that show actual operational movement.