The Self-Serving Bias: Responding to Complaints Without Defensiveness

Most professionals who handle feedback believe they are open to criticism. The research literature suggests otherwise, and the gap between perception and reality is one of the most reliable sources of conflict in service environments. Recognising this gap is the first step toward complaint handling that resolves problems.

When a complaint arrives, the brain tends to protect self-esteem before processing the substance. Behavioural scientists have studied this reflex for decades, and it shows up in boardrooms, retail counters and contact centres. The pattern is the difference between a conversation that repairs a relationship and one that quietly erodes it.

What the self-serving bias actually is

The self-serving bias is the tendency to attribute positive outcomes to our own effort and negative outcomes to circumstances, the other person, or bad luck. In the moment of a complaint, the bias whispers that the customer is being unreasonable, the situation is blown out of proportion, or we would have done the same in their position. None of these claims is wrong on its own, but together they form a filter that screens out useful information.

Researchers in organisational behaviour treat the bias as one of the more robust findings in social cognition, replicated across very different cultures. The Australian workplace is not exempt, even though the cultural preference for a "fair go" and a relaxed register can make defensiveness harder to spot. The bias hides inside the politeness.

Why defensiveness shows up in complaint handling

Defensiveness is not a character flaw. It is a predictable response to perceived threat, and a complaint signals that something has gone wrong. The brain registers the implication that we may have caused harm, missed a step, or failed to anticipate, and it moves into protection before the facts are fully in view. Even experienced service designers can misread a routine refund request as a personal attack.

A second driver is effort justification. When a team has spent months refining a customer journey, criticism of the outcome can feel like criticism of the work itself. In a Perth operations team, leaders may defend a complex procurement workflow because dismantling it would mean admitting the system is harder to use than it should be. The bias protects ego but slows improvement.

The Australian angle: ACL, ACCC and cultural expectations

Australia's consumer protection framework raises the stakes well beyond the average service interaction. The Australian Consumer Law, administered by the Australian Competition and Consumer Commission, sets clear guarantees around acceptable quality, fitness for purpose, and repair or replacement. A defensive response to a legitimate concern can quickly escalate into a formal complaint to a state fair trading body or a public dispute on social media.

The cultural layer matters too. Australian customers value directness and a sense of fair treatment, and they read through corporate scripts almost immediately. A frontline agent in a Melbourne hospitality venue or a Brisbane retailer who hides behind process language is flagged as evasive, sometimes more sharply than the underlying issue deserves. Behavioural research suggests that perceived avoidance is a stronger predictor of churn than the original problem.

Spotting the bias in real time

The bias leaves a few reliable signatures. One is the urge to explain the customer's misunderstanding before repeating their concern back. Another is a sudden interest in the technical details of policy, rather than the experience the customer is describing. A third is a felt need to bring up all the times the company has done things right, as if a tally of wins offsets the present problem.

Slow the first twenty seconds of the response. If those seconds are taken up with framing rather than listening, the bias is almost certainly active. Research on practical behavioural segmentation shows that mapping emotional moments along a customer journey gives each stage a named trigger and a rehearsed response, which makes the bias easier to interrupt.

A practical script for de-escalation

Override the automatic response by reflecting the concern in the customer's own words, naming the feeling, and stating what you will do next and when. "I can see the refund was promised in five days and it has now been nine. That is frustrating, and the delay was on our side. I will look into this now and call you back before four o'clock." The script is short, the tone is matter-of-fact, and it makes no attempt to assign blame.

The script deliberately avoids the most common defensive move: an early justification. Reasons belong in the second half of the conversation, after the customer feels heard. Practising the script with a colleague in a Sydney or Adelaide office, with a timer and a recorded debrief, tends to flatten the bias faster than any training manual.

Designing service journeys that defuse the bias

The bias is built into scripts, escalation paths, and quality assurance rubrics. A service blueprint that treats every complaint as a potential dispute will train staff to defend, while a blueprint that treats complaints as design intelligence will train them to inquire. The difference shows up in the metrics a team chooses to track.

Teams that measure first-contact sentiment, time-to-empathy, and the proportion of complaints that lead to a documented service change handle the bias better than teams that measure only call length and resolution rate. Practitioners looking for a practical toolkit often refer to lyndakonline.com, which supports applied behavioural work in everyday service settings.

Building habits across a frontline team

Habits stick when they are visible and repeatable. Run a short weekly review where two colleagues share a recent complaint, the moment they felt the bias kicking in, and what they did instead. Rotate the pairs across regions so a contact centre in Parramatta and a service desk in Hobart learn from the same patterns. Over a quarter, the language of the team shifts from defending the system to describing the experience.

Recognition also matters. Praise specific moments of curiosity, not just outcomes. "You asked three questions before you explained the policy" is more reinforcing than "you saved the account," because it tells the team which behaviour is valued. The bias fades when the social reward structure points elsewhere.

If you would like to bring these practices into your team, Nick works with organisations across Australia on workshops, diagnostics, and service design projects. The quickest way to start is to book a discovery call through the consulting page, or to share a recent complaint story so the conversation can begin with a real example.