Skip to main content
Welcome, DevOps soft-skills students — I’m Michael Forrester. This lesson compares two leadership approaches through a real-world story: one that undermines teams and one that aligns and empowers them. The contrast shows how leadership choices shape team dynamics, velocity, and long-term resilience.

​
Summary

  • A single VP centralized control and created bottlenecks, eroding autonomy and collaboration.
  • A DevOps-focused director applied transparency, prioritization, and lightweight processes to increase team health and delivery.
  • The lesson: leadership that empowers teams produces better outcomes than leadership that micromanages and punishes experimentation.

​
The scenario

A few years ago I led a DevOps-focused team while a newly hired VP of Infrastructure oversaw the entire department. Initially, everyone was learning the domain and organization. Over time it became clear the infrastructure and DevOps groups were operating in silos, and many development teams were even more disconnected. Because I attended cross-team leadership meetings, I had a front-row view of how the VP made decisions and how those decisions affected other teams.

​
The pattern I observed

Over several weeks, a clear pattern emerged in the VP’s behavior:
  • Frequent criticism and dismissal of new ideas, which discouraged experimentation.
  • Repeated interjection into day-to-day work rather than enabling teams to solve problems themselves.
  • Centralized, manual decision-making that created chokepoints and slowed delivery.
  • Little emphasis on training, collaboration, or building team autonomy.
In contrast, I introduced DevOps practices on my team—capacity planning, clear prioritization, deliberate communication, and active efforts to break down silos. Those practices increased engagement, clarified flow, and improved performance. When asked to help replicate these practices organization-wide, the VP undermined the effort by discrediting techniques and reasserting control. The contrast is instructive: one leadership style erodes autonomy and collaboration, causing dysfunction; the other cultivates trust, continuous improvement, and higher performance.
Effective DevOps leadership enables teams: increase transparency, build psychological safety, break down silos, empower people, and encourage continuous improvement.

​
Core principles to foster healthy DevOps teams

  1. Transparency and psychological safety
  • Make work visible so teams and leaders can see progress, impediments, and outcomes.
  • Foster psychological safety: encourage open discussions about risks and mistakes and treat failures as learning opportunities.
  1. Break down silos
  • Reduce handoffs and friction among teams that collectively deliver value.
  • Encourage cross-functional collaboration and shared ownership so skills are available or accessible end-to-end.
  1. Empowerment over micromanagement
  • Provide context, resources, and training; then grant teams autonomy to make decisions.
  • Focus leadership effort on removing impediments rather than intervening in routine decisions.
  1. Continuous improvement
  • Treat processes as systems: measure bottlenecks, iterate on flow improvements, and standardize what works.
  • Promote safe experimentation and learning from outcomes; small experiments yield data to inform decisions.

​
Practical checklist to apply these principles

​
Implementation tips

  • Start small: pilot a visibility board or a shared retrospective template with one team before scaling.
  • Measure what matters: cycle time, deployment frequency, lead time for changes, and mean time to recover (MTTR).
  • Celebrate learning: highlight experiments that taught the team something—even if they didn’t succeed.
Avoid behaviors that centralize control, punish experimentation, or enforce rigid siloed processes—these create bottlenecks, lower morale, and block continuous improvement.

​
Final thoughts

Leadership is a choice. Every interaction and decision either aligns and empowers teams or erodes their effectiveness. Whether you have formal authority or lead by influence, you can create an environment that is transparent, psychologically safe, collaborative, and empowered. Choose to align, not wreck. Build up rather than break down. The success of any DevOps effort depends less on tools and more on the strength of teams and the culture that surrounds them. Thank you for reading. — Michael Forrester Remember: leadership is a choice. Choose to align, not wreck.

Watch Video