How a Company Retreat Can Rebuild Team Alignment After a Reorganization

1 October 2026by Chris Meier

A reorganization can be complete on paper but take longer to feel complete to the people working inside it. Reporting lines change. Teams combine. Responsibilities move from one person or department to another.

Even once the new org chart goes live, people are often still figuring out who owns what, which decisions they can make, and how their work now connects with colleagues they barely worked with before.

Which is why team alignment is one of the most important jobs after a reorganization. And a company retreat or team offsite can give you something that another org chart presentation or company-wide email cannot: enough shared time to work through what the new structure means.

The goal isn’t to persuade everyone that the reorganization was the right decision. It’s to help the reorganized team understand how work gets done now.

A new structure doesn’t create team alignment by itself

Most reorganizations are necessarily designed at an organizational level. Leadership decides which teams sit where, who reports to whom, where responsibilities belong, and how the new structure supports the company’s priorities.

Then the people inside that structure need to make it work.

McKinsey’s 2024 research on organizational transformation makes the team-level problem much clearer. Changing the structure is only part of the work. The new organization still depends on teams understanding what they are responsible for, how they work with other teams, and how decisions get made. That is where a post-reorganization retreat can be useful. It can give people time to turn a new structure into practical ways of working.

The gap between the formal structure and everyday work is where many post-reorganization problems appear.

Someone inherits responsibility for an area but not all the information or authority they need. Two teams assume the other owns a decision. A manager continues approving something that now belongs elsewhere. Teams brought together under one leader still work as separate groups because nobody has changed the routines around them.

These aren’t necessarily signs that the reorganization failed, but they do mean that people need time to translate structure into behavior.

And a company retreat can give them that time.

Use the company retreat to answer what changed for this team

Senior leaders may have spent months discussing a reorganization before it is announced. Most employees haven’t.

They are entering the conversation much later.

After a reorganization, people usually want to know how the change affects their own work. Who do they report to now? What decisions can they make? What has moved into or out of their role? Gallup’s research on disruptive organizational change reinforces the need for frequent communication and opportunities for employees to be heard, with managers helping people understand what the change means for them.

This creates a useful starting point for a post-reorganization team offsite.

Nobody needs senior management to spend half the company retreat presenting the rationale again. What they need is enough context to understand the decisions, followed by opportunities to bring the conversation closer to their own work.

People need to leave understanding things such as:

what their team is now responsible for
which responsibilities moved elsewhere
where ownership is shared
which people or teams they now depend on
what decisions they can make themselves
where decisions need to be escalated
which priorities have changed because of the new structure

Some questions will be straightforward. Others may expose issues leadership hasn’t resolved yet, but this is useful information too. It is better to identify an unclear responsibility while 30 people are in the room than after three teams have spent a month working around it.

Make role clarity part of team alignment

Telling people that their job title hasn’t changed doesn’t necessarily mean their role hasn’t changed.

A reorganization can alter somebody’s day-to-day work without changing their job title. They may have new stakeholders, fewer approval steps, more cross-functional responsibilities, different priorities, or a new manager who expects decisions to happen differently.

And the first company retreat after a reorganization is a good place to make those changes visible.

Map responsibilities around the work

Start with the work the reorganized team is expected to deliver. For each important area, establish:

Who owns the outcome?
Who needs to contribute?
Who makes the final decision?
Who needs to be consulted before that decision?
Who needs to know once the decision has been made?

The exact framework you follow is less important than the answers. And pay particular attention to work that crosses the old organizational boundaries. If marketing and product now share an objective that previously sat mostly with one team, for example, having both state they’ll collaborate more closely isn’t enough. Instead, decide what each side owns and where the handoffs happen.

Establishing this type of role clarity is less about an HR exercise and more about preventing duplicated work, stalled decisions, and frustrated colleagues.

Find the new dependencies before they become bottlenecks

Changing an org chart often creates relationships that didn’t exist before. A team that could previously complete most of its work internally may now depend on another department for data, approval, technical input, or customer information. Two previously separate teams may suddenly share resources, and a central function may now support several business units instead of one.

But what looks perfectly sensible in the reorganization plan can still cause trouble in day-to-day work. So, use part of the company retreat for teams to identify the work they need from others and what others now need from them. Focus on real workflows rather than broad statements about collaboration.

For example:

“We need finance approval before these proposals can go out.”
“Customer success now needs product input before committing to implementation dates.”
“Regional teams need the central marketing team to supply campaign assets two weeks earlier.”
“This decision now moves from the functional lead to the business-unit lead.”

Once those relationships are visible, you can discuss where response times, information, or decision rights are unclear. This makes cross-functional collaboration more practical, since people can see where their work connects rather than being told to “break down silos.”

Build new working agreements for the reorganized team

A reorganization is a good reason to revisit the team’s working agreements. Agree how people will communicate, collaborate, run meetings, and make decisions in the new setup. If the team has changed, some of the old ways of working may no longer make sense.

Decide how the team will communicate

Keep this discussion practical.

Which information belongs in Slack or Teams? What needs an email? Which decisions should be documented somewhere permanent? When does a problem need a meeting rather than another message thread?

