The classic trap for a designer who posts is the showcase: a polished mockup, three emojis, "excited to share". Recruiters, product managers and fellow designers read for something else. They want to see how you think: which problem, which hypothesis, which trade-off, which observed result. The five templates below start from moments you already live through on a project. Replace the brackets with true facts, and only publish what your employer or client allows you to show.

What makes a UX designer's post credible

Your readers fall into three groups: peers judging rigor, recruiters looking for signs of method, and product teams wondering how you work with them. A few rules serve all three.

  • A problem before a screen. Open on the user's difficulty, not on the interface you drew.
  • An observable fact: a sentence heard in a test, a flow abandoned at a precise step, a real technical constraint.
  • An owned decision, with what you ruled out and why.
  • No confidential data: blur brands, drop internal figures, ask permission before showing a screen.
  • A closing question a peer can answer in one line.

Template 1: the hypothesis that turned out wrong

This is the most honest format and the one peers read most. Tell what you believed, what the test showed, and what you changed.

I thought a single-page form would feel reassuring. In a test with five people, three hesitated at its length and dropped out before the second block. We split it into three steps with a visible summary each time. My takeaway: a long form scares people before they even read it. Which hypothesis surprised you most this year?

Keep the lesson actionable: a reader should be able to reuse it in their next test, with their own users. Avoid grand conclusions drawn from five participants: say plainly that it was a small test, and what you would check next with more people.

Template 2: the design decision explained

Changing a button label, removing a field, moving a navigation: these decisions look small, but readers want the reasoning. Give the context, the options you set aside and the criterion that decided it.

We removed the "company" field from the [product] sign-up form. Context: many visitors stopped at that line. Options set aside: making it optional, because it would still have been a point of hesitation. Deciding criterion: ask for the company later, once the person has seen the value. We will track whether completed sign-ups change. How do you trade off useful data against friction?

Saying what could change your mind is a mark of maturity. It shows the decision depends on context.

Template 3: a user interview takeaway

One sentence from a user is often worth more than a chart. Quote it without a name or company, and explain what it changed in how you design.

In an interview, a user told me: "I never know if it's saved." Nothing in the interface reassured her. We added a discreet "Saved at 2:32 pm" state at the top of the page. It is not spectacular, but the doubt disappeared from the following interviews. Which user sentence made you change a screen?

Template 4: working with developers

Few designers talk about what happens between the mockup and production, yet product teams appreciate it most. Tell about a compromise, a constraint found late, a solution found together.

My mockup had a smooth animation on the dashboard. Talking with the engineering team, we saw it would slow loading on modest devices. We replaced it with a simple state change that renders faster. My takeaway: asking early what is expensive to build saves everyone time. Which design and engineering trade-off taught you the most?

Template 5: the case study in three lines

A full case study lives on your portfolio. On LinkedIn, sum it up in three lines: the problem, what you did, what you observed. Put the link in the first comment rather than in the text, so the post stays readable without leaving the page.

Problem: new [product] customers could not find the billing page. What I did: a card sort with eight people, then a new navigation structure. What I observed: in testing, everyone found the page on the first try. The detailed case study is in the comments. What would you do differently?

Rhythm, hooks and publishing

A sustainable rhythm beats an ambitious one: a post every week for three months says more about you than ten posts in two days followed by silence. Vary the templates, read each post aloud, and cut any sentence you would not say to a colleague across the table.

For the first sentence, draw on our LinkedIn hooks. Other jobs have their own angles: see the templates for a software developer, useful if you work daily with an engineering team, or the full set of LinkedIn post templates. To understand why a post is or is not pushed, read the LinkedIn algorithm entry.

A word on the first hour: answering the first comments sincerely is part of the job. Podavera helps you get exchanges on your posts among professionals, but no tool replaces a useful post. You can create a free Podavera account and start with 20 free credits.