Module 5: Working Process
Talent gets you hired once. Process gets you rehired. This module is the unglamorous machinery that keeps design work profitable: briefs that surface problems before you've designed anything, revision rules that stop the endless loop, and delivery habits that make clients feel looked after.
Briefs that prevent chaos
Most bad design projects aren't bad design — they're bad briefs. "Make it pop" is not a brief. Neither is a screenshot of a competitor with "like this, but different." Your job, before any design happens, is to run a short intake that forces the decisions clients usually postpone until revision three. Ten minutes of questions here routinely saves three rounds later, and rounds are where freelance margins go to die.
The questions that matter: Who is this for? (One audience, described concretely — "women 30–45 who already follow two other coaches" beats "everyone.") What should it make them do? Book, buy, save, share, show up. What does the brand never do? Colors, words, imagery that are off-limits. Show me three things you like and one you'd never post. Examples communicate taste faster than adjectives ever will. What already exists? Logo files, photos, past posts that worked. Who approves, and by when? One named person, one deadline. Put it in a form, not a chat thread, and keep the answers in the project file.
Then play it back. Before designing, send a short note: "Here's what I'm making, for whom, in this style, delivered on this date — tell me now if I've got any of it wrong." That message feels like overhead. It is actually insurance: most "you went the wrong direction" disasters die right there, while fixing them still costs a sentence instead of a redesign. If a client resists the brief itself — won't name an audience, won't share examples, wants you to "just try some things" — that's a red flag about how every future round will go. Price that risk in, or walk.
A new client wants a flyer designed today. Their whole brief is: "Something bold and modern — make it pop. You'll know it when you see it. Audience is basically everyone." What do you do first?
Revision discipline: rounds in writing, feedback translated
Revisions are where design work quietly stops being profitable. A package priced for two rounds that takes five has effectively cut your rate nearly in half, and the damage rarely comes from a difficult client — it comes from a process that never defined what a round is. So define it, in writing, before work starts: a revision round is one consolidated set of changes requested at one time, against the agreed brief. Two rounds are included in most packages. A change of direction — new audience, new offer, "actually, let's try a totally different look" — is not a revision. It's new scope, quoted as such.
The second skill is translation. Clients give feedback in feelings: "it's not premium enough," "my partner thinks it's boring," "can it be more fun?" Feelings aren't actionable until you convert them into design decisions: premium becomes more whitespace, a serif display face, and a restrained palette; boring becomes a stronger first-frame contrast and one bolder claim. Reply with the translation, not a fresh guess: "To make it feel more premium, I'll open up the spacing, switch the headline to the serif, and pull the palette back to two colors — say the word and I'll run that round." Now the client is approving a direction, and the next version tests a decision instead of your telepathy.
Keep every round in one written thread, with versions numbered and dated. When round four arrives, you don't argue — you point at the record and offer the options: ship version three as approved under the brief, or open a change order at your stated rate for the new direction. Said early and calmly, with the paperwork right there, this conversation is short. The clients worth keeping respect it, because the same discipline that limits their revisions is what gets their work delivered on time.
Your package includes two revision rounds. A client is on round two of a post set and writes: "Actually, let's scrap this direction entirely — new offer, younger audience, brighter look. Should be quick." What's the professional move?
Delivery: files, naming, and organization clients bless you for
Delivery is the last thing a client experiences in every project, which makes it the thing they remember. A designer who sends one flattened image in a chat thread, named final_FINAL2.png, forces the client to become their own file clerk. A designer who delivers an organized folder gets described to other business owners as "so professional" — and referred.
Deliver in a structure, every time. A project folder with subfolders by use: Print (press-ready PDFs with bleed where relevant), Social (exports at platform sizes, named by date and topic), Web (right-sized, compressed images), and Source (the editable Figma link or packaged Illustrator files, per your agreement). File names should tell a stranger what the file is without opening it: brand_project_assettype_date_v1. No "final" in a filename, ever — versions are numbers, and the number in the folder is the truth. Include a one-line readme in the folder: what each subfolder is for and which file to send the printer.
Two habits seal it. First, send exports in the formats the client will actually touch — PNG and JPG for social, PDF for print, SVG for logos — rather than making them ask you to convert things at 9 p.m. before a launch. Second, keep your own archive of everything, organized the same way, for at least a year. Clients lose files constantly. The designer who re-sends the exact asset in four minutes, from a system instead of a scroll through old messages, has just demonstrated precisely why the retainer is worth it. Sloppy delivery makes good design feel amateur. Clean delivery makes solid design feel premium — at zero extra design cost.
A client messages at night: "Printer needs the logo file in an hour and I can't find it." Six months ago you delivered it inside a chat thread as logo-final-final.png. What does this situation most directly show?
What you can now do
- Run a short intake before any designing that forces the decisions clients usually postpone until revision three — ten minutes of questions that save rounds later.
- Define a revision round in writing before work starts — one consolidated set of changes, requested at one time — and translate vague feedback into specific, actionable moves.
- Deliver an organized folder with sane file names a client can navigate without you, instead of one flattened image in a chat thread named final_FINAL2.png.