Becoming a Head of Software Architecture: You are in Charge, Now What?
summary
A new Head of Software Architecture role is shaped into an actionable function: a governance team plus a standards board enforces a service-based architecture and a staged approach to a PHP monolith—encapsulate within the monolith then extract—with decisions logged as architectural decision records and a one‑page A4 strategy. Automation (Terraform, certificate/DB provisioning) reduces friction for rules like encryption. Result: clearer ownership, faster features, lower cloud cost, and an unexpected division adopts the same strategy.
AI-written summary · about
chapters (24)
- 0:00Head of architecture role
- 1:29Architect's core responsibilities
- 3:58Architecting for change
- 7:50System design constraints
- 11:17Translating business and tech
- 13:05Head of architecture duties
- 14:31Technology strategy alignment
- 19:03Governance and standardization
- 25:26New company role shaping
- 27:09Architecture leadership skills
- 30:40Navigating company politics
- 35:18New role expectations
- 37:49Evaluating tools and processes
- 41:18Stakeholder feedback gathering
- 44:24Business goals implications
- 47:30System and team challenges
- 53:33Governance guidelines
- 57:05Architectural decision docs
- 1:01:40Architecture governance team
- 1:04:10Tech strategy and autonomy
- 1:10:35Architecture change obstacles
- 1:15:56Key takeaways
- 1:29:27Answering audience questions on resistance and uncooperative teams
- 1:30:55Closing remarks
related talks
16mEveryone architect!
44mWhen your boss decides to have an architecture team…
14mthe growing role of software architects
45mDemocratising Software Architecture
46mTHE too MANY FACES OF ARCHITECTURE
48mDown the Ivory Tower towards Agile Architecture
27mSoftware Architects and Autonomous Teams
38mPractices for Effective Continuous Software Architecture