What we’ve learned from watching giants merge.

Over the past two decades, REDspace has had the privilege of working alongside some of the most talented teams in media, often during moments of enormous change.

 

Mergers like CBS and Viacom, Warner and AT&T, and others are never easy, but they are also where some of the most impressive collaboration, resilience, and creativity we’ve ever seen tends to emerge. We’re proud of the role we’ve played inside these organizations and grateful for the trust placed in us during periods when the stakes were high and the outcomes deeply visible.

 

From the outside, these mergers are framed as bold strategic plays. From the inside, they feel more like rebuilding a jet engine at 30,000 feet while passengers keep buying tickets – and asking when wi-fi will be faster.

 

Here’s what actually happens. What goes better than expected, what goes worse, and what it really means for engineers living inside the blast radius.

Part 1. What goes better than you’d think

 

 

1. The urgency is real

 

Mergers create an unmistakable sense of now-or-never. Budgets that were frozen for years suddenly thaw. Decisions that once bounced between committees get made in days. Entire teams are told, “We’re consolidating platforms. Pick something and go.”

 

For companies like REDspace, this is when transformation actually becomes possible. Not because leadership suddenly became visionary, but because politics are temporarily suspended by necessity. Everyone knows the clock is ticking.

 

Recommendation: Create a 90-day decision fast lane with named owners and a 72-hour SLA. Urgency only matters if decisions can’t be re-litigated.

 

 

2. Innovation windows briefly open

 

During mergers, nobody truly owns anything for a while. That weird vacuum creates opportunity.

 

We’ve seen the following:

• New streaming architectures greenlit that would have died in pre-merger bureaucracy.
• Legacy systems are questioned for the first time in a decade.
• Engineers are suddenly allowed to try tools, workflows, and vendors that were previously off-policy.

 

It doesn’t last forever, but while it’s open, it’s often a great chance to improve efficiency in a meaningful way.

 

Recommendation: Time-box a 30-45 day sprint to replace or bypass one untouchable legacy system. The goal is proof, not perfection.

 

 

 

3. Relationships suddenly matter more than org charts

 

In the chaos, people stop relying on process and start relying on people they trust. This is where long-standing partnerships shine.

 

At REDspace, many of our strongest moments didn’t come from contracts or RFPs. They came from someone inside the newly merged company saying, “I need help, and I know you’ll just get it done.”

 

In situations like this, when things absolutely need to get done, trust becomes a currency as pure as gold.

 

Recommendation: Identify the 5-10 people who actually unblock work and invest in them weekly. In a merger, trust is infrastructure.

Part 2. What goes worse than anyone admits

 

None of what follows comes from bad intent. In fact, it usually emerges from capable people trying to protect teams, systems, and decisions that once made sense.

 

 

1. Allegiances don’t disappear. They harden.

 

Every merger comes with two (or more) tribes. The legacy people on the acquired side, and the legacy people on the acquiring side.

 

While people may now share a logo, their loyalties remain deeply personal. Careers, friendships, grudges, and reputations do not reset on merger day.

 

As a result, teams naturally advocate for the platforms they know best. Decisions are framed as technical, but driven by history. Neutral ideas are sometimes seen as existential threats. In many cases, those allegiances exist because people built something they were genuinely proud of. Protecting it isn’t political — it’s personal. This is rarely malicious. It’s human.

 

In this environment, leadership team members who can remain genuinely objective are disproportionately valuable. They aren’t defending past architectures or protecting historical wins. They’re trusted precisely because they optimize for the future state, not the legacy narrative. When those leaders are visible, teams are far more willing to accept difficult decisions.

 

Recommendation: Run all major platform decisions through mixed legacy teams and require joint sign-off, so no group(s) feel decisions are being done to them.

 

 

 

2. The squeeze in the middle

 

Executives merge. Front-line engineers keep shipping. But middle management often gets crushed in between.

 

We’ve watched talented directors and VPs lose their mandates overnight, be told to collaborate with former competitors who now sit across the hall, and spend months re-pitching their own existence.

 

That pressure trickles straight down into engineering. Priorities shift, rewrites appear suddenly, and the ground never quite feels stable.

 

Recommendation: Within 30 days, reissue written mandates for every director and VP: scope, decision rights, and what they no longer own. Ambiguity is the enemy.

 

 

 

3. Technical debt explodes

 

Everyone talks about synergies. What that usually means in practice is, “Can we duct-tape these two incompatible universes together before earnings season?” (The answer is usually “yes” followed closely by “we’ll clean it up later.”)

 

APIs collide. Workflows double. Identity systems don’t align. Toolchains overlap. No one has time to clean anything because the roadmap is now a political artifact.

 

The result is not transformation. It is an accumulation of risk, complexity, and invisible fragility.

 

Recommendation: Create a merger-specific “integration debt backlog” with executive visibility and funding, reviewed monthly alongside financial KPIs.

Part 3. The reality on the ground for engineers and what you can do

 

While mergers are exhausting, they are also some of the fastest accelerators of professional growth we’ve seen. Engineers who navigate them well often emerge with skills that compound for years.

 

 

 

1. You will inherit things you didn’t choose

 

You will be asked to maintain systems you disagree with, integrate platforms you would never have architected, and support tools whose creators no longer work there.

 

This is not a failure of leadership. It is the unavoidable tax of corporate gravity.

 

Recommendation: Document what you inherit on Day 1. Identify potential ownership gaps, known risks, and “do-not-touch” areas. Socialize the list early to reset expectations before blame begins to appear.

 

 

 

2. Your job becomes 40 percent engineering, 60 percent translation

 

Suddenly, your real value is not just in what you build, but in what you interpret.

 

Translating business urgency into technical reality. Explaining technical constraints in a politically safe way. Helping teams from different corporate histories find shared language.

 

The engineers who thrive are not the loudest or the smartest. They are the ones who can bridge worlds.

 

Recommendation: Write a translation memo: what the business is asking for, what’s technically possible, what’s risky, and what trade-offs are being made.

 

 

 

3. Relationships become your true leverage

 

During mergers, processes are broken. Titles are fluid. Budgets are uncertain.

 

What remains stable are relationships.

 

Practical advice. Invest time in people, not org charts. Learn the history behind the systems you’re touching. Who built them, and why? Do not pick sides publicly. Be a connector, not a champion of one legacy.

 

The engineers who are remembered after the dust settles are the ones who made others successful.

 

Recommendation: Proactively build a cross-legacy contact list and check-in monthly with each person to unblock their work, not yours.

The takeaway

 

At REDspace, working alongside giants like CBS, Viacom, Warner, and AT&T has taught us that technology rarely fails during mergers. Relationships do. The companies that survive are not the ones with the best roadmaps, but the ones that manage trust across old boundaries.

 

And for the individual engineer, the real career skill is not mastering the next framework. It is learning how to navigate ambiguity, complexity, and allegiances while still shipping great software.

 

We’ve seen mergers succeed – not perfectly, but meaningfully – when teams choose curiosity over defensiveness, relationships over rigid process, and progress over legacy pride.

 

Those moments are why we keep saying yes to this work.