Getting Executive Buy-In for Improvement Projects

Improvement projects rarely die in the Analyze phase. They die in conference rooms before they begin, when a sound idea arrives dressed as enthusiasm and meets an executive who has heard enthusiasm before. The proposal is earnest, the problem is real, and the answer is a polite version of no — because nobody translated the project into the only language executives are paid to speak: resources, risk, and return.

This is not cynicism about leadership. Executives allocate scarce things — people’s hours, budget, political capital, their own attention — among more requests than they can possibly fund. A proposal that asks for those things owes them a business case. The good news is that a Six Sigma project, honestly framed, makes an unusually strong one. The method practically writes it for you, if you let it.

Translate defects into the currency of the business

Inside the team, the problem is a defect rate, a cycle time, a first-pass yield. In the executive’s office, those numbers must become cost, capacity, risk, or customer impact — the currencies that already appear on leadership agendas. Rework is labor purchased twice. Waiting is capacity paid for and not used. Errors that reach customers are churn risk and reputation risk. You do not need invented precision to make the translation; ranges and honest arithmetic outperform theatrical exactness every time. The point is that the executive should never have to convert your units into theirs. Do the conversion before you walk in.

Bring a baseline, not a promise

The weakest proposals lead with projected savings. The strongest lead with what already exists: a small sample of real data. Pull twenty recent invoices, orders, or cases and walk their actual history through the process. Even a modest baseline changes the conversation from speculation to fact — and it demonstrates the method before asking anyone to fund it. Then be candid about uncertainty. State what you know, what you do not, and that the Measure phase exists precisely to replace estimates with evidence. Executives extend more trust to people who show their error bars than to people who show none.

Scope a project an executive can say yes to

The price of yes rises with scope. A proposal to transform quality across the company requires faith; a proposal to cut invoice-approval errors in one department requires only modest attention. Bound the project tightly — one process, one defect, a defined start and end, a timeline measured in weeks rather than quarters. A small, finished project is worth more than a large, ambitious one that never closes, because the first yes is really a purchase of evidence. Deliver once and the second yes is cheaper. That is how real programs get built: one credible project at a time.

Ask for specific commitments, not general support

“We have leadership support” is the most common epitaph on failed projects. Support that costs nothing means nothing. When you ask for sponsorship, name the commitments precisely:

1. 01Named people, with hours — team members released for a defined slice of their week, agreed with their managers
2. 02Access — data, systems, and permission to observe the process where it actually runs
3. 03Authority to pilot — the right to test changes within an agreed scope without a second approval cycle
4. 04A standing review — a short, recurring slot on the sponsor’s calendar for phase-gate decisions
5. 05Public ownership — the sponsor presents the results upward as their own accountability, not as a favor to the team

An executive who agrees to these five things is a sponsor. An executive who offers encouragement instead has told you, usefully and early, that the project is not yet ready — or that you are asking the wrong executive.

Retire the objections before they are raised

Three objections arrive so reliably that showing up without answers is negligent. “We tried this before and it did not stick” — usually true, and usually because the effort had no Control phase; explain, specifically, what will be different this time. “We do not have time” — the time is already being spent, invisibly, on rework and firefighting; the project proposes spending some of it on the cure instead of the symptom. “This is manufacturing methodology” — the method was born at Motorola in 1986, but it moved into hospitals, banks, insurers, and back offices decades ago, because every organization runs on processes and every process produces defects.

After the yes, report in the currency you sold

Buy-in is not a transaction; it is a subscription, renewed at every review. Report progress in the same business terms the proposal used. Keep reviews short and decision-focused. Surface bad news early — a sponsor surprised in month three is a sponsor lost. And when the project closes, hand the sponsor the win in public. Executives fund what makes them credible. A leader who has personally banked one improvement result becomes the easiest yes in the building for the next one.

Executives do not buy methods. They buy outcomes that happen to have a method attached.

Learn to build the case properly

Chartering — the problem statement, the scope, the business case, the sponsor’s role — is a core skill of our Green Belt program: 35 hours built around a full simulated project, with a 100-question proctored exam, one free retake, and lifetime access for $299. And if the executives themselves are the obstacle, there is a quieter tactic. Our White Belt program is free, takes about six hours, and ends in a 30-question exam. Leaders who understand the method stop needing to be sold on it. They start asking why more projects are not already underway.