OrgOS · Transparent Org Tooling

Transparency did the managers' job — until two hundred people broke it.

The whole thing runs on transparency: salaries, finances, project assignments, reviews — open to everyone. That holds at forty. At two hundred, the hallway stops scaling. What lives in one person's head stays there, and the org grows a quiet hierarchy to route around the gap.

The ask said design tooling for a 200-person company with no management layer. The actual ask: build coordination that doesn't smuggle a hierarchy back in through the side door. Every obvious feature — task assignment, approval flows, escalation paths — was a manager wearing a different name. The job was saying no to each one.

Here the user base and the org structure were the same two hundred humans. So every design decision was an organizational one — there was no other kind. Get a screen wrong and you don't ship a bug; you reintroduce the boss the whole company was built to do without.

The safe features all had a manager hiding inside them.

Every coordination tool ships the same defaults: assign the task, route it for approval, escalate when it stalls. Each one quietly puts somebody above somebody else. Build them and the org chart grows back overnight — just rendered in software instead of titles. The thing that made the company itself would have died in the tooling meant to support it.

So the real deliverable was never a feature list. It was a coordination model that could carry two hundred people without ever electing a router — and the discipline to refuse every feature that smuggled one back in.

I made transparency do the coordinating — pull, not push.

The one decision: replace assignment with visibility. Who's on what, who's blocked, who decides — visible to everyone, always. Pull, not push. Commitments, not assignments. Nobody hands you work; you see what's open and you pick it up. Eight modules — staffing, comp, OKRs, onboarding — all spoke one object model, so the org could rebuild its own process with nobody in the room to arbitrate.

The commitments board below is the clearest version of it. An open ask sits there until someone chooses it — flip transparency off and you watch the coordination disappear with it, identities blurred, the board gone quiet. That switch is the whole argument in one control.

What it cost: transparency only coordinates if people trust it enough to act.

Making the work visible was the easy half. Getting two hundred people to actually pull from an open board — instead of waiting for the manager who no longer existed — was the hard half. A board nobody trusts is just a prettier inbox. The design wasn't done when the screens shipped; it was done when people believed the screens enough to commit on their own.

A model that's right but unadopted is indistinguishable from one that's wrong. The trust layer is the product.

Most coordination tooling fails the same way: it makes information available and assumes people will act on it. They don't — not until the system has earned it. That's the check I run on every AI product now. The model being correct is table stakes; whether anyone trusts it enough to move is where the real work lives.

The interesting part is how transparency replaced the org chart.

Out of respect for the client's confidentiality, the artifacts stay off the public page. Details are confidential; I'll walk through the artifacts and numbers on a call under mutual NDA.

Design Patterns Demonstrated

This project is a detailed case study in designing for human-in-the-loop decision-making at scaled organizational settings:

• Human-in-Loop Patterns: Decentralized peer leveling, transparent company salary setting, and collaborative project prioritization bidding workflows.