InsightsLeadership & Culture

Your last reorganisation changed the chart and almost nothing else.

By Uttam Dinodia1 min readView this post on LinkedIn

The product shipped the same way, because the conversations never moved.

Around 2002, Amazon was one tangled system. Teams broke each other's code and waited on each other to ship.

Jeff Bezos issued a blunt internal mandate. Every team would expose its work through interfaces, and could connect only through them. The memo reportedly ended: comply, or be fired.

The mandate looked technical. Its real effect was on who had to talk to whom.

The architecture followed. Years later, those same interfaces became Amazon Web Services.

In 1968, computer scientist Melvin Conway observed something now called Conway's Law: any organisation that designs a system produces a copy of its own communication structure. Three teams that barely speak build three parts that barely connect.

Microsoft and Harvard researchers later put numbers on it. How far apart two teams sat predicted defects better than how complex the code was.

It was written about software, but it holds for everything a company builds. Your customer journey is shaped like your org chart. So is your reporting. The handoffs that frustrate customers are usually the gaps between two teams that do not talk.

This is why most reorganisations disappoint. They move boxes on a slide and leave the real communication lines where they were.

A company does not choose whether its structure shows up in its product. Only whether it put it there on purpose.

Which seam in your product is really a gap between two teams?

Uttam Dinodia

Uttam Dinodia

Pharmaceutical Business Consultant & Executive Director, A One Afro Limited

Over 22 years in pharmaceutical supply. Helps international manufacturers and Zambian institutions with public tenders, ZAMRA regulatory pathways and distribution.