Should I pitch to my manager first or bring the idea straight to a bigger meeting?

Manager first, almost always — ambushing your own manager in front of theirs converts a potential sponsor into an opponent in one move. The exception is organisations with a designed route for ideas (an innovation forum, a suggestion process with teeth); even then, telling your manager it's going in costs nothing and preserves the relationship the pilot will need.

How polished does the pitch need to be — slides, a document, or just talking?

Match the room's native format: some organisations think in slides, some in one-page papers, some across a desk. What matters more than polish is the leave-behind — one page someone can forward without you attached: the problem with its figure, the fix, the honest cost, the first step, and your name. Retellability decides more pitches than production values do.

What if someone senior takes my idea and presents it as theirs?

Paper trails help more than confrontation: the dated one-pager, the email thread, the pilot write-up with your name on it all make authorship checkable without a scene. And sponsorship usually looks a bit like theft from close up — a director re-telling your idea in their own words is often the idea succeeding. Judge by outcomes: if the work and the credit both keep flowing away from you, that's a pattern worth acting on; one retold pitch isn't.

How do I pitch an idea when I'm junior and the room is senior?

Lean into the one advantage juniority carries: proximity to the problem. 'I do this task forty times a week, and here's what it actually costs us' is evidence the senior room cannot generate for itself. Keep the ask pilot-sized, borrow authority where it's offered — a team lead's endorsement, a figure from a system the room trusts — and let the specificity do the talking. Rooms forgive junior polish; they don't forgive vagueness.

What makes the strongest first step for a workplace idea?

Small enough that the room in front of you can approve it without escalating, real enough to produce a number worth reconvening over, and reversible enough that a kill costs nobody face. Six weeks, one team, one measure, a named review date, and you volunteering to run it is the shape senior people say yes to — the UK government's own Green Book guidance on appraising proposals runs on the same logic at national scale.

Grow

Pitching an idea at work: the questions that decide it, worked

Updated 12 August 2026

Ideas at work are not judged in the presenting — they are judged in the questioning. Almost anyone can describe a good idea for two minutes; what separates the pitch that moves from the pitch that gets a warm 'interesting, leave it with me' is the five minutes after, when the room probes cost, risk, precedent, and your own staying power. This page is built around that truth: one worked opening, then the pushback questions that actually decide these conversations, each with an answer that survives it.

The other thing experienced pitchers know: the decision is rarely made in the meeting anyway. Your manager or their board will re-tell your idea to someone else, without you in the room, in about four sentences. If those four sentences don't survive the retelling — problem, fix, cost, first step — the idea dies politely in a corridor. Everything below is shaped for retellability: numbers that stick, a first step small enough to say yes to, and a cost of doing nothing that does the arguing while you're elsewhere.

A register note: the winning tone is owner, not salesperson. You are not overcoming objections; you are helping a colleague spend the organisation's money and attention well — which means conceding the weak flank yourself before someone finds it, sizing honestly, and asking for the smallest decision that gets the idea into contact with reality. The worked answers model that register throughout.

Your career — see where this workplace conversation fits in the wider loop.

What the room is weighing

Whether you've priced it or just imagined it. The first pass is always for a cost — hours, money, disruption — and 'I haven't costed it yet' ends most pitches on the spot. A rough, honest figure with its workings beats a precise-sounding one you can't defend.
Whether the problem is real or the solution is shopping for one. Rooms listen for evidence the pain exists — tickets, delays, rework, complaints, a figure from the last quarter — before they'll spend a minute on the remedy. Ideas that open with the remedy read as hobbies.
What happens when they poke it. The probing is partly about the idea and mostly about you: do you concede honestly, defend with evidence, distinguish 'don't know yet' from 'doesn't matter'? The pitch is a sample of what you'd be like to trust with the pilot.
Whether saying yes is small. Senior people say no to programmes and yes to experiments. If the first step needs a fortnight, one spreadsheet, and no budget line, the room can say yes without asking anyone — and rooms take the yes they can give today over the one they'd have to escalate.

The two-minute opening: how do you frame the idea before the questions start?

Why it's asked: You usually get one uninterrupted run at the idea — everything after is dialogue. The opening's job is not to be complete; it is to leave a retellable spine (problem with a figure, fix in a sentence, cost, first step) and to hand the room its first question deliberately, rather than letting it pick a hostile one at random.

Model answerTeam meeting slot, operations analyst, parcel logistics

