If you’ve been in tech leadership long enough, you’ve probably heard Conway’s Law more times than you can count. It’s a familiar refrain: your system design mirrors your team structure. But how often has simply recognizing this helped you solve a real problem?
Conway’s Law always comes up when systems break down or organizations try to align their teams. It’s a helpful lens—but it’s rarely the complete answer.
It’s easy to spot when team structures and systems are out of sync. What’s harder is figuring out how to fix it. Too often, we assume the answer is to reorganize—shuffle teams, create new reporting lines, or merge groups in the hope that better alignment will follow.
But reorgs are rarely the magic bullet they seem to be. They’re disruptive, expensive, and come with hidden costs that can outweigh the benefits. They can feel like using a sledgehammer to drive a nail in—overkill for the problem at hand and likely to create new challenges along the way.
Conway’s Law is a great starting point, but it’s not the whole picture. Real-world challenges often reveal that while team structures influence design, it’s the relationships between individuals and teams, the decisions they make, and the context they share that determine whether things truly work.
Relationships are the Missing Link
Sometimes, the problem isn’t team structure. The problem is team interaction.
Weak relationships between teams lead to isolated decisions, creating friction and disjointed systems. Even with the perfect team structure on paper, things can fall apart when teams aren’t collaborating. Miscommunications, assumptions, and a lack of shared context compound, turning simple tasks into avoidable challenges.
What stands out is how much easier things are when teams already have a baseline relationship. When there’s trust and familiarity, teams naturally reach out, ask questions, and close gaps before bigger problems arise. They focus on solutions instead of wasting time second-guessing intentions or navigating formalities.
Not every team has the luxury of strong existing relationships, but even small steps can make a difference. Casual cross-team introductions, shadowing sessions, or informal Slack channels can foster trust without adding unnecessary processes.
It’s not about encouraging communication for its own sake; it’s about creating an environment where people feel confident bypassing red tape and talking to the right person at the right time. With stronger relationships, teams move faster, problems get solved sooner, and collaboration feels seamless instead of forced.
Weak Relationships Lead to Disjointed Architecture
Architecture isn’t just technical; it’s a reflection of how teams interact—or don’t. When relationships between teams are weak, those cracks inevitably show up in the systems they build.
When teams don’t stay connected, decisions get made in silos. People solve for their own priorities, not the bigger picture, and that disconnect starts to creep into the architecture. Over time, this disconnect leads to systems that feel disjointed with misaligned interfaces, redundant components, and unnecessarily complex setups that become difficult to manage.
Take, for instance, a team building a shared data pipeline. Without communicating effectively with the teams that depend on it, they might opt for batch processing. Meanwhile, those dependent teams might need real-time data streams to meet users’ expectations. This mismatch might lead one of those teams to patch together their own solution outside of the data pipeline team’s purview, wasting both time and effort. It’s not about bad intentions; it’s just what happens when teams don’t have strong relationships that tie them together.
When teams stay connected and share context, those gaps close quickly. Decisions align more naturally, and potential misalignments get caught early. Simple check-ins or early collaboration can stop minor misunderstandings from becoming major problems, keeping the system cohesive and easier to manage.
Strong relationships don’t just make collaboration easier—they lead to systems that are simpler, more cohesive, and better able to adapt over time.
Targeted Change Over Big Reorgs
There’s a cost to every reorg that people underestimate. It’s not just about the new structure—it’s about all the hidden disruptions.
The truth is, big reorgs come with massive hidden costs that aren’t always obvious upfront:
- Lost productivity: Teams need time to adjust to new structures and reporting lines, often delaying critical work.
- Damaged morale: Reorgs can leave people feeling uncertain about their roles or frustrated by changes they didn’t ask for.
- Communication breakdowns: Existing channels often need to be rebuilt, leaving teams disconnected during the transition.
- Technical debt creep: Shifting team responsibilities can result in abandoned projects or rushed handoffs, adding complexity to systems.
Even when the intentions are good, the disruption can outweigh the benefits, leaving teams scrambling to fix new problems they didn’t anticipate.
Reorgs aren’t inherently bad, but they should be a last resort when trying to reinforce desired collaboration patterns or architectural changes. Instead of jumping straight to a full-scale reorg, it’s worth asking: is there a smaller, more targeted change that could address the same issue? Maybe it’s giving a specific team more ownership over their system or creating a cross-functional group to tackle a shared problem. These targeted adjustments often solve problems faster without throwing the whole organization into chaos.
We’ve seen situations where leaders took a step back and made one or two precise changes—like shifting reporting lines for a single team or temporarily embedding a specialist into another group. These tweaks didn’t get covered in executive briefs, but they had an outsized impact on alignment and productivity.
Often, the problem isn’t the structure itself—it’s the relationships, context, or ownership within that structure. But when the issue does stem from the structure, a targeted reorg—small, focused changes like shifting ownership, redefining responsibilities, or adjusting team boundaries—can address misalignments without throwing the whole organization into chaos. These smaller adjustments often solve problems faster, saving time, money, and frustration compared to a full-blown reorg.
The Bottom Line
If there’s one takeaway, it’s that successful systems and organizations don’t thrive on structure alone. Relationships matter. Context matters. And alignment—between teams, decisions, and architecture—matters most of all. Context and alignment are all downstream outcomes of strong relationships.
Conway’s Law gives us a valuable starting point, but it’s not the silver bullet. Strong relationships close communication gaps and prevent decisions made in silos. Thoughtful architecture reduces friction and creates space for collaboration. And small, targeted changes can solve real problems without introducing unnecessary chaos.
If you’re exploring ways to improve collaboration in your organization or want to brainstorm ideas, let’s trade notes. Sometimes, the best solutions come from just talking it through.