All articles

August 17, 2026 - 3 min read

Why 'consider revising your bid strategy' is not advice

"Consider revising your bid strategy." "Reconsider your targeting." "Monitor closely and adjust as needed." Recommendations phrased like this share one quiet property: there is no outcome that could ever prove them wrong. Vague enough to survive any result, they read as advice and function as cover -- for the tool that generated them and for the specialist who has to relay them to a client.

What makes a recommendation falsifiable

The fix is not softer or harder language, it is structure. A recommendation worth acting on names three things: what is expected to happen, which metric shows it, and the date it gets checked against reality. Strip any one of those out and what remains is an opinion wearing a prediction's clothes -- confident-sounding, but with nothing at stake.

A worked comparison

Illustrative pair: "Consider raising tROAS during the evening peak" commits to nothing -- if CPA goes up, down, or sideways next month, the sentence was never wrong, because it never said what should happen. "Raise tROAS 10% during the 19:00-22:00 window; expect CPA to fall within three weeks" is a different kind of statement entirely. It can fail. If CPA does not fall, that is a real, recorded miss -- not a sentence vague enough to reinterpret after the fact.

The harder habit: recording the misses

Recording a win is easy and flattering. Recording that a hypothesis was tried and did not pan out is the habit that actually builds a trustworthy track record, and it is the one almost nobody keeps, because it requires writing down in advance what would count as failure. A system -- or a specialist -- that only remembers its wins is not learning from its own history. It is curating a highlight reel.

Why 'I don't know yet' belongs in the same discipline

The same standard shows up in a smaller, less flattering place: being willing to say there is not enough data to conclude anything, instead of forcing a confident-sounding answer because a client meeting is in an hour. A tool, or a specialist, that always has an answer is not more capable than one that sometimes says it does not know yet. It is only less honest about the difference between the two.

None of this makes a recommendation more likely to be right. It makes it possible to find out -- and a track record built on statements that could have failed, and sometimes did, is worth more than one built on statements that never could have.

See how the Decision Framework applies to your own accounts.

Request a demo