Preparing Your Architecture Work for a Reorganisation
Reorganisations arrive with little warning and plenty of anxiety. Teams are merged, managers change and priorities shift. For architects, the risk is twofold: the work they have done may lose its sponsors, and the knowledge they hold may be lost in the shuffle. Yet architecture can also be a stabilising force, because it describes what the organisation does regardless of who reports to whom. These steps help you protect the value of your work when structures change. None of it requires special tools, only a few conversations, some tidy notes and the willingness to start before the announcement lands on everyone’s desk.
Separate the capabilities from the org chart
Make sure your models describe what the organisation does, such as handling claims or planning deliveries, rather than which department does it. Capabilities survive a reorganisation; boxes on a chart do not. If your diagrams are tied to team names, take time now to restate them in terms of activities that will continue whoever owns them.
Record who relies on what
List the services, data and decisions that each team depends on. When teams merge or split, these dependencies are where things break. A simple table of provider, consumer and agreement can prevent weeks of confusion. Share it with the people leading the change, who often lack visibility of such links.
Capture the reasons behind decisions
New managers will ask why things are the way they are. If the reasons exist only in people’s heads, they may be lost or reinvented. Gather the main decisions of the past year with a sentence of context each. This short record helps newcomers respect good choices and question weak ones fairly.
Get Oliver Selmon’s stories in your inbox
Join Medium for free to get updates from this writer.
Offer a clear picture to leaders
Leaders planning a reorganisation need to understand the consequences. Offer a one-page view showing which capabilities and systems will be affected by different options. Present it as support, not as an attempt to steer the outcome. Being useful in this moment strengthens trust and shows the practical value of architecture.
Keep communication steady
During change, rumours spread quickly. Keep your own communication calm, regular and factual. Share what you know, say what you do not know yet and give a date for the next update. Colleagues remember who stayed steady when others were unsettled, and that reputation lasts well beyond the reorganisation.
Look after your own position
Think about what you want from the change and talk to your manager early. Keep your skills visible and your relationships warm. If your role shifts, treat it as a chance to broaden your experience. Taking small, deliberate steps in the Succeed Fast spirit keeps you adaptable.
Use the change to remove clutter
A reorganisation is a rare moment when people accept that things will be different. Use it to retire documents that nobody reads, merge duplicate lists and simplify approval steps that have outlived their purpose. Doing this with the new owners, not behind their backs, builds goodwill and leaves a cleaner foundation for the next phase of work.
Keep learning through the change
Periods of change are a good time to invest in practical skills. A hands-on enterprise architecture workshop can give you fresh techniques and peers to compare notes with, and you can see the options on the EACOE website. Start by updating one diagram so that it describes capabilities rather than teams.
