How Leaders Kill Innovation By Playing Agile Safe
- Steven Granese

- Jun 10
- 4 min read
Updated: Sep 26

Agile has become the enemy of new ideas in many companies, and I've witnessed this phenomenon over the past 15 years of product leadership. What started as a way to create useful tension between customer needs and team skills has turned into a planning exercise that removes the friction needed for breakthrough thinking. The original promise of Agile was to create healthy tension through two opposing forces: the Product Owner fighting for customer value and the Scrum Master protecting team freedom. This tension was supposed to drive new ideas through creative problem-solving, but somewhere along the way, we turned Agile into a comfortable way to just get work done. When leaders give teams answers instead of problems, they steal the creative energy that comes from wrestling with tough questions. The result is teams that execute brilliantly but create nothing new.
"Agile has become the enemy of new ideas in many companies."
The Comfortable Trap Of Giving Teams Answers
Leaders today fall into three common traps that kill new ideas while appearing to help their teams succeed. The first trap involves handing teams pre-made answers disguised as planning, which removes the mental tension needed for creative breakthroughs. When a leader walks into a sprint planning meeting with detailed user stories that describe precisely how to build a feature, they've turned their development team into highly skilled assembly line workers. The second trap centers around putting one person in charge, typically a project manager or tech lead, who becomes the bottleneck for creative thinking and removes the healthy debate between customer needs and technical reality. The third trap focuses on individual performance numbers rather than team results, creating an environment where people prioritize personal speed over team success. These patterns feel good because work gets done, stories get completed, and velocity charts go up, but new ideas die quietly in conference rooms where the most challenging questions never get asked.
Creating Space For Breakthrough Thinking
The cure for idea-killing Agile requires leaders to become comfortable with messiness and give their teams real decision-making power. I've seen great results when leaders give their Product Owners and Scrum Masters permission to fight productively about priorities, scope, and technical approaches. This means showing teams customer problems rather than ready-made answers, then stepping back to let the creative tension between user needs and technical limits drive new solutions. Teams need space to think, try things, and repeat without the pressure of hitting speed targets that reward fast work over smart work. The goal shifts from completing the most story points per sprint to learning the most and creating the most value, even when that learning comes through failures and dead ends. When teams truly own both the problem and the answer, they understand customer needs and technical possibilities better, which leads to breakthrough solutions.
The Three Horizons Of Innovation Leadership

Innovation happens across three distinct time horizons, and effective leaders create different types of environments for each horizon to thrive. Horizon 1 innovation focuses on improving existing products and processes, where teams need clear constraints and rapid feedback loops to optimize current capabilities. Horizon 2 innovation explores adjacent possibilities and new market opportunities, requiring teams to balance current customer needs with emerging trends and technologies. Horizon 3 innovation pursues transformational breakthroughs that may not yield results for years, requiring leaders to create safe spaces for experimentation without immediate ROI pressure. The mistake I see repeatedly is leaders trying to apply the same management approach across these different innovation horizons. Teams working on Horizon 1 improvements need tight feedback loops and clear success metrics, while teams exploring Horizon 3 possibilities need patience, resources, and protection from short-term performance pressure. Effective leaders establish distinct operational rhythms, success metrics, and risk tolerances for teams operating in various innovation horizons.
OKRs as Idea Enablers
Objectives and Key Results become powerful tools for generating new ideas when leaders use them to define results rather than dictate how to work. The magic happens when OKRs set clear finish lines while leaving the path completely open for teams to figure out. I've watched teams achieve significant breakthroughs when their OKRs focused on customer impact numbers rather than feature delivery dates or technical specs. The key insight is that OKRs should create agreement around what success looks like without dictating how teams should achieve that success. When done well, OKRs become permission slips for teams to try new things, take calculated risks, and explore unconventional approaches to attain their goals. The moment leaders start using OKRs to control execution details or timeline milestones, they turn a powerful framework into another compliance exercise that stops creativity.
"When done well, OKRs become permission slips for teams to try new things, take calculated risks, and explore unconventional approaches to attain their goals."
Building Your Innovation Operating System
Creating consistent new ideas requires leaders to design company systems that naturally produce the conditions for breakthrough thinking. This involves establishing team structures, meeting schedules, and decision-making processes that maintain a useful tension between competing priorities and viewpoints. The Scrum framework provides a solid foundation, but only when leaders resist the urge to remove friction by providing teams with ready-made answers or appointing single decision-makers who eliminate healthy debate. New ideas thrive when teams have clear problems to solve, different viewpoints to consider, and enough freedom to pursue unusual approaches. Leaders must measure team success through customer impact and learning speed rather than traditional efficiency numbers that prioritize predictable work over creative work. Companies that consistently create new ideas have learned to accept the messy, uncertain process of creative problem-solving rather than chasing the comfortable illusion of better planning and execution.





