The projects that go well are the ones where the client sends me a photograph of something real in the first message. A ribbon, the venue, the dress fabric, the cake, the wall colour of the room it is happening in. That one image is worth more than a page of description, because it fixes a colour and a mood I would otherwise be guessing at.
Everything else in this post is downstream of that. Design work is a translation problem: what is in your head has to get into a file. Most of what makes a project smooth is about making that translation shorter.
What to send at the start
Send these six things in your first message and the first concept will be much closer:
- The facts. Occasion, date, start time, venue name and city, and roughly how many households. Time of day matters more than people expect, because an evening event and a lunchtime event want different weight and different colour.
- A photograph of something real. The venue, the flowers, a fabric, a paint chip, a piece of furniture in the room. Real objects have fixed colours. Screenshots do not, because your screen has already changed them.
- Two or three references you like, with one sentence each saying what you like about it. The sentence is the important part. “This one, but for the type” and “this one, but for the colour” tell me two entirely different things about the same two images.
- One thing you have seen and disliked. This is the most underused piece of a brief. Knowing you hate script, or hate cream, or hate anything that looks rustic, eliminates a whole quadrant immediately.
- Constraints you already have. An envelope you have bought, a size the printer requires, a colour the venue is imposing, a deadline that is not moving.
- Wording, or a note that you do not have it yet. Placeholder is fine early. The wording guides will sort the final version.
What is not useful is a Pinterest board with forty pins and no commentary. Forty pins tell me you have been looking. They do not tell me which three you would actually choose, and a board usually contains contradictory directions that you resolved in your head without noticing.
How revisions actually work
A revision round is one collected set of changes, considered together, applied in one pass. It is not one change.
That distinction is where most confusion comes from. If you send me four separate messages across three days, each with one change, that is not four rounds and I will not treat it as four rounds, but it is a worse way to work than one message with four notes. Changes interact. Making the date bigger affects the space around the names, which affects whether the venue line still balances. If I make those adjustments one at a time in sequence, I am re-solving the same layout four times, and each solution is compromised by the last.
So the useful habit is to sit with a concept for a day, write down everything, then send it once. Sleep on it if you can. The notes people write immediately and the notes they write the next morning are often different, and the next morning ones are usually right.
Rounds are finite. That is not a trap, it is what keeps a project from wandering forever, and in practice most projects use fewer than they have. What uses them up is not the number of changes, it is changing direction. Two rounds of refinement is normal. A round that says “actually, what if it were completely different” is a new project wearing a revision’s clothing.
How to give feedback that works
“I do not love it” is a real feeling and it is not usable information. Not because you owe me a diagnosis, but because I cannot act on it, and I will have to come back and ask, which costs you a day.
The trick is to describe the effect rather than prescribe the fix. You are the expert on how it feels. I am the one who knows which lever produces that feeling.
Instead of “make the names bigger”, try “the names are not the first thing I see”. Those sound the same and they are not. The second one might be solved by size, or by moving the names, or by lightening what is competing with them, and one of those three is better than the others.
Some translations that work:
- “It feels cold.” Actionable. Usually palette temperature or the amount of white space.
- “It feels cluttered.” Actionable. Usually too many pieces of information at equal weight.
- “It looks like a business card.” Very actionable. Nearly always the typeface or the alignment.
- “It does not feel like us.” Actionable if you follow it with one sentence about who you are. “We are quite casual and this looks formal” is enough.
- “Can you try a few options?” Not actionable, and it usually means something specific is wrong that you have not put your finger on yet. Tell me what you are reacting to and I will find it faster than a shotgun of variations will.
Also worth saying: if you like it, say that clearly. Designers get a great deal of “hmm, let me think” and it is genuinely hard to tell the difference between quiet approval and quiet disappointment.
One voice, please
If a project has three decision makers, that is fine, but I need one person to talk to.
The failure mode is not disagreement, it is receiving contradictory instructions in two separate messages, agreeing to both, and producing something that satisfies nobody. It happens most often on weddings with involved parents and on organisational work where a committee is involved.
So gather the opinions on your side, resolve the contradictions between yourselves, and send me the resolved version. If two people genuinely disagree and want my view, ask me directly and I will give you a straight answer about which one serves the event better.
Timing, and the thing that actually causes rushes
The most common cause of a rushed project is not a late start. It is wording that is not finalised.
Design and copy are not independent. A layout built around a two line hosting statement does not survive that statement becoming four lines, and a name that grows from eight characters to twenty-two changes the whole balance of a card. Every time final wording arrives after the design is settled, the design gets reopened.
So settle the wording early, even roughly. Names spelled exactly as they will appear, including middle names and honorifics. The hosting line agreed with whoever is hosting. Titles right. And once the design is approved, proofread it properly, out loud, with someone else reading the original details aloud to you. Check the day of the week against the date. That is the single most common error on a finished invitation and it is invisible to everyone until the day it is not.
What you get, and where the project ends
Because I deliver files rather than printed pieces, the handover is the end of my part. You get a print-ready PDF built to your trim size with bleed, plus the text-message and story-sized files for sending digitally.
Printing, envelopes, addressing and mailing are yours. I am happy to tell you what to ask a printer for, and to set the files to whatever specification they give you, but I do not place the order and I do not manage the print. Knowing that boundary at the start is part of what makes a project go well too.