Yeah, that's a really good point. There is no "one-size fits all solution" to how an architecture team should be composed (if it should exist at all for a company) nor is there an easy answer for how it should operate.

I really like this though:

> software architecture is about making certain you have as few tools as possible, to do a job, with the flexibility to accommodate other tools, when necessary.

This really resonates--one thing I've noticed is a growing complexity of like-systems and finding ways to reduce unnecessary complexity seems like it could be very beneficial for any organization.