
Disruption Does Not Come from the Boardroom: Building Bottom-Up Innovation Cultures
The best disruptive idea at Disney did not come from Bob Iger. It came from a junior developer who got frustrated with queuing systems and sketched out what became MagicBand on a napkin during his lunch break.
The breakthrough that transformed American Express's customer service? A call centre agent in Phoenix who redesigned the workflow between her coffee break and her next call.
Yet most organisations still treat innovation like a top-down mandate. The board sets the vision. Strategy gets cascaded. Innovation theatre begins.
Here is what I have learned after building innovation programmes inside companies like NatWest and ING: disruption does not come from the boardroom. It comes from the person closest to the problem who finally gets permission to solve it.
Why boardroom innovation fails
Executives see patterns across markets. They spot trends. They understand competitive threats. What they do not see is the specific friction that makes your customer want to throw their phone at the wall.
That frustrated customer service rep? She hears that friction 40 times a day. The product manager buried three layers down? He gets the angry user feedback that never makes it to the weekly reports.
When innovation starts in the boardroom, you get solutions to yesterday's problems built by people who have never used your product. When it starts on the ground floor, you get solutions to problems your customers are having right now.
The difference is not just better ideas. It is better adoption. When someone builds the solution to their own daily frustration, they become your biggest advocate for rolling it out.
The scout system that actually works
At ESADE, we studied companies that consistently produce breakthrough innovations from within. The pattern was always the same: they had created internal "scouts" who could spot opportunities and had the autonomy to act on them.
These were not dedicated innovation teams. They were regular employees who had been given three things: permission to experiment, resources to test ideas quickly, and a direct line to decision makers who could say yes.
The key insight from our research? Innovation scouts are made, not born. Anyone can learn to spot opportunities if you give them the right behavioural cues.
Action step one: Create the 15% rule
Google's famous "20% time" sounds appealing but rarely works in practice. Most people need more structure than complete freedom.
Instead, implement a 15% rule with guardrails. Every employee gets one afternoon per week to work on improvements to their immediate work environment. Not blue-sky innovation. Not disrupting entire industries. Just making their job easier or their customers happier.
The constraint is crucial. When people focus on problems they encounter daily, they build solutions that actually get used. Set up a simple submission process where anyone can propose a small experiment. Give them two weeks and a £500 budget to test it.
Action step two: Build reverse mentoring programmes
Your junior employees understand your customers better than your senior leadership. They are on social media where your customers complain. They use your competitors' products. They see the gaps between what you promise and what you deliver.
Pair each senior leader with someone at least two levels below them for monthly "reverse mentoring" sessions. The agenda is simple: what frustrates you about how we work? What do our customers really want that we are not giving them?
Make it formal. Put it in calendars. Give the junior person explicit permission to challenge assumptions. Some of your best strategic insights will come from these conversations.
Action step three: Fund small bets, not big strategies
Most innovation budgets get spent on elaborate programmes that take 18 months to show results. By then, the problem has changed or the team has moved on.
Instead, create a monthly "small bets" fund. Any employee can request up to £2000 to test an idea that could improve customer experience or operational efficiency. The only requirements: it must be testable within 30 days and they must present results to the team.
Ninety percent will fail. That is the point. The 10% that work will more than pay for the programme, and you will have created a culture where trying things is normal, not scary.
The companies I work with that consistently innovate do not have better strategies. They have more experiments running. Their advantage is not vision, it is velocity.
Real innovation happens when you stop asking "what should we build?" and start asking "what tiny experiment could we run this week?"


