Company World Models: How 1,000 Engineers Stop Playing Telephone

2,000 years of organizational design was information routing built for human limitations.

The Roman Army invented span of control. Prussia invented middle management. McKinsey codified the matrixed organization. Spotify tried squads. Zappos tried holacracy. Valve tried flat hierarchy.

Every one of those experiments reverted to hierarchy at scale because there wasn’t a tool that could replace what those layers did.

Until now.

Conway’s Law is crushing you

Conway’s Law says organizations design systems that mirror their own communication structure. Your information flow determines your product quality.

If your org fragments learning across Slack threads, Jira tickets, Confluence pages, and people’s heads, your product reflects that fragmentation.

You’ll ship the wrong thing faster.

Design has their personas. Product has their PRDs. Engineering has their architecture docs. Sales has their battlecards. Nobody has the full picture.

The product mirrors that fragmentation. If you work in enterprise software, you feel this every day.

Learning at the edge decays instantly

Here’s how it actually works in practice:

Product, design, and research go learn from the territory. They talk to users. They observe behavior. They come back and build artifacts — personas, journey maps, storyboards, research readouts.

And those artifacts start decaying the moment they’re created.

They live in a wiki that nobody visits. In a Confluence page last edited in 2023. In someone’s head — and when that person takes a new job, the learning goes with them.

The map is not the territory. And the deck you made last year does not survive first contact with the market this year. Especially when the technology underneath shifts every day.

Every function sees different terrain

Every function learns from the territory through a different lens:

Design learns the user journey. Product learns the market opportunity. Engineering learns the technical constraints. Sales learns what makes someone sign.

Each function has a subjective view of the territory. Each one builds their own map.

The old model: those maps are fragmented. Siloed. Design, product, engineering, and sales each maintain separate artifacts that rarely cross-pollinate. When they do, it’s through meetings — which is just hierarchy’s information routing at work.

The new model: a continuously evolving map that everyone contributes to simultaneously, from their own subjective lens. Same substrate, different perspectives. The map gets richer every sprint because every function adds what they learned.

Design adds user behavior observations. Product adds market signal. Engineering adds technical constraints and decisions. Sales adds what closed and what didn’t — and why.

The company self-model

This is what a company world model is: a shared substrate where subjective learning from every function compounds into a unified, continuously updated understanding of the territory you operate in.

It’s the same self-model primitive that powers customer world models — but pointed inward.

Where the customer world model asks “what does this user believe and want?”, the company world model asks “what does this organization understand and how does it coordinate?”

Both are models of self. Both compound. Both run on the same substrate.

What this looks like in practice

At Dayforce, I helped improve AI adoption across 1,000+ engineers from 15% to over 50% in two months.

The key wasn’t better tools or more training. It was instrumenting where execution breaks down — not just where code ships.

Where were engineers hitting walls with AI-assisted development? Which teams had figured out effective patterns? Where were the handoff failures between design intent and engineering implementation? What did the teams that shipped fast actually do differently?

Traditional hierarchy can’t route this information fast enough. By the time a pattern is identified in one team, documented, reviewed, and distributed through management layers, the context has shifted.

The company self-model captures these patterns in real time, across every team, from every function’s perspective. The learning compounds automatically.

The enterprise imperative

If you’re a VP of Engineering at an enterprise software company, here’s what’s at stake:

Your product is a reflection of your org. If learning is fragmented, so is the product. Your competitors — or the frontier labs — will build a coherent version faster.

Your people are your sensing network. Every IC who makes contact with customers, code, or market signal is generating learning. If that learning stays in their head, it walks out the door when they do.

Your coordination is your competitive advantage. Not your features. Features are plugins now. Your ability to learn faster and coordinate better than the frontier labs — that’s the moat.

The company world model doesn’t replace your people. It amplifies them. It gives every function a shared substrate to contribute to and draw from. The map stays current. The learning compounds. Conway’s Law works for you instead of against you.

Start with Sprint Zero

Sprint Zero diagnoses where your organizational learning breaks down. In 4 weeks, we map the gaps between what your teams know and what your product reflects.

If the coordination is there, we show you how to compound it. If it’s not, we build the substrate.

Find out where your learning breaks down →

---

This post is part of the SaaSpocalypse Survival Guide series.