I want two minutes on the redelivery problem, and I'll start with the number: last quarter we made 4,100 second attempts in this region, and our own data says most of them were doomed before the van left — wrong safe-place notes, dead phone numbers, flats with no access instructions.

The idea is unglamorous: a forty-eight-hour pre-delivery check for the addresses that have burned us before. We already flag them in the routing tool — we just do nothing with the flag. A part-time coordinator working that list — calling, fixing notes, rebooking — is the whole intervention.

Cost, honestly: about £11,000 a quarter in hours, plus two days of routing-team time to expose the flag list. Against that, each avoided second attempt saves a van slot we currently price at £14.

I'm not asking for the programme. I'm asking for a six-week pilot on the Reading depot's list, measured on second-attempt volume, and I'll run it alongside my own job. If the number doesn't move, I'll kill it myself and tell you why.

'What does it cost — really — and where does the time come from?'

Why it's asked: The first serious probe, and the one that sorts owners from enthusiasts. 'Really' is the operative word: the room is testing whether your figure includes the hidden lines — your own hours, other teams' time, the disruption while it beds in. Concede the full cost before they find it; a pitch that under-prices itself once is discounted forever after.

Model answerPushback round, HR advisor pitching an induction rebuild, engineering firm

The full version, including the lines that usually get hidden.

Direct cost: about £3,500 — the licence for the checklist tool and two catered half-days for the pilot cohort's buddies. That's the small part.

Time, which is the real spend: roughly sixty hours of mine over eight weeks, which I'll take from the reporting pack I currently rebuild manually each month — Priya has agreed to absorb the June one, and that trade is in writing. Fifteen hours from team leads for the buddy training. And the honest disruption line: the first cohort through a new induction always asks more questions, so their managers lose a bit of week one.

What I'm NOT counting, deliberately: the time we already lose to the current mess — the same questions answered individually forty times, the leaver at month three we spent twelve weeks recruiting. That's not a cost of the idea; it's the cost of not doing it, and it's the line I'd put my name against.

If the pilot works, the scale-up needs a proper costing — I'd rather come back with pilot data than guess it today.

'What's the risk if it goes wrong — and what breaks while you're busy doing this?'

Why it's asked: The two-headed risk probe: the idea's own downside, and the opportunity cost of you. Rooms fear the second more than the first — every improvement pitch is implicitly a bid to spend your attention, and your manager is pricing what stops getting done. The strong answer bounds both honestly and names the kill-switch, because a reversible idea is a fundable one.

Model answerSenior review, band 6 pitching a discharge-checklist change, NHS trust

Two risks, and they're different sizes.

The idea going wrong: bounded, because of what the pilot deliberately isn't. We're adding a checklist step to the discharge huddle on one ward, for six weeks — we are not touching the electronic record, not changing who authorises discharge, and nothing in the step can delay a medically ready patient, because the checklist runs alongside the existing process rather than gating it. If it adds friction, the failure mode is 'we wasted ten minutes a day for six weeks', and the ward sister can kill it any Friday. That's the whole downside.

What breaks while I do it: fair question. The audit prep is mine and it's immovable, so I've sized this at four hours a week, and the thing I'll visibly drop is my seat in the Tuesday bed meeting — Marcus covers, and he's agreed rather than been volunteered.

What I can't promise is that readmissions move in six weeks — that figure is noisy. What will move, if this works, is completed-checklist discharges and the pharmacy callbacks, and those we can count weekly.

'Hasn't this been tried before? Why will it work this time?'

Why it's asked: In any organisation older than five years, something like your idea has usually been attempted, and the room's veterans remember the corpse. Never dismiss the history — the person asking may have led it. The answer that lands: know the previous attempt better than the room does, name specifically what killed it, and show which of those conditions has changed. If you haven't done that homework, this question ends the meeting.

Model answerBoard pushback, marketing manager, building society

It has — 2022, the 'branch advocates' scheme, and I went and found out what happened before bringing this in, because I assumed someone in this room would remember it. Sandra ran it; I bought her a coffee.

Three things killed it, on her account. It was fifteen branches at once, so no branch got real support. The content was produced centrally and arrived late, so advocates had nothing timely to share. And it was measured on head-office impressions rather than anything a branch cared about.

What's different in this version is each of those, specifically: two branches, not fifteen; the branches make the content and we clear it within a day — the clearance rota is the only central piece; and the measure is local — appointments booked from local channels, which branch managers already track and already want.

What's the same, honestly, is the underlying bet: that local voices carry further than central ones. If that bet was simply wrong, this fails too — but 2022 never tested the bet, it tested whether an unsupported pilot can survive, and we knew the answer to that already.

