How to get senior leadership to back an idea

Senior leaders rarely back ideas; they back reduced uncertainty. To get a yes, link your idea to a problem they already own, show evidence from a small test rather than a big plan, ask for a specific, limited commitment, and talk to the right people before the meeting where the decision is made. Most good ideas are turned down not because they're wrong but because they arrive as large, vague requests with no proof.

This piece is for the person with the idea. If you're the leader trying to make ideas easier to bring forward, read innovation culture: what it is, and how leaders actually build it.

Why good ideas get turned down

Before the steps, it helps to see the pitch from the other side of the table. A senior leader hearing your idea is thinking about:

• Their priorities. They have a short list of things they're accountable for this year. Anything not on it competes for scarce attention.
• Risk to them. If this goes wrong, whose name is on it? In public organisations, the downside often feels bigger than the upside.
• Cost of saying yes. Not only money. Political capital, management time, and the precedent of approving something unproven.
• Who else supports it. Leaders look for signals that peers and the people who'd implement it are on board.

Researchers Jane Dutton and Susan Ashford, in a 1993 paper on "issue selling", described how middle managers raise issues to top management and why framing, timing and relationships matter as much as the merits. In practice: the same idea can be rejected in one meeting and approved in another, depending on how it's packaged.

How to get backing: eight steps

1. Start from their problem, not your idea. Find the problem your idea solves that a senior leader already cares about. Check the strategy, the annual plan, the KPIs they report on, or what they've said recently in town halls. Then lead with that: "You've said cutting repeat customer contacts is a priority this year. I have a way to test one cause of it." If you can't connect your idea to any leadership priority, that's important information. Either reframe it or wait.

2. Map who matters. Decisions are rarely made by one person in one meeting. Use a stakeholder map to identify the decision-maker, the people they listen to, the people who'd have to implement it and the people who might quietly object. The finance partner and the operations head often matter as much as the sponsor.

3. Shrink the ask. "Approve a new service" is hard to say yes to. "Let us test it for four weeks in one branch with existing staff" is easy. Break your idea into the smallest step that would produce useful evidence, and ask only for that. A small ask also reduces the personal risk for the person approving it.

4. Bring evidence, even a little. One test with real users beats ten slides of projections. Before you pitch, run the cheapest test you can within your own authority: ten interviews, a manual version of the service for a few people (a concierge test), or a paper prototype. Frame what you're testing as a hypothesis. Then you're not asking leadership to believe you; you're showing them something. (More on this in how to test an idea before you build it.)

5. Make the value case simple. Leaders need to know what changes if this works, for whom, and roughly how much it's worth. A value case on one page is enough: the problem, the cost of the problem today, what the idea changes, what it would take, and what you'll know after the next step. Don't inflate the numbers. Senior people have seen many optimistic projections and discount them heavily.

6. Name the risks before they do. Run a short premortem with a colleague: imagine the idea has failed in a year and list why. Address the top two or three in your pitch. Raising risks yourself builds credibility, and it takes away the easiest reason to say no.

7. Pre-wire the decision. Don't let the formal meeting be the first time key people hear the idea. Have short individual conversations with the sponsor and the most likely objectors beforehand. Ask for their concerns and adjust. In many organisations, and particularly in hierarchical settings where open disagreement in a senior meeting is uncomfortable, the real decision is shaped in these conversations. (See innovation in hierarchical cultures.)

8. Ask for a clear decision, with a date. End with a specific request: "Can we have approval to run the four-week test starting on the first of next month, with a review on the fifth week?" Agree in advance what result would justify the next step and what would mean stopping. If the answer is no, ask what evidence would change it. A clear no with a reason is more useful than a polite "let's revisit".

When you present, lead with the answer. Barbara Minto's Pyramid Principle, developed from her work at McKinsey, is the standard reference for this: state your recommendation first, then the supporting reasons, then the detail. Senior people often decide in the first few minutes.

An example

Illustrative. A service designer at a city council in New Zealand believes residents would report more potholes and street faults if they could do it by text message rather than through the council's online form. Her first attempt is a ten-slide proposal for a new reporting channel. It's politely deferred.

She tries again. She notices that the infrastructure director's annual targets include faster repair times, and that slow reporting delays repairs. She sets up a temporary number in one ward for three weeks, with a colleague manually logging texts into the existing system. Residents send in more reports than the online form received from that ward over the same period, with photos.

Before the next leadership meeting, she meets the director's deputy and the head of customer services, who worries about staff workload. She adds a cap on the pilot's volume. In the meeting, she opens with one sentence: "A three-week test in one ward suggests text reporting gets more faults reported, and I'd like approval to extend it to three wards for two months." She gets it, with a clear review date.

Do's and don'ts

Do

• Connect your idea to a priority leadership already owns.
• Ask for the smallest step that produces evidence.
• Test something within your own authority before you pitch.
• Raise the main risks yourself.
• Talk to key people individually before the formal meeting.

Don't

• Lead with the solution and a long backstory.
• Ask for a full budget for an untested idea.
• Inflate the benefits. It costs you credibility for the next idea too.
• Surprise a senior person in front of their peers.
• Accept a vague "let's discuss later". Ask what would change the answer.

Questions people ask

How do you pitch an idea to senior management? Start with the problem they care about, give your recommendation in one sentence, show the evidence from a small test, name the risks and how you'll manage them, and ask for a specific, limited decision. Keep it to a few minutes and a page or two.

What if leadership says no? Ask what evidence would change their view and whether a smaller test would be acceptable. A no is often a "not like this" or "not yet". If the idea doesn't connect to any current priority, it may be better to wait for the right moment than to keep pushing.

How do I get buy-in when I'm not senior? Build allies first: your own manager, the people who'd implement it, and someone close to the decision-maker. Let your manager share the credit and the pitch. Middle managers can be strong allies if they see something in it for their own goals; see middle managers: the quiet blockers, and how to win them.

Where to go next

The method guides that help most are the stakeholder map for finding who matters, the value case for a one-page argument, the concierge test for cheap evidence, and the premortem for naming risks first. More in the method guides.