Lead a combined org when the two sides run on opposite tempos.
Help people leaders lead a combined org when one side runs on urgency and speed and the other on structure and rules, so cultural friction and redundancy anxiety do not become the unmanaged operating system.
The combine is done on paper. One side still ships on urgency. The other still ships on rules. Each side already has a story about the other: too fast and no structure, or slow and bound to process. People are asking who is redundant. Home managers do not have an answer they can say out loud.
Stay on that clash. This is not a post-merger integration cadre. This is not an inherited coaching stack to continue or fold. This is not a named-change cohort, and it is not a CEO-transition funding roadmap. The job is to keep opposite tempos from becoming the unmanaged operating system.
If managers cannot say what is true yet, the hallway will write the org chart for them.
Two clocks, one org chart.
Operator pattern, not a cited sample. Two shops are now one. The fast side believes structure is delay. The structured side believes speed is sloppiness. Both are trying to protect work they already know how to do. That reading is a judgment from the floor, not a culture score, and not an integration maturity model we will invent.
A deal leftover that still has a coaching invoice is a different decision (inherited coaching after an acquisition). Incoming and outgoing CEOs aligning what to fund is a transition roadmap (leadership development roadmap during a CEO transition). Come back here when the chairs are filled and the two clocks still insult each other.
Each side already has a story.
Operator view: the structured shop calls the other reckless. The urgent shop calls the first bureaucratic. Those stories show up in standups, in whose template gets used, and in who gets invited to the real meeting. A named-change cohort will rehearse the insult if you have not written the tempos as facts (change-tied leader cohorts).
Post-combine culture also shows up as busyness and muddy promotion rules (busyness as success, raises vs promotions). Channel rules help only after people know which clock they are on (distributed team communication norms). Transitions need resilience, not a second catalog (resilience during transitions).
Not a PMI costume. We will not sequence workstreams, integration workbooks, or a 100-day close curriculum. If you need that binder, you are on a different job. This page is the week the two clocks already collided.
Redundancy is the hallway OS.
People will not wait for the clean chart. They will ask their manager who is overlapping, whose role survives, and whether last year's work still counts. Home managers often do not know. Pretending everything is fine is its own cost (the hidden cost of pretending you are fine).
Specialist identity that refuses the new work is a cousin, not this page (specialist to generalist). A vision that dies one layer down is a cascade failure (when CEO vision dies at the pod GM). Stay here when the unmanaged system is tempo plus redundancy talk.
What this is not.
| If you are actually deciding | Go here instead |
|---|---|
| A live coaching stack arrived with the deal | Inherited coaching after an acquisition |
| Managers need a cohort around a named change they can already explain | Change-tied leader cohorts |
| Incoming and outgoing CEOs must align what to fund | LD roadmap during a CEO transition |
| Busyness became the promotion rule after the combine | Busyness as success, raises vs promotions |
Inheritance is continue, expand, or fold. A named change you can already brief is a change-tied cohort. Come back here when the two clocks are the fight and managers have no sentence for the hallway.
Give managers a sentence they can say.
Write the two tempos as facts, not insults
Urgency-and-speed is a way of shipping. Structure-and-rules is a way of shipping. Put both on one page with what each side is trying to protect. If the first artifact is a values poster, you already lost the week.
Give home managers a line for questions they cannot answer
They will be asked who is staying, whose process wins, and whether their job still exists. A true "we do not know yet, here is who decides, here is when" is better than a cheerful shrug. Silence is how redundancy anxiety becomes the operating system.
Coach the clash in the live week, not after the chart freezes
The chart will stay messy. The hallway will not wait. A room for the managers who sit between the two clocks is the work. Do not wait for a clean PMI plan that never arrives.
TOGETHER can hold the managers who sit between the two clocks. SCALE can hold a parent-owned manager layer once the tempos are named. Do not buy either as a silent PMI substitute.
What good looks like. A manager can say what each tempo protects, who decides overlap, and when the next true answer lands. If the only change is a "we are one team" slide, the hallway is still the operating system.
Name the two clocks before the hallway writes the chart.
Bring the two tempos, the redundancy questions managers cannot answer, and who decides overlap. We will map a sentence and a room. We will not write a PMI binder.
Book a strategy callFrequently asked questions
Two orgs just combined and each side hates the other's pace. What do people leaders do first?
Name the tempo clash out loud and give home managers a sentence they can use when they do not have answers. One side will call the other reckless. The other will call the first slow. If you leave that unlabeled, redundancy anxiety becomes how the combined org actually runs.
Is this a post-merger integration playbook for coaching?
No. We will not write a PMI cadre or a 100-day integration curriculum. The job is the live week after a combine: opposite operating tempos, and managers who cannot tell their teams what is true yet.
Should we decide the inherited coaching program at the same time?
That is a different fork. Inherited coaching is continue, expand, or fold a stack that arrived with a deal. Come back here when the fight is how work moves, not which vendor invoice survived closing.
Is a change-tied leader cohort the fix?
Not as the first move. A named-change cohort assumes you can already tell managers what the change means. Here they do not have that sentence. Write the tempo rules and the redundancy answer first. A theme cohort will only rehearse the insult.