The Whiteboard That Ran the Company
Sometimes the most important system in an organisation isn't in the tech stack. It's a whiteboard in a corridor that nobody official put there.
I was walking through the operations floor of a logistics company last year when I noticed something odd. There was a whiteboard next to the kitchen, covered in scribbled names, arrows, and colour-coded magnets. It looked like organised chaos.
“What’s that?” I asked.
The ops manager laughed. “That’s how we actually run the place.”
Turns out, the company had a perfectly good project management system. Licences paid, dashboards configured, training completed. Nobody used it. Instead, every morning, the shift leads would gather around this whiteboard and sort out the day. Who’s covering what. Which trucks are delayed. Which client is about to escalate.
The whiteboard had no version history, no audit trail, no API integrations. It also had no login screen, no permissions model, and no twelve-step workflow to update a status. You just walked up and moved a magnet.
The informal system always wins
This isn’t unusual. In almost every organisation I’ve spent time in, there’s an informal system that does the real coordination work. A shared spreadsheet that’s become mission-critical. A WhatsApp group that moves faster than the ticketing system. A weekly catch-up that isn’t on any org chart but is where the actual decisions get made.
These systems emerge because they solve a problem the formal system doesn’t. Usually speed, but sometimes trust, context, or just the simple ability to say “this is broken” without filling in a form.
The interesting question isn’t whether informal systems exist. They always do. The interesting question is what they tell you about the gaps in your formal systems.
What the whiteboard was actually saying
That logistics whiteboard was telling a story, if you knew how to read it. It was saying: your project management tool assumes stable, predictable work streams, but our reality is volatile and exception-heavy. It was saying: the people who need to coordinate are all in the same room, so a tool designed for distributed teams adds friction without adding value. It was saying: the information that matters changes every four hours, and your system updates once a day.
None of that was a failure of the people. It was a failure of fit.
Don’t kill the whiteboard
The temptation, especially for new technology leaders, is to eliminate these informal systems. They’re ungoverned. They’re a risk. They don’t feed into the reporting layer. All true.
But killing the whiteboard without understanding why it exists is how you get compliance without coordination. The formal system gets used because it has to be, and the real coordination just goes underground, into DMs, side conversations, and the car park after work.
If you find a whiteboard running your company, don’t replace it. Study it. It’s the most honest piece of organisational design you’ll find.