The Question That Keeps the Conversation From Happening

A founder I worked with had been circling a conversation with his operations lead for about six weeks. He'd rehearsed it. He'd written a version of it in his notes app. Twice he'd scheduled the meeting and twice he'd filled it with other agenda items. When I asked what was stopping him, he said something I hear constantly: "I keep going back and forth on whether I should even say anything."

That sentence is the trap. Not the fear. Not the stakes. The question itself.

"Should I say something?" sounds like a reasonable thing to ask. It isn't. It's an unanswerable question, and unanswerable questions don't get resolved. They get re-litigated. Every morning the founder woke up and argued the case again, both sides, in his own head. Prosecution before coffee, defense by lunch. Six weeks of deliberation that produced no verdict, because the question was never built to produce one.

This is what delay actually looks like from the inside. It rarely feels like avoidance. It feels like careful thinking.

The way out is not more deliberation. It's a better question. Three of them, actually, and each one has a yes or a no.

Does this need to be said?
Not "am I annoyed" and not "would I prefer things were different." The filter is consequence. If this continues unaddressed, does something real degrade: a result, a relationship, a standard, trust? Irritations fail this filter all the time, and that's the point. Plenty of things don't need to be said, and knowing that clearly is a relief, not a failure.

Does it need to be said now?
This filter exists to kill the most respectable-sounding excuse in leadership: "I'm waiting for better timing." Sometimes timing is real. The person is mid-crisis, the room is wrong, the moment is genuinely hot. But "now" here means soon and deliberate, not this instant and unprepared. If the honest answer is "there is no specific better moment I'm waiting for, just a vaguer future one," the answer is yes, it needs to be said now.

Does it need to be said by me?
The honest exit. Sometimes the answer is no. The conversation belongs to their direct manager, or a peer, or someone with a relationship you don't have. This filter isn't a loyalty test you're supposed to pass. It's a routing question. When the answer is no, your job changes: it becomes making sure the right person has the conversation, not having it yourself and calling that leadership.

Together these three questions are the Three-Filter Test, and here's what it does that "should I?" never could: it ends. Three yeses means the conversation is overdue, and the deliberation phase is over. Any no means you now know precisely why you're not having it, which is a completely different state than circling it. Clarity about why you're waiting is a decision. Vague intention is avoidance wearing a suit.

One boundary worth naming. The test decides whether. It says nothing about how. Those are separate problems, and collapsing them is its own form of delay: leaders postpone the decision to speak because they haven't figured out the delivery, when the delivery only gets figured out after the decision is made. Urgency resolves whether. Preparation resolves how.

The founder with the six-week loop ran the test in about ninety seconds. Yes, yes, yes. The conversation happened that week. It went fine, the way most of them do once they finally happen. What he'd been protecting himself from was not the conversation. It was the verdict.

Take the conversation you've been circling. Run the three filters. What did you get?

‍

Watch the video here. And if you want more of these, hit subscribe.

In all that we do, let us seek wisdom, discipline, courage & justice.

Be well,
Keita

‍