← Insights·Leadership

Make Your Leaders Own the Plan, Not Just Accept the Number

Your leaders nodded. A nod is not a plan. What to settle before accepting their commitment, and what stays yours afterward.

By Ken Gavranovic · November 18, 2026

Picture the January leadership meeting. The target goes up on the slide. Everyone nods.

Now picture April. Same room. One leader is explaining why another team let them down. Another is raising a risk that was visible in January. And you’re spending the afternoon making decisions your leaders should have made.

Two habits erode ownership: “they didn’t deliver,” where another function’s miss ends the conversation, and “we all own it,” where a target belongs to everyone until someone has to act.

A number handed down can land as a demand people acknowledge without deciding how to deliver it. The nod may also be sincere. I've covered separately why silence is not agreement . This is about what you require after the nod.

You do not want your team to accept the number. You want them to own it.

I’ve been a CEO, and I’ve served as an EVP. I want both sides of this handoff held to a clear agreement. Everyone can recite the playbook. The handoff is where it gets done or lost.

The deal is simple: call it out now, or own it later. A known concern withheld during planning doesn’t erase responsibility when the number slips. Planning closes the initial negotiation; it doesn’t close the channel for bad news.

Here’s the practice I’d use: a way to decide whether a plan is ready to accept, and a way to manage against it once it is. Two caveats. It’s a starting point, not a tested protocol. And it can’t fix a plan that lacks the capability, capacity or strategy to succeed. Completed paperwork just makes that gap easier to miss. If your current process already covers this ground, use what follows to pressure-test it, not to replace it.

One owner per number, one definition per measure

Every number gets one primary owner, even when delivery is shared. Two leaders running a function together still name a primary for revenue and for each initiative. A result that needs sales, product and support still carries one name.

Shared means nobody. That’s the risk when “shared” becomes a substitute for naming who must coordinate delivery and answer for the result. Joint work is essential. Leaving its overall ownership unspecified is the problem.

Give each owner one to three measures, defined so two people would calculate them the same way: formula, reporting period, inclusions and exclusions, baseline, target and target date. Name who produces the figure separately from who owns the result. Finance may calculate the margin; the operating leader manages the choices that affect it.

Then give that leader usable authority and capacity. Specify which spending, staffing and delivery decisions they can make, and where they need an executive decision. An owner with a target and no say over the resources that move it has been handed a knot.

Before accepting the plan, put one primary name beside every number and check that the person can actually make the decisions the plan requires.

The plan goes up

Hand down the number with the reason it is this number: the market opportunity, the economics, the commitment behind it. Explain what is fixed and what remains open to challenge. Otherwise you’re asking the leader to defend reasoning you haven’t shared.

The leader comes back with a written plan, in their own words, not a restated version of the slide. It covers four things: the bridge from today’s run rate to the target; the two to four initiatives that will close the gap; one named owner for each; and what done looks like, with a date.

Require the arithmetic behind that bridge. When does each initiative start contributing? What assumption supports its expected effect? Are two initiatives claiming the same improvement? A list of worthwhile projects can still leave the revenue gap untouched.

Writing makes those choices inspectable, not correct. It won’t prove motivation or validate the assumptions, and it doesn’t matter much whether the goal was assigned or negotiated, since capable leaders commit to assigned targets and co-written plans can still be fantasy. The test is simpler: has the leader worked through delivery, and can they defend the choices?

Your slide with the leader’s name on it is not a plan. Send it back and ask them to explain the bridge, including the assumption they would test first.

Clear the dependencies before accepting the plan

Bring the leaders together for a clearing session, borrowing the idea of settlement: both sides check and confirm the same obligation before either relies on it.

Each leader brings a dependency register, a list of what they need, from whom, how much or what capacity, by when, and the status: agreed, still to discuss, or a decision for you. Include what the requester must supply before the provider can start and what counts as a completed delivery.

Each leader also brings the reciprocal list: what everyone else needs from them. Compare the two. A dependency appearing only in the requester’s plan hasn’t become the provider’s commitment.

A request to another function isn’t an agreement until that function’s leader confirms it. No signature needed; a dated reply in the shared record will do. What matters is that both leaders have committed, explicitly, to the same work by the same date. That’s what takes “they didn’t deliver” off the table in April.

Confirmation requires a capacity check. Have each provider review all incoming requests together, alongside their own work. Individually reasonable promises can compete for the same specialist or delivery slot. If the work won’t fit, decide what moves, what gets funded or which approach changes. Don’t collect confirmations over an unresolved shortage.

