The three things management cares about (and why most pitches miss them)
1. Does this solve a real problem or create real value? Not just activity. Not just engagement numbers. Real business impact. What problem are you solving? How will the organization be better off?
2. Can you sustain this without constant heroic efforts or a big budget? A program that requires a dedicated VP and a six-figure annual budget to run a couple of idea campaigns won't renew. A program that generates ideas quarterly with one person at 20% of their time has a chance.
3. How will you know it's working? Management doesn't need perfection. They need proof. "We ran four campaigns, generated 200 ideas, and implemented 12 of them. Eight are on track toward savings of roughly 500,000 kr. Four are still in implementation." That's the kind of answer that makes management lean in.
Most pitches for starting an idea management program fail because they focus on enthusiasm, potential, and best practices. Management hears these things and thinks: "That sounds good, but it's going to be a resource burden."
The business case on one page
You don't need a slide deck. You need one page that answers these three questions:
What problem are we solving? (Paragraph, max 75 words)
Example: "We're not systematically capturing insights from the people closest to the work. Good ideas get lost or implemented ad hoc. We want to channel this into a structured process so we can evaluate, prioritize, and act on the best thinking."
How will we know it's working? (Metrics, 3 to 5)
Example: Participation rate in each campaign (target: 15% of invited population for broad campaigns, 40% for targeted campaigns). Time from idea submission to feedback (target: 2 weeks). Implementation rate for advanced ideas (target: 60 to 70% of ideas marked for implementation actually get implemented). Generated value from implemented ideas (roughly estimated value for ideas with clear ROI). Repeat participation rate (target: 30% of campaign 1 participants also participate in campaign 2).
What do we need to get started? (Resources and timeline, brief)
Example: "One person at 25% FTE to manage campaigns, platform for submissions and evaluation (we have budget for a cost-effective SaaS option), 60 days to launch the first campaign, quarterly campaigns thereafter."
That's the business case. That's what management needs to hear.
The conversation that closes the deal
Use the one-page business case to start the conversation. Come prepared to answer these follow-up questions:
"Why do you think people will actually participate?" Answer: "We're targeting a specific problem and a specific population for the first campaign. The participation target is 15%, which is achievable if we address the challenge clearly and show early momentum."
"How do we know this won't just generate ideas we can't implement?" Answer: "We'll be clear in the challenge about what's in scope, what resources are available, and what timeline we're working with. We'll have a clear decision framework for evaluating ideas against the goal."
"What happens if it doesn't work?" Answer: "We run the first campaign as a pilot project. After 60 days we have clear data on participation, idea quality, and feasibility. We decide whether to continue based on this data, not on enthusiasm."
"How much will this actually cost?" Answer: "The platform costs X kr per month. The internal FTE for running campaigns equals X kr per year. Total comes in under the investment threshold for one person."
The one mistake that kills support
Overselling the program in the early stages. Don't claim you'll generate 500 ideas or implement 10% of them or save 2 million. Start smaller and exceed the target. When management sees that the program actually produces value, they'll be interested in scaling it.
The first campaign is a proof of concept. Treat it that way when you make the pitch.
Building an executive summary
Here's a template for a one-pager:
- Headline: "Idea management program: Capturing value from our employees"
- Problem: One sentence about the gap between current state and desired state
- Solution: One sentence about the structured program
- Expected results: 3-5 metrics
- Resources: Costs and time commitment
- Timeline: Pilot phase (days/weeks), evaluation, scaling
- Risks: 2-3 possible challenges and how you'll handle them
Management as participant, not just budget approver
An underrated approach: invite at least one member of the leadership team to participate in the first campaign. Not as an evaluator, but as a participant who submits ideas. This does two things: it shows you believe in it enough for leadership to participate, and it gives them real understanding of the process instead of just statistics.
Handling skeptics
Management can be skeptical in several ways:
"We've tried this before and it didn't work." Answer: "We're focusing on a specific problem this time, not broad innovation. We're also more careful with target audience planning than we were last time."
"That sounds like extra work for people who are already overloaded." Answer: "Simple idea submissions take 5 minutes. We're targeting people closest to the problem—for them, it's their daily work, not extra."
"How do we know the ideas are good?" Answer: "We use a clear scoring system. Every idea is assessed against the same criteria. We don't implement anything without having these three things: feasibility, impact, and alignment with goals."
The ROI numbers that impress management
Concrete numbers beat potential numbers. Let's give an example:
If an implemented idea saves 50,000 kr and you implement two ideas per campaign, annual value is 200,000 kr (two campaigns). If the program cost is 150,000 kr/year, net gain is 50,000 kr in year one, plus the scale grows next year. That's a number that makes management nod.
Following up after approval
You got the support. Now the real work begins. Two important things:
1. Run the pilot exactly as you promised. If you promised 15% participation and got 14%, that's a success. If you got 45%, that's also a success, but then you set the target too low and can't repeat it. Aim for the target.
2. Report regularly. Three weeks in, six weeks in, ten weeks in to the pilot. "Here's where we are." Management doesn't need surprises at the final presentation.
Scaling after the pilot
If the pilot succeeds (which it should, if you set small, achievable targets), the next step is scaling. Now you can talk about broader visions. "This year we ran four campaigns and implemented two ideas. Next year we can run six campaigns focused on cost savings and customer experience."
Management will be much more open when they already see it's working.
Executing the actual program
So you have management support and budget. The next step is actually launching the program. See Your first idea challenge: from question to decision in 10 days for step-by-step guidance.
Communication to the organization
Management approval means nothing if the organization doesn't know about it. From day one of your first campaign, employees need to know this has management support. It makes it feel real, not like an experiment.
Use How to write an idea challenge that actually gets relevant ideas to build unified messaging.
Long-term success tracking
After the first campaign, you start tracking these metrics continuously: participation rate, idea quality (via scoring), implementation rate, financial value from implemented ideas, and repeat participation from campaign to campaign.
See How to measure your innovation program without lying to yourself for a deeper guide on measurement.
Common mistakes when pitching for support
Focusing too much on the technology. Management doesn't care about the platform. They care about results. Mention the platform briefly and move on.
Calling this an "innovation program." The word "innovation" raises expectations for remarkable, game-changing ideas. You know better. Say "idea management" or "employee idea program." This sets the right expectation bar.
Forgetting to say why now. Why should we start this now? What changed? "We've identified a cost savings problem that our workforce can solve if we ask them right." Or "We want to improve employee engagement and this is a concrete way to show we listen." Give them a why-now moment.
How long does it take to get management approval for an idea program?
Plan on two to four weeks if you have a clear business case with concrete numbers. If you go in with vague promises about "innovation culture," it could take months, if it gets approved at all. The key is showing ROI potential early.
What do I do if management says no the first time?
Ask specifically what's missing. Often it's that they want to see proof before investing. Propose a minimal pilot (10 days, 50 participants, no extra cost) and come back with concrete results.
Do we need a dedicated budget to get started?
Not necessarily. A pilot can be run with existing resources. Platforms like Hives.co start from 695 EUR per month, which often fits within an existing budget. The real cost decision comes when you want to scale after the pilot.
Related guides
- How to measure your innovation program without lying to yourself
- How to write an idea challenge that actually gets relevant ideas
- One-pager on innovation for management
- Your first idea challenge: from question to decision in 10 days
- Communication templates for idea campaigns
- How to measure ROI for your innovation program
See our full comparison of the 10 best idea management tools
.jpeg)
.webp)

.jpeg)