What engineering leaders should measure, balance, and build.
Everyone wants a high-performing engineering team.
Ask what that means and the answer often collapses into a proxy:
More output. Faster delivery. Fewer defects. Higher engagement. Strong individual ratings. A team that always gets things done.
Then ask how high performance should be measured, and the proxy becomes the target.
Activity is rewarded as impact. One strong individual hides collective weakness. A delivery metric becomes a judgment about the entire team. A short period of exceptional output becomes the expected baseline.
Leaders cannot evaluate or build high performance until they answer two questions:
- Whose performance are we discussing?
- What evidence would demonstrate it?
This article focuses on team performance.
A high-performing engineering team fulfills its mission consistently and predictably, uses resources responsibly, adapts to change, becomes progressively more capable, and improves the wider system around it.
Start by naming whose performance
Performance needs a unit.
Individual performance means fulfilling a role and creating the expected impact. It includes outcomes, behaviors, judgment, autonomy, and alignment with the principles of the team and organization.
As someone becomes more senior, their contribution should extend beyond personal execution. They improve decisions, systems, standards, and the performance of people around them.
A high-performing individual may elevate colleagues who want to grow. They may also carry work when others cannot or will not contribute at the required level. That effort can protect an important collective outcome and demonstrate significant individual impact.
When carrying others becomes the operating model, it also reveals collective dependency.
Leaders should recognize exceptional contributions accurately without allowing a team result to hide persistent individual gaps. They remain responsible for hiring well, developing people, and acting decisively when someone repeatedly fails to meet the standard.
Team performance evaluates something different: what a group of interdependent people becomes capable of achieving together.
Define performance before measuring it
Team performance is the ability to fulfill its mission.
A team performs when it delivers the expected business outcomes within the relevant constraints of quality, time, cost, and scope.
This separates performance from activity.
Lines of code, completed tickets, deployments, meetings, and hours worked describe what happened. They demonstrate performance only when connected to an outcome the team exists to create.
High performance is the ability to fulfill that mission consistently and predictably, using resources responsibly, while learning, adapting, increasing future capability, and positively influencing the surrounding environment.
A team that produces the same mediocre result repeatedly is consistent, not high-performing. A team that protects its capacity but fails to create meaningful outcomes is sustainable, not high-performing. A team that delivers exceptional results but cannot learn or adapt has achieved something important, but its capability remains limited.
High performance does not mean continuously exceeding every expectation. If extraordinary output becomes the minimum accepted level, it is no longer extraordinary. It is simply an unsustainable baseline.
Software engineering offers useful performance models, although none completely defines a high-performing team.
The SPACE framework establishes that developer productivity cannot be captured through one metric or dimension.
DORA measures team-level software delivery performance through five metrics covering throughput and instability. It also warns against allowing one metric to become the target or comparing teams operating in different contexts.
SPACE focuses on developer productivity. DORA focuses on software delivery. Team high performance requires a wider view.
High performance is built through balance
A leader needs evidence across six dimensions:
- Results: Did the team fulfill its mission and produce meaningful business outcomes?
- Execution: Did it deliver with the expected quality, predictability, and use of resources?
- Consistency: Can it sustain results without depending continuously on heroics or favorable circumstances?
- Adaptability: Does it respond effectively to change, problems, and new information?
- Future capability: Are its people, processes, technology, and decisions becoming stronger?
- Influence: Does it help improve the people, teams, and wider system around it?
High performance is often presented as the product of relentless pressure. People push harder, sacrifice more, and tolerate unhealthy conditions in pursuit of an exceptional result.
I do not believe high performance requires degrading people. I believe it is built through balance.
Balance does not mean comfort, lower ambition, or equal attention to everything. It means understanding which dimension needs attention, which trade-off is acceptable, and what cost must be addressed.
Strong results and healthy working conditions can coexist. DORA’s research associates continuous delivery with stronger software delivery performance and quality, lower burnout, higher job satisfaction, and better organizational culture. This does not define complete team high performance, but it challenges the assumption that engineering performance must come at the expense of people.
Balance also exists between people.
Different backgrounds, cultures, perspectives, personalities, skills, and areas of expertise give a team more ways to understand and solve a problem. Difference alone does not produce performance. A shared mission, trust, and accountability turn those differences into complementary contribution.
This is the purpose of Balanced Engineering Leadership. Value, speed, quality, and sustainable execution help leaders navigate the trade-offs involved in delivering meaningful results. The six high-performance dimensions reveal the capability produced through those decisions over time.
When one dimension is maximized by repeatedly weakening people, quality, capacity, standards, or trust, the team accumulates execution debt. Balance prevents today’s result from quietly compromising the next one.
Turn evidence into a leadership decision
After a meaningful delivery or performance period, run a Capability Review.
- Record the result
State the mission, expected outcome, what was achieved, and which constraints mattered.
Separate completed output from the change it produced. The value evidence introduced in The Value Gap provides a useful sequence:
Output → Usage or adoption → Change → Business outcome → Impact
- Examine the evidence
Review the six dimensions using relevant qualitative and quantitative evidence.
Where did the team demonstrate strong performance? Where is the conclusion based mainly on perception, assumption, or one favorable result?
- Identify enablers and fragilities
Identify the skills, behaviors, decisions, practices, and systems that helped produce the result.
Then expose what depended on heroics, concentrated knowledge, excessive effort, favorable circumstances, deferred quality, or unresolved individual performance gaps.
Preserve accurate individual recognition. A team result should not erase meaningful differences in contribution.
- Strengthen one condition
Choose the fragility that creates the greatest risk or the capability that offers the greatest improvement.
Define one action, assign an owner, and select an observable signal for a future review.
End the review with a decision
The review should produce:
- result supported by evidence;
- enabler to preserve;
- fragility that should not become the baseline;
- owned action;
- signal that will show whether capability improved.
The review turns the result into an input for a concrete leadership decision instead of another retrospective observation.
Build capability and earn the reputation
Reputation matters. It influences trust, credibility, opportunity, and how much autonomy a team or leader receives.
The strongest reputation is built on results that can be explained, repeated, and improved.
Recognize the results. Appreciate the specific behaviors and effort that generated them. Give exceptional individual contributors accurate credit. Address the gaps that collective success might hide.
When the intended result was not achieved, effort alone should not be presented as performance. Recognize learning only when it changes what happens next.
Ask:
- What did we learn?
- What decision, behavior, or practice will change?
- When will we examine the evidence again?
Without changed action and follow-up, “we learned” is only a statement.
A peak shows the highest point a team has reached.
High performance is the capability to keep producing meaningful results, adapt when conditions change, and leave the team and its surroundings stronger through the work.