The recipe blog taught you the wrong lesson
You know the site. You wanted the temperature and the time. You got a childhood memoir, three autoplay ads, and a “jump to recipe” button buried below the fold. Everyone hates this. We all agree it is bad.
Then those same people go to work and write a 1,500-word blog post that puts the answer at the bottom. The clever hook. The throat-clearing intro. The “in today’s fast-paced world.” The actual point four scrolls down, if it is there at all.
Your B2B content is the recipe blog. You just cannot smell it.
Directness is the most human thing you can do
The defense of the fluff is always the same. Personality. Storytelling. The human touch. As if answering the question quickly were somehow rude.
Flip it. When someone gives you exactly what you needed, in the fewest words, with no games, how does that feel? It feels like respect. It feels like they value your time. That is the human touch. The padding is the robotic part. A model can generate an endless warm-up. Only a person who actually knows the answer can cut straight to it.
This is a skill, not a shortcut
Here is the part people miss. Directness is harder than padding. Anyone can write 1,500 words. Saying the true thing in 300 takes judgment about what to cut, and judgment is the one thing that does not come free. The blank-page writer hides behind volume. The practitioner says the useful thing and stops.
What this means for search and AI
This used to be a taste argument. It is not anymore. AI search rewards the page that answers the question in the first two sentences, because that is the chunk it can lift and cite. The recipe-at-the-bottom post does not get quoted in an AI answer. The page that leads with the answer does. Directness went from a style preference to a distribution strategy.
I still write the fluffy version first sometimes. The warm-up paragraph is how I clear my throat before I know what I actually think. The difference is I delete it now. The first draft is for me. The published version is for the reader. If your intro is really you figuring out your own point, fine. Just do not make the reader sit through your figuring.
The fix is usually a system, not a sentence
If every post your team ships buries the answer, that is not a writing problem you solve one headline at a time. It is a process that has no step where someone asks “what is the one thing this page is here to say, and is it in the first two lines.” Build that step in once and every future post inherits it. That is the whole idea behind Systems-Led Growth, and it is what the next episode gets into.