How to run a 1:1 with a designer who thinks everything is fine

Some people tell you when something is wrong. Others don't. The ones who don't aren't hiding things from you maliciously. They've usually developed a pattern of handling friction internally, and the 1:1 doesn't give them a compelling reason to break it.

If you're getting "things are good" every week from a particular designer, the most common reading is that things genuinely are good. The second most common reading is that the designer doesn't expect the 1:1 to be useful, so they're going through the motions. That second case is worth distinguishing from the first, because the designer who says everything is fine right up until they give notice will show up in your retrospective as obvious in hindsight.

The format problem

Most 1:1s are structured in a way that rewards people who come prepared with problems. You ask what's on their mind. If nothing is, the meeting loses direction and both people fill the time with project status updates.

Status updates are the enemy of a good 1:1. Not because they're useless, but because they replace the kind of conversation that only happens when there's no other venue for it. If the 1:1 becomes a project check-in, the designer learns that the meeting is for reporting, not for talking about how work actually feels, what's frustrating them, or what they want to be doing differently.

Quiet designers will default to reporting because it's easier and expected. Your job is to make the conversation worth more than that.

What tends to open things up

The questions that produce real information are usually specific and backward-looking. "How did that presentation go?" is better than "How are you feeling about your work?" The first one has a concrete answer. The second one requires the designer to interpret their emotional state and decide whether to share it, which is a higher bar.

Ask about moments, not states. "Was there anything this week that felt harder than it should have?" is more generative than "Is anything frustrating you?" The first question is easier to answer because it references an event rather than a disposition.

You can also ask about the work in ways that surface friction without framing it as a complaint. "What would you have done differently on that project if you'd had more time?" often produces honesty that "what's not going well?" doesn't.

The goal is to lower the cost of saying something true. Quiet designers don't typically stay quiet because they're secretive. They stay quiet because the effort of raising something doesn't feel worth the uncertainty of how it will land.

When to push and when not to

There's a version of this that tips into pressure, and it's worth knowing the difference. Asking more specific questions and creating better conditions for honesty is one thing. Communicating that you need the designer to surface problems, that their silence is itself a problem, is another.

Some people are private. Some are processing slowly. A designer who says things are fine every week and then, six months in, raises a well-formed concern about something that had been bothering them is not someone who failed to give you real-time feedback. They just worked differently from the extroverts on your team.

What you're trying to detect is disengagement, not introversion. The signals are different. A disengaged designer stops bringing ideas, starts doing minimum-viable work, and goes quiet in group settings too. An introverted designer keeps producing and still shows up, just doesn't narrate their inner experience in 1:1s.

What I've found actually works

The most reliable tool I've found is consistency over time. A quiet designer who has had twenty 1:1s with the same person will eventually say something true, because they've built up enough evidence that the conversation is safe. The designers who leave without warning are usually the ones whose manager gave up on the meeting after a few uncomfortable silences.

One thing that helps is sharing something yourself. Not performing vulnerability, but being concrete about something you're working on or uncertain about. It demonstrates that the meeting is bidirectional and that honesty doesn't require having a crisis to report.

The last thing worth noting is that "everything is fine" can be true. Some designers genuinely have a relatively low-friction experience at work for long stretches. Don't manufacture problems to find if there are none. But if the phrase "everything is fine" has started to feel like a formality rather than an observation, that's worth staying curious about.