Tech leaders often say they want their teams to experiment and pursue new ideas. But even seemingly reasonable management practices can make creative risks feel too costly or time-consuming. When those pressures become part of everyday work, employees may become less willing to test unfamiliar approaches or challenge established ways of working.
The disconnect between encouraging innovation and making room for it isn’t always obvious to leaders. Here, members of Forbes Technology Council explore the management habits that can quietly hold innovation back and explain what leaders can do differently to support experimentation.
1. Treating Every Experiment As A Delivery Commitment
The mistake is making every experiment a delivery commitment. Having managed program managers and engineers, I’d separate learning goals from ship dates. Only 13% of AI users in Microsoft’s 2026 survey said reinvention was rewarded when results fell short. Set a question, a budget and a stop date; disproving the idea can still be a useful result. – Swapnil Upganlawar, Amazon
2. Banning AI Tools Instead Of Setting Guardrails
Blanket bans and strict restrictions on AI tools kill innovation. Blocking doesn’t stop adoption. It creates an AI lockdown paradox, where employees move their work to personal devices and accounts. Leaders end up with all of the security risk and none of the visibility. Instead of acting as the “Department of No,” leaders should put automated guardrails in place that let teams experiment safely. – Rick Caccia, WitnessAI
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
3. Rewarding Only Safe Goals
Only rewarding safe goals undermines innovation. If people are judged only on goals, they make conservative plans and stop proposing big bets. We want people who set goals they might miss and run their area like owners. We judge them on how far they moved the business and what they learned. – Chris Szymansky, Fieldguide
4. Rushing Teams Into Execution
Rushing teams into execution before giving them space to understand, experiment and learn stifles experimentation. Innovation suffers when leaders don’t take the time to deeply understand the problem, connect it to a meaningful business outcome, and bring the right cross-functional teams together. Release in small, meaningful increments; test, learn and iterate. Great innovation needs both freedom to experiment and discipline around outcomes. – Benu Aggarwal, Milestone, Inc.
5. Punishing Failed Experiments
Punishing failed experiments while celebrating innovation holds teams back. When leaders demand certainty before approving new ideas or judge every experiment by immediate returns, teams learn that playing it safe is rewarded. Innovation requires disciplined experimentation, clear boundaries and permission to learn. The real test of leadership is not how it celebrates success but how it responds when a well-designed experiment fails. – Maman Ibrahim, EugeneZonda
6. Overengineering Experimentation
Overengineering experimentation quietly kills innovation. Discipline matters, but every experiment doesn’t need to become a project. Give teams a clear problem, guardrails and the autonomy to test, learn and iterate quickly. The goal isn’t less process. It’s making sure the process serves innovation—not the other way around. – Abhijit Kakhandiki, BMC Software
7. Scheduling Every Sprint At Full Capacity
Filling every sprint to 100% quietly kills innovation. Leaders say they want experiments, then plan the roadmap so tightly that there is no room to try anything. People will not test a new idea when it means missing a committed deadline. If experimentation matters, it needs space on the calendar. Keep some capacity unplanned and protect it when delivery pressure builds. – Mudit Singh, TestMu AI (LambdaTest)
8. Defining Features Before Understanding User Needs
Starting with features instead of user problems kills innovation. When epics and features are defined before the team understands user needs, experimentation is compressed into implementation. UX and delivery teams are left optimizing a predetermined solution instead of using discovery to jointly design a better one. Engage UX strategists from the start. This gives teams the greatest autonomy to design the best solution. – April Ho-Nishimura, Infineon Technologies AG
9. Pushing New Technology Before Teams Are Ready
Prioritizing trends and buzzwords over how comfortable employees are with adopting new technologies can undermine innovation. Leaders may see a new tool or tech stack as an opportunity to innovate, but forcing it on a team without considering their experience can have the opposite effect. Innovation works best when people have the time, support and freedom to explore technology rather than simply follow trends. – Artem Lalaiants, RiskSeal, Inc.
10. Treating Existing Workflows As Untouchable
Treating the existing workflow as untouchable quietly kills innovation. In recent banking discussions, leaders emphasized redesigning the process before deciding where AI belongs. Asking teams to experiment while preserving every approval, handoff and metric limits what they can discover. Give teams permission to question how work gets done and test a better way with clear guardrails and outcomes. – Gregg Aldana, Appian
11. Demanding Results Without Fostering Creativity
Demanding outcomes without fostering the culture that supports innovation is counterproductive. Leadership needs to put more emphasis on people as half of the factors in successful outcomes. Providing your people with a culture that fosters creativity, open debate and collaboration is necessary for experimentation and for turning that experimentation into commercial products. – Susan Odle, StorMagic
12. Prescribing Projects Instead Of Setting Direction
Giving teams a destination when what they need is a direction limits innovation. A list of approved projects only contains what leadership has imagined, so teams never get past those ideas. With AI, we set clear limits on data access, then handed every department a blank page and one direction: Try things and find your own use cases. Ideas came from every function, not from the plan we drew up in advance. – Alex Saric, Ivalua
13. Requiring Business Cases Before Testing Ideas
Requiring a business case before anyone is allowed to try something can shut down experimentation. Leaders say they want experimentation, then ask for projected ROI on a two-week test, which guarantees that only safe, incremental ideas get proposed. Give teams a small preapproved budget and time box for experiments, and ask for a business case only after the test produces evidence. – Agung Dwi Sandi, rankpillar Group
14. Judging Experiments By Established-Product Metrics
Judging experiments by the same metrics as established products quietly kills innovation. Teams learn to protect quarterly targets instead of testing bold ideas. A space mission needs ground tests that expose weaknesses before launch; tech teams need that same permission to discover what fails. The space mindset: Reward disciplined learning, with clear hypotheses, bounded resources and evidence that informs the next decision. Make learning a performance goal. – Shelli Brunswick, SB Global LLC
15. Enforcing Rigid Roadmaps And Deadlines
Roadmaps and dates can constrain innovation. Often, management is trying to forecast the impact of things on the business, and because of this, they put expectations around dates, delivery and impact. But innovation requires a lot of experimentation, and the first version is often not correct or impactful in the way you expect. It is the constant iteration that drives real results, and that is hard to quantify and predict. – Mark Beare, Malwarebytes
16. Demanding Financial Proof Before Prototyping
Having to report to a CFO to justify market demand when the technology has not even been prototyped, tested or taken to market is a sure way to kill innovation. While innovation teams need to work in a resource-disciplined manner, finance should not have a seat at the table during the early stages of innovation, concepting and user testing. – Mark Francis, CaregiverZone
17. Dismissing Ideas Instead Of Exploring Their Potential
Innovation must not be limited by a long list of constraints. It also must be presented to the right audience. Wheeled luggage was patented in 1970 but did not become widely popular until two decades later. How management delivers their message when an innovative idea presented does not meet current needs is critical. For example, “That’s not what I am looking for” versus “How do you see this idea resolving the issues in front of us?” create two different impacts. – Irene Thong, Oglethorpe Power
18. Requiring Multiple Approvals Before Testing
Requiring too many layers of approval before anyone can test an idea discourages innovation. Having worked through several major technology shifts, I’ve learned that you rarely know exactly what will work until you try it. When every experiment requires multiple meetings and executive sign-off, people stop bringing forward ideas. Give teams room to test things without making them defend every idea first. – Nada Usina, NU Advisory Partners
19. Rewarding Certainty Over Learning
Rewarding people for knowing rather than learning stifles innovation. When teams are expected to have the right answer before they experiment, they stick to familiar problems and safer solutions. Leaders need to make it easier to be wrong, test assumptions and learn quickly. The point of experimentation isn’t always to succeed. Sometimes it’s simply to find out what doesn’t work and why. – Dhiraj Rajaram, Mu Sigma