Every morning at 6:15, before the coffee kicked in, before anyone checked email, before anyone even said good morning — we stood in front of the board.
Five letters. Big. Color-coded. Red or green. That was it. No slide decks. No "let me pull up the metrics." Just the board, hanging on the wall at the entrance to the plant floor, telling you the truth about your operation whether you wanted to hear it or not.
S. Q. D. I. C.
Safety. Quality. Delivery. Inventory. Cost.
I was twenty-four the first time I stood in front of one. Honeywell. Night shift had just handed off. The board was mostly green — except Safety, which was red. Someone had tripped over a hose that shouldn't have been there. No injury, but a near-miss is a red. Period. No debate, no "well technically," no "but nobody got hurt." Red.
The shift supervisor didn't flinch. Didn't make excuses. Just said, "We left a hose across a walkway. We fixed it. Here's what we're doing so it doesn't happen again." Thirty seconds. Done. Next letter.
That stuck with me in a way I didn't fully understand until years later.
Here's the thing about the board that took me a long time to appreciate: it's a set of boolean questions. Each letter gets exactly one answer. Red or green. Did anyone get hurt or nearly hurt? Red or green. Did we ship product that met spec on the first pass? Red or green. Did we hit our delivery targets? Red or green. Is work-in-progress within acceptable limits? Red or green. Are we operating within budget? Red or green.
There is no yellow. There is no "trending in the right direction." There is no "it depends on how you measure it."
Red. Or green.
That level of clarity is uncomfortable for people who are used to narratives. You can't spin the board. You can't reframe a red as a "learning opportunity" while you're standing in front of your entire crew at shift handoff. The board is the board. It says what it says.
But here's what most people miss — the boolean is the starting point, not the answer. Green doesn't mean "stop paying attention." Red doesn't mean "panic." The real work is the questions you ask after you see the color.
Safety is red. Okay — what systems were involved? What's the blast radius if it had gone worse? Who reviewed the procedure, and did they understand the domain well enough to catch it?
Quality is red. Okay — what failed first-pass? Was the spec clear before production started, or were we building to a moving target? What's our first-pass yield telling us about the process, not just the product?
Inventory is red. How much finished work is sitting in a queue waiting for someone to look at it? What's the oldest thing in that pile? Is our production rate outpacing our ability to review and ship?
The board gives you the boolean. You bring the curiosity.
I think about the board a lot these days.
Not because I'm still on a plant floor — though some mornings, wrangling a fleet of coding agents feels eerily similar to managing a production line. Same questions, different medium. And when I built my own board — the one I actually use now — I changed more than the letters. I changed the colors.
Not red and green. Red and blue.
It sounds small. It isn't. Green is what the plant floor gave me, and I'm grateful for it. But green belongs to that world — to chemical reactors and shift handoffs and hoses across walkways. When I sat down to build a board for software, for the work we do every day, I wanted it to look like us. Blue is the color of the craft. It's the color of the discipline. When a metric lights up blue, it means we did the work and it held. When it lights up red, it means we have work to do.
Same boolean. Same honesty. Different house.
So here's what my board asks every day:
Did anything we shipped today cause harm? Blue or red. Was every layer locked down — least privilege, keys protected, access boundaries clear? Blue or red. Was it validated against a spec that a human actually wrote and understood? Blue or red. What's our first-pass yield on work coming off the line — how much of it is shippable without revision? Blue or red. How much work is sitting in a pile, unreviewed, right now? Blue or red. What's the fully loaded cost — including rework, review time, and the work that didn't happen because we were sorting garbage? Blue or red.
Six questions. Six booleans. No yellow.
I added a letter, by the way. The original board has five. Mine has six.
Security.
In manufacturing, safety and security blur together. They're both about "don't let bad things happen." But in software, they're distinct concerns with distinct disciplines. Safety asks: could this code hurt someone if it fails? Security asks: is every layer locked down? Least privilege? Keys protected? Access boundaries clear?
They're both boolean questions. They both demand the deeper inquiry after the color. But they require different expertise, different reviews, different muscle memory. Collapsing them into one letter is how you miss things. And missing things in either category is how you end up on the news.
So my board reads S-S-Q-D-I-C. Six letters. Six booleans. Six sets of questions that earn the right to light up blue.
The discipline was never the board itself. The board is just paint and magnets — or pixels and a deploy pipeline. The discipline is showing up every morning, standing in front of it, and owning what it says. Not explaining. Not reframing. Owning.
Blue means you did the work. Red means you have work to do. Both are fine. Both are honest. The only unacceptable color is the one you didn't bother to check.