The Sentence

I used to give this advice all the time. Sit in a board meeting, listen to a founder talk for twenty minutes about their ICP, and say: "Can you put that in one sentence?" It's a great coaching move. Clean, incisive, slightly annoying. I was very pleased with myself.

Now I'm the one staring at the whiteboard. And I can tell you... it's a completely different experience from this side.

We spent three weeks running research calls, building ICP heatmaps, analysing segments. The data was clear. The team was circling something. Everyone could feel it. And yet nobody moved. Not because we lacked insight, but because we lacked the sentence.

I've started calling this "insight lag" (which is the kind of term you coin when you want to feel like you've contributed something to the discourse). It's the gap between when data is clearly saying a thing and when a team actually acts on it. I used to think it was a discipline problem. I'd watch it happen in companies I advised and assume the founder just needed to be sharper. Faster. More decisive.

The truth is that it's not a discipline problem. It's a commitment problem. Because the sentence isn't a communication exercise. It's a bet. Writing "managers and project leads in fast-moving service businesses, 20 to 500 employees" means you've ruled things out. It means you've picked. And most teams, including mine, will do weeks of excellent analytical work to avoid the moment of picking.

Sofia put that sentence on a doc three weeks ago. Twenty calls were booked by the following week. Not because the data changed. Because the sentence landed.

Then last week, Sancar said in a morning sync: "The core JTBD is capture and prioritise, not meeting prep." He'd been building toward this for months. The research had been pointing at it. But that one sentence, nine words, did what five decks couldn't. We renamed the company the same week.

When I was advising, I thought "say it in one sentence" was about clarity. About communication hygiene. Now that I'm building, I understand it differently. The sentence comes last, not first. You can't write it without doing all the messy, circling, slightly frustrating work that precedes it. The sentence isn't a shortcut to the insight. It's the evidence that the insight is complete.

What I didn't appreciate from the advisory side is how much courage it takes. Every week you don't write the sentence, you get to keep your options open. You get to stay in the comfortable analytical middle where nothing has been ruled out and nobody is wrong yet. The sentence ends that. It creates something precise enough to disagree with... which is exactly why it creates alignment.

I now do the thing I used to do to other founders (probably with slightly irritating regularity, the team will confirm this). I interrupt analytical conversations to ask: can you say that in one sentence? But I ask it differently now. Not as a coaching move. As a diagnostic. If we can't write the sentence, we haven't finished thinking. We've just finished talking.

I'll leave you with E.M. Forster: "How do I know what I think until I see what I say?"