How to Build a Measurable Operational Improvement Plan Your Board Will Accept

The request was short: “Bring a measurable operational improvement plan to the next meeting.” The owners, the board or the private equity sponsor want to see which numbers will move, by how much, by when, and who is accountable. The meeting is on the calendar.

You know where many of the problems are. You may even have a list of initiatives already. But a list will not survive the questions that are coming: Why these projects? How do they add up to the target? What if one of them slips? Who owns each one? How will we know it is working?

This guide explains how to build a plan that answers those questions — and, just as importantly, how to structure it so it actually gets executed after the meeting.

What owners and boards are really asking for

Behind the request are usually four expectations:

• Clarity — a short list of priorities, not everything that could be improved
• Linkage — a clear line from each project to the financial and operational outcomes they care about
• Credibility — numbers built on real baselines, with assumptions stated
• Ownership and cadence — a named owner for every result and a regular review rhythm

An operational improvement plan is not a strategic plan. The strategic plan says where the business is going. The operational improvement plan says which processes will change, which metrics will move, by how much, and who owns each result.

Step 1: Agree the outcomes that matter

Start by confirming the three to five business outcomes the owners care most about. Common ones include:

• Gross margin or EBITDA improvement
• Cash and working capital (inventory, lead time)
• On-time delivery and customer performance
• Capacity to support growth
• Quality and cost of poor quality
• Safety performance

Resist the temptation to include everything. Each outcome added dilutes focus and resources. If the owners’ priorities are unclear, ask directly — guessing wrong is expensive.

Step 2: Baseline with numbers finance will stand behind

Every target needs a baseline, and every baseline needs to be credible. Work with finance to confirm the current values, the data sources and the definitions. If the baseline for on-time delivery is disputed, the target will be too. This step often surfaces data quality problems — better to find them now than in front of the board.

Step 3: Assess where the improvement will come from

A structured operational assessment identifies the biggest opportunities against each outcome. Typical sources include constraint capacity and flow (for delivery and growth), the hidden factory of scrap, rework, premium freight and recovery overtime (for margin), inventory and lead time (for cash), and maintenance reliability (for capacity and cost).

Our guides on quantifying the hidden factory and diagnosing late deliveries describe two of the most common assessment areas in more detail.

Step 4: Use Hoshin Kanri to connect it all

Hoshin Kanri, also called strategy deployment or policy deployment, is the lean method for aligning an organization’s improvement effort with its most important objectives. Its most recognizable tool is the X-matrix, a single page that connects:

• Breakthrough objectives — the multi-year outcomes (for example, “become the on-time leader in our segment”)
• Annual objectives — this year’s measurable targets that move toward them
• Improvement priorities — the specific projects and initiatives
• Metrics — how progress will be measured
• Owners — who is accountable for each priority

The X-matrix forces two useful disciplines. First, every project must connect to an objective — if it does not, it probably should not be on the list. Second, the limited space forces trade-offs, which is exactly what boards want to see.

Hoshin also includes catchball — a back-and-forth process in which leaders at each level discuss targets and resources before committing. Plans developed with catchball are more realistic and more owned than plans handed down.

Step 5: Build a project portfolio sized to scope

Under the X-matrix sits the project portfolio. Each improvement priority is broken into projects, and each project is matched to the right method:

Scope	Method	Typical use in the plan
Focused problem, clear owner	A3 problem solving	Quick wins, specific losses
Defined area, flow or layout	Kaizen event	Constraint capacity, changeover, office flow
Chronic variation, complex causes	Six Sigma / DMAIC	Scrap, yield, process capability
End-to-end redesign	Value stream program	Lead time, inventory, multi-area change

A balanced portfolio includes some quick wins to build momentum and credibility, alongside larger projects that deliver the bulk of the value. Sequence projects so that resources — especially key people — are not overloaded. See choosing between A3, Kaizen and Six Sigma for more on matching method to scope.

Step 6: Build the savings bridge

The savings bridge is the page that answers “how does this add up?” It starts with the baseline, shows the contribution of each project (or group of projects), and ends at the committed target. It should show:

• The estimated contribution of each project, with its assumptions
• The timing — when each contribution is expected to begin
• A distinction between hard savings and cost avoidance or capacity
• A confidence level or risk rating for each item

A good bridge includes some margin for slippage. Boards generally prefer a realistic plan with a buffer over an optimistic one that depends on everything going right.

Step 7: Present it clearly

For the meeting itself, keep it simple. A typical structure: the outcomes and baselines; the X-matrix; the savings bridge; the first-wave projects with owners and dates; the review cadence; and the key risks and how they will be managed. Anticipate the hardest questions and address them directly.

Step 8: Execute with a monthly review cadence

A plan that is presented and then filed will be remembered for the wrong reasons at the next meeting. Execution depends on a regular rhythm:

• Weekly — project owners review progress and obstacles with their teams
• Monthly — the leadership team reviews each priority against plan, using the X-matrix and bridge; off-track items get countermeasures, not just explanations
• Quarterly — verified results are reported to the owners or board, and the portfolio is adjusted
• Annually — the plan is refreshed and the next wave is built

Verified results are essential. Each project’s savings should be confirmed with finance using agreed rules before they are counted on the bridge.

Common mistakes

• Too many priorities, so nothing gets enough resources
• Targets without baselines, or baselines finance disputes
• Projects that do not connect to an outcome
• A bridge with no allowance for slippage
• No review cadence after the meeting
• Counting savings before they are verified

Where QMSLean fits — and where our sister companies do

QMSLean owns the operational side: the assessment, the X-matrix, the project portfolio, the savings bridge and the execution support. For board governance, acquisitions or fractional executive leadership, our sister company ConsultFactor is the right partner. If the board is asking about supplier risk, SupplySourceSync handles that side.

See our situation page: “Our owners or board want a measurable improvement plan by the next meeting.” Related reading: the ROI of Lean Six Sigma.

Tell us what’s going on

Have a plan due? Describe what the owners are asking for and a Lean practitioner will reply with how we would approach it. Request a Situation Review, try the free ROI Calculator, or contact us at [email protected].