Design X runs on shared work: redesigns, before and afters, portfolio launches, half-finished components posted at midnight. The replies under them split into two piles. "Clean!" and "love the type" in one pile. Unasked-for redesigns and "the kerning is off" in the other. Neither pile gets anyone followed, because neither shows how the replier thinks about design.
The replies below do. They name one thing that works, in design language, and offer one observation the author can act on. They also know when to ask before critiquing, which is a skill most of the second pile has never learned. Fifteen examples, grouped by the kind of post, each with a note on why it works. Make them yours by swapping in what you actually see.
Ask before you critique
A post that shows work is not always a request for feedback. Someone sharing a finished client project wants it seen, not fixed. Someone posting "thoughts?" with a screenshot wants exactly the opposite. Read the caption first. When it is unclear, the first reply can be a question: what stage is this at, and what are you unsure about? That one question is worth more than any critique delivered to someone who did not want one.
When critique is wanted, the structure that works is one specific strength, one specific observation, in the vocabulary of the craft. Hierarchy, contrast, spacing, type scale, affordance. Not "it feels off". The vocabulary does two jobs: it makes the feedback usable, and it tells everyone reading that you know what you are looking at.
Replying to a redesign
A before and after redesign
The after has one clear primary action and the before had three, which is the whole win here. One thing to check: the secondary text dropped to a grey that may fail contrast on the lighter background.
- Why it works:
- You name the structural improvement in design terms, then flag one measurable issue. Both are things the author can verify.
A redesign that lost something
Cleaner, no question. I miss the price being visible before the click though. Was that a deliberate move to the next step, or did it fall off during the simplification?
- When:
- The new version is prettier but dropped information.
- Why it works:
- You credit the improvement and raise the loss as a question, leaving room for a good reason you do not know about.
A redesign where the type is off
The new type scale has two sizes doing one job: the card title and the section label are close enough that my eye treats them as the same level. Bumping the label down a step would separate them.
- Why it works:
- A precise diagnosis with the fix built in. The author can test it in two minutes.
Someone asks which version is better
B, for one reason: the eye lands on the headline first and then the button. In A it lands on the illustration and has to come back. Pretty is a tie, hierarchy is not.
- When:
- An A or B poll with two screenshots.
- Why it works:
- A vote plus the single reason behind it, in a form other designers will agree or disagree with.
Replying to work in progress
Early work needs different feedback from finished work. Polishing notes are wasted on a wireframe. The useful reply at this stage is about structure, audience or the screen they have not designed yet.
An early draft, asking for thoughts
At this stage I would only ask one thing: who is this screen for, the person setting it up or the person using it every day? The answer decides whether settings belong up front or tucked away.
- Why it works:
- You hold back the polish notes and ask the question that shapes everything after it.
A work in progress with a gap
Promising. Before polishing, the empty state is going to be the first screen most users see, and right now it is a blank card. Worth designing that one early, it changes how the rest feels.
- Why it works:
- You point at the missing screen rather than the visible one, which is the kind of thing experienced designers notice.
A designer stuck on a component
Had this exact problem with a date range picker. What worked was two separate inputs with a calendar that only appears on focus. The combined widget looked smarter and tested worse.
- When:
- Someone is iterating in public and frustrated.
- Why it works:
- A solution from your own work, with the honest note that the clever version lost.
Replying to portfolio and case study posts
A portfolio launch
The case studies that say what you were asked to do and what you changed your mind about are the strong ones. The second project does this and the first does not. I would lead with the second.
- Why it works:
- Feedback on the storytelling, not the pixels, with a concrete reordering they can do tonight.
A case study with no outcomes
Beautiful work. The thing a hiring manager will look for and not find is what happened after launch. Even "shipped in six weeks and onboarding tickets dropped" would carry it.
- When:
- A case study shows process and visuals but no result.
- Why it works:
- You name the reader (a hiring manager) and give a modest example of what would satisfy them.
A student or junior shares work
This is good for where you are, and the icon set is better than most paid ones. Two things to practise next: spacing between groups, and one colour fewer per screen. Keep posting these.
- Why it works:
- Honest about level, specific about the strength, two practice targets, and encouragement to keep sharing.
Replying to design debates
A take that designers should code
Learned enough to prototype and it changed my hand-offs more than my designs. I do not ship code and do not want to. "Should code" and "should understand constraints" are different claims.
- Why it works:
- Personal experience, a clear boundary, and a distinction that reframes a tired debate.
A debate about design systems
Ours saved us on the third product and slowed us on the first. With one product, a Figma file with strict naming does most of the job. The system earns its cost when something has to be the same in two places.
- Why it works:
- Both sides from the same team's history, ending with a rule of thumb people can apply.
Someone says a famous redesign is bad
The icon is weaker, agreed. But look at the app chrome: they moved the main action into the thumb zone and made the type bigger. The logo is what people can see in a post, the rest is what users feel.
- When:
- A big brand rebrand is getting dunked on.
- Why it works:
- You concede the popular point and redirect attention to the part that matters in use. Designers will reply.
When the work is simply good
Sometimes there is nothing to fix. Say so, name what makes it good, and ask about the craft. A question about how they did it is the most flattering reply a designer can get.
Work that needs no fix
Nothing to add. The way the labels sit inside the fields and then slide up is the smoothest version of that pattern I have seen. Which easing did you use?
- Why it works:
- Specific praise in craft language, then a question about method that the author will enjoy answering.
A designer shares a process shot
The thirty rejected marks are the most useful part of this post. Most people only show the winner. The one in the second row, third from left, would have been my pick. Curious why it lost.
- Why it works:
- You reward showing the process, pick a specific rejected option and ask about the decision. Three reasons to reply.
Making these yours
- 01Read the caption to learn what kind of feedback, if any, is wanted. When unsure, ask what stage it is at.
- 02Find the one structural thing that works and say it in craft vocabulary: hierarchy, contrast, spacing, affordance.
- 03Pick one observation they can act on today. Prefer things they can verify (contrast, type scale) over taste.
- 04For early work, skip polish and ask about audience or the missing screen.
- 05For finished work you admire, ask about method. Easing, grid, type pairing, how many rounds.
- 06Keep it to three lines. If you have more, offer to send notes by DM and let them choose.
Do
- Name the specific strength before any observation.
- Ask before critiquing when the caption does not invite it.
- Use measurable language where you can: contrast, size steps, alignment.
Don't
- Do not post your own redesign of someone's work in their replies unless they asked for one.
- Do not say "it feels off" without saying what and where.
- Do not critique a junior's work the way you would a senior's. Two practice points, not ten.
Replies bring people to your profile, and a designer's profile has to show work. The X growth guide for designers covers how to post visually without becoming a portfolio dump, and post ideas for designers has worked examples. When the critique lands on you, replying to criticism has the other side of this page. Sharing a text post as an image is one way to show type choices, and the post to image tool does that in the browser.
GuideX growth for designersProcess shots, redesigns of real things, critique as a two-way format and the text that carries an image.BuzzyX · X growth workspace
Grow on X with posts that sound like you.
Compose in your voice, schedule the week, find posts worth replying to and read real analytics from the X API. $29/mo after the trial, everything included.
Frequently
asked questions
Something else on your mind? Get in touch.
Should I give critique that was not asked for?
Not on finished or client work, and not on a post that is clearly celebrating. If the caption asks for thoughts, go ahead. If it does not, ask what stage it is at or whether they want notes, and respect the answer.
How do I critique without sounding arrogant?
Lead with a specific strength, frame observations as things you noticed rather than verdicts, and use questions where you might be missing context. "Was that a deliberate trade-off?" is critique that respects the designer.
Is it okay to disagree with a popular designer's take?
Yes, with reasons from your own work. Design X rewards a well-argued minority view far more than it punishes it, as long as the tone stays about the work and not the person.
What if I only have praise?
Make it specific and ask about the craft. Naming the exact pattern you admire and asking how it was built is a reply designers love to answer, and it shows your eye as clearly as a critique would.
Should I reply with my own version of the design?
Only when explicitly invited, and even then as an offer rather than a reveal. Posting your redesign under someone's work reads as a takeover. A DM with notes, offered in the reply, is almost always better received.