The Frequency

When I think about successfully merging subcultures, I don’t start with trying to create a single “new culture.” I start by designing shared services that force healthy collaboration without erasing identity. I learned this the hard way working across large, mission-driven organizations like Mayo Clinic and the State of North Dakota.

In both cases, you’re not dealing with one culture, you’re dealing with many. Clinicians versus administrators. State agencies versus central IT. Highly autonomous experts who are used to running their own show. If you try to impose a top-down cultural mandate, it fails fast. People protect their identity even harder.

The strategy that worked was building cohesion through shared services with shared outcomes. Instead of arguing about values or norms, we aligned teams around common platforms, processes, and accountability. Identity management, security operations, data services, procurement systems. These were services everyone depended on, regardless of their subculture.

The key was that the services were co-designed. Representatives from each group helped define what “good” looked like, what success metrics mattered, and where flexibility was non-negotiable. That created ownership. People stopped seeing the service as something being done to them and started seeing it as something they were responsible for together.

Cohesion followed naturally. Not because we forced sameness, but because people were solving real problems side by side. Trust grew through delivery. Respect came from seeing other groups operate under different constraints but toward the same outcome. This worked very well across over 200 different teams.

The lesson for me was simple. You don’t merge cultures by talking about culture. You merge them by giving people shared work, shared incentives, and shared wins. Culture catches up to behavior every time.

Look, you can’t just flatten subcultures. That’s a mistake I see leaders make all the time. Instead, you’ve got to treat them like specialized assets. In global engineering, teams naturally cluster around their technical functions or their regional hubs. You have to acknowledge those differences but anchor everyone to a shared delivery framework. We call it building a third culture. It’s basically a neutral ground where we take the best bits from every group and turn them into our global standards. It’s not about losing your identity; it’s about contributing to the master playbook.

If I had to pick one strategy that really moved the needle, it’s what we call Cross-Functional Outcome Pods. We take people from different silos and throw them into small, autonomous units. They’re responsible for one specific feature or one specific client. But here’s the kicker: we tie their bonuses and performance reviews to the pod’s collective success, not their individual departmental goals. When you put people in the trenches together on a high-stakes project, the us versus them mentality dies pretty fast. They stop fighting over whose way is better and just focus on the fastest way to win. It forces collaboration in a way a memo never could.

Managing subcultures is really just about building human trust. You can get buried in the mechanics of governance, but that’s not where the real work happens. People need to feel like their unique perspective is being integrated into the mission, not erased by it. When leadership chooses shared accountability over forced uniformity, the cohesion takes care of itself. The team figures out pretty quickly that they can’t win unless they’re actually aligned.

We had a cultural clash when expanding from our Nepal team to hiring in Australia. Nepal team valued hierarchy and formal communication whilst Australian hires wanted flat structure and casual interaction. Creating tension nobody was talking about openly.

What worked was rotating people through cross-cultural pairing on projects. Nepal developer worked directly with Australian project manager for three months, then we swapped pairs. Forced people to actually understand why the other group worked differently instead of just being frustrated by it.

Stopped being “us versus them” once people saw the other culture’s approach had genuine benefits. Nepal team’s structured process prevented chaos, Australian team’s directness caught problems faster. Both valuable, just different.

Sales-driven and compliance-led cultures butt heads when under stress. It happened frequently in our contact-centre ops. We bridged them by focusing on customer outcomes (not scripts/targets) as the common language across coaching, QA and escalation reviews.

What was most effective was teaching managers to become translators. Explaining why the standards exist, and where wiggle room is OK. Finding that balance maintained identity, fostered trust, decreased conflict and increased consistency at scale.

We’re fully remote across multiple time zones. When you can’t see each other, subcultures form fast. The early hires develop one way of working. The newer people develop another. Neither is wrong, but they start clashing over small stuff.

One thing that helped was killing side channels. We had a pattern where certain people would hash things out privately, then announce decisions. Everyone else felt blindsided. Resented it. Started reading into every meeting they weren’t invited to.

Now, the rule is: if it affects someone’s work, they’re in the conversation. Slows things down occasionally. But nobody’s sitting there wondering what’s being said about them. That paranoia is more expensive than a few extra Zooms.

Merging different subcultures inside an organisation is rarely about forcing uniformity. In my experience, the most effective approach has been creating shared purpose before enforcing shared processes. When teams come from different backgrounds, departments, or even legacy companies, they carry their own habits, language, and informal rules. Trying to standardise everything immediately usually creates resistance, and I have seen tension increase when identity feels threatened.

One strategy that proved particularly effective was defining a clear common outcome that everyone could align behind. Instead of focusing first on how teams worked, I focused on why the work mattered. We organised structured cross-team workshops where each group explained their priorities, challenges, and success metrics. This created visibility. People stopped assuming and started understanding.

After that, we built joint goals tied to measurable results rather than departmental preferences. For example, instead of marketing chasing leads and operations chasing efficiency separately, we aligned both around customer retention targets. Shared metrics changed conversations. Teams began collaborating because success became interconnected.

Another powerful element was rotating ownership on small projects. When members from different subcultures worked together on defined tasks, they experienced each other’s work styles directly. Informal trust developed faster than through top-down messaging.

Language also mattered. We intentionally created a unified vocabulary for reporting and communication. Misalignment often comes from different interpretations of the same terms. Standard definitions reduced confusion.

The biggest lesson I learned is that cohesion grows through shared wins, not enforced rules. When teams achieve something together, barriers soften naturally. Cultural integration is not about erasing differences. It is about connecting strengths under a common direction.

In the end, clarity of purpose, transparent communication, and cross-functional collaboration built stronger unity than any policy document could.