I’d start with a two-hour session for a prepared leadership team with a manageable register. Bring the requesting and providing leaders, with finance or operations helping check capacity. Larger unresolved sets need more preparation or another session.

Your job in the room is to decide the funding, staffing and priority conflicts the leaders cannot settle within their authority. Keep the discussion on delivery rather than casually reopening every target. But if the available capacity cannot support the number, face that decision before accepting the plan.

What leaves is a confirmed register for each leader, plus your recorded decisions. A critical gap needs a funded resolution, a different delivery approach or an explicit decision to accept the exposure with its consequences visible. A decision date alone doesn’t close it. If you proceed with an unconfirmed dependency, keep it labeled that way.

The clearing doesn’t stop dependencies from failing. It kills the blanket defense that someone else was supposed to handle it. When a miss comes up in April, there’s a record: who committed to what, by when, and what happened. The conversation moves from blame to facts.

A provider’s missed commitment belongs in the review by name and date. A confirmation establishes agreement, not deliverability, and a failed line doesn’t automatically explain the whole miss. The requester still owns monitoring, mitigation and timely escalation.

Book the clearing before accepting plans. Leave no critical request disguised as an agreement.

The risk window and the confidence line

Planning is the initial window for challenging the commitment with the risks you can see. Each leader lists what could stop the plan, its likely impact and likelihood, the warning trigger, the mitigation and its owner.

Then ask for two numbers: the result they would bet on and the stretch target you’ve asked for, with the assumptions separating them. That gap is the confidence line. A plan without one is a nod.

A bet number with nothing behind it is an opinion with a number attached, not a forecast. Ask what supports it: current demand, delivery history, who’s actually available, and which assumptions haven’t been tested. If the answers don’t support the stretch and you keep it as the target anyway, that can be the right call. Write down the gap between the bet and the stretch, and what you’re betting on to close it.

Run a premortem. Tell the team the date has passed and the plan has failed, and ask: what happened? Have everyone write down their reasons alone first, so the loudest or most senior voice doesn’t set the agenda. Then, for the risks that matter, ask two questions: what early signal would tell us this is happening, and what should we change now? It won’t catch everything, but it makes it safe to say the thing everyone was thinking.

Risks disclosed during planning become explicit company choices. For each material risk, record your decision: accept the exposure, fund mitigation, change the mix of work or adjust the target. Assign the follow-through. A risk list that changes no decision or preparation is just a longer plan.

Accepting the plan transfers ownership of execution, on the terms you both agreed. That cuts both ways. The leader owes you early warning when a risk appears or an assumption breaks. You owe them an honest reset when you change priorities, resources or scope. And a risk discovered in March belongs in March’s meeting, not saved for April, whether or not it was on January’s list.

When something was missed, ask what the leader knew in January, and what they could reasonably have found out with honest preparation. Not what everyone knows now. April’s outcome doesn’t make January’s uncertainty disappear. If it’s genuinely unclear whether they should have seen it, don’t assume bad faith. Deal with the risk, then fix the planning process so the next cycle catches it.

A genuine shock, one nobody could reasonably have seen coming, is yours to decide how to handle. The leader’s job is to act within their authority and bring you anything beyond it, fast. A risk they should have raised and didn’t is another matter. It explains the miss. It doesn’t excuse it.

Your part is to hear a bet number below the stretch without punishing the honesty behind it. Challenge weak assumptions, ask for better evidence and help close the gap. But don’t demand that the bet match the stretch as proof of commitment, or you’ll teach your leaders to tell you what you want to hear.

Before accepting the number, record the risk decisions and put the confidence line on the plan itself.

Report on it: everyone has a number

Then apply the same discipline one level down. Each of the leader’s direct reports gets one to three defined measures they can meaningfully influence, each with a calculation, reporting period and target. Show how their contribution connects to the leader’s result.

That connection often isn’t arithmetic. Sales bookings and services delivery hours can’t simply be added up into progress. And more activity doesn’t mean a better outcome. Choose measures that show whether the work is producing the business or customer result you intended.

Review team measures weekly and each leader’s plan monthly, using the dependency register and risk list. For outcomes that take longer to emerge, review useful earlier evidence without pretending the final result changes every Friday. Escalate time-sensitive problems between meetings.

Use a fixed report with the target, actual performance, current forecast and an on-track or off-track assessment supported by evidence. State what changed, the supported explanation and the next response. If the cause is uncertain, say so and assign the investigation.

