Sometimes architecture is simply a discussion, a dialogue, not necessarily a diagram or architectural artefact.
It’s not only about just transformation or change initiatives. You may achieve more by cancelling a change initiative through meaningful discussion – walking through the current landscape, the technical debt it might bring and the size of investment vs ROI.
Architecture is an engagement.
You might get frustrated that people don’t understand architecture, so take time to explain and show them how they benefit from using architecture and architectural thinking.
Make them part of architectural decision-making.
To borrow from ‘Doing EA’, what can architects do to navigate the situation –
“This architecture stuff doesn’t make sense” – so we need to find ways in which it does make sense for them.
“It doesn’t apply to our context” – so we need to show where it applies, and why.
“It’s just theory” – so we need to show how it works in practice.
“No-one bothered to ask us” – so we need to show where it does take their experience into account.
“We don’t have time for this stuff!” – so we need to show why they don’t have time to not do “this stuff.”
How are you navigating resistance to architecture engagement in your context? Happy to learn your perspective.

