
What is the Leadership Stack?
When a technical systems breaks you don't fix it from the front end, you look for bugs in the stack. The Leadership Stack applies that same idea to human systems (like your team).
Learn MoreDebugging the Leadership Stack
Each layer of the Leadership Stack builds on the layer below it. Bugs higher in the stack are easier to identify, but are often rooted by more subtle bugs deeper in the stack. Visualizing where a bug originates helps leaders decide where to focus their debugging efforts.
IT Leaders | Debugging Human Systems: A new model for navigating the technical leadership paradox - Maureen Carruthers
IT Leaders is the podcast for IT Directors, CIOs, and technology decision-makers seeking actionable insights and executive-level leadership strategies. Produced by the IT Leaders Council and powered by Expedient, each episode features expert guest speakers, peer-to-peer discussions, and real-world stories from the front lines of enterprise IT. Recorded live at leadership events in Indianapolis, IN, Columbus, OH, and expanding nationwide, IT Leaders delivers vendor-neutral content focused on cloud strategy, digital transformation, data center modernization, and IT operations leadership. Join the conversation that helps shape the future of IT.

Signs of an interface bug
- Miscommunication
- Dropped or duplicated work
- Poorly distributed work loads
- Neglected administrative or maintenance work
Signs of a data bug
- Over or under engineered solutions
- Difficulty transitioning to new procedures or priorities
- Proposed solutions fail to meet business requirements
Signs of a permissions bug
- Team lacks the information or resources required to meet its goals.
- Effort spent focusing on what others need to change blocks progress the team could make on their own.
- The team is responsible for an outcome they don't have the power to achive
Signs of a Security bug
- Reluctance to share bad news
- Resistance to feedback
- Focus on blame/ CYA behaviors
- Miscalibration around risk
- Oversharing
- Lack of proactive action
Signs of an Operating System bug
- Organizational goals change faster than projects can be completed
- Objectives are interpreted differently across the organization
- Expectations are enforced inconsistently
- Institutional knowledge is shared primarily by oral tradition
- Organizational documentation and operational reality contradict each other
