TL;DR: Yesterday’s post diagnosed a hidden bottleneck: four co-packers stalled on a decision I’d parked, not a delay they owned, with a clean three-question check to find it. Here’s the honest follow-up. I didn’t need the diagnosis. I knew on day one that sourcing those three ingredients was mine to settle. The nine days of follow-ups were a performance of diligence, staged so I wouldn’t have to decide. Before you reach for any framework, run the day-one test: did you already know the answer when this started? If you did, it was never a bottleneck. It was avoidance with good email hygiene.
This is a companion to the bottleneck wasn’t the vendor, it was a decision I parked. Read that one first. This is the part I didn’t want to admit to myself yet.
Yesterday I published a tidy post about hidden bottlenecks. It had a three-question diagnostic, a line from Goldratt, and a clean ending where the bottleneck “moved.” Every word of it is true. It’s also the version I was comfortable publishing.
Here’s the part I’ve been sitting on.
When I read those four threads back to back, what hit me wasn’t that the vendors were waiting on me. It was how busy I’d looked while deciding nothing. A dozen replies. Same-hour responses. A signed NDA, sample jars in the mail, a steady drip of polite reminders. If you’d glanced at my calendar that week, you’d have called me responsive. I was responsive to everything except the one decision that mattered.
I knew that. I was avoiding it. Not on day nine, when I read the threads back to back and “found” the pattern. I knew on day one. The first co-packer email saying they couldn’t source the saffron, rose petals, or mushroom powder landed in my inbox, and a quiet part of me read it and understood right away: that one’s yours, Dan. I didn’t need a framework to find that bottleneck. I built the framework afterward, partly so the nine days would have a respectable explanation.
The answer was never the problem
I only saw what I’d done after re-reading an essay by David Cain, who writes Raptitude, a blog about paying closer attention to ordinary life. He boils a lot of stuck moments down to one infuriating sentence: “Do what has to be done, when it has to be done, and do it that way every time.” His point isn’t about productivity. It’s that we usually already know what needs doing. The drama of being stuck is the search for any option that isn’t just doing it. Hesitation is rarely about not knowing. It’s about not wanting to act.
That’s all nine days of follow-ups were: a search for a third option. In the last post, I called it a make-or-buy decision that hides a secret third choice, waiting. This is the same confession from the inside. Waiting didn’t feel like a choice. It felt like work. It felt like diligence. That’s the trap. The most convincing disguise for not deciding is being relentlessly responsive to everything next to the decision.
The day-one test
The Stall Check from the last post is for when you genuinely can’t see the bottleneck, when the block is real and hiding behind someone else’s silence. The day-one test runs before any of that, because half the time you’re not actually confused:
On day one, did I already know whose call this was?
If the answer is honestly no, if you couldn’t name the owner at the start, then you have a real visibility problem, and the Stall Check earns its keep. Go find the hidden input.
But if the answer is yes, put the framework down. You don’t have a diagnostic problem. You have a willingness problem, and the two need opposite treatments. You can’t diagnose your way out of not wanting to decide. No amount of clever process catches a decision you already made and chose to leave on the floor.
Here’s the uncomfortable reason I reached for “hidden bottleneck” in the first place. A process problem flatters you. A willingness problem doesn’t. “Hidden bottleneck” casts me as the sharp detective who cracked the case. “I avoided it” casts me as the guy who let four partners idle for a week and a half because the call was hard and I’d rather look busy than be wrong. The label I grabbed first was the tell.
Avoidance wears the uniform of diligence
Here’s what I want to leave you with, because I doubt I’m the only one.
Not deciding rarely looks like sloth. It looks like work. You answer fast. You keep the thread warm. You follow up, you forward, you circle back. Every one of those is real effort, and none of it is the effort. The tell is simple: it’s all motion that never asks you to commit anything. If a week is full of activity about a decision and empty of the decision itself, that’s not diligence. That’s indecision.
In the last post, I wrote that a parked decision shows up “wearing someone else’s delay as a costume.” I had it half right. The vendors’ silence didn’t hide the truth. My own carefulness did.
FAQ
How is the day-one test different from the Stall Check? The Stall Check locates a bottleneck you genuinely can’t see. The day-one test asks whether it was ever hidden at all. One is for confusion, one is for avoidance. Run the day-one test first. If it comes back “I knew,” skip the diagnostic and go straight to deciding.
Isn’t following up the responsible thing to do? Yes, when the next input is genuinely someone else’s to produce. No, when the follow-up stands in for a decision that’s yours. The tell: are you nudging them to resolve something you haven’t resolved? Then the politeness is just procrastination with a signature line.
What if I really didn’t know the answer on day one? Then it’s a real visibility problem. The day-one test clears, you run the Stall Check, and you find the hidden input. The test isn’t an accusation. It’s a way to separate “I’m confused” from “I’m avoiding,” which is the split that decides what you do next.
Why do we prefer “bottleneck” over “avoidance”? Because a process problem flatters you and a willingness problem indicts you. “Hidden bottleneck” lets you be the clever one who found it. “I parked it because it was hard” doesn’t. The word you reach for first is often the first clue about which one you’re actually in.
What’s the one thing I should do this week? Take the item you’ve followed up on the most, the thread you keep nudging, and ask: did I know the answer on day one? If yes, make the smallest reversible version of that decision today. Then notice you didn’t need a framework. You needed to stop performing.
What I’m doing about it
This week, I’m not adding another framework. I’m doing the opposite. I listed every Trevean thread I’d quietly filed under “waiting on someone else”: the at-scale co-packer, the next phase with our design partner, the spec for our next blend. Next to each, I wrote the day-one answer fast, before I could dress it up. More of them than I’d like came back the same way: you already knew.
The saffron is already moving. I’m hand-blending the market-test batch, like I said last time. The rest are getting the smallest version treatment this week, one decision at a time, no diagnostic required.
I didn’t have a bottleneck to find. I had an answer to admit. The nine days were just how long it took me to stop being impressively busy and say it.
Leave a Reply