The Rise of Architecture-as-a-Service
From the architect in the room to the architecture engine
My role got reclassified that year into Strategy, Planning & Project — one line on an org chart, but a real signal: architecture had stopped being treated as a technical specialty and started being treated as a strategic capability. This was the year I stopped being "the architect in the room" and became something closer to the architecture engine of the organization.
The volume alone told the story: security-tooling assessments, a print-management platform review spanning DNS and data-protection alignment, cloud site-to-site VPN redundancy, even a review of something as small-sounding as workstation reboot automation, each one run through the same repeatable procedure of interviews, checklists, and formal sign-off. I started authoring templates, beginning with an architecture software-review template, because the real unlock wasn't reviewing more things myself. It was letting other people think like architects too. That's what Architecture-as-a-Service actually means.
I also moved into heavier system-architecture work, an industrial plant-systems design with real failover use cases and data-flow mapping, and earned a seat contributing to the IT Governance Board's quarterly architecture assessment: enterprise strategy now, not operational review.