Accountability as Infrastructure

“There are three things we can’t have: we can’t have complacency, we can’t have selfishness, and we can’t lose our accountability.” —Nick Saban

From Rangers to Tech Teams

Serving as a U.S. Army Ranger, I quickly realized accountability wasn’t just military jargon—it determined mission outcomes. I watched squads thrive or crumble, depending on how they handled responsibility. Now, in tech, I see similar patterns. While code replaces combat, accountability remains crucial. Both worlds need a culture where people own their choices, learn from their mistakes, and challenge each other. Real accountability propels teams forward, whether in a firefight or a startup. It molds separate individuals into a unified force that innovates and adapts. This Ranger lesson has shaped my approach in every tech firm I’ve joined since leaving the service.

The Accountability Crisis

Research shows that only 15% of employees know their organization’s top goals. This gap between leadership vision and team awareness creates an “accountability crisis.” Organizations often have leadership with clear objectives and hardworking teams, but communication breaks down somewhere in between. This results in misaligned efforts, inefficient resource use, and dissatisfied teams. The challenge for leaders is to transform accountability from a negative concept into a driver for growth and innovation.

Diagnose, Don’t Blame

Teams often begin with positive intentions, but obstacles arise. It’s important to analyze not just what went wrong but why it happened. This approach helps identify problems before they escalate. As Brené Brown states, “Clear is kind. Unclear is unkind.” This principle is directly applicable to accountability.

To identify hidden obstacles:

• Encourage open communication with your team.

• Ask specific questions: What is causing delays? Where are we experiencing difficulties?

• Establish an environment of trust for open dialogue.

Teams often need help with process inefficiencies, competing priorities, or resource limitations. Leaders must identify these underlying issues. Metrics such as Defect Rates and Mean Time to Recovery can provide valuable insights. These tools help transform accountability into a constructive challenge rather than a punitive measure. The goal is to create an environment where your team is motivated to identify and address obstacles, knowing they have leadership support.

Measure Causes, Not Just Outcomes

Effective accountability requires understanding both outcomes and their causes. When teams repeatedly miss Key Performance Indicators (KPIs) or Objectives and Key Results (OKRs), a thorough investigation is necessary. Evaluate the project scope, potential distractions, and resource availability.

DORA (DevOps Research and Assessment) metrics can provide valuable insights. For example, examine your Deployment Frequency—how often does your team successfully release to production? Also, consider your Change Failure Rate—what percentage of deployments fail? These metrics provide information about your processes and where improvements might be needed.

Leaders should also hold themselves accountable. It’s essential to regularly ask: “Am I providing clear direction? Are my expectations realistic?” This self-evaluation sets an example for the entire team.

The Playbook in Practice

At a medium-sized software company, the product development team consistently missed deadlines. The Vice President of Engineering implemented a strategy of “compassionate accountability.”

She organized a team review, creating an open environment for discussion. This process revealed several issues:

• The team was understaffed for the project requirements.

• Design and development teams lacked clear communication protocols.

• The team needed to have a shared understanding of project priorities.

Using DORA metrics, the VP found that their Deployment Frequency was low and the Change Failure Rate was high. Instead of assigning blame, she collaborated with the team to:

• Adjust the project timeline and increase the number of developers.

• Implement a new process for design-development collaboration.

• Develop a transparent system for prioritizing features.

The results were significant. In three months, the team doubled its Deployment Frequency and reduced the Change Failure Rate by 40%. Additionally, team morale improved, and there was an increased sense of ownership throughout the team.

Your First Move

Compassionate accountability starts with diagnosis, not blame. When teams miss targets, this playbook applies: create space for honest assessment, use metrics to find root causes, and adjust resources or timelines based on what you learn. The goal isn’t to excuse poor performance—it’s to separate outcome from cause, so you can fix what’s actually broken. Trust enables that honesty. Without it, teams hide problems until they’re unfixable.