The Whiteboard Bubble
Your CEO read an article. Apparently some startup made a billion dollars and they attribute it to whiteboards. Whiteboards on wheels. Whiteboards in every room. A culture of whiteboarding.
So now it's Q1 and the mandate comes down: whiteboard usage is a KPI. Every team needs to be using whiteboards. We're buying 50 of them. This is the future.
Here's what happens next.
The junior dev is thrilled. They grab a marker and start doodling. Architecture diagrams everywhere. Boxes connected by arrows. There's a box labeled "Auth" and a box labeled "Database" and a box labeled "AI Magic" and it all flows together beautifully.
The CEO walks by, sees the junior dev frantically whiteboarding, and thinks: now that's initiative—give this kid a promotion.
Meanwhile, the senior engineers stare at the board and feel their souls leave their bodies. "Auth" is not a box. Auth is a nightmare of edge cases, token expiration, refresh flows, role-based access control, and six months of security audits. But it's on the whiteboard, so it must be a box.
The skeptical manager refuses to participate. "We have notebooks," they say. "Notebooks are permanent. Notebooks are searchable. Anything on a whiteboard gets erased and lost. This is a fad."
Their team isn't allowed to whiteboard. Some of them want to. They've seen what the good whiteboard users can do—the ones who actually think through problems, sketch out possibilities, iterate fast. But their manager said no, so they sit at their desks and watch.
The metrics-driven manager goes all in. Their entire team is whiteboarding constantly. Usage is through the roof. The CEO sees the numbers and gives them a raise.
What the CEO doesn't see: the whiteboards are covered in nonsense. Flowcharts that don't flow. Architectures that would collapse under their own weight. People drawing exponential growth curves for the company, as if drawing the curve makes it happen.
But hey—whiteboard usage is up 300%.
The cracked engineer uses the whiteboard exactly right. They sketch out the authentication system, think through every edge case, diagram the data flows. It's beautiful. Then they erase it and move on to the next thing.
Three weeks later, no one remembers what they decided. The nuance is gone. The details are gone. The cracked engineer has it all in their head, but they're the only one, and they're about to go on vacation.
The process person sees everyone else whiteboarding and figures they should too. They don't really understand what makes a good whiteboard session, but they watched someone draw flowcharts once, so they draw flowcharts.
The flowcharts are technically correct. They're also completely useless. Every box is hand-wavy. Every arrow skips the hard part. But it looks like the whiteboard is being used correctly, so no one says anything.
Here's the thing about whiteboards: they're a lever, not a solution.
A whiteboard lets you externalize your thinking. It lets you sketch fast, iterate fast, get ideas out of your head and into a space where other people can see them and push back.
But the whiteboard doesn't think for you.
If you don't understand your problem, the whiteboard will just reflect your confusion back at you—in boxes and arrows, looking very official.
If you skip the hard parts, the whiteboard won't fill them in. It'll just show a box labeled "Auth" where six months of work should be.
If you draw an exponential growth curve, you haven't created growth. You've created a drawing.
The people getting real value from whiteboards aren't using them because the CEO mandated it. They're using them because they already know how to think through problems, and the whiteboard accelerates that process. They frame the problem before they pick up the marker. They know that everything they draw needs to be verified. They bring people over to challenge their diagrams, not to admire them.
The whiteboard doesn't replace the thinking. It amplifies it. Good thinking becomes great. Bad thinking becomes a mess that everyone now has to take seriously because it's on the whiteboard.
So before you mandate whiteboard usage across your company, ask yourself:
Have you taught people how to think through problems? Or just told them to use a new tool?
Have you created a culture where someone can say "that diagram is wrong" without getting fired? Or does being on the whiteboard make an idea untouchable?
Are you measuring whiteboard usage or whiteboard value?
Because the companies that actually got a billion dollars from whiteboards? They didn't get it from the whiteboards. They got it from people who already knew how to frame problems, articulate tradeoffs, and think clearly—and the whiteboard just made that visible.
You can't buy that at Office Depot.
Oh, and everywhere I said "whiteboard"?
I meant AI.