If the reorganization has combined teams from different parts of the company, don’t assume they already use the same conventions.

One group may make decisions in meetings and record very little afterward. Another may work asynchronously and expect a written record of almost everything. Neither approach automatically becomes the new standard because the teams now share a manager.

Agree what will work for the new group.

Decide how decisions will be made

Changing reporting lines often changes decision-making even when nobody explicitly talks about it.

Name the decisions the team makes regularly and decide who now owns them.

You don’t need a governance framework for every minor choice. Concentrate on the decisions that are currently slow, disputed, duplicated, or repeatedly escalated.

People should know when they have authority to move ahead and when somebody else needs to be involved.

Revisit the meeting rhythm

A combined team doesn’t need to inherit every meeting from the teams that came before it.

Review the existing calendar together. Keep the meetings that still serve a clear purpose, drop the ones that don’t, and decide where the reorganized team needs a new forum.

Atlassian’s State of Teams research found that teams often struggle with unclear goals, competing priorities, and different ways of planning and tracking work. A reorganization can bring those differences into sharper focus when previously separate teams suddenly need to work as one.

Use the review to agree where different kinds of work, decisions, and updates should happen, rather than adding meetings by default.

Make team alignment a working session

A post-reorganization retreat can easily turn into a very expensive all-hands meeting.

Leadership presents the new structure. People listen. There’s a Q&A. Everyone goes for dinner. And then very little changes by the time they return to work.

If team alignment is the purpose, people need to do some of the work themselves.

That means building sessions around specific decisions and outputs rather than broad discussion prompts. Instead of asking, “How do we feel about the new structure?”, ask the group to identify the three handoffs that currently cause the most confusion and decide how each one should work.

Instead of “Any thoughts on communication?”, give teams a draft set of communication norms and ask them what needs to change.

And when you need input from a larger group, use a format that gives more people a chance to contribute. We’ve written about structuring discussion at a team offsite using the 1-2-4-All method, which moves people from individual thinking into progressively larger group discussions.

After a reorganization, that structure can be particularly helpful when senior leaders and individual contributors are discussing the same changes.

Don’t use the company retreat to pretend every concern has disappeared

A reorganization can involve difficult decisions. Some people may have lost colleagues, taken on responsibilities they didn’t ask for, or found themselves working in a structure they’re still getting used to.

A team retreat shouldn’t try to manufacture enthusiasm. Give people room to raise genuine operating concerns, but keep the discussion focused on the parts of the new setup the team can clarify or improve.

You may not be able to revisit the reorganization itself. You can, however, resolve uncertainty around ownership, approval routes, responsibilities, and how teams are expected to work together.

Keep bringing the conversation back to what the team can make clearer, change, or test.

Turn discussions into agreements people can use

The most valuable output from a post-reorganization retreat probably won’t be a slide deck.

It will be a short record of how the team has agreed to work.

Before people leave, capture the decisions you have made. Depending on the reorganization, that might include:

responsibility and ownership changes
important cross-team dependencies
decision rights and escalation routes
communication channels and expectations
meeting changes
immediate priorities
unresolved questions and who will answer them
a date for reviewing the new working agreements

Assign an owner to anything that needs follow-up.

For unresolved issues, record the question rather than writing something vague such as “leadership to review.” Name the person responsible and when the team can expect an answer.

Treat the working agreements the same way. They don’t need to be permanent. Once the reorganized team has worked within the new setup for a while, revisit them and adjust anything that isn’t working.

A reorganization creates a new starting point. Some problems will only become obvious once people are back in their day-to-day work.

Measure whether team alignment improved after the company retreat

A good post-reorganization retreat should produce changes you can observe later.

Don’t measure success by whether attendees enjoyed the destination or thought the sessions were interesting. Those can be useful event-planning signals, but they won’t tell you whether the reorganized team works better.

Instead, decide in advance what should be different several weeks later.

For example:

fewer decisions are being escalated because ownership is clearer
a recurring cross-team bottleneck has been removed
people can explain the team’s top priorities consistently
responsibilities that previously overlapped now have clear owners
the new communication and meeting agreements are being used
teams know who to involve when work crosses organizational boundaries

You can then check what has changed after people have had time to work within the new setup.

As with any team offsite, measure success by what changed afterward, rather than relying only on the immediate post-trip reaction.

For a reorganized team, the test is simply whether people are spending less time figuring out how the new organization works and more time getting work done within it.

Plan the company retreat around the work the reorganization created

A post-reorganization retreat doesn’t need to be three days of workshops.

People still need breaks. They need informal time together, particularly when previously separate teams are meeting as one group for the first time. Shared meals and activities can create conversations that would never appear on the agenda.

But the company retreat should have a clear job.

The reorganization changed how people are expected to work together. Use the time away from everyday calendars to make those expectations understandable, find the places where the structure is still unclear, and agree on practical ways of working.

If you’re planning a company retreat after a reorganization, we can help you find the right setting for the conversations your team needs to have. From accommodation and meeting spaces to transport, meals, and activities, a Retreat Specialist can help you plan the logistics around the work you want to get done. Schedule an intro call.