by Ber | Jun 23, 2026 | Client Life
There is a specific sound a creative makes when they open an email titled “small tweaks – see attached.” It is not a scream. It is quieter than that. It is the sound of someone realizing that the attachment is a PowerPoint file, that the PowerPoint file is 14MB, and that somewhere inside it their carefully kerned headline has been stretched to 140% width, recolored to a blue nobody approved, and parked next to a clip-art arrow. The client has redesigned your work. In PowerPoint. And they are very proud.
This is not feedback. Feedback is a sentence. This is a hostage video, performed by your own layout, in a hostage of an application. And it happens to all of us. So let’s name the genre, study its specimens, and figure out how to survive the client who mistook Microsoft Office for Adobe Creative Cloud.
The Anatomy of the PowerPoint Redesign
It always starts the same way. You deliver something clean. The client opens it, feels a stirring of creative ambition, and decides the fastest way to communicate “move that a bit” is to do it themselves. They have one tool that lets them move things. It is PowerPoint. So they screenshot your design, paste it onto a slide, and begin operating.
The results are forensically identifiable. The image is now slightly blurry, because it was screenshotted, pasted, resized, screenshotted again, and emailed through a compression algorithm that hates you. The fonts have silently swapped to Calibri, because of course they have. There is a text box, semi-transparent, hovering over your logo like a ghost that pays no rent. And there is, inevitably, a WordArt gradient somewhere, deployed with the confidence of a person who has never once doubted themselves.
The cover note reads: “Just a quick mockup to show what I mean – obviously you’ll make it nice.” Obviously. You’ll make it nice. As though “nice” were a filter you forgot to apply, rather than the entire reason they hired a professional in the first place.
Why They Do It (a Theory of Mind)
It would be easy to be cruel here, and we will be, but first some empathy, because empathy is a competitive advantage and also because it makes the cruelty land harder. The client redesigns your work in PowerPoint because PowerPoint is the only design tool they have ever been given permission to touch. Their entire professional life has been conducted inside slides. To them, dragging a box and changing its fill is not vandalism – it is the highest form of self-expression their software has ever allowed.
The problem is that “I can move a box” and “I understand visual hierarchy” feel identical from the inside. This is the same cognitive glitch that powers the client whose nephew knows about design and the eternal demand to make the logo bigger. Owning the tool feels like owning the craft. It is not. Owning a piano does not make you Rachmaninoff, and owning PowerPoint does not make you a designer – it makes you a person with a piano-shaped object and a lot of enthusiasm.
The Damage Is Rarely the Pixels
Here is the part nobody warns you about in school. The actual PowerPoint file is not the threat. You can ignore the file. The threat is what the file does to the conversation. Once a client has physically moved your headline three inches to the left, they are no longer evaluating your work – they are defending their own. You are now negotiating against a co-author who showed up uninvited, and every note from here is really a note about their slide, not your design.
This is how a single round of revisions metastasizes into round fourteen. The PowerPoint becomes the new brief. The blurry screenshot becomes the source of truth. And you spend the next two weeks reverse-engineering what they meant from what they did, which is the most expensive form of mind-reading in the professional world.
How to Take Back the Layout (Without Taking a Hostage)
The instinct is to write a 600-word email explaining why their gradient is a crime. Do not do this. Nobody has ever been argued out of a design opinion they arrived at through the joy of dragging a box. Instead, redirect the energy.
First, translate, don’t litigate. Open their PowerPoint and ask yourself what problem they were actually trying to solve. The stretched headline usually means “I don’t feel the emphasis.” The recolor usually means “this doesn’t feel like us.” Solve the underlying problem in your own tool, properly, and present that. You are not rejecting their idea – you are promoting it from PowerPoint to production.
Second, reclaim the format early. The reason clients reach for PowerPoint is that you gave them a static JPEG and no other way to point. Hand them an annotation tool. Hand them a comment thread. Hand them a phone call. Give the impulse somewhere to go that isn’t a slide deck.
Third, hold the line on what “reference” means. A reference is something that already exists that you both look at. A reference is not a thing they built out of your thing. When the file arrives, a calm “Great – I’ll take these as direction and bring back a proper version” reasserts, gently, who is holding the pen. This is the same backbone you need when you say no without losing the client: you are not refusing their input, you are refusing to let the input become the deliverable.
The Quiet Dignity of the Source File
Somewhere out there is a designer who received a PowerPoint redesign, felt the small quiet death, and instead of replying chose to make something genuinely better than both the original and the client’s version. That designer kept their rates, kept their sanity, and kept the pen. That designer is the goal.
The PowerPoint client is not malicious. They are just armed. The work is to be so clear, so fast, and so obviously in control of the craft that they never feel the need to pick up the weapon. And on the days when they do anyway, when the 14MB attachment lands and the Calibri stares back at you – remember that the gradient is not an attack on your taste. It is a clumsy love letter that says “I care about this and I don’t know how to help.” Answer it like a professional. Then quietly delete the slide.
The Long Game Is Owning the Pen
Every PowerPoint redesign is really a test of who the client believes is in charge of the craft. Win that quietly and consistently and the files stop coming, because trust is the only thing that ever truly retires the screenshot. Lose it once and you teach the client that dragging a box is a valid way to brief you – a lesson they will apply with enthusiasm for the rest of the relationship. The designers who never get the 14MB attachment are not luckier; they are clearer. They set the terms of feedback before the first deliverable lands, they make the act of pointing easy and the act of redesigning hard, and they treat every blurry slide not as an insult but as a symptom of a process gap they can close. Protect the pen the way you protect the work, because in the end they are the same thing.
At NoBriefs we made Fuck The Brief for exactly this moment – the deep breath before you reopen the file. Wear it, ungroup nothing, and go make it nice. Visit the shop and dress for the round you didn’t ask for.
by Ber | Jun 20, 2026 | Client Life
The project is delivered. The invoice cleared. You’re already three jobs deep into forgetting this client existed. Then the email lands, friendly as a knife: “Hey! Quick one — can you send me the source files?” Four words, one exclamation point, and the entire economic logic of your business quietly set on fire. It always arrives after the relationship is technically over, phrased like a favour you’d be weird to refuse. It is not a favour. It is the most expensive sentence anyone will say to you all year, and you’ll probably say yes.
The Request That Arrives After the Invoice Clears
Timing is the tell. Nobody asks for source files during the project, when the conversation is alive and the scope is on the table. They ask afterward, in the soft administrative afterglow, when saying no feels petty and saying yes feels like good service. The framing — “quick one” — is doing a staggering amount of work. It recasts your layered, named, lovingly organised working files as a USB stick you forgot to hand over. As if the deliverable and the machinery that produced it are the same object. They are not. You sold them a chair. They are now asking for the workshop, the lathe, and the tree.
And here’s the part nobody says out loud: in most jurisdictions, unless your contract explicitly transfers them, the working files and the underlying intellectual property are yours. The client bought a licence to use a final deliverable. They did not buy the editable, infinitely reusable engine behind it. This isn’t pedantry. It’s the difference between selling a meal and selling the recipe, the kitchen, and the right to open a restaurant.
What They Think They’re Asking For (and What They’re Actually Asking For)
The client genuinely believes they’re asking for a file. In their head it’s housekeeping — tidy up, hand over the folder, done. What they’re actually asking for is the ability to never hire you again. Source files mean their nephew can “just tweak it.” Source files mean the in-house junior can resize the logo at 11pm without paying you. Source files mean your craft becomes their template, edited forever by people who will make it worse and then blame the original.
This is the same instinct that powers half the indignities in this industry — the belief that the valuable part is the asset, not the thinking. It’s a cousin of paying in exposure and a sibling of spec work: in every case, the client is trying to extract the expensive thing (your judgement) while paying only for the cheap thing (the export). The source file request is just the politest version, because it arrives after you’ve already been paid, wearing the costume of a reasonable cleanup task.
The Polite Heist, Decoded
Let’s translate a few classics, because the genre has dialects:
“We just want them for our records.” Nobody archives layered Illustrator files for sentimental reasons. This means: we want optionality we didn’t pay for.
“It’ll save us going back and forth in future.” Correct. Specifically, it’ll save them going back and forth with you, because there will be no future with you.
“Our other agency needs them.” Ah. So the files aren’t for records. They’re a dowry for your replacement, and you’ve been asked to gift-wrap your own succession.
“It’s all paid for, right?” The deliverable is paid for. The means of production is a separate line item that, funnily enough, was never on the invoice — because they never asked, and you never quoted it, and now we’re all pretending that silence was a transfer of ownership.
How to Say Yes Without Setting Your Margins on Fire
You don’t have to refuse. Refusing makes you the villain in a story they’ll tell at networking events. Instead, do the thing that reframes the entire request: price it. Source files are a product, so sell them like one. A source file release fee — a clean, confident number — does three things at once. It signals the files have value (which trains the client to treat them as valuable). It converts a relationship-ending favour into a revenue event. And it filters: a client who genuinely needs the files will pay; a client who was chancing it will suddenly remember they don’t need them after all.
The healthier fix is upstream, in the contract, before anyone falls in love with the work. State plainly what the fee buys (a licence to use the final deliverable) and what it doesn’t (ownership of working files, which are available for an additional, named sum). Do this and the post-delivery email stops being an ambush and becomes a price check. You stop improvising boundaries at your most tired and least leveraged. This is the same energy as learning how to fire a client or surviving the Friday 5pm revision: boundaries set in advance are policy; boundaries set in the moment are a fight.
The Source File Is a Boundary, Not a Folder
Here’s the reframe that makes the whole thing simple. The source file request isn’t really about files. It’s a test of whether you understand what you sell. Designers who think they sell PNGs hand over the source files for free and wonder why they can’t raise their rates. Designers who understand they sell judgement, applied repeatedly, by a specific brain treat the working files as the keys to that brain — and they don’t leave the keys in the door because someone said “quick one.”
You are allowed to be generous. You are allowed to hand them over, even gladly, for the right client at the right price. What you are not required to do is treat your own intellectual property as a rounding error because refusing felt awkward over email. The awkwardness is the cost of the boundary. Pay it once, in a sentence, instead of paying forever in unpaid edits and a client who learned they could have the whole workshop for the price of a chair.
The Junior Who Inherits Your File (and Your Reputation)
Picture the afterlife of a source file you’ve handed over for free. It lands on the desktop of someone who was not in any of the meetings, has none of the context, and possesses exactly enough software access to be dangerous. They nudge the kerning. They swap the brand blue for a blue that is technically also blue. They stretch the logo because the new banner is wider and nobody told them logos have feelings. Six months later that mangled artwork is in the wild, and it still carries the faint genetic signature of your work — close enough that anyone who knows your portfolio will assume you made the ugly version. You didn’t. But you gave them the means, for free, with an exclamation point, because saying no felt rude.
That’s the hidden cost nobody puts on the invoice: handing over editable files doesn’t just forfeit future income, it outsources your quality control to strangers and keeps your name attached to the results. Craft isn’t only what you make; it’s what survives contact with the people who edit it later. A finished, locked deliverable protects the work and the reputation that made it worth buying. The source file surrenders both — which is precisely why it’s worth a number, not a shrug.
Stop handing over the workshop for free. If you need a daily reminder that your craft is not a free export, the NoBriefs shop stocks the gear for it — Fuck The Brief for the meetings, KPI Shark for the reports, and the Spreadsheet Sloth for the rate card you keep promising to update. Wear the boundary so you don’t have to argue it. Browse the rebellion →
by Ber | Jun 7, 2026 | Client Life
There is no phrase in the creative industry more dangerous than “can you just.” It arrives wrapped in friendliness, dressed as a favor, weighing approximately nothing. “Can you just move the logo a touch.” “Can you just try it in a different blue.” “Can you just send over a couple of options.” Each one sounds like a five-minute task. Each one is a trapdoor. By Friday you have done forty “justs,” rebuilt the layout three times, and somehow you are the one apologizing for being slow. The word “just” is doing an enormous amount of unpaid labor in that sentence, and so, increasingly, are you.
The grammar of getting away with it
“Just” is a minimizer. Linguists would call it a hedge; we call it a heist. Its entire job is to shrink the perceived size of a request so the person receiving it feels unreasonable for treating it as work. “Can you redesign the homepage hero, source new imagery, and rewrite the headline” is a project. “Can you just freshen up the top of the page” is the same project with the price tag torn off. The task did not change. The framing did. And framing, as every person in this industry knows, is the whole game.
The genius of “can you just” is that it pre-loads your answer. Say no and you look precious, difficult, not a team player. Say yes and you have agreed to an undefined amount of work for a defined amount of zero. Most of us say yes, because we are agreeable people who got into this field to make things, not to litigate the boundaries of a statement of work. That instinct is lovely. It is also exactly why “just” keeps winning.
Death by a thousand tiny favors
No single “just” ever kills a project. That is the entire problem. A scope does not collapse in one dramatic act; it erodes one harmless-looking request at a time, which is why this is really just scope creep wearing a friendlier outfit. Each ask is too small to invoice, too small to push back on, too small to even mention. So you absorb it. Then you absorb the next one. Then you look up and realize the “quick refresh” has quietly become a second project running invisibly alongside the first, with no brief, no budget line, and no end date.
We have all lived the sequel: the “quick revision” that devoured three weeks. It always starts the same way. One tweak. Then a tweak to the tweak. Then a stakeholder who wasn’t in the first three rounds appears with “just one small thing.” The compounding is the cruelty. Twenty minutes here, an afternoon there, a Saturday you don’t mention to anyone — and the math never makes it onto the invoice, because each individual piece was, technically, just.
Why we keep saying yes to nothing
Let’s be honest about our side of this. The reason “can you just” works is that creatives are terrified of looking difficult. We have internalized the idea that being easy to work with is the same as being good, and that drawing a line around our time is somehow unprofessional. So we perform agreeableness at our own expense. We say “sure, no problem” to a request that is, in fact, a problem, because the alternative feels like conflict and we would rather eat the hours than have the conversation.
There is also a quieter reason: we secretly enjoy being the person who can pull it off. The hero who turns the impossible “just” around by end of day gets a thank-you, a little hit of usefulness, a story to tell. The trouble is that the reward for absorbing free work is more free work. You train people to ask, because asking costs them nothing and gets them everything. Generosity, repeated without a boundary, stops reading as generosity and starts reading as the rate.
How to defuse a “just” without becoming insufferable
You do not need to become the freelancer who cites the contract every time someone breathes near the file. You need a few calm reflexes. The first is to translate, out loud and cheerfully: “Happy to — just so I scope it right, that’s a new layout plus fresh imagery, so it’d sit at about half a day. Want me to fold it into this round or quote it separately?” You have not refused anything. You have simply removed the word “just” from the sentence and let the actual size of the request stand in daylight. Most reasonable clients, faced with the real shape of the ask, adjust. The unreasonable ones reveal themselves, which is also useful information.
The second reflex is to make the trade visible. “I can absolutely add that — it’ll push the deadline by a day, or we can swap it for one of the items already in scope.” Time and money are the same substance, and the moment a “just” has to displace something else, it stops being free in everyone’s mind, not just yours. This is also a good moment to remember that pricing your work without flinching is a skill you can build: charging what you’re worth without apologizing is the long game that makes the “justs” survivable.
The third reflex is the hardest and the most important: notice the pattern, not the instance. Any one “can you just” is fine. A relationship built entirely out of them is a renegotiation that never happened. If a client’s every request arrives pre-shrunk, the problem isn’t the requests — it’s that the original agreement was a fiction you both signed and quietly abandoned.
It helps to keep a private tally for a single week. Write down every “just” as it lands, with an honest estimate of the minutes it actually cost. By Friday you will not have a feeling, you will have a number, and numbers are how you stop arguing with yourself about whether you’re being precious. Nine times out of ten the tally is genuinely shocking — a day and a half of unbilled work hiding inside a relationship everyone agreed was “low-maintenance.” That tally is not ammunition for a fight. It is information for a decision: renegotiate the scope, raise the rate, or accept the cost with your eyes open. Any of those is fine. Sleepwalking into it is the only option that isn’t.
The two words, reclaimed
Here is the part nobody tells you: you are allowed to use “just” too. “I’ll just need that confirmed in writing.” “We’ll just add it to next sprint.” “That’s just outside what we agreed, so let’s talk numbers.” The word is not the enemy. The asymmetry is. When only one side of the relationship gets to minimize and the other side gets to absorb, you are not a collaborator, you are a buffer. Reclaim the word and the balance comes back with it.
The creative industry runs on goodwill, and goodwill is genuinely one of the best things about it. But goodwill is a gift, not a billing model, and the difference between the two is the difference between a career and a slow, polite burnout. If you need a daily reminder to keep that line where it belongs, that is precisely the energy behind Fuck The Brief — and if you’d rather your dashboards stopped lying to you while you’re at it, KPI Shark is over there too, quietly judging your vanity metrics on your behalf.
So the next time someone slides a “can you just” across the table, smile, translate it back into its real size, and let them decide whether they still want it at full price. Usually they don’t. And the hours you save are the most expensive ones you’ll ever get back. Wear the boundary. Shop the rebellion at nobriefsclub.com.
Bring a card to the next one
We built a free Meeting Bingo generator: five decks, a fresh 5×5 card every time, printable. Mark a square every time somebody says it out loud.
by Ber | Jun 5, 2026 | Client Life
The Request for Proposal is one of the marketing world’s most elegant contradictions: a document designed to find the best creative partner, architected to eliminate anyone interesting. Every agency receives the same forty-page questionnaire. Every agency spends three weeks writing a tailored response. The client picks whoever was already on the shortlist before the brief went out — or whoever quoted €3,000 less than everyone else.
The RFP is procurement dressed in marketing clothing. It carries the language of creative selection — “tell us your approach,” “share examples of similar work,” “describe your creative process” — while applying the logic of office supply purchasing: standardize inputs, compare outputs, minimize cost. It is a contact sport between two parties pretending to want different things, both of whom know exactly how this ends.
The Theater of Due Diligence
Before we discuss the RFP itself, we should acknowledge what it actually is: a paper trail. Not a selection tool — a paper trail. The legal department wants documentation that the procurement process was competitive. The CFO wants evidence that three quotes were obtained. The CMO already knows which agency they want to hire; they just need 40 pages of questionnaire responses to justify the choice to Finance.
This is why RFPs are simultaneously exhaustive and irrelevant. They ask about everything — case studies, team composition, methodology, technology stack, DEI policies, cybersecurity protocols, crisis communication experience — and use approximately 15% of that information in the actual decision. The rest exists to fill the required fields in the procurement system.
If you’ve ever received an RFP with a mandatory section on your agency’s physical security procedures for a social media retainer, you’ve touched the procedural ceiling of modern marketing procurement. Someone in Legal added that field in 2018 after a data breach at a different vendor and nobody has ever removed it.
The Questions That Reveal Everything (About the Client)
An RFP tells you more about the client than any brief. Read it carefully and you will understand exactly who has power in this organization, what went wrong with the previous agency, and whether you will ever be able to do interesting work here.
“Describe your approach to stakeholder management.” Translation: we have difficult internal stakeholders and we’re outsourcing the problem to you.
“Provide three case studies of campaigns with measured ROI.” Translation: someone senior got burned by an unmeasurable brand campaign and now everything must have numbers attached, including things that are structurally impossible to measure.
“Describe how you handle revisions.” Translation: the last agency billed for revisions and it created a diplomatic incident.
“What is your experience working with regulated industries?” Translation: Legal and Compliance will be in every review meeting and have veto power over anything with personality.
The agency credentials deck and the RFP response are the two most carefully curated documents in the creative industry — and the two least likely to resemble the actual working relationship they supposedly predict.
Unpaid Strategy, Dressed as Evaluation
Here is the moment where the RFP crosses from annoying to genuinely extractive: the strategic thinking section.
“Based on the information provided, please share your initial thinking on how you would approach this challenge.” Translation: we want three weeks of strategic thinking from five agencies, at zero cost, to validate the direction we’ve already chosen — and we will absolutely use the ideas from the agencies we don’t hire.
This is not speculation. It is industry practice so normalized that most agencies do it without complaint. The logic: you need to demonstrate capability to win the work. The reality: you are funding the client’s strategy with your own time and expertise, in competition with four other agencies doing the same thing, with no guarantee of compensation for any of it.
The spec work trap was supposed to be about portfolio pieces for student competitions. In practice, it lives most comfortably inside the RFP process of a Fortune 500 company with a nine-figure marketing budget that can’t find €5,000 to compensate the five agencies it asked to think strategically for free.
The defense of this practice — “it’s standard,” “you knew what you were signing up for,” “it weeds out agencies who aren’t serious” — is a masterwork of circular reasoning. It’s standard because everyone does it. Everyone does it because it’s standard. The agencies who push back are “difficult.” The clients who pay for pitches are “enlightened.” Most clients are not enlightened.
The Pre-Selected Winner and the Agencies Who Don’t Know It Yet
Let’s be honest about something. In a significant percentage of competitive RFP processes, one agency is the incumbent or preferred option going in. The RFP is issued because procurement policy requires competitive bids above a certain contract value. The incumbent knows this. The other agencies do not.
This creates an asymmetry so profound it would be funny if it weren’t three weeks of your team’s time. The incumbent writes a response that mirrors the client’s existing language, processes, and preferences — because they’ve been inside the building. The challengers write responses that demonstrate capability — because they haven’t. The incumbent wins. The challengers learn they were “very close” and “we’d love to work with you on future opportunities.”
The future opportunity is another RFP.
Not every RFP is pre-decided. Some clients genuinely want fresh perspectives and use the process to find them. Those clients tend to write briefs that are actually interesting, ask questions that reveal curiosity rather than caution, and behave like humans during the pitch process. They’re recognizable. They’re also in the minority.
A Modest Proposal: How to Respond to RFPs Without Losing Your Soul
First, qualify harder than the client is qualifying you. Before you commit to forty pages of response, ask the questions the RFP doesn’t answer: How many agencies are you speaking to? Is there an incumbent? What does success look like in year one? Who makes the final decision? A client who won’t answer these questions is a client running a procurement exercise, not a creative search. You’re allowed to not participate.
Second, decide what you’re willing to give away. Strategic frameworks: fine. Specific campaign concepts executed to presentation quality: no. The line is blurry, but it exists, and you should know where yours is before you start writing.
Third, treat the RFP response as a demonstration of judgment, not compliance. The agencies that win interesting work from RFPs are the ones who answer the question differently from everyone else — not more completely, differently. The forty-page questionnaire is asking for the same thing from everyone. The answer that wins is the one that makes the client feel like someone finally understood the problem.
Finally, track your win rate. If you’re investing three weeks per RFP and winning less than 30% of them, you’re running a subsidy program for clients who don’t hire you. The Fuck The Brief ethos applies here too: know which rules are worth breaking, including the unwritten rule that says you have to respond to every RFP just because it arrived in your inbox.
The RFP is not going away. Procurement processes exist for reasons, some of them even defensible. But you don’t have to approach every forty-page questionnaire with the enthusiasm of someone who believes the best proposal wins. Sometimes the best proposal wins. Sometimes it’s the golf buddy. Know the difference before you start writing.
Say it without saying it
The Fuck The Brief tee is the one that says it out loud. Wear it to the kick-off at your own risk.
by Ber | Jun 5, 2026 | Client Life
There’s a phrase that should trigger an immediate 40% surcharge on your quote. Five innocent words, delivered with the serene confidence of someone who has never once opened a project management tool in their professional life: “It’s really quite simple.”
By the time they finish explaining what “simple” means, you’re staring at three interconnected platforms, a bilingual version for the Portuguese market, two rounds of user testing with real customers (their cousin and their assistant don’t count), a launch video the CEO wants to post on LinkedIn, and a microsite that needs to integrate with a CRM nobody on their team knows how to use. Oh, and the timeline is eight weeks because “we told the board we’d launch in Q3.”
Welcome to one of the great lies of the creative industry. Not malicious. Not even conscious. Just the eternal optimism of someone who has never had to build the thing they just described.
Why “Simple” Is a Threat Disguised as a Brief
The client who opens with “it’s simple” isn’t trying to deceive you. They genuinely believe it. In their mind, they can already see the finished product — clean, functional, beautiful — and they’ve simply omitted from their mental image the 400 hours of decisions, revisions, stakeholder reviews, technical constraints, and late-night Slack messages that stand between concept and launch.
This is not stupidity. It’s the gap between consuming a product and making one. Everyone who has ever eaten at a restaurant knows what good food tastes like. That doesn’t mean they know how to run a kitchen. The client who says “it’s simple” is the person who ate at a Michelin-starred restaurant and came home confident they could replicate the soufflé.
“Simple” is a brief written in the future tense — a description of how it will feel to use the finished product, not a description of the work required to create it.
Your job, unfortunately, is to live in the present tense.
The Anatomy of a “Simple” Project
Let’s conduct a brief autopsy. The client says they need “a simple website refresh.” Here is what “simple” expands into once the kickoff meeting is done:
A homepage that communicates three different value propositions simultaneously, because the Sales team, the Marketing director, and the CEO all have different ideas about what the company actually does. A contact form connected to a CRM that IT hasn’t upgraded since 2019. A blog section that needs to import 340 old posts without breaking the URL structure. Mobile optimization for “every device” — which turns out to include a Samsung Galaxy S8 that the Finance director refuses to replace. Accessibility compliance for the European market, flagged on day six by Legal, who wasn’t in the kickoff. And, inevitably, a version in English and another in Spanish because “we have clients in Latin America,” which was not mentioned in the original brief.
None of this is unusual. None of this is unreasonable. But precisely zero of it was in the original “it’s simple” framing that set your timeline and budget.
The scope creep didn’t arrive all at once. It came in through the side door, one “while we’re at it” at a time, each individual request perfectly logical in isolation, catastrophic in aggregate.
The Clarification Chain and Other Forms of Slow Bureaucratic Torture
Once you’ve accepted the project — because the budget looked reasonable for “something simple” — you’ll enter what is technically called the Discovery Phase and what is emotionally called the Phase Where You Realize How Much You Didn’t Know You Didn’t Know.
You send a questionnaire. You get partial answers three days later, with three questions answered and two new ones added. You schedule a call to clarify. On the call, three new stakeholders appear who have not read the questionnaire. The stakeholders disagree with each other on fundamental questions about the project. Someone suggests “another alignment call” to resolve the disagreement. The alignment call requires a preparation document. The preparation document generates comments. The comments require a response document.
Forty-seven emails later, you have a brief that is 11 pages long, covers all the things the original brief left out, and bears no relationship to the timeline or budget agreed at the start. Nobody has lied to you at any point. The project was always this complex. It just wasn’t described that way.
This is why the brief nobody reads is sometimes preferable to no brief at all — at least it forces someone to write down what they actually want before you start building it.
Why Clients Say “Simple” (And What They Actually Mean)
Four things are happening simultaneously when a client describes a complex project as simple:
Wishful thinking. They want it to be simple. If it sounds simple, maybe it will be simple. If you agree it’s simple, you’ll quote a simple price. This is not strategy — it’s magical thinking with a budget attached.
Comparison to the wrong reference point. The client is comparing this project to a previous project that went smoothly. They forget the two years of painful iteration that preceded the smooth experience. The smooth version felt simple because all the complexity was already solved.
Genuine ignorance of the craft. Most people have no idea how long anything creative takes. They’ve been told by productivity gurus that focus eliminates friction. They believe a redesign that took another agency six months “should” take four weeks because they’ve seen faster turnarounds in YouTube tutorials.
Anxiety about the quote. “It’s simple” is sometimes a preemptive negotiation tactic. If they establish simplicity before you quote, they have a reference point to push back against your fee. “But you agreed it was simple.”
How to Defuse the Simplicity Bomb Without Losing the Client
You don’t win this argument by proving the project is complex. You win it by making the complexity visible before it becomes your problem.
Scope documentation before kickoff. Not a one-page summary — a proper breakdown of deliverables, assumptions, dependencies, and what happens when any of those assumptions prove false. Slow down the “yes” to speed up the delivery.
Ask the question that clients hate: “What happens if we launch on time but the CRM integration isn’t ready?” Watch the simplicity evaporate. The question doesn’t kill the project — it kills the illusion that there are no trade-offs.
Price the complexity, not the brief. If the brief says “simple website refresh” and your experience says that always means three months of scope expansion, quote three months. Justify it. Lose the client who wanted a four-week quote, or deliver the four-week version and let them live with what four weeks actually buys.
The brief that doesn’t make you cry is not the client’s responsibility to write. It’s yours to extract. The only person surprised by the complexity of a “simple” project is the creative professional who didn’t ask enough questions before starting.
The Simple Truth About Simple Projects
There are no simple projects. There are well-scoped projects and poorly-scoped ones. There are projects with aligned stakeholders and projects with seven people who have never agreed on anything in their professional lives. There are projects with realistic budgets and projects where the client’s mental image of the finished product costs three times what they’re willing to pay for it.
“Simple” is not a project descriptor. It’s a feeling — the feeling the client wants to have when it’s done. And feelings, as any strategist will tell you at great length, are not deliverables.
The next time a prospect leads with “it’s really quite simple,” smile, nod, and open your laptop. You’re about to write a very long scope document. Or you can save yourself the drama — grab a KPI Shark for your desk as a reminder that complexity is always circling beneath the surface, and it’s better to see it coming.
Simple projects exist. They just don’t start with “it’s really quite simple.”
by Ber | May 29, 2026 | Client Life
The project is done. The files have been delivered. The client has sent a two-word email that says “looks great” and you’ll spend the next three weeks wondering if that’s approval or passive aggression. The invoice is out. Everyone exhales.
And then — nothing. Someone mentions a debrief. Someone else says “yes, definitely, let’s schedule it.” A calendar invite goes out for three weeks from now, placed optimistically in a window between two pitches and a brand refresh kickoff. The meeting gets bumped. Then bumped again. And then, quietly, with no ceremony whatsoever, it disappears from the calendar entirely and is never spoken of again.
This is not an accident. This is the creative industry’s most consistent, most consequential, most completely ignored ritual: the post-project debrief that was always going to happen and never does.
The One Meeting That Would Actually Make You Better
Let’s be honest about what a proper debrief looks like in theory. You sit down as a team — creative, account, strategy, production — and you ask the questions that matter: What did the client actually want versus what they said they wanted? Where did the brief go wrong? Which revision killed the concept and why did we let it? What would we do differently, and is “differently” even possible given the same constraints?
This is, in principle, the single most valuable meeting any creative team can have. It contains the institutional knowledge that would make the next project better, the next brief sharper, the next client relationship more honest. It is, practically speaking, a free training programme conducted by people who were actually there.
Which is precisely why nobody does it. In a business where the incentive structure rewards the appearance of momentum over the reality of learning, stopping to reflect is structurally penalized. The next project is already waiting. The next client has already called. There is always, always a fire that needs putting out more urgently than the education that comes from examining last fire’s ashes.
The Institutional Amnesia Industrial Complex
The creative industry has developed an almost pathological relationship with forgetting. Teams make the same mistakes on the same types of projects for the same types of clients, year after year, because the knowledge that would prevent those mistakes lives in the heads of people who are already three projects behind and therefore not available for the conversation.
Senior creatives carry scar tissue that junior ones haven’t earned yet. Account managers develop instincts about which clients will pull the budget in Q4, which approvals will take four weeks regardless of what the brief says, which stakeholder’s opinion will surface in round seven with enough force to undo everything that came before. This is valuable intelligence. It is almost never written down. It circulates through gossip, through warnings issued on the way to a kickoff, through the knowing look exchanged between two colleagues when a particular client name appears on a project brief.
The debrief would capture this. The debrief would turn individual scar tissue into collective immunity. But the debrief doesn’t happen, so instead every new project manager learns the same lessons from scratch, usually on a Tuesday afternoon when the stakes are highest and the time is shortest.
Some agencies have tried to institutionalize this through project management tools, post-mortem templates, end-of-quarter review sessions. These efforts are not wrong. They are just, reliably, populated with information so sanitized it is useless. Nobody writes in the retrospective template that the brief was incoherent because the client doesn’t actually know what they want and the account team was too afraid to push back. Nobody notes that the concept died in internal review because the creative director had a territorial moment in front of the client. The template gets filled with observations like “communication could be improved” and “timeline had some challenges” and then filed somewhere that ensures nobody reads it.
What We’re Actually Protecting When We Skip It
Here is the uncomfortable truth about why debriefs don’t happen: they require honesty that most agency environments aren’t structured to support. A real debrief means asking whether the brief was good. It means asking whether the account team protected the work or protected the relationship. It means asking whether the creative direction made the work better or just made it different. These are reasonable professional questions. They are also, in most workplace cultures, socially catastrophic to ask out loud.
So instead, agencies develop a collective fiction about each project. The narrative gets assembled in the week after delivery: the difficulties become “challenges we navigated,” the compromises become “collaborative refinements,” the disasters become “learning experiences” in a way that ensures nothing is actually learned. The team moves on, carrying the same unexamined assumptions into the next brief, where they will produce slightly different versions of the same outcome.
This is not laziness. It is self-preservation. And it is costing the industry — in repeated mistakes, in avoidable conflicts, in the slow accumulation of bad habits that eventually become agency culture.
You can track your project’s performance with the approach outlined in our honest guide to KPIs — the numbers that actually matter — but metrics can’t capture whether your team learned something or just survived something. That distinction requires a conversation nobody is scheduling.
The Anatomy of the Almost-Debrief
When debriefs do happen, which is approximately as often as a client reads the brand guidelines, they follow a predictable structure. First, fifteen minutes of everyone agreeing that the project “went pretty well overall.” Then, ten minutes of diplomatically worded feedback that sounds like criticism but has been sanded down until it’s aerodynamically inoffensive. Then, one person with either no political instincts or a pathological commitment to honesty says something true, the room goes slightly awkward, and the session ends two items before the agenda concludes with everyone agreeing to “action items” that will be forgotten before the lift doors close.
What’s missing is the psychological safety that would allow the actual conversations to happen. The account manager won’t say the client brief was inadequate because they wrote part of it. The creative lead won’t say the revisions undermined the work because the person who approved the revisions is sitting across the table. The junior designer won’t say they had a better idea in round two that got dismissed because that’s not how junior designers survive in agencies.
A debrief is, at its heart, an exercise in institutional honesty. And institutional honesty requires trust, psychological safety, and a culture that rewards accurate diagnosis over comfortable fiction. Most agencies do not have this. Which is why most agencies keep making the same mistakes, booking the same types of difficult clients, producing the same kind of compromised work, and wondering why the industry feels increasingly like running in place.
The Brief That Would Actually Help
If debriefs did happen — properly, honestly, without the performance of politeness that makes them useless — what would they produce? Probably something like this: actual intelligence about which client relationships are structurally healthy and which ones extract value without creating it. Real data about where projects derail and at which point intervention would have helped. Honest assessment of which creative directions were genuinely strong and which were defended out of ego rather than conviction.
They’d produce, in short, a more honest picture of how the work actually gets made. And that picture, however uncomfortable, is the only foundation on which you actually improve.
The irony is that the industry spends enormous resources on planning — on brief development, on strategy decks, on kickoff meetings that should have been emails (we’ve written about those) — and essentially nothing on learning from what happens after. We plan aggressively and reflect almost never. We treat the beginning of a project as the critical moment and the end as a formality to be processed quickly before the next beginning.
The debrief would close that loop. It would connect end to beginning in a way that actually accumulates wisdom rather than just accumulating invoices. It would make the agency, over time, genuinely smarter about its own work.
But it’s Tuesday and there’s a pitch on Thursday, so let’s just move on.
If you’re tired of surviving projects that could have been better, visit the NoBriefs shop — built for creatives who’ve made it to the end of the project and are already being handed the next brief before they’ve caught their breath. Because the work doesn’t stop. It just changes clients.
