Nobody Asks the Second Question

There is a moment in almost every marketing meeting that I have started watching for. Somebody puts a number on the screen. Leads are up eleven percent. The room nods. Somebody says “nice.” And then the deck advances.

Nobody asks the second question.

It is not that the second question is hard to think of. Everybody in that room already has it. Up eleven percent against what, last month or last September? Is that the whole number, or did one campaign carry the entire lift while everything else sagged? Are these the same kind of leads we had in the spring, or did somebody quietly switch a form back on? Did any of them buy anything?

The questions are right there, fully formed, sitting behind everyone’s teeth. They die there because everyone in the room has learned what asking costs.

The price of a follow-up

Here is the accounting nobody writes down.

The first question is free. It was answered in advance, by someone who spent two days building the deck, pulling from four tools, pasting into a spreadsheet, and fixing the one chart that kept rendering wrong. That work is already sunk. Asking for the number on the slide costs nothing because the number on the slide is the product.

The second question is not in the deck. The second question is a Slack message to the one person who knows how the pull works. That person has a queue. The queue is four days deep on a good week. Answering you means re-running an export, re-joining it to a different source, and remembering which of the three “customer” definitions the team agreed on in a meeting last year. It is a small project. You are asking for a small project, in public, in front of the person who built the deck, about a number that was presented as good news.

So you say “nice” instead. Everybody says “nice.” The meeting moves on, and the organization records that it reviewed its performance.

What gets trained out

People are not incurious. Curiosity gets extinguished the ordinary way, by not being rewarded.

Ask a follow-up in January and you get an answer in February, after the decision it was supposed to inform has already been made. Ask one in March and you get a polite “let me look into that” that never lands. Ask one in May and you learn that the answer requires a joint session with three people and a shared screen. By June you have stopped asking, and you have not decided to stop asking. You have just noticed that questions do not go anywhere, the way you notice a door is locked and quit turning the handle.

What is left is a culture that treats reporting as an update rather than an investigation. The monthly review becomes a broadcast. Numbers are delivered, received, and filed. Nobody is lying and nobody is stupid. The loop just does not close.

A report you cannot interrogate is not information. It is a press release about your own company.

The reports get longer, which makes it worse

Smart teams notice the silence and try to fix it the obvious way: anticipate the questions. So the deck grows. Now there are twelve slides of channel breakouts and a cohort view and an appendix. Somebody adds a tab.

This does not help, because anticipated questions are not the same as real ones. The real question is always the one specific to the thing that just happened, and the thing that just happened was not on the roadmap when the template was built. You cannot pre-answer “why did enterprise pipeline stall in the Midwest in the last three weeks.” You can only answer it when someone asks, which is exactly the case the reporting process is worst at.

So the deck gets heavier, fewer people read it, and the ratio of effort to decisions made gets quietly worse every quarter. Most teams are producing more reporting than they were five years ago and making the same number of informed calls.

Where the value actually was

Nothing useful is in the first number. The first number is a headline. It tells you a direction and nothing about cause, which means it cannot tell you what to do next.

Everything you would actually act on lives two or three questions down. Not “leads are up,” but “leads are up because one partner webinar ran in week two and those leads convert at a third the rate of the rest, so the headline is flattering and the pipeline is not.” That sentence is three follow-ups deep. It is also the only version of the story a person could make a budget decision from.

The gap between those two sentences is not an analytics problem in the technical sense. It is a latency problem. When a follow-up takes four days, you get one per month, and you never get to the third one. When a follow-up takes forty seconds, you get to the third one before the meeting ends, and the conversation changes character entirely. It stops being a status update and starts being an argument, in the good sense.

How to tell if this is you

Not a vendor checklist. Just things to notice in your own building.

• The last three “great questions” in a review that got a “let me follow up on that.” Did any of them actually come back?
• How many people in your organization can answer a new question about marketing performance without asking someone else first.
• Whether anyone has ever changed their mind during a reporting meeting, as opposed to after one.
• The gap between when a number is observed and when anybody knows why it moved. If that gap is measured in weeks, your reporting is a historical record, not a control system.

The last one is the real tell. History is fine. Most marketing reporting is just very expensive history.

The fix is boring

There is no clever framework here. The reason nobody asks the second question is that the data lives in eight systems that do not agree on what a customer is, and every follow-up is a small integration project performed by hand. Make the follow-up cheap and people ask. Keep it expensive and they will keep saying “nice” and advancing the deck, forever, politely.

That is most of what we care about at I Hate Marketing. We put the whole messy stack, the CRM and the ad platforms and the web data and the billing system, into one place that you can just ask questions of, so the third question costs the same as the first. If your meetings have gone quiet in the way described above, that is the problem worth solving. Here is what we built, if you want to look at it.

Or do not. But notice the silence next time. It is telling you something about your stack, not about your team.