Keep the target, forecast and actual distinct. The forecast changes with the evidence. The target changes through an explicit authorized decision, with the reason and date recorded. Review the plan against the number instead of quietly rewriting the number to match the result.

No material problem leaves the meeting without a next step, one named owner and a date to check back. That applies to you too: if the team is waiting on your decision, it goes on the list with your name next to it. And when you move resources, update the commitments and forecasts that depended on them. Don’t leave leaders reporting against assumptions you removed.

Watch quality and customer outcomes alongside the target. Meeting the number by postponing necessary work or passing costs to another function is a reason to examine the measures and incentives.

Put the report and review dates in place the week the plan is accepted.

Where it breaks in the room

Knowing the five parts is easy. Using them means interrupting the meeting at exactly the moment everyone wants to move on. Here’s where I’d expect it to break down, and what I’d do.

The unexplained target and the returned slide. If you handed down the number without the why, fix that first. You can’t fairly judge a plan built on context you never gave. If the leader hands your slide back with their name on it, ask for the decisions underneath: which work will produce the improvement, and why that work? Set a date for them to come back. If the reasoning is still missing the second time, the issue isn’t the slide. It’s preparation, understanding or capability, and each calls for a different conversation.

The co-owned target and the wish-list register. Name one primary owner. Then have each providing leader confirm their commitment out loud. The requester doesn’t get to speak for them. If a provider can’t commit, mark the line open and make the tradeoff yourself. Surfacing a shortage isn’t failure. Failure is the shortage leaving the room wearing an agreed label.

The empty risk window. No risks listed can mean three things: the plan really is low-risk, nobody looked hard, or people have learned that naming a concern sounds like weakness. You can’t tell which from the room. Ask leaders one at a time what they examined and what would change their forecast. A premortem will surface more risks, but it won’t explain the silence. Only those individual conversations will.

The punished forecast. A leader says the number they’d bet on is 90 percent of the stretch. If you punish them for it, everyone learns to hide the next gap. Your reaction to the first honest number is the policy. The rest is posters. Ask instead what would close the gap and what decision they need from you. And if you get it wrong, say so in the same room and reopen the discussion.

The activity alibi. Activity measures slip through because they’re easy to report. Test them with one question: what would count as failure even if the team hit the activity target? If the team finishes the work but the customer still can’t use it, redefine what “done” means and how you check it. Keep activity measures for running the work. Just don’t let them claim the result.

The monthly reopening. By midyear, the temptation is yours. A leader wants to reopen the number because delivery is hard. A slipping commitment deserves scrutiny, but it isn’t automatically a personal failure. Ask what changed in the plan and what they recommend. If the target genuinely no longer makes sense, change it openly, with the right authority in the room. Otherwise, hold the target and agree on the recovery.

Throughout all of this, reward the behavior you want. Give visible credit to whoever flags an overcommitment early enough for the company to choose differently. If praise only goes to people who report green, your written rules have competition.

None of this is hard to describe. The hard part is running it with a number at stake: making the uncomfortable call, then checking whether it changed anything. I’ve written about accountability that examines reasoning as well as results. These reviews are where that standard holds or breaks. Get them right, and April’s meeting looks different: fewer explanations, fewer surprises.

What changes for you

The aim is fewer routine decisions returning to your desk and earlier visibility into misses. At the second monthly review, check whether problems are arriving sooner, whether owners are acting and whether your own unresolved decisions are delaying them. Early on, more escalation can be a useful correction to silence. Fewer escalations alone prove very little.

You still own the reason for the number, company-level resource conflicts, accepted risks and authorized target changes. You also owe owners usable authority and a timely answer when they reach its limits. The handoff gives you a clearer management job. It doesn’t remove you from it.

This week, give every leader a named date for the plan, dependency register, risk list with its confidence line and team measures. Book the clearing session and the first monthly review before those plans come back.

Take three questions into the room: Which number would you bet on, and what separates it from the stretch? Which dependencies have the provider’s written confirmation? Which assumption, if it proved wrong, would make us change the plan?

Call it out now, or own it later.

Frequently asked questions

How do I get my leaders to own the plan behind their numbers instead of just accepting the target?

Make ownership a condition of acceptance: hand the number down with the reason it is this number and with what is fixed and what remains open to challenge, then require one primary owner on every number, a written plan in the leader's own words, written confirmation of every cross-team dependency, and a risk list recording the result the leader would bet on beside the stretch target you asked for. Once you accept on those terms, execution belongs to the leader: they owe you early warning when a risk appears or an assumption breaks, and you owe them usable authority and an honest reset when you change priorities, resources or scope. Treat the practice as a starting point, not a tested protocol, and know it can't fix a plan that lacks the capability, capacity or strategy to succeed.

