Every position here is a working one. These are not marketing statements. They are the views that shape how engagements are run and how technical decisions are made.
The foundation
Sixteen Pillars operates across sixteen domains — the technical and organisational disciplines that determine whether a business’s technology is an asset or a liability.
The common thread is that technical decisions are never purely technical. A data model encodes how an organisation understands its own business. An architecture encodes what the organisation values — speed, reliability, security, maintainability. A governance framework encodes how the organisation behaves when nobody is watching.
Getting these things right is not a software problem. It is a leadership problem. It requires someone in the room who understands both the technology and the business consequences of technical decisions.
The Data First position
Every engagement starts with the data model.
This is not a preference. It is the result of consistent observation: most of the significant technical problems an organisation carries — fragmented systems, compliance gaps, architecture nobody fully controls, integrations that break — trace back to data that was never properly defined or governed.
The data model is the foundation. Everything built on top of it inherits its properties — good and bad. Getting it right at the start changes every decision that follows.
The governance position
Governance is not what happens during an audit. It is what happens when nobody is watching.
A well-governed technical function does not look different under scrutiny than it looks on a normal Tuesday. The policies are operating. The standards are being applied. The owners are accountable. The data is what it claims to be.
Most organisations have governance documentation. Fewer have governance that operates. The gap between the two is where technical risk lives.
The first principles position
The fundamentals of computing have not changed since the 1980s. Data structures, logic, constraints, systems thinking — these are not concepts that were superseded by modern frameworks and cloud infrastructure. They are the basis on which modern frameworks and cloud infrastructure are built.
Most of the problems that appear in enterprise systems appear because someone stopped working from first principles and started working from assumptions about what the framework would handle. It rarely handles it.
The writing
What follows is an ongoing record of positions, observations, and analysis. Written from practice, not theory.
Projects without a reference point
June 9, 2026
Most organisations do not have a technology problem. They have a direction problem. The technology works, after a fashion. Projects get approved and delivered. Tools get purchased. Systems get built. And yet the organisation finds itself unable to change quickly, unable to scale cleanly, unable to answer a simple question about its own data without
You cannot enumerate the vectors
June 9, 2026
Every organisation builds its threat model around what it knows. The perimeter is defended. The known entry points are monitored. The obvious risks are documented. And somewhere in the building, a guest WiFi network has its password written on a card in reception, and an accounts database is sitting open on the internal network because
BI should be a query, not a project
June 9, 2026
When your taxonomy is right, business intelligence falls out of the data naturally. Someone asks a question. The system answers it. The answer is consistent, trusted, and repeatable. The dashboard is a view, not an assembly exercise. Most organisations do not have this. They have something that looks like it from a distance — reports,
A constraint that moves isn’t a constraint
June 9, 2026
Every organisation has rules nobody can source. “It must be Windows.” “The creative team only work on Macs.” “We don’t use open source.” Stated with the authority of policy, enforced with the consistency of law, and — when you ask where they came from — traceable to nothing more than habit, a long-departed IT manager’s
Complexity by permission
June 9, 2026
Enterprise systems are usually simpler than yours. That is not what most people expect to hear. The assumption is that large organisations are where complexity lives — layers of process, legacy decisions, accumulated technical debt. And they have all of that. But they also have something smaller organisations rarely develop: someone whose job it is
The system nobody will touch
June 9, 2026
You know the one. It runs. It has always run. Nobody touches it. Not because it is well-built. Because touching it is dangerous. Somewhere in your organisation there is a server — probably Windows, probably MSSQL — running software that was built during a growth phase and never properly maintained after that phase ended. The
