Telling a Weak Brief From Weak Execution
You are looking at a post that did not work. It scrolled past without landing, and you want to know who is responsible, the people who made it or whoever decided what should be made. “This didn’t work” is not an answer, it restates the problem, and it can mean at least two different things.
Two different failures, one flat scroll past
Call the first execution failure: a workable brief and a sound idea, not delivered well. Call the second strategy failure: exactly what was asked, delivered competently, and what was asked was wrong for the account or the moment. Both land on the feed looking the same: flat, forgettable, easy to scroll past.
The complication is that you, judging from outside, never see the brief. You see the finished post and nothing upstream of it. Every diagnosis has to be built from what is visible in the thing itself, working backward from a symptom rather than forward from a cause you can inspect.
What a strategy failure looks like when the craft is fine
Nothing about the making of the post is wrong. The edit is clean, the copy reads fine at the sentence level, the visual system matches the account’s established look. Pull any single frame or line out and the answer is yes, it is well made. The flaw only shows up when you ask why this exists at all, not how well it was made: a well built answer to a question nobody watching was asking, visible only once you step back from the shot and ask what job the post was supposed to do for this account, and notice the answer is thin or absent.
One secondary signal worth reading, carefully: how the audience responded in the comments. Not a specific volume or rate, since no figures back that up here, but the character of the response, polite confusion or quiet where the account usually gets some reaction. Not proof, but a nudge.
What an execution failure looks like when the idea was sound
Run the same test the other way and you get the mirror image. The premise makes sense. Described in a sentence, you would nod, that sounds like something this account should be posting. The complaint arrives at a different level, a shot, a sentence, a transition: the pacing drags, the caption undercuts the visual, the type is hard to read, the cut lands a half beat late. Imagine a more capable team given the same brief. A sharper editor fixes this without changing what the post was trying to do, whereas in a strategy failure the flaw was never in the doing, so no better team fixes it without also changing the brief.
A short checklist for telling them apart on sight
- Do the individual craft decisions hold up on their own merit: framing, cut points, word choice, type. If each is defensible in isolation, craft is probably not where the failure sits.
- Would a different execution of the same idea plausibly have worked. Picture the same premise handled by a sharper team. If it clearly lands now, this points toward execution, not strategy.
- Does the post aim at something real about this account’s actual audience, or at a trend that does not obviously belong to that audience.
- Treat this as a heuristic for someone who cannot see the brief, not a substitute for knowing what was asked. Some cases stay genuinely ambiguous. Read those as ambiguous rather than forcing them into one column.
The case that looks like both, and how to still call it
Most real posts are not a clean example of either failure. More often you get a soft idea and a slightly loose edit at once, neither flaw severe enough alone to explain the miss.
Ask one question: which flaw, fixed alone, would have saved the post. If tightening the edit alone would have made the idea land, treat it as primarily execution. If no amount of tightening would have made it land, treat it as primarily strategy.
Guard against the misreading that runs the other way: assuming rough edges must mean an execution problem, since rough edges are the most obvious thing to point at. A loose edit is sometimes what a team produces when it does not believe in the brief it was handed and does not commit to executing it. The scrappiness can be the residue of a strategy failure, not evidence against one.
Why this distinction matters for how you judge an agency’s work at all
Attributing a failure to the wrong layer produces two mistakes in opposite directions: dismissing a capable craft team over a strategy problem they did not create, or excusing weak execution because the idea happened to be sound.
Judging whether social media work is genuinely good depends on making this separation, and doing it once, on one post, is never enough to trust. A fair read requires seeing the pattern across a body of work. For a broader look at inferring strategy from public output, see reading strategy from what an agency actually posts, and for how an idea can look different once it ships, see the difference between concept work and work that shipped.
Look at several posts from the same account before settling on a verdict, since one campaign is not a body of work, and a single post is as incomplete a basis for judgment as what a portfolio leaves out. One post gives you a hypothesis. A pattern gives you a verdict.
See more of the work we’ve selected
Browse this year’s selections to see the editorial picks this method supports, or if you know an agency whose work holds up under this kind of scrutiny, nominate an agency.
FAQ
Can a single post ever prove which kind of failure happened?
No. One post gives you a hypothesis, not a verdict, because you cannot see the brief and a single data point cannot rule out either explanation. The checklist above is for forming a read on one post, but confidence should come from a pattern across several posts, not one.
Is a post with obvious production flaws automatically an execution failure?
No. Rough execution is sometimes what a team produces when it does not believe in a weak brief and does not commit to it, so a scrappy post can still be primarily a strategy problem wearing a craft problem’s clothes.
Sources
- https://thesocialagencyawards.com/blog/reading-strategy-from-public-output/, checked 2026-09-09
- https://thesocialagencyawards.com/blog/concept-work-vs-work-that-shipped/, checked 2026-09-09
- https://thesocialagencyawards.com/blog/one-campaign-is-not-a-body-of-work/, checked 2026-09-09
- https://thesocialagencyawards.com/blog/what-a-portfolio-leaves-out/, checked 2026-09-09
- https://thesocialagencyawards.com/winners/, checked 2026-09-09
- https://thesocialagencyawards.com/nominate-your-agency/, checked 2026-09-09