Technology architecture - Concept
Architect postures
The stance an architect or architecture team takes on a programme — from advising to governing to hands-on delivery
What's it for?
Makes clear how much an architect will advise, set rules, review work or help design it directly.
For example…
On a regulated core banking change, the architecture posture is governance-heavy: review designs and sign off standards, while delivery teams write the code.
On a fast-moving product, the architect takes an embedded posture: joining design sessions and helping teams make decisions rather than only reviewing them later.
Think of it like…
A building inspector who sometimes only checks plans, sometimes sketches structural fixes, and sometimes sits with the crew on site — the posture depends on the job