THE FIELD GUIDE · SITUATION
Make a Recommendation Before You Have Perfect Information
Situation
You help put together a monthly customer newsletter.
Two months ago, the team introduced a new recurring section. On the first send, it got unusually strong clicks. On the second, performance was fairly ordinary.
There is a complication: the first newsletter also contained a major product announcement, so you cannot tell how much of that nice-looking result came from the new section itself.
The section takes up roughly a quarter of the newsletter. If you keep it, you give up space that would otherwise go to a customer story—a format that has performed reliably in the past.
The next issue has to be locked today.
Your call
Your manager asks: “Do you think we should keep the new section next month?”
What would you recommend?
Take a moment before you continue.
Here is the annoying part
“I need more data” is a perfectly reasonable observation.
It is not yet a recommendation.
And in this case, waiting is also a decision. The newsletter still has to contain something next month.
You do not have enough evidence to know whether the new section is a winner. You do have enough to make a provisional call.
So say what the evidence actually gives you: one unusually strong result, one ordinary one, and a first issue with a big product announcement muddying the picture. Name what you still don’t know—whether the section itself is doing the work—and then make a call for this issue anyway.
The important part is to leave the uncertainty visible. What would make you keep the section? What would make you cut it next time?
One defensible answer
“I’d keep the section for one more issue, but I wouldn’t expand it yet. The first result was strong, but the product announcement may have driven some of that performance, and the second send was more ordinary. One more comparable issue should give us a cleaner read. If it still doesn’t outperform the customer-story slot, I’d go back to the proven format.”
That is not the only defensible recommendation.
You might reasonably decide that the opportunity cost of giving up another customer story is too high and recommend cutting the section now.
The important part is not matching my answer. It is being able to make a call for now while keeping the uncertainty—and what would change your mind—visible.
The Office Auntie version
You do not need perfect information to make a recommendation.
You do need to say what your recommendation depends on.
Boundary worth knowing
A conditional recommendation is not permission to invent missing facts. If the missing information makes the decision unsafe, unauthorized, or impossible to evaluate responsibly, get what is required.
A NOTE ON THE EVIDENCE
This is a practical translation of recommendation-under-uncertainty reasoning, not a validated decision method.
WHERE TO GO NEXT
Prerequisite concept: What Actually Matters Here?
Same judgment move: Everything Is Urgent
Complication / boundary case: The AI Answer Sounds Plausible. What Do You Verify?