Engineering organisations often evaluate themselves through the lens of their strongest engineers.
The architect who can debug anything.
The senior developer who knows every subsystem.
The person everyone calls when production misbehaves.
These individuals are valuable. Their presence often keeps fragile systems operating.
Their presence can also hide structural problems.
A system that depends on a handful of exceptional individuals is not necessarily strong. It may simply be surviving through concentrated effort and accumulated knowledge. When those individuals leave, the organisation frequently discovers that the underlying structure was never stable.
A more reliable signal of organisational health appears elsewhere.
Healthy engineering organisations allow ordinary competent engineers to produce excellent work.
Not the exceptional engineers. The normal ones.
The engineers who understand their domain, follow sound practices and collaborate effectively when the surrounding structure allows it.
The behaviour of those engineers reveals whether the system itself is working.
Observations from the field
After many years moving between organisations certain patterns become difficult to ignore.
Some environments produce constant escalation. Decisions stall. Knowledge accumulates in small pockets. Engineers become dependent on a few individuals who understand how the system truly behaves.
Other environments feel noticeably different within a short period of time.
Decisions have clear destinations. Architectural ownership exists. Engineers can reason about the system without needing access to a hidden map stored in someone else's head.
The contrast is rarely caused by superior intelligence. Most engineers across companies are broadly comparable in ability.
The difference lies in how the organisation structures authority, knowledge and responsibility.
The hero illusion
Organisations often celebrate hero engineers.
Heroics feel reassuring because they resolve visible problems quickly. The database is failing. A senior engineer appears, diagnoses the issue and restores the system. The event reinforces the belief that strong individuals are the primary drivers of success.
The reality is less flattering.
Hero cultures frequently emerge when systems are structurally fragile. Documentation is incomplete. Architectural ownership is ambiguous. Knowledge accumulates in isolated pockets because the incentives reward individual survival rather than shared understanding.
Engineers respond rationally to those incentives. Protecting specialised knowledge becomes a form of job security. Complex systems develop guardians rather than maintainers.
Over time the organisation becomes dependent on these individuals.
The heroes did not design the system this way. The structure produced them.
Knowledge and power
Knowledge concentration creates an unusual organisational dynamic.
The engineer who understands a critical subsystem becomes indispensable. Operational stability depends on their presence. Decisions begin to route through them even when their formal authority does not require it.
Influence follows dependency.
This influence is rarely malicious. It often emerges from necessity. The system simply cannot function without the knowledge embedded in that individual.
Yet the effect remains the same.
Architectural decisions slow down. Ownership becomes blurred. Other engineers hesitate to modify systems they cannot fully understand.
The organisation gradually shifts from collaborative engineering to guarded expertise.
Power vacuums
A second structural pattern appears when authority is poorly defined.
When it is unclear who owns architectural direction or who resolves conflicting priorities the organisation produces informal centres of influence. Certain individuals become coordinators, interpreters or intermediaries between groups.
These figures often appear competent because they navigate ambiguity effectively. They understand how to move decisions forward when the official structure cannot.
Their presence is usually a symptom rather than a cause.
Clear authority structures rarely generate these roles. Ambiguous organisations almost always do.
Engineering systems suffer when technical direction becomes dependent on negotiation rather than ownership.
Ordinary engineers as the real metric
Healthy engineering organisations behave differently.
Engineers understand which systems they own. Architectural decisions escalate through clear paths. Knowledge moves through documentation, code reviews and shared operational practices rather than private memory.
Most importantly ordinary engineers can contribute effectively without extraordinary intervention.
A developer joining a project can understand the system within a reasonable time. Changes do not require navigating informal political channels. Production incidents are resolved through established operational procedures rather than the heroic arrival of a single expert.
Competent engineers thrive under these conditions because the structure supports them.
The system itself becomes the source of reliability.
The quiet test of governance
Many discussions of engineering leadership focus on tools, methodologies or development processes.
Governance rarely receives the same attention.
Yet governance determines how authority flows, how knowledge spreads and how decisions resolve when systems become complex.
Poor governance produces hero cultures and knowledge monopolies.
Functional governance produces something far less dramatic and far more valuable.
Ordinary engineers quietly doing excellent work.
The strongest engineering organisations are rarely the ones with the most visible heroes.
They are the ones where competence scales because the structure allows it.
Good systems do not require heroes - they allow ordinary engineers to succeed.