Systems That Do Not Require Heroes
Why healthy engineering organisations allow ordinary engineers to do excellent work
Governance determines whether engineering systems depend on heroes or enable ordinary engineers to succeed.
Engineering organisations often evaluate themselves through the lens of their strongest engineers.
Structural Design for Technical Organisations
A working articulation of the structural principles I use when operating in technical leadership roles.
The Crank The Code Structural Operating Model
What Actually Causes an Unstable Product Roadmap
Roadmap instability is rarely about estimation. It is about authority.
What Actually Causes an Unstable Product Roadmap
Crystalline
A forensic lens applied to decision architecture
Architecture
Reducing option space as a leadership discipline
The CTO’s job is to reduce option space so effort compounds rather than fragments.
Decision compression as a leadership discipline
The cost of directional instability
Frequent direction changes erase structural compounding even when output appears strong.
Direction changes destroy compounding
Why acceleration outlasts speed
Acceleration, not raw speed, determines whether organisations truly scale.
Speed is visible. Acceleration is structural.
When authority makes merit visible
Meritocracy is produced by explicit decision boundaries not cultural encouragement.
Meritocracy is not a cultural value
Structure is what allows speed to persist
Early authority design increases startup velocity rather than slowing it.
Speed collapses without structure
The structural cost of delegation without authority
Delegating responsibility without decision rights is structural harm not empowerment.
Delegation without authority is organisational harm
Designing authority as a primary CTO function
The CTO’s primary work is designing authority not generating ideas.
Authority design is the CTO’s primary work
Designing junior pipelines in an age of AI
If junior pipelines are structural capacity then they must be deliberately designed rather than culturally assumed.
Designing junior pipelines in an age of AI
Junior pipelines are structural not sentimental
Removing junior pipelines optimises short term output while increasing long term structural risk.
Junior pipelines are structural not sentimental
Authority mapped to decision type
Decision authority should be designed around decision type not job title.
Design authority around decision type not role title
Decision load as a structural signal
If the CTO is making too many decisions the operating model is leaking authority.
If the CTO is making too many decisions
An operating model for when the CTO role is working
When authority is aligned, the CTO role collapses into a small number of quiet functions.
When the CTO role stops being busy
When roles reach their natural end
Some roles exist to disappear once the system stabilises.
Roles designed to vanish
When escalation paths are implicit
Exposure to requirements is not the same as authority over them.
Requirements without resolution
When discovery cannot be timeboxed
Some organisations need certainty before they can tolerate discovery.
When certainty is required before it exists
Why programme management still absorbs blame
Programme management often carries accountability without decision authority.
Accountability without authority at scale
When work is delegated without definition
Delegation fails when responsibility travels further than definition.
When responsibility outruns meaning
Risk aversion, displacement and the cost of entrepreneurial ideas
When organisations cannot tolerate risk, they often relocate it instead.
When ideas are recognised but not owned
When leadership is a by-product
Leadership that has to be encouraged is usually compensating for something else.
When leadership is not the goal
When competence becomes a liability
Competence often hides the very problems organisations need to see.
When competence becomes a liability
The things that never happen
Some of the most expensive organisational failures never produce a metric.
What never appears on a dashboard
Special circumstances
Some organisational problems cannot be solved from inside the hierarchy that created them.
When normal mechanisms stop working
Decision latency is the performance problem
Slow decisions shape slow systems long before runtime behaviour is discussed.
Where performance really slows down
Why performance begins with how teams think
Performance problems begin with product decisions and organisational behaviour long before code exists.
Why organisational behaviour matters more than tools
The architectural mistakes you make before the first profiler runs
The decisions that lock in latency long before there is anything to measure.
Where latency really gets decided
When more data stops changing the answer
What happened when I stopped arguing with intuition and ran the model one hundred thousand times.