How to brief a designer from swipe comments
Swipe comments can become a design brief when you cluster them first. Hire the designer for one change the votes repeated, not for a mood called make it pop.
Picture Lena, a founder in Berlin, forwarding a homepage detail page to a designer with the note "they hated it, can you make it better before Friday." The designer opens the capture, sees a crush rate, a pile of comments, and no rank order. Friday will produce a new visual system because that is what an open brief produces. The comments that said the buyer was missing will survive inside a prettier file. Lena will have spent the engagement and will not know if the noun got fixed. A brief from swipe comments is the opposite shape. The comments pick one job. The designer does that job. LandingCrush does not do the design work, and the about page says the product's feedback is not professional design advice.
Start from the cluster, not from the rate. The clustering steps are in how to turn roast comments into an edit. This article assumes you have a repeated, specific point and you need someone else to execute it. If you do not have the cluster yet, do not hire. You would be paying a professional to guess which orphan comment was the strategy.
Write the brief on one page, in this order
The order matters because designers, like founders, will gravitate to the most interesting constraint if you bury the job.
The job is one sentence. "Make the first screen name a finance lead and ask only for a demo. Leave the product's actual offer alone." If the sentence needs "and also refresh the brand," you have two projects. Split them. The vote can judge one.
The evidence is three comments, quoted, plus the crush rate and the vote count so the designer knows the sample. Include a comment that disagrees, if you have one, so you are not hiding the split. "Four comments say the buyer is unclear. One says the page is fine and the logo is the problem. Rate is 52 percent on 63 votes." That is a grown-up brief. A folder of screenshots with no quotes is not.
The non-goals are a list. Do not redesign the type system. Do not change the button's destination. Do not add a second hero action. Do not invent a customer metric. Non-goals are how you keep Friday from becoming a new company. They feel restrictive. They are the kindness. A designer can do excellent work inside a fence. Without a fence they have to interview you for the strategy, and you already spent the comments on that interview.
The offer line sits under the non-goals. Who it is for, what they get, what they do next. The designer may not break that line to make a layout work. If the line is too long for the phone, the job is to keep the meaning and cut words, not to swap the buyer for a shorter noun. The headline rules in how to test a headline without changing the offer apply to the words they propose.
References are optional and dangerous. If you include a Hall of Fame page, include the critique note that says what you are borrowing and what you refuse to copy. A naked screenshot will be treated as a spec. The refusal list is in the Hall of Fame critique. One reference is enough.
Hand over the capture they must beat
Give them the exact desktop and mobile captures that were submitted, not a Figma file that has already drifted. The vote was on the capture. A brief that points at a newer, unsubmitted file asks the designer to fix a page voters never saw. If the product has moved on, say so and consider the comments historical. Do not pretend the old roast applies to a hero you rewrote yesterday.
Tell them which screen the cluster is about. A mobile complaint fixed only on the desktop frame will look done in review and fail the next phone vote. Ask for both captures back, at the same crop you can submit. LandingCrush accepts a URL or uploaded screenshots. The file you get back should be submittable without a reinterpretation.
Ask for one alternative, not three directions, when the cluster is specific. Three directions reopen the strategy. You can explore directions before a vote, in your own time, including with the Style Explorer as a way to look at visual approaches. Once comments have named a job, more directions are how the job gets diluted. If the designer believes the job is wrong, they should say so before drawing. That conversation is cheaper than three unused files.
Review the work against the cluster, not against taste
When the file returns, run the comments like a checklist. Did the buyer get named? Does the first screen ask for one action? Did the offer line survive? Did any non-goal get violated? Score those pass or fail before you talk about whether you like the picture. Liking the picture is allowed. It is not the acceptance test. The acceptance test is the sentence you hired them with.
Run the five-second timer yourself, logo covered, using the hero check. If you cannot say the buyer and the action, the file is not ready, even if it is handsome. Send it back with the failed line. Do not add a new requirement in the same email. Scope creep at review is how briefs rot.
You might be thinking a good designer should also fix the things you did not mention. They will see those things. Park them. A second problem can be the next brief after the next vote. If you accept a bonus redesign, you cannot attribute the next crush rate to the cluster. You will be back in Lena's Friday, with a prettier page and a muddy lesson.
The AI critique scores are not a brief. A 6 out of 10 on visual hierarchy is a model's note from 0 to 10. It can hint. It cannot replace quoted comments. If you paste a panel verdict into the brief, label it as a preview from fictional personas and do not let it outrank the cluster. The separation is in the AI Panel article.
Submit the designer's page as a variant, then pay attention to the same cluster
The design is not done when you like it. It is ready to be judged again. Submit it. If the old page should remain live for a comparison, you need a submission slot for both. The free plan includes one active homepage. Creator Pro includes unlimited submissions at $19 a month or $190 a year. Wait for approval. Then read new comments for the original cluster.
Success is specific. People stop saying the buyer is missing. They may start saying something else. That is a new cluster, not a failure of the designer, unless they broke a non-goal and caused it. The crush rate may move modestly. Read it with the count and with velocity so a quiet week does not look like a verdict. Those readings are in the velocity article and the crush-rate article beside it.
If the cluster remains, do not immediately commission a new visual system. Look at whether the words actually changed. Many "redesigns" keep the vague noun and restyle the frame. The voters were never angry at the frame. Show the designer the new comments and the old sentence. Ask for another pass on that sentence only.
Pay for implementation quality. Hierarchy, spacing, button states, and a mobile layout engineering can build are the designer's craft. LandingCrush will not specify a type scale. A crush rate will not either. The comparison of votes, designers, and friend polls is the longer version of who owns which question. Your brief should respect the line. You bring the repeated comment. They bring a page a developer can ship. The swipe tells you whether the comment went quiet. Your analytics tell you whether the business moved after you ship.
Keep the brief in the project so Friday stays small
Attach the one-page brief to the submission note. The next person who wants to "take it further" has to argue with the non-goals. That friction is healthy. Homepage design expands to fill the anxiety in the room. Comments are a way to shrink the anxiety to a sentence. A designer who receives a sentence can finish. A designer who receives a feeling will keep going, because the feeling has no edge.
The next time you forward a detail page, can you point to the one sentence the designer is allowed to make true?
Common questions
Q: Should I send the designer every comment?
A: Send the cluster, quoted, and one disagreement if it exists. A dump of every remark, including jokes, recreates the unranked pile.
Q: Can LandingCrush replace the designer?
A: No. Votes and comments record preference and criticism. A designer builds the page. The product describes its feedback as informational, not as a design engagement.
Q: When do I know the brief worked?
A: When new comments stop repeating the problem you hired them to fix, on a vote count you are willing to cite. The crush rate alone is not the acceptance test.