Work skill · Working with people

Understanding why people react

Notices how other people respond, works out the reason, and changes their own approach to fit.

Updated 21 November 2026 · 4 min read · by the hire.center team

On this page (7)
  1. What it is
  2. What it looks like at work
  3. Why it matters in different kinds of jobs
  4. Why interviews often miss it
  5. How a work situation can show it
  6. What to ask in an interview
  7. What hire.center shows, and its limits
Working with people

What it is

Notices how other people respond, works out the reason, and changes their own approach to fit. It is not the same as being friendly or a good listener in general. The skill has three parts you can see: noticing a reaction, finding a likely reason for it, and doing something different because of it.

What it looks like at work

In everyday work, it often looks like this
  1. Notice how people respond
  2. Work out the reason
  3. Change approach to fit
The skill in general terms, from its definition. Real work mixes the steps.
  • Healthcare

    A nurse sees that a patient nods at every instruction but never asks a question, suspects the plan has not been understood, and asks the patient to explain it back in their own words.

  • Software

    A software developer notices that a product manager goes quiet when an estimate is shared, guesses it breaks a promise already made to a client, and offers two smaller options.

  • Finance

    An accountant sees a department head push back on a cost report, realises that team expects to be blamed for the overrun, and starts with the cause instead of the total.

  • Electrical work

    An electrician notices a homeowner keeps returning to the price, works out that the budget is fixed, and explains which parts of the job can wait.

  • Retail

    A shop assistant sees a customer hesitate at the till, guesses the price is not what the shelf said, and checks it before being asked.

Why it matters in different kinds of jobs

Almost all work passes through other people: colleagues, customers, patients, pupils, suppliers. When someone misreads why a person is reacting, effort goes into the wrong fix, and small friction grows into conflict or a lost client. In jobs with the public, this skill shapes trust and the number of complaints. In technical and back-office jobs it shows up in meetings, code reviews and handovers, where a misread objection can stall a project for weeks. In leadership roles it is part of noticing early that someone in the team does not agree with a plan they have just accepted. Research on interpersonal skills at work treats this kind of reading of others as part of a wider set of skills for communicating and building working relationships (Klein, DeRouin & Salas, 2006).

Why interviews often miss it

Interviews tend to judge this skill from how the candidate comes across in the room. Research on what interviews measure finds that applied social skills are among the things interviewers rate most often (Huffcutt, Conway, Roth & Stone, 2001). But an interview is a polite conversation that mostly follows a script. A pleasant, articulate candidate can seem perceptive without ever showing that they noticed a reaction and changed course because of it.

How a work situation can show it

A realistic work situation can include a person whose reaction does not match their words: a colleague who agrees to a plan but clearly will not support it, or a customer whose question hides a different concern. You then see whether the candidate picks up on it, asks or checks the reason, and adjusts what they do next. It happens in the moment, not in a story told later. Research on behaviour at work describes a general idea: a tendency shows most clearly when the situation calls for it (Tett & Burnett, 2003).

What to ask in an interview

  1. "Tell me about a time someone reacted to you in a way you did not expect. What did you think was going on?"

    Follow-up: "How did you check whether you were right?"

  2. "Describe a time you changed how you were explaining something halfway through. What made you change?"

    Follow-up: "What did you do differently, and what happened?"

  3. "Tell me about a colleague or client you found hard to work with at first. What did you learn about why they acted that way?"

    Follow-up: "What did you change in how you worked with them?"

Listen for a specific reaction, a reason the candidate tested rather than assumed, and a change in what they did.

To see it with a situation from your own job, read how it works and pricing.

What hire.center shows, and its limits

In hire.center, a candidate handles one realistic work situation built from the job. The scorecard shows the candidate's own words for each skill the recruiter chose, or says there was not enough evidence. One situation shows one situation, not the whole job, and it does not test technical knowledge. A person makes the hiring decision. Our quality checks so far use AI-played candidates in six example jobs, most of them with customers or colleagues at the centre of the work. We are extending them to more kinds of jobs.

See the work skills a CV can't show

Take the candidate's seat in a 15-minute work situation, then read your own scorecard. Free, no card.