I didn’t set out to become a systems architect. In fact, I didn’t even know that’s what I was becoming. There was no grand plan, no formal training, no moment where someone handed me a title. It happened the same way most systems failures happen: slowly, then all at once.
What I did have was a habit. Whenever something broke — a workflow, a process, a piece of software, an organisation — I couldn’t leave it alone. I needed to understand why. Not the surface‑level “why,” but the structural one. The hidden one. The one nobody sees until it’s too late.
Most people move on when something fails. I map it.
I started noticing patterns. The same failure modes appeared everywhere: unclear ownership, mismatched incentives, brittle assumptions, invisible dependencies, and the classic “we built this fast and hoped it wouldn’t collapse.” Different domains, same architecture problems.
I wasn’t trying to fix things. I was trying to understand them. But understanding inevitably leads to repair, and repair inevitably leads to design. Eventually I realised I wasn’t just analysing systems — I was architecting them.
Not officially. Not ceremonially. Just… functionally.
I became the person who could see the structure beneath the mess. The person who could explain why something was breaking and what would happen next. The person who could redesign the thing so it wouldn’t break again.
People started asking me questions that only architects get asked.
“Why is this happening?”
“How do we stop it?”
“What should this look like instead?”
“What’s the underlying pattern here?”
I didn’t have a job title for it. I didn’t need one. The work defined itself.
Over time, I realised that “systems architect” was simply the most accurate description of what I was already doing. Not in the traditional enterprise sense — no UML diagrams, no formal frameworks, no ivory‑tower abstractions. More like: the person who sees the real structure beneath the chaos and can articulate it clearly enough that others finally understand what they’re dealing with.
I didn’t choose this role. It emerged from the way I think.
This blog is where I map those patterns.
Not to complain about broken systems, but to understand them.
Not to point fingers, but to expose the architecture beneath the failure.
Not to be clever, but to be clear.
If you’ve ever looked at a collapsing process, a failing institution, or a chaotic piece of technology and thought, “This shouldn’t be happening,” you’re in the right place.
I became a systems architect by accident.
Maybe you did too.