Listenly

How does Devon Middleditch approach leading innovation teams versus project delivery teams differently?

Answered at 30:14 in How to Become a Leader in Digital Engineering with Devon Middleditch · Digital Construction Podcast

— questions searchable right now

How does Devon Middleditch approach leading innovation teams versus project delivery teams differently?

Innovation teams operate in a fundamentally different mindset than project delivery teams. They reject controls and constraints — they need space to think big-picture and freedom to operate, not timesheets and strict program boundaries. Project delivery teams, by contrast, thrive with structure. The core skill for any leader is recognizing which type of team you're managing and adapting your approach accordingly.

The Innovation Mindset Requires Freedom, Not Oversight

People inventing the future are demotivated by the same management tools that work elsewhere. Tight controls, rigid governance, budget micro-management — these create friction in spaces where experimental thinking is the job. As Devon Middleditch explains in the Digital Construction Podcast, innovation teams need you to speak their language, not impose yours on them.

This doesn't mean anarchy. It means giving teams autonomy within a clear vision. A leader's role shifts from gatekeeper to enabler: you remove obstacles, clarify the big picture, and trust the team to find the path forward. Worrying about whether someone logged their hours is the wrong conversation entirely.

Project Delivery Teams Need the Opposite Structure

Paradoxically, the disciplines that kill innovation are exactly what project delivery teams require. Clear milestones, accountability checkpoints, documented decisions, and scope management aren't bureaucracy here — they're survival. A delivered project has measurable outcomes; an innovation sprint's value is often invisible until much later.

Digital Construction Podcast on Digital Construction PodcastAll answers from this podcast →
Full answer and detailsRead the whole answer, key facts and every other question from this episode

In short

Innovation teams operate in a fundamentally different mindset than project delivery teams.

Digital Construction Podcast · How to Become a Leader in Digital Engineering with Devon Middleditch · Digital Construction Podcast · answer at 30:14

Key takeaways

  • They reject controls and constraints — they need space to think big-picture and freedom to operate, not timesheets and strict program boundaries.
  • People inventing the future are demotivated by the same management tools that work elsewhere.
  • Paradoxically, the disciplines that kill innovation are exactly what project delivery teams require.

The full answer · about 1 min

Innovation teams operate in a fundamentally different mindset than project delivery teams. They reject controls and constraints — they need space to think big-picture and freedom to operate, not timesheets and strict program boundaries. Project delivery teams, by contrast, thrive with structure. The core skill for any leader is recognizing which type of team you're managing and adapting your approach accordingly.

The Innovation Mindset Requires Freedom, Not Oversight

People inventing the future are demotivated by the same management tools that work elsewhere. Tight controls, rigid governance, budget micro-management — these create friction in spaces where experimental thinking is the job. As Devon Middleditch explains in the Digital Construction Podcast, innovation teams need you to speak their language, not impose yours on them.

This doesn't mean anarchy. It means giving teams autonomy within a clear vision. A leader's role shifts from gatekeeper to enabler: you remove obstacles, clarify the big picture, and trust the team to find the path forward. Worrying about whether someone logged their hours is the wrong conversation entirely.

Project Delivery Teams Need the Opposite Structure

Paradoxically, the disciplines that kill innovation are exactly what project delivery teams require. Clear milestones, accountability checkpoints, documented decisions, and scope management aren't bureaucracy here — they're survival. A delivered project has measurable outcomes; an innovation sprint's value is often invisible until much later.

More answers from this episode

 ·  All answers from Digital Construction Podcast →
—
—
0:00
0:00