Over the years, I’ve seen established teams continue performing well at their work while growing less willing to question how they do it. They still deliver things on a regular basis. They have leaders with proven record knowing how to get a job across the finish line. A lot of that comes from arrangements they’ve worked over time to get right.
It makes sense to protect what’s working. But when keeping things predictable is what earns people trust and recognition, the immediate risks of changing can feel more pressing than the bigger longer-term risks of staying the same. Over time, that can limit what the team takes on. When a new opportunity calls for something its usual methods can’t deliver, the team needs room to change how it works. It’s easier to make that room while things are still going well.
Think about a team with a deadline coming up. The familiar approach has a track record, and everyone knows their part. Trying something different takes time and effort. If the team gets judged on what it delivers this month, it has good reason to choose the path of least resistance. Each time it does, it gets better at the method it already knows. The alternatives stay unexercised, which makes them even harder to justify the next time.
That difference showed up in a lab experiment where people ran a simulated business. When their pay depended on later results, and early setbacks didn’t count against them, they explored more and were more likely to find a new strategy. How people were rewarded changed what they were willing to try. 1
A study of patenting in the photography and paint industries found that firms with more formal quality management tended to produce more inventions that built on what they already knew. A larger share of their patents covered inventions that built on existing knowledge. That’s what makes this pattern hard to spot: a team can keep producing valuable improvements while its work becomes more concentrated on what it already knows. Good results alone aren’t a reason to leave its ways of working unquestioned. 2
When Brad Bird joined Pixar, the studio had already made three hits. Bird recalled that its leaders were worried about getting too comfortable with how they worked. They brought him in to challenge their methods and were willing to try a different way if he could make the case for it. 3
Bird’s first Pixar film, The Incredibles, called for a lot of sets and things that were hard to animate at the time, including human characters, hair, water, and fire. When he showed the story reels, the technical team worried the film would take far too long and cost too much to make. Bird asked to work with people at Pixar who had ideas for doing things differently. As he tells it, those ideas rarely got a chance because the usual methods were already producing good films. 3
One change was to work out camera movements in the storyboards and commit to them early. That let the artists build only the parts of a set the camera would see. A set could look great from the planned angle and fall apart if you moved the camera a few feet. Bird gave up the freedom to change some shots later. In return, the team could build more sets and make a film on a scale that had looked impractical. 3
That’s what I mean by controlled disruption. The team had a specific problem to solve, permission to change how it worked, and a tradeoff it could live with. For Pixar, growth meant being able to make a more ambitious film. Getting there meant revisiting methods that had already made the studio successful.
I think of this as pruning. A gardener might cut back a branch that’s still growing to give another part of the plant room to grow. A team can do something similar by letting go of a step it once needed to do good work.
Say a product team has long relied on detailed designs, specialist handoffs, and approval before engineers start building. Those arrangements have helped it avoid expensive mistakes. With AI making working prototypes cheaper to build, the team could try one project without that sequence. A small group of people with design and engineering skills could build possible answers together and test them with users. Suppose the trial produces a better result in less time: users uncover problems earlier, and the team finds answers it would have rejected on paper. The lesson wouldn’t just be to add prototyping to the existing process. It would be to stop requiring detailed designs and approval before building this kind of product.
For any creative team, whether it makes films, builds products, or designs skyscrapers, changing how the work gets done can also change the roles and skills it needs. The product team might need more people who can move between designing, building, and testing, rather than separate groups specialising in each stage. That could mean reshaping or removing roles, helping people develop new skills, or bringing in others. These changes are harder than removing a process step, but keeping every role, handoff, and requirement intact would mean not acting on what the trial showed. Pruning means letting go of arrangements that no longer earn their place, even when they once helped the team succeed.
For leaders, that means making time for a trial, giving people the authority to change the arrangement, and acting on what they learn. Doing this while the team is meeting its commitments gives it time to develop new ways of working before it has to depend on them.
Which established arrangement are we willing to reconsider while the team is still doing well?
Ederer, F., & Manso, G. (2013). Is Pay for Performance Detrimental to Innovation? Management Science, 59(7), 1496–1513.
Benner, M. J., & Tushman, M. L. (2002). Process Management and Technological Innovation: A Longitudinal Study of the Photography and Paint Industries. Administrative Science Quarterly, 47(4), 676–706.
McKinsey Quarterly (2008). Innovation Lessons from Pixar: An Interview with Oscar-Winning Director Brad Bird.