Builder's Notebook
What Engineering Taught Me About Business
Essay
I studied Computer Systems Engineering at the University of Sunderland, and for a long time I thought of that as a credential that qualified me to write software. It took longer to realise it had actually given me something more durable than that: a way of taking a problem apart.
Engineering trains you to think in terms of architecture, dependencies, constraints and failure modes. Before you build anything, you ask what it depends on, what happens when a piece of it fails, and where the actual bottleneck is, as opposed to where it appears to be. None of that is specific to code. It applies just as well to an organisation, a go-to-market plan, or a regulatory process.
When I moved from technical roles into building companies, I didn't set that way of thinking aside. I started pointing it at different objects. A business that isn't growing has a constraint somewhere, the same way a slow system has a bottleneck somewhere. The job is to find the actual constraint rather than the one that's easiest to see, and that's rarely the first thing a founder blames.
It also changed how I think about risk. In engineering, you design for failure modes before they happen, because retrofitting reliability after something breaks in production is far more expensive than building for it from the start. I carried that into how I think about regulation and compliance in financial infrastructure specifically. Treating them as requirements from day one, not features bolted on after a problem appears, is a direct descendant of that engineering instinct.
The honest version of this is that I didn't leave engineering behind when I became an entrepreneur. I started applying engineering thinking to organisations and businesses instead of only to systems. The discipline is the same. Only the material changed.