Here we are again, my friends, back for another installment of Dear Lewis.
One of my clients is Greg (not his real name). He’s a VP at a fast-growing tech company. His team is sharp, the kind of engineers other companies fight over. And they cannot hit a deadline to save their lives.
“Lewis, I’ve got a whiteboard in my office with every project date on it,” Greg told me. “Half of them are crossed out and rewritten. Some three times. I don’t get it. These people are brilliant. Why can’t they finish on time?”
I asked him what he’d already tried.
“Everything,” he said. “Daily standups. A shared Gantt chart everyone can see. I started calling out slipped dates in the all-hands, gently, just to keep people honest. I even built in extra buffer time so a small slip wouldn’t blow up the whole roadmap.”
“And?”
“It got worse.” Greg rubbed his eyes. “People started padding their estimates so hard that a two-week task turned into a five-week quote. Nobody wants to be the one called out on the whiteboard, so now everyone just says whatever protects them. We’re slower than before, and I trust the dates even less.”
This is the part where most advice tells you to tighten the screws. More check-ins. Harder consequences. A better project management tool. I told Greg none of that would work, because he wasn’t solving the real problem.
“Greg,” I said, “your team doesn’t have a discipline problem. Your deadlines don’t mean anything, so their brains have stopped treating them as real.”
He blinked. “They’re literally on a whiteboard.”
“Sure. But what happens on this date,” I said, pointing to one of his crossed-out lines, “if the team hits it?”
Silence.
“And what happens if they miss it?”
More silence. Nothing happened either way. No customer saw it. No contract depended on it. No consequence landed. The date was just a number Greg wrote down because a VP is supposed to write dates down.
Here’s the thing about a deadline with no real stakes attached: it’s not a deadline. It’s a guess wearing a deadline’s clothes. And smart engineers are pattern-matchers. Once missing a date costs nothing and hitting one earns nothing, their brains file it where it belongs. Optional.
Greg wasn’t managing a discipline problem. He was managing a signal problem. His dates carried no real information, so nobody’s brain bothered to act on them.
That’s when we built the SIGNAL framework, so every deadline Greg sets actually means something.
Before Greg wrote another date on that whiteboard, I had him run what I call the External Anchor Test. For any proposed deadline, he asks one question out loud:
“What happens in the real world on this date if we miss it?”
If the honest answer is “nothing,” it’s not a deadline. It’s a target, and he labels it that way instead of dressing it up as a hard date.
Greg ran this test on his whiteboard and cut it in half. The dates tied to a customer’s go-live or a compliance filing stayed. The ones that existed because “Q3 felt right” got relabeled as targets, openly, with no pretending.
Buffer time didn’t work because Greg only found out about a slip when it had already happened. So we replaced the daily status theater with the Two-Thirds Check. At the two-thirds mark of any timeline, every owner reports one word.
Green: on track, no ask
Yellow: at risk, here’s what I need
Red: already slipping, here’s the new plan
The script for Yellow or Red is fixed, so nobody has to improvise an excuse:
“I’m behind because [X]. I need [Y] by [Z] to get back on track.”
A yellow flag at the two-thirds mark is cheap. A red surprise on the due date is expensive. The Two-Thirds Check moves the bad news earlier, when it’s still fixable.
Greg’s team had learned to speak in fog, because fog is safe. We killed the fog with a simple swap:
Before: “We’ll try to get this done sometime next sprint.”
After: “This ships Thursday, June 12, 5pm.”
A range gives everyone room to disagree later about whether it slipped. One number doesn’t. Greg made this the house style for every commitment, spoken or written.
“The team is working on it” was Greg’s most common sentence. It was also useless: a team can’t be accountable. A person can.
Before: “The team is working on the ledger migration.”
After: “Maria owns the ledger migration. She flags blockers to me. I don’t chase her for status.”
Naming one owner per deliverable did something unexpected. People started volunteering for ownership instead of hiding inside “the team.” Visible work finally came with credit, not just risk.
A missed deadline used to just quietly move. Nobody discussed why. We replaced that silence with the Renegotiation Meeting. Any Red status triggers a mandatory fifteen-minute meeting with Greg, same day, same script.
“Here’s what changed. Here’s the new date. Here’s what I need to hit it this time.”
The meeting isn’t punishment. It’s a cost, a real one: fifteen minutes of a VP’s direct attention, on the record, every single time. Missing a date stopped being free.
Finally, Greg started keeping what he calls the Slip Ledger. One line per deadline, per owner, tracking whether it was hit, and if not, why.
Scope creep: the ask grew mid-project
Dependency: someone else’s slip caused this one
Estimation: the original number was wrong
No excuse: it just didn’t get done
Three months in, the ledger told him something the whiteboard never could. Two engineers had a scope-creep pattern that meant Greg’s intake process was broken, not their discipline. One engineer had a No Excuse pattern three times running, and that was a different, much smaller conversation.
Six weeks after we started, Greg texted me a photo of his whiteboard. Same board, same wall. But it looked different. Fewer dates, each one tied to something real. A small column of green, yellow, and red magnets sat next to each name.
A week later she called, laughing. “Elena flagged Yellow on her project yesterday,” he said. “Two years ago she would’ve gone dark and told me the night before it was late. Yesterday she just said, ‘I’m behind, I need two more days from the data team.’ She made Thursday.”
Greg’s team hadn’t gotten more disciplined. His deadlines had finally started telling the truth, and once they did, his team started telling him the truth back.
Keep those dates honest (and your whiteboard less crowded),
Lewis C. Lin
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.