|
Issue 003 |

Not slower. Stiller.
WHAT’S INSIDE
THE TOPIC: Ann Marie Almariei on defining “good,” turning briefs into blueprints, and giving teams something concrete to check their work against.
THE CHECK: A visual guide to the artifact each deliverable should be checked against before it reaches the client.
THE SIGNAL: Fresh perspectives from around the industry.
The Topic
What Good Looks Like
Define good before you build it, then let the whole team build against it.

A brief proposes. It holds options, open questions, white space. A blueprint confirms. By the time it exists, the direction has been chosen. The client has weighed in, the expert has been interviewed, the competition has been analyzed, the weaker options have been cut, and the narrative has been streamlined into one coherent path. What no longer belongs to that path is gone, so nothing stale gets pulled back in by mistake.
The blueprint is the vision cut from the brief.
Call it a wireframe, a storyboard, an outline, a comp. Whatever your discipline names it, it’s the same thing: the point where options become a decision. A brief can keep living and evolving; the blueprint carries every open question answered, plus one thing the brief never had: it shows what good looks like.
Good has to answer to two sides at once. One is the client: what this piece has to do for the business. The other is the audience: what they’re actually searching for, how they behave once they find it, and the one action we want them to take when they’re done. A blueprint that only satisfies the stakeholder produces work that gets approved and ignored. One that only satisfies the audience produces work that gets loved and misses the point. Holding both in the same document is the job.
Closing the open questions is the craft, and it starts with inspiration.
I scan the ecosystem: what’s been done that’s close? Where did those examples do amazing things? Where does our opportunity differ, and what’s been left on the table? What’s the audience searching for, and what’s performing right now? All these answers can be navigated in the blueprint.
Then comes structure. An outline, an order, a nomenclature. When the structure feels right, I check it back against the brief for what’s missing, and there may be a few rounds of refinement -- in fact, there should be.
The blueprint takes on the shape of the work. For an article, it’s a narrative arc. For a commercial film, it’s a pre-pro book with the script, casting, locations, a detailed shot list and shooting schedule. For a website, it’s a wireframe and the UX strategy behind it, settling what lives where before any screen gets designed. When the deliverable recurs (a monthly dashboard, a content series), the blueprint iterates until it becomes the standard.
Whatever the form, the blueprint’s job is one: a through-line the whole cross-functional team can build against.
So what actually goes in? For one financial services client, the blueprint for every article carries the angle, the search intent behind it, the action we want the reader to take, the outline section by section, the link strategy, the legal guardrails, and the most important thing: a benchmark for the piece, so the finished draft has something to be measured against. Anyone picking up that blueprint, on day one or day three hundred, can hold a draft next to the benchmark and see the gap. Review that used to take hours takes one, and the time comes back as attention to the writing.
None of this is new. The stakes are.
Storyboards were pinned to studio walls long before anyone typed a prompt. But the blueprint matters more now than it did thirty years ago, not less. Increasingly we’re using AI to accelerate our work, and AI has no judgment of its own. It can only interpret your request based on data that already exists. A specialized team fills the gaps in a loose blueprint with experience. A model can’t. So the blueprint gets explicit.
Does the story flow? Does that source feel on brand? Where’s the opportunity to visualize an idea, or make it personal and relatable? Writing the standard down doesn’t replace that judgment. It’s how the judgment gets protected.
So we’d like to know: what does a blueprint look like in your line of work? What does it have to carry before you’d let anyone, or anything, build from it? However you answer, that’s what good looks like.
|
This issue's contributor
Ann Marie Almariei
Creative director and AI orchestrator who has spent two decades connecting story to strategy for everyone from Coca-Cola, Samsung, and Kraft Foods to hundreds of startups and small businesses, and now builds the human-centered workflows that let teams do it faster.
|
The Check
Before the client sees the work, what does the work answer to?
| The deliverable | The thing you check it against | What the check catches |
|---|---|---|
| Article | Outline of the narrative arc | A section that reads well but doesn't move the argument forward |
| Film | Script & storyboard | A beautiful shot that has no place in the edit |
| Website | Wireframe & UX strategy | A page with no clear next step for the visitor |
| Monthly dashboard | Reporting template & data source | A number that looks right and can't be traced back to where it came from |
If you can't name what's in the middle column, you don't have a blueprint yet. You have a brief.
THE SIGNAL


