Talented technical organizations slow down when standards, decision authority, and accountability stay ambiguous. PACE is the lens for removing that ambiguity: practice, accountability, and consistent execution.
Its application is phased and specific to the situation. The sequence below is the part that does not change.
Accountability is not supervision
Whenever servant leadership comes up, the same question follows: where does accountability fit?
Most leaders answer it wrong. They treat accountability as more oversight. More check ins. More approvals. More visibility into what the team is doing hour by hour.
That is not accountability. That is supervision, and senior engineers can tell the difference immediately.
Real accountability starts with a standard that everyone can see. When the bar is visible and the expectations are clear, practice leaders and senior architects hold themselves to it. It does not have to be chased.
The leader's job is to set that standard, equip the team to meet it, and then get out of the way.
That last part is where technical leaders struggle most, and not because they doubt their people. It is because they came up as engineers. They know how they would solve the problem, and letting someone solve it a different way feels like risk.
It is not risk. It is leadership.
Four questions before calling it a performance problem
Taking over a team that is not performing invites the easy story, which is that the wrong people were inherited. Sometimes replacing people is necessary. Most of the time it is the laziest available diagnosis.
The more useful finding is usually that the team was not incapable. They were unclear. Nobody had told them what good looked like. Nobody had given them the context to make decisions. Nobody had invested in their development in a long time. They had been managed, but they had not been led.
So the questions come in order.
- Do they know the standard?
- Do they have what they need to meet it?
- Have they been given the authority to act?
- Do they actually want to?
The first three are the leader's job to fix. Fix them, and much of what looked like underperformance turns out to be capable people who were operating in a vacuum.
A few will not respond even after the investment is made and the path is clear. That is when accountability has teeth. But that decision comes last, after the leadership work is done, not before it.
Invest before you hold accountable
This is the principle the sequence protects. Holding someone accountable to a standard they were never given, with tools they were never provided, is not accountability. It is blame arriving on a schedule.
Investment first is also what makes the eventual accountability credible. When the standard is visible, the equipping is real, and the authority is genuine, the small number of people who still choose not to engage have made a choice everyone can see.
The transition that decides everything
The hardest transition in a technical career is not individual contributor to manager. It is moving from knowing the right answer to trusting the team to find it.
Every engineer who has made that shift recognizes it immediately. Everyone who has not is still wondering why their strongest people keep leaving.
When a team is struggling, look at the leadership before looking at the people. Most of the time the gap is one that someone above them failed to close.
Working principles
- Invest before you hold accountable.
- Evaluate before prescribing.
- Push decisions down and hold the line consistently.
- Judge standards and outcomes, not personalities.