Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

The hidden gap that kills good ideas

Five ways leaders can move ideas from insight to action.

[Photo: Getty Images]

Profile photo of Sheri Jacobs

CEO, Author, Global Keynote Speaker · Avenue M Group

A few years ago, Diana, a junior member of my team, knocked on my office door with an idea. She worked on the front line, fielding calls and email inquiries while tracking customer retention. The questions she heard every day gave her a perspective that wasn’t obvious to senior management.

Diana knew we were struggling to keep customers, and she thought she understood why. When new customers signed up, we bombarded them with so much information and so many offers that they started ignoring our messages. They would contact us with questions we had already answered because the answers were buried. Diana suggested sending information in a slower, more intentional drip. We tried her idea, and engagement rose. Sales and retention improved, too.

Her idea worked, but what stayed with me was how easily it could have gone nowhere. A promising idea might surface in a customer complaint or a frontline workaround. Sometimes it comes from a new employee asking why things are done a certain way. Many workplace cultures have a hidden gap where those ideas disappear.

1. SHARPEN THE OBSERVATION

In my work with leadership teams across industries, I’ve watched strong ideas lose momentum without ever being formally rejected. Someone raises an idea in a weekly team meeting, but it stalls because no one owns the decision. Another idea gets approved, but no one has time to work on it. A pilot produces useful findings that no one reviews. Each gap seems small. Together, they determine whether an idea ever reaches the people it could serve.

Employees often see the first signal before leaders have the full picture. At that point, the idea may still sound vague, such as “we need to simplify the onboarding process.” An employee might say, “We shouldn’t require the customer to change their behavior. We should meet them where they are.” Those observations are easy to praise and just as easy to postpone.

Ideas often stall during the handoffs between noticing an opportunity, making a decision, running an experiment, and acting on what the experiment reveals. Leaders can strengthen those handoffs and sharpen the observation by asking a few practical questions: What happened and who was affected? How often does it occur? What would improve if the problem were solved?

These questions turn a passing thought into something the organization can evaluate. They also keep the employee from having to build a complete business case before anyone has agreed that the problem deserves attention.

2. NAME A DECISION OWNER

Many organizations encourage employees to submit ideas. Fewer make the route to a decision visible. A suggestion box or innovation portal quickly becomes storage when nobody owns the next move.

Decision ownership doesn’t have to be complicated. Name the person who can authorize further discovery or approve a small test. That person should also be able to explain why an idea needs to wait or why the organization won’t pursue it.

A clear answer preserves trust, even when the answer is no. Silence teaches people that contributing an idea creates extra work with little chance that anything will happen.

3. SET BOUNDARIES FOR THE EXPERIMENT

Teams can become so focused on getting it right and avoiding risk that they never try anything new. Give the experiment a champion who can offer guidance. Then identify who will run the test and how much time it can consume. Be clear about which customers, employees, or systems may be included. Every new priority enters an already full calendar, so capacity must be part of the decision.

The best next step is usually smaller than the original idea. A team considering a redesigned service might test one feature with one customer segment for two weeks. Clear boundaries establish the budget and timeline. They also define who will participate and how much risk the organization will accept, giving the team room to act without returning for permission at every turn.

4. CLOSE THE LOOP

A pilot can produce useful learning and still disappear. This happens when the organization schedules the activity but never schedules the decision that should follow it. Before the test begins, set a review date and agree on the evidence that will guide the next move.

The findings might support expanding the idea or revising it. They may also show that it’s time to stop. Whatever happens, communicate the result to the people who contributed.

A test that falls short can reveal that an assumption was wrong or expose a customer need the team had missed. Sometimes it points the team in a better direction. Capturing those lessons allows the next experiment to start with more knowledge than the last one.

5. MAKE THE PATH VISIBLE

A simple idea path can work in almost any organization. For each promising idea, answer five questions:

1. What problem or opportunity have we observed?
2. Who owns the next decision, and by when?
3. What is the smallest credible test, given our boundaries and available capacity?
4. When will we review what happened?
5. How will we share what we learned?

Diana’s suggestion improved our retention numbers because it found a route from her desk to a decision, then into a real test. Most organizations have a Diana. Far fewer have given her a clear path.

Sheri Jacobs is CEO of Avenue M Group.