Combining the Organisational Structure After a Post Merger: Steps in Role Mapping

When the legal merger closes, the company is left with two charts, two sets of titles, two grade logics and two archives of job descriptions. The question employees ask on announcement day is much shorter: who do I report to, and is my job changing?

The work that answers it is the post-merger organisational structure. It runs alongside the culture programme, but it has its own steps, its own data and its own order of decisions. culture integration after a merger or acquisition sets the shared way of working; the structural side defines reporting lines, position content and headcount decisions. HR owns the process, and senior management sets the principles of the target structure.

This work has two readers, and each brings a different question to the same table. HR builds the position content, the grade structure and the transition timetable. Senior management asks when the result expected from the merger becomes visible: until the structural decisions are settled, synergy targets do not reach unit level, and the longer uncertainty lasts in critical roles, the more client relationships are exposed.

Through Which Steps Is the Post-Merger Organisational Structure Established?

The order of the steps drives the outcome. The work starts with senior management writing down the principles of the target structure: which functions centralise, which business lines carry their own resource, how many grades there will be, and the band the span of control sits in. Without those principles, work that goes straight to position level turns into an argument in which every function defends its own proposal.

In the second step, HR moves both existing structures into one format: title, grade, reporting position, job description, headcount and cost. The task that takes the most time here is working out whether the same title describes the same job in both companies.

The third step maps functions: what each function corresponds to in the target structure, its scope and its reporting line. The fourth maps positions, the fifth covers headcount decisions, and the sixth is the announcement and the transition. Keeping that order means decisions start from the structure rather than from the individual.

On the data side, two rules set the pace. First, a fixed cut-off date: headcount data from both sides is taken as at the same date, and later movements are tracked on a separate list. Second, a single-source rule: the system each field comes from is agreed up front and the table runs in one file. Without them, the discussion drifts from content to which list is correct. The time needed to gather the data goes into the timetable too; where the two sides run different systems, this step alone can take several weeks.

The Method of the Role Mapping Exercise

Position mapping produces a defensible output when it follows a defined method:

→  A common position dictionary: one place recording what each title on either side actually describes

→  Job content: placed side by side at the level of core responsibility, decision authority and process ownership

→  Type of match: one-to-one, partial, and positions with no equivalent in the target structure, each marked separately

→  Grade alignment: grades from both sides expressed in a common band structure

→  Critical roles: positions that must continue because of client relationships, technical knowledge or regulatory duties

→  Succession needs: knowledge areas that rest with a single person

Once the table is complete, the positions in the target structure and the headcount arriving from both sides can be read side by side.

Governance matters as much as method. HR takes the table to a working group with unit managers represented from both sides: each function confirms the matches in its own area, HR consolidates, and open items go up for decision. Partially overlapping positions take up most of those sessions. Where part of a job moves to another position in the target structure, the table records who now carries that responsibility.

Most of the argument in mapping comes from titles. Where the same title sits at a different grade in each company, HR decides on job content rather than on the title: put decision authority, budget responsibility and number of reports side by side, and the band the position belongs to becomes visible. The title is written afterwards.

Sequencing Headcount Decisions and the Announcement

Headcount decisions come after the criteria are written down. HR works to three: the competencies the position requires, experience in the relevant area, and existing review records. With the criteria set at the start, decisions do not have to be justified after the fact, and employees from both sides are assessed on the same measure.

Roles marked as critical get a separate plan. Those people are told early, their place in the target structure is confirmed, and they are given a point of contact for the transition. Where the client relationship and the technical knowledge sit with one person, handing that knowledge over goes into the same plan with dates against it. HR owns the plan; the decision belongs to the senior manager of the function.

The announcement is the second half of this stage. Managers hear before employees do; a manager who does not know the new shape of their own team or its first-period priorities cannot answer questions on the day. The message to employees carries three things: the new reporting line, what changes in the job, and the transition timetable.

Before the announcement, HR prepares a short question-and-answer set for managers: who is moving, what happens to pay where a title changes, how to apply for open positions. Without it, the same question gets a different answer in each unit, and correcting that takes days.

Some roles may stay attached to both lines for a while. Writing down that the arrangement is temporary, the date it ends, and which decision sits with which manager in the meantime takes a good deal of the uncertainty out of the period.

Monitoring the Transition and Reviewing the Structure

After the announcement, the administrative steps go onto a timetable: recording the new reporting lines in the systems, updating approval flows and authorisations, reissuing job descriptions under the new position names, and sharing the chart as a single file. An owner and a date against each item keeps the transition from running open-ended.

The post-merger organisational structure is not finished at the announcement. Over the first six months HR watches four indicators: positions whose mapping is unfinished, how open positions are filling, continuity in critical roles, and the topics employee questions cluster around. That last one points straight at what the announcement left out.

The table is read again at day ninety and day one hundred and eighty. The output usually falls under three headings: updating job descriptions, correcting imbalances in the span of control, and closing the temporary dual reporting arrangement. With unit managers in the room, the corrections are considered alongside how the work actually runs.

Throughout the transition there is one current chart in the company, and HR owns it. Once units start circulating their own copies, the question of who reports where opens up again in every meeting.

For senior management, this work puts the expected result of the merger on a timetable. Until the structural decisions are done, synergy targets do not reach unit level and the budget discussion runs on the sum of two structures. To see how we design post-merger structural work, you can look at our corporate transformation consulting service.

At Kaan Böke Yönetim Danışmanlığı, we bring 35+ years of corporate experience and 25+ years of C-level leadership perspective to strategic, applicable solutions. To build the post-merger organisational structure and run the role mapping exercise in your company, get in touch.