Skip to content
Book a demo Get Started

You Bought a Company. Now Whose Org Chart Wins?

Nathan Evans

Neither. Put the company you bought on your map exactly as it is, next to your own, and let the two grow together one role at a time. That is how integrations really happen.

Imagine a Swiss company called Roncieux. It machines high-precision parts and runs on roles: the work is split into small, clearly owned responsibilities, and people hold several of them across teams. Last year it acquired a German firm, Gebrüder Haldner, a family business making precision parts for surgical instruments, run the same way for three generations.

Haldner is organized the traditional way. There is a managing director at the top, a couple of department heads below, and the workshop below them. A clean pyramid. Everyone knows their box and their boss. It has worked for the family for decades.

So now there are two companies under one roof, and two completely different ways of organizing. The question everyone asks first is a blunt one: whose org chart wins?

Our answer is: neither, at least not on day one. The integrations that work don’t pick a winner. They put both organizations side by side, connect them, and let them merge over time, one role after another. Since Peerdom 5.3 you can do exactly that on a single map.

The two ways this usually goes wrong

Force the new company into your structure on day one. You bought Haldner, so Haldner now works the Roncieux way, effective immediately. New teams, new titles, new vocabulary. The trouble is that the people who have made those surgical parts for thirty years suddenly cannot find themselves on the map. The thing you paid for, their know-how, walks out the door with the third person to quit.

Leave them completely alone. The other reflex is to promise you will integrate “later.” Later rarely arrives. Two years on there are still two companies, two systems, and none of the shared strength the deal was supposed to create. You own Haldner on paper and nothing has actually joined up.

Both mistakes come from the same missing thing: nobody can see the two organizations together, so every integration decision is made in the dark.

Put the company you bought on your map, as it is

Before you change anything, add the acquired company to your own map as one group. Do not tidy it. Do not translate it into your way of working. Just make its real structure visible, next to yours.

Haldner is a hierarchy, so it should look like one. In Peerdom 5.3, a group can draw its own branch in its own layout: set the Haldner group to Org Chart in its Design tab, and it shows as the org chart its people know, right inside the Roncieux map. Roncieux keeps its bubbles. One map, two ways of organizing, both honest.

The Roncieux SA map in Bubble layout. The acquired company Gebrüder Haldner sits inside it as a gold round frame with its org chart drawn inside, next to the Roncieux groups Metrology, Regulatory Affairs, Management, Production, Quality and Supply Chain Day one: Haldner joins the Roncieux map as the org chart it is

Zoom in, and Haldner reads exactly as before: the managing director, then Production, Administration, Quality and Purchasing, each with its head and its people.

Close-up of Gebrüder Haldner drawn as an org chart inside its round frame: Managing Director at the top, then Production with CNC Machinist, Head of Production and Polisher, and Administration, Quality and Purchasing below, each with two roles and the people in them Nobody at Haldner has to look for themselves: their structure is on the map as they know it

Two useful things happen the moment you can see it. Nobody at Haldner feels erased, because their structure is on the map as they know it. And you now look at both companies in one picture, instead of comparing two mental models that never quite line up. That alone takes a lot of the heat out of the “whose way wins” fight.

Merge them over time, role by role

With both structures on one map, integration stops being one enormous decision and becomes a series of small, obvious ones.

You can see where the two overlap. Both companies have quality control. Both do purchasing. Those are the places to decide, deliberately, whether to merge, keep separate, or share. You can see what is unique to Haldner, the parts of the craft worth protecting exactly as they are. And you can see the seams, the handful of roles where the two companies actually need to connect.

Run the integration work as projects across the whole organization. Here, one project builds a single quality system for both companies. Select it, and the map draws lines from the project’s outline to every role involved, in the Roncieux bubbles and in the Haldner org chart alike.

The Roncieux SA map with the project "One quality standard" selected: one outline runs around the whole map, and lines run from it to quality roles in the Roncieux bubbles and to two rows in the Haldner org chart. The project panel lists its six colleagues, with Nathalie Brandt as leader The integration project runs around both companies, with lines to the roles on each side

Then move one role at a time, at a pace the acquired team can absorb. When Haldner’s inspector joins the Roncieux quality group, you drag that one role across. The org chart gets a little smaller, the shared structure a little larger, and everyone can watch it happen. Some parts of Haldner may merge within months. Others, like a workshop that works best as a hierarchy, may keep their org chart for years. Both are fine, because both are visible.

With Time travel in Peerdom+, you can later go back through weekly snapshots of the map and see how the two companies grew together.

This is what really happens in successful integrations: not a winner on day one, but two organizations that slowly become one. The same pattern carries larger organizations that run a hierarchy and a network side by side for good, which we describe in Every Organization Is Two Organizations.

Model the change before you commit to it

Reorganizing a company you have just bought is a nervous business, and it is easy to get wrong when you are guessing. It helps to sketch the next step as a draft first, a proposed map that nobody works from yet, and look at it before anyone’s job actually moves. You can try merging the two quality functions on paper, see who ends up accountable for what, and adjust, all before a single real change lands on a real person.

What to do if you are integrating an acquisition

  1. Add the acquired company to your map as one group, exactly as it is today. Draw it as the org chart it is. Change nothing yet.
  2. Compare the two structures in one picture.
  3. Find the overlaps, the unique strengths, and the few real seams between them.
  4. Run the integration work as projects across both companies, and move one role at a time at a pace people can absorb.
  5. Draft big changes first, and look at them before they touch anyone.

The goal is not to decide whose org chart wins. It is to keep what you bought while the two companies genuinely grow together, and you can only do that if you can see both of them clearly, on one map.

Common questions

Should the acquired company adopt our structure? Eventually, in the parts where it makes sense, and gradually. On day one, no. Forcing an overnight change is the fastest way to lose the people and the know-how you just paid for. Start by putting both structures on one map, then integrate role by role.

The two companies organize completely differently. Isn’t that a problem? Only if you hide it. Since Peerdom 5.3, a hierarchy and a role-based organization can sit on the same map, each drawn in the layout that fits it: an org chart for one and bubbles or circles for the other. Seeing the difference honestly is what lets you decide what to merge and what to leave.

When does the acquired company’s org chart go away? When it no longer describes how its people work. As roles move into the shared structure, the org chart shrinks. Once you no longer need it, switch the group back to the organization’s layout. Some parts may keep their org chart for good, and that is fine.

How do we avoid losing key people during integration? Keep their world recognizable while things change. When people can still find themselves and their responsibilities on the map, a reorganization feels like careful adjustment instead of erasure. Moving one role at a time, visibly, beats a single overnight redesign.

What is a living org chart? It is a map of your organization that shows roles and responsibilities, not just names and titles, and that teams keep up to date themselves. In an acquisition it lets you hold two structures on one map, compare them honestly, and integrate them one clear step at a time.

Roncieux and Gebrüder Haldner are illustrative examples, not real Peerdom customers. They stand in for the kind of acquisition where a role-based company takes on a traditional family firm, so the pattern is easy to follow.

Answer six questions and get your org chart, free

Keep reading