The check-in rarely fails at the question. It fails at the reply.

"How are you going?" "Yeah, fine. Busy." Most check-ins end there, and most leaders count it as a check-in done. The question was asked, the intention was good, and everyone moves on to the agenda. But a check-in is not measured by whether you asked. It is measured by what happened in the minute after the answer. Most leaders know this instinctively. Very few have ever had that minute modelled for them.

Organisations have spent years encouraging leaders to ask. Far less attention has gone to what to say when the answer is not "fine". That is the moment the conversation is won or lost, and it rarely takes more than a minute. It is also the part that decides whether people answer honestly next time.

Four replies that close the door

None of these is unkind. Each is a reasonable instinct. That is why they are so common.

Solving too early. "Have you tried blocking out time in your calendar?" The advice may even be good. But it arrives before the person has finished, and it signals that the conversation is now over.

Reassuring too fast. "You will be fine, you always are." Comforting to say, and it closes down the very thing the person had started to share.

Making it about you. "I had exactly the same thing last year." Meant as solidarity, it moves the spotlight. The person stops talking and starts listening to you.

Closing the loop before anything changes. "Let me know if you need anything." A sincere offer that hands the whole next step back to the person who was already finding it hard to ask.

Why good leaders fall into them

Most leaders were promoted for solving problems. When someone says "not really", the instinct to fix is strong, and so is the discomfort of not knowing what to say.

In A+B=C terms, the leader is having their own reaction. The answer is the event. A thought arrives, often "I need to fix this" or "I am not equipped for this". The feeling that follows is the warning, and the quick reply is the behaviour that ends the conversation. Last week’s post The announcement was the same. The thought was not. looked at the person receiving the news. This is the leader on the other side of the table.

What the research says, and what it does not

Professor Amy Edmondson's research at Harvard defines psychological safety as a shared belief that a team is safe for interpersonal risk-taking (Edmondson, 1999). Her work links it with team learning behaviour: people raising problems, asking for help and admitting mistakes.

Her research does not show that any single conversation creates psychological safety. It is a shared belief, built across many small moments. But the reply to "not really" is one of those moments, and people remember it. It tells them whether to answer honestly next time.

It also explains why a single good check-in can feel as though it changed nothing. The benefit builds over time, and so does the cost of the reply that closes the door.

From Notice to Next

Notice to Next is the four-step check-in I teach leaders.

Notice what has changed, in behaviour you can see rather than a guess about how someone feels. Open with what you noticed, without a diagnosis attached. Listen for longer than is comfortable, before offering anything. Next means agreeing one step together.

Next is not fixing. It might be a change to the work, a follow-up on Thursday, or pointing to support the person can choose to use. A leader's role is not to assess or treat. It is to make sure the conversation does not end at "let me know". What happens after they say no covers the harder version of this, when the answer is a closed door.

The Check-in Conversation, including the Notice to Next approach, is free in the Academy Resource Library.

Where the conversation meets the work

A check-in that ends with an agreed next step only holds if the work allows it. If someone says the workload is unsustainable, and the next step is a conversation about priorities, that conversation needs a leader with the authority to change something. Otherwise the check-in becomes a ritual: honest answers, no movement, and people learn to say "fine".

Poor support and high job demands are both named psychosocial hazards in ISO 45003 and also in Safe Work Australia's model Code of Practice (2022). The check-in is often where they first become visible. What the organisation does next decides whether the conversation was a control or a courtesy.

Worth asking

1. When our leaders check in, what do they actually do in the minute after the answer?

2. Which of the four replies do we hear most often in our teams, and from whom?

3. Have we taught our leaders what to say next, or only to ask?

4. If someone in our team said "not really" tomorrow, would their leader know the next step, and would the work allow them to take it?

The point

The question is the easy part. The reply is the whole check-in.

Most leaders do not need a script. They need to know what to stop doing in the first minute, and what comes next.

And when the honest answer points at the work itself, the next step has to be allowed to change it.

Stay Curious,

Genevieve


Asking is a habit. Knowing what to say next is a capability, and capability has to be built.

Explore The Psychologically Safe Leader →


This article is general information about work design and leadership capability. It is not legal advice, work health and safety advice, or clinical advice.

Genevieve Johnson

Genevieve Johnson is a psychologist and the founder of Oasis Mind Body®. She spent three years as in-house psychologist at ExxonMobil, working inside an operational corporate environment rather than alongside one, following a decade leading teams in business.

She is a PhD candidate at Bond University, where her research examines workplace psychological health, and holds a BA, PGDipPsych, MPsych (Forensic) and an MBA.

Her work translates psychological science into something a leader can actually use day to day, built for the realities of how work gets done rather than how it looks on an org chart.

Next
Next

The announcement was the same. The thought was not.