'Why now? We're mid-restructure / mid-budget / mid-everything.'

Why it's asked: Half genuine bandwidth concern, half a polite shelf. The answer that survives it prices the delay: what six more months of the problem costs, in the figures you opened with — and where the moment is genuinely load-bearing (a contract renewal, a system migration that makes the change cheap now and expensive later), name it. If there is no real reason for now, concede the timing and book the specific later — a pitch that returns on schedule reads as judgement, not defeat.

'Who else has signed up to this? What does [the affected team] think?'

Why it's asked: The coalition probe. Senior people rarely fund an idea whose affected parties are hearing about it for the first time in their meeting — that is how turf wars start, and they know it. The strong answer names the conversations already had: the team lead who reviewed the draft, the sceptic whose objection reshaped step two, the function that asked for a seat on the pilot. One pre-briefed sceptic in your corner outweighs three enthusiastic bystanders.

'How will we know it's working — and who's accountable when it isn't?'

Why it's asked: The measurement question, with the ownership question riding behind it. Pick one or two measures that move within the pilot window and are counted by systems the room already trusts — not a dashboard you'd have to build to prove your own case. And answer the second half in the first person: 'me — reporting fortnightly, and recommending the kill if the number sits flat'. Accountability volunteered is the cheapest credibility available.

'Interesting — leave it with me.'

Why it's asked: Not a question, but the most decisive line in the meeting, because unmanaged it means the idea just entered the drawer where ideas go to age. The move is gentle conversion: 'gladly — can I make it easy?' then offer the one-pager for forwarding, ask who else should see it, and propose a check-in date. If the check-in gets diaried, the idea is alive; if it can't be, you've learned that too, at the cost of one sentence.

'Could we do a cheaper version of this?'

Why it's asked: A buying signal wearing a frown — nobody haggles over an idea they've rejected. Have the smaller shape ready before the meeting: the version with no licence cost, the manual version, the one-team version. Concede what the cheap version won't prove, so the discount is informed rather than quiet. The trap to refuse politely is the version so small it can't demonstrate anything — a pilot designed to be affordable rather than to answer the question kills the idea slowly instead of testing it quickly.

The answer is no. What does the professional close sound like?

Why it's asked: A no taken well is an investment: ask what would have to be true for a yes — a quieter quarter, pilot data from elsewhere, a different cost shape — and whether you can bring it back when that's true. Thank the room for the probing, mean it, and write up what you learned; the second pitch of a returned idea starts three questions ahead. Ideas rarely die of no; they die of the pitcher taking the no personally and never returning.

FAQ

Should I pitch to my manager first or bring the idea straight to a bigger meeting?: Manager first, almost always — ambushing your own manager in front of theirs converts a potential sponsor into an opponent in one move. The exception is organisations with a designed route for ideas (an innovation forum, a suggestion process with teeth); even then, telling your manager it's going in costs nothing and preserves the relationship the pilot will need.
How polished does the pitch need to be — slides, a document, or just talking?: Match the room's native format: some organisations think in slides, some in one-page papers, some across a desk. What matters more than polish is the leave-behind — one page someone can forward without you attached: the problem with its figure, the fix, the honest cost, the first step, and your name. Retellability decides more pitches than production values do.
What if someone senior takes my idea and presents it as theirs?: Paper trails help more than confrontation: the dated one-pager, the email thread, the pilot write-up with your name on it all make authorship checkable without a scene. And sponsorship usually looks a bit like theft from close up — a director re-telling your idea in their own words is often the idea succeeding. Judge by outcomes: if the work and the credit both keep flowing away from you, that's a pattern worth acting on; one retold pitch isn't.
How do I pitch an idea when I'm junior and the room is senior?: Lean into the one advantage juniority carries: proximity to the problem. 'I do this task forty times a week, and here's what it actually costs us' is evidence the senior room cannot generate for itself. Keep the ask pilot-sized, borrow authority where it's offered — a team lead's endorsement, a figure from a system the room trusts — and let the specificity do the talking. Rooms forgive junior polish; they don't forgive vagueness.
What makes the strongest first step for a workplace idea?: Small enough that the room in front of you can approve it without escalating, real enough to produce a number worth reconvening over, and reversible enough that a kill costs nobody face. Six weeks, one team, one measure, a named review date, and you volunteering to run it is the shape senior people say yes to — the UK government's own Green Book guidance on appraising proposals runs on the same logic at national scale.