Stop Hoarding Decisions If You Want Real Innovation

Subheadline: Give teams clear decision authority, carve out time for tests and treat failed trials as useful data so good ideas don’t die in approval queues
Too many companies say they want fresh thinking while keeping the power to decide tightly in a few hands. The result is familiar: a frontline worker notices a recurring customer problem, sketches a modest fix and routes it up the chain—only for the suggestion to stall behind layers of sign-offs. When approvals take weeks and everyday choices still bounce back to senior leaders, employees learn it’s safer to wait than to act. That kills momentum and discourages the next raise-your-hand moment.
Start by translating general encouragement into specific latitude. “Use your judgment” sounds nice, but it’s often meaningless without guardrails. Identify one type of routine decision your staff currently escalates, and spell out what they may decide on their own, what limits apply and when they must pause for review. Share the reasoning behind those limits so people can apply the rule to new situations. For example, a marketing lead might be allowed to run a small alternate email subject-line test so long as it follows brand copy rules, respects data privacy and includes a clear rollback plan. The degree of oversight should match the stakes: reversible, low-cost trials can move fast; changes touching contracts, customer data or large budgets deserve more scrutiny. And leaders must stick to their word. If you hand off a choice and then reopen it because you would have done it differently, employees will revert to waiting for you.
Creating space is as important as granting authority. Experimentation requires time, and that time has to come from somewhere in the workday. Ask teams to point out routine chores that eat hours but ask little judgment—manual data entry, duplicative status updates or one-person routing tasks are common offenders. Decide whether those tasks can be simplified, automated or dropped. Freeing a few hours each week can turn a reactive job into one that probes why problems recur. When teams propose a test, keep the scope manageable: define the problem, outline the change, name who’s accountable, list the evidence that will count as success and set a firm review date. Small pilots that fit alongside normal workstand a better chance of completion. Leaders also need to call what can wait; when every ongoing task remains tagged urgent, teams won’t believe experimentation is a real priority.
What happens after a disappointing test matters as much as the experiment itself. When a trial produces worse outcomes than expected, leaders should walk through the original hypothesis, review how the test was executed and surface what the results actually show. Was the team operating within the agreed boundaries? Did they spot trouble early? Can they say what elements to keep, tweak or abandon? Treat sloppy execution differently from a well-run test that simply disproved an assumption. And don’t confuse busyness with progress: five superficial pilots don’t beat one carefully designed experiment that produces usable findings. Recognize clear logic, disciplined execution and insights that other teams can reuse. Announce what changed, what was learned and what the next steps are—follow-through signals that experimentation is worth the effort.
Practical steps leaders can take now include hunting down recurring handoffs and unclear ownership; naming specific decisions teams may make without sign-off; protecting brief, recurring windows for improvement work; and building a simple review routine for experiments, successful or not. A common-sense rule is to treat low-risk pilots as something teams can launch within a short timeframe, while high-impact choices follow a faster, but still necessary, review path.
If you want people to bring ideas, give them a real chance to act. Saying “be creative” in a town-hall won’t cut it when the approval process you set up during the company’s early days still governs daily choices. Do the structural work—clarify authority, free up a little time and make sure failed tests produce useful lessons—and you’ll see more employees willing to try the next fix.

Comments