Thinking

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.