Recommendations that go nowhere

The analysis was careful, the numbers held up, and the recommendation at the end was reasonable. The reader said it was helpful, and nothing happened: no decision, no objection, no follow-up question. A month later the thing you recommended against went ahead anyway.

The instinct is to make the next analysis more rigorous: more data, a better model, a cleaner chart. Occasionally that is the problem. Far more often the analysis was fine and the recommendation was the wrong shape. It answered a question, and the reader needed a decision.

I have written about the version of this that plays out in the boardroom, where the stakes make it obvious. The quieter version happens every week, in the last slide of a deck or the last paragraph of a document, and it is where most analysts learn, or fail to learn, how influence actually works.

Three questions find the problem quickly. What decision was the reader trying to make, and did the recommendation name it? Was there an alternative, or only your answer? Where was the uncertainty, and did you show it or hide it?

Name the decision, in the reader’s words

A finding tells someone what is true. A recommendation tells them what to do about a decision they own. Take an illustrative case: “trial users who connect a data source in their first week convert far more often” is a finding. “Make connecting a source the first step of onboarding, ahead of the product tour” is a recommendation, and only if someone owns onboarding and is deciding what to change in it.

If you cannot name the decision, its owner, and roughly when it will be made, you have a finding. Findings are worth sending. They are not worth being disappointed about when nobody acts on them, because there was nothing to act on.

The reader’s words matter more than they seem to. The analyst writes “improve activation”; the product lead is deciding whether the new onboarding ships this quarter or next. The first is the analyst’s frame. The second is the one that gets a reply.

Offer an alternative you would accept

A single recommendation asks for a yes or a no, and the easiest answer to a yes-or-no question nobody asked is “not now.” That is how a recommendation goes nowhere without anyone rejecting it.

An alternative changes the question from “do you accept my answer” to “which of these do you prefer,” and it shows you have weighed the reader’s constraints and not only your analysis. It has to be a real alternative: one you would support, with its own cost stated. A straw option that exists to make yours look good is recognized at once, and it spends the credibility the real option needed.

State the condition that would change your mind

Uncertainty is where most recommendations lose the reader, in one of two ways. Hidden, it makes the recommendation read as surer than the evidence, which works until the first time it is wrong. Listed as caveats at the end, it reads as hedging and hands the reader a reason to wait.

The alternative is to state it as a condition: what would have to be true for the recommendation to be wrong, and how everyone will find out. “Make connecting a source the first step, and if activation among new trials has not risen in six weeks, revert: the users who connect early may simply be the keen ones.” That sentence does three jobs. It admits the weakness in the evidence, it gives the reader a safe way to say yes, and it says in advance what failure looks like.

A recommendation with a stated condition is easier to accept, because it can be undone on terms agreed beforehand. It is also easier to be wrong in, which matters more over a career than any single call.

The same recommendation, rewritten

The scenario is illustrative, not taken from any organization. The analysis behind both columns is identical.

	Before	After
Decision	Not stated	Whether the onboarding change ships this quarter. Owner: the product lead, at planning in three weeks
Recommendation	“Consider emphasizing data connection earlier in onboarding.”	Make connecting a data source the first step, ahead of the tour
Alternative	None	Keep the tour first and prompt a connection at its end: a smaller effect for less engineering
Uncertainty	Four caveats about correlation, in a footnote	If activation among new trials has not risen in six weeks, revert
Ask	“Happy to discuss.”	A decision at planning, between the two options

Before, the reader had to work out what the analysis meant for them. After, they only have to choose.

Take it back to the same person

When this is a pattern, the practice I suggest is to take the last recommendation that went nowhere, rewrite it as decision, alternative, condition, and take it back to the same person. Not a new stakeholder, and not a new analysis.

Going back to the same person is what makes it a test. If the rewrite gets a decision, the shape was the problem and you know what to change. If it still goes nowhere, the cause is elsewhere, and that is worth knowing too: the decision was made before your work arrived, it was never theirs to make, or the timing is wrong. Each has a different fix, and none of them is a better chart. The first of those, being brought in after the decision, is what the boardroom case study is about.

Declined is not the same as nowhere

A recommendation declined with a reason has not gone nowhere. It informed a decision, and the reason is information you did not have. The failure this essay is about is the other one: no decision, no reason, no reply.

Count “declined with a reason” as the format working, and keep a record of what you recommended, what was decided, and what happened. Over a year that record becomes the most honest evidence you have of your own judgment. It is usually more useful, and more humbling, than anyone’s feedback.

What it costs

It takes longer. Finding out who owns the decision and when it will be made means a conversation before the analysis, not after. A real alternative means doing part of the analysis twice.

It exposes you. Naming the decision invites “that isn’t yours to decide.” Offering an alternative means the reader may choose the one you like less. A stated condition gives everyone a precise way to show you were wrong. A finding with caveats is safer. It is also easier to ignore, and that safety is most of the reason it goes nowhere.

Some readers want the number, not the options. Not every request is a decision in disguise; sometimes the number really is the deliverable. The skill is telling the two apart, and asking what the number is for is usually enough.