System Thinking & Architecture
Seeing patterns, dependencies, and consequences across the whole enterprise, not just the system directly in front of you.
System thinking is the discipline that connects every other domain here. It began as a quiet shift in 2014, when I noticed that incidents repeated because of shared root causes rather than bad luck, and matured through the TOGAF-driven architecture lens of 2018 and the scaled Architecture-as-a-Service model of 2022 into the enterprise-strategy altitude of 2026.
How the thinking works
- Recognizing recurring patterns and systemic root causes instead of treating each incident in isolation
- Operating at two altitudes in the same conversation: enterprise strategy and technical execution
- Enterprise Architecture frameworks (TOGAF-informed principles, review processes, checklists and templates)
- Teaching architectural thinking to other teams rather than being the sole gatekeeper
- Designing for the risk a decision creates three years out, not just whether it works today
Why it matters
Architecture is not the diagrams or the documents. It is the thinking that produces them, and a lot of that thinking is mediation: a project timeline pulling one way, a security requirement pulling another, an infrastructure constraint neither side wants to hear about.
Moving between the smallest technical detail and the largest strategy question without dropping either is the whole skill. I am still not consistently good at it.