Who should own a number when the work is shared across teams?

Every number gets one primary owner even when delivery is shared, so two leaders running a function together still name a primary for revenue and for each initiative, and a result that needs sales, product and support still carries one name. Give each owner one to three measures defined so two people would calculate them the same way, covering the formula, reporting period, inclusions and exclusions, baseline, target and target date, and name who produces the figure separately from who owns the result. Then give the owner usable authority and capacity by spelling out which spending, staffing and delivery decisions they can make and where they need an executive decision, because an owner with a target and no say over the resources that move it has been handed a knot.

What should a leader's written plan include before I accept it?

Four things: the bridge from today's run rate to the target, the two to four initiatives that will close the gap, one named owner for each initiative, and what done looks like, with a date. Require the arithmetic behind the bridge too, meaning when each initiative starts contributing, what assumption supports its expected effect, and whether two initiatives are claiming the same improvement, because a list of worthwhile projects can still leave the revenue gap untouched. The plan has to be in the leader's own words rather than a restated version of your slide, so if your slide comes back with their name on it, send it back and ask them to explain the bridge, starting with the assumption they would test first.

How do I confirm cross-team dependencies before accepting the plan?

Bring the leaders together before you accept anything, beginning with a two-hour session for a prepared leadership team, and have each leader bring a dependency register listing what they need, from whom, how much or what capacity, by when, and the status as agreed, still to discuss, or a decision for you, plus the reciprocal list of what everyone else needs from them. A dependency that shows up only in the requester's list hasn't become the provider's commitment; it becomes one only when the providing leader confirms it, which can be a dated reply in the shared record rather than a signature. Have each provider check all incoming requests against their own capacity before confirming, since individually reasonable promises can compete for the same specialist or delivery slot, and when the work won't fit, you decide what moves, what gets funded or which approach changes, with any dependency you proceed with unconfirmed kept labeled that way.

How do I get my leaders to be honest about risks and the number they'd really bet on?

During planning, have each leader list what could stop the plan, its likely impact and likelihood, the warning trigger, the mitigation and its owner, and ask them for two numbers, the result they would bet on and the stretch target you asked for, with the assumptions separating them. That gap is the confidence line, and a plan without one is a nod, so test any bet number by asking what supports it, things like current demand, delivery history, who's actually available and which assumptions haven't been tested. If the answers don't support the stretch and you keep it as the target anyway, that can be the right call, but write down the gap and what you're betting on to close it, and don't punish the honesty, because your reaction to the first honest number is the policy.

How do I run a premortem with my leadership team?

Tell the team the date has passed and the plan has failed, and ask what happened, having everyone write down their reasons alone first so the loudest or most senior voice doesn't set the agenda. Then, for the risks that matter, ask what early signal would tell you this is happening and what you should change now; it won't catch everything, but it makes it safe to say the thing everyone was thinking. Follow it by recording your decision for each material risk, whether to accept the exposure, fund mitigation, change the mix of work or adjust the target, with the follow-through assigned, because a risk list that changes no decision or preparation is just a longer plan.

What should reporting and reviews look like once the plan is accepted?

Everyone has a number: each of the leader's direct reports gets one to three defined measures they can meaningfully influence, each with a calculation, reporting period and target, and you review those team measures weekly and each leader's plan monthly using the dependency register and the risk list, escalating time-sensitive problems between meetings. Use a fixed report stating the target, actual performance, the current forecast and an on-track or off-track assessment supported by evidence, and keep the target, forecast and actual distinct, since the forecast changes with the evidence while the target changes only through an explicit authorized decision with the reason and date recorded. No material problem leaves the meeting without a next step, one named owner and a date to check back, and that includes your own decisions when the team is waiting on you.

When a number is missed, how do I tell whether the leader should have seen it coming?

Ask what the leader knew in January and what they could reasonably have found out with honest preparation, not what everyone knows now, because April's outcome doesn't make January's uncertainty disappear. If it's genuinely unclear whether they should have seen it, don't assume bad faith; deal with the risk, then fix the planning process so the next cycle catches it. A genuine shock nobody could reasonably have seen coming is yours to decide how to handle, while a risk they should have raised and didn't explains the miss but doesn't excuse it.

Keep reading

Work with KenMore insights