The four-ears model (Vier-Ohren-Modell) is an interpersonal communication framework developed by German psychologist Friedemann Schulz von Thun, which assumes that every message can be received on four distinct levels: factual, relationship, appeal, and self-revelation. When the sender and receiver focus on different layers of the same message, misunderstanding occurs and that is the root cause of a vast number of problems in IT teams.
Why communication in IT is a matter of project life and death
I’ve been working in IT for over a decade as a QA lead, but also as a regular team member across various projects. I’ve seen first-hand how important communication is and how dangerous ambiguity can be. This isn’t just my gut feeling: research from two independent industry reports shows that poor communication was a direct cause of project failure in 56% of cases, with the PMI Pulse of the Profession (2013) report indicating that 56% of at-risk project budget – $75 million out of every $135 million at risk per $1 billion spent is attributable to ineffective communication. (source)
This isn’t a „soft” problem. It’s a project management problem.
When a leadership training I attended briefly touched on the four-ears model, I decided to dig deeper. What I found immediately connected to dozens of situations from my own career.
What is the four-ears model?
The four-ears model was developed by Friedemann Schulz von Thun a German psychologist and expert in interpersonal communication. He published it in 1981, building on two earlier frameworks: Watzlawick’s communication model and Bühler’s Organon model. Von Thun later founded the Schulz von Thun Institute for Communication in Hamburg and went on to develop further concepts, including the „inner team” model.
The core premise is this: every message between a sender and a receiver contains four layers simultaneously, and problems arise when the sender intends to reach one layer, but the receiver picks up on a different one.
His classic example: a passenger says to the driver, „The traffic light is green.” Depending on which ear the driver listens with, they might hear a fact, a command to drive, an offer of help, or an expression of impatience. Same words four possible receptions.
The four layers of every message
| Layer | Also known as | What it conveys |
|---|---|---|
| Factual | Matter ear | Raw data and facts, no emotional charge |
| Relationship | Relationship ear | What the sender thinks about the receiver |
| Appeal | Appeal ear | What the sender wants the receiver to do |
| Self-revelation | Self-disclosure ear | What the sender reveals about themselves |
Every spoken sentence can be examined through all four lenses at once. The question is: which one does the receiver pick up on and is it the same one the sender intended to emphasize?
Three real-life examples from an IT team
Here are specific sentences that come up in everyday work and how each one can be received in four completely different ways.
Example 1: Code Review
Statement: „This piece of code doesn’t meet our Clean Code standards.”
- Factual layer: The code needs fixing; it doesn’t comply with the guidelines.
- Appeal layer: Rewrite this code to make it more readable.
- Relationship layer: You wrote bad code – you’re a bad developer.
- Self-revelation layer: I’m worried we have messy code sitting in our repository.
The relationship layer is particularly dangerous here, especially in communication between QA and developers. When reporting a bug, it’s critical not to „resonate” with that layer. The goal is to stick to facts and a clear appeal. This is a constant challenge in that working relationship.
Example 2: An Overdue Ticket
Statement: „This ticket in Jira is still open, even though it was supposed to be closed yesterday.”
- Factual layer: The ticket wasn’t closed on time.
- Appeal layer: Close this ticket now / please update its status.
- Relationship layer: I’m unreliable, I’m not on top of my responsibilities.
- Self-revelation layer: Our planning is off / I’m feeling the pressure of time.
The same sentence spoken in a manager’s conversation with HR about a specific employee immediately shifts toward the relationship layer, despite identical wording. Context changes everything.
Example 3: No Progress on a User Story
Statement: „I haven’t seen any progress on this user story since the last daily.”
- Factual layer: No changes since yesterday. A neutral fact, neither good nor bad.
- Appeal layer: Get moving on this story, you’re blocking the sprint.
- Relationship layer: I’m slacking off, I can’t keep up.
- Self-revelation layer: I’m worried we won’t meet the deadline.
Imagine two versions of the same situation. A Scrum Master glances at the board and mutters to himself: „I haven’t seen any progress on this user story since the last daily…” that sounds like a plain observation. But when they say directly: „Piotr, I haven’t seen any progress on this user story since the last daily” it becomes an almost explicit appeal to act. Same sentence, different layer.
And if today is the last day of the sprint? Even said gently, it will be received as an appeal, because context creates pressure.
What determines which ear we listen with?
This is the key question and the answer isn’t simple. Based on the research behind this model and my own experience, I identify six main factors:
1. Situational context At the start of a sprint, the same sentence lands very differently than at the end. A tense final day and a relaxed retrospective are two completely different contexts for identical words.
2. Personality and dominant ear Each of us has a dominant ear. If we’re sensitive to criticism, our relationship ear is „larger, we’ll interpret feedback as a personal attack even when the speaker just wanted to state a fact. It’s worth knowing this about yourself.
3. The listener’s emotional state Someone who’s sleep-deprived, under-caffeinated, or frustrated will interpret the same message very differently than a rested person. The relationship and appeal ears grow disproportionately large.
4. The relationship between sender and receiver We write differently to a colleague we trust than to someone we barely know. Trust creates a safe space for a message a lack of trust means any sentence can land „in the wrong place.” Hierarchy is a particularly sensitive factor: a receiver who feels insecure in their relationship with a sender will search for hidden criticism where none exists.
5. Organizational culture In relaxed teams, a jokey comment about an overdue task passes without friction. In formal ones, it can cause real tension. Some organizations are results-driven, others are relationship-driven and communication looks completely different in each.
6. Clarity and tone of the sender’s message The clearer the message and the more the tone matches the intent, the higher the chance it reaches the right ear. An emotional tone signals self-revelation. A commanding tone signals appeal. Neutral and specific signals facts.
Remote work and written communication
When we moved to remote work and messaging apps, this dynamic shifted significantly. Gestures, intonation, and facial expressions everything that helps decode intent in face-to-face conversation disappeared. Emojis and winking faces emerged precisely to „soften” written text and signal which ear a message is aimed at.
Written communication does give the sender more time to choose words carefully. That’s a space worth using deliberately which brings me to the practical techniques below.
How to reach the right ear: practical techniques
As the sender
- State your intent clearly. If you want someone to close a ticket by tomorrow say it directly: „Please close this ticket by tomorrow.” Don’t say „The ticket is still open” and hope the receiver figures it out. They might not — or they might figure out something completely different.
- Match your tone and language to the layer you want to activate. If you’re stressed about a deadline and want to communicate that say so: „I’m stressed, the deadline is bearing down on us, let’s speed this up.” That’s both an appeal and self-revelation and it’s honest. Better than a dry: „The feature isn’t ready.”
- Provide context upfront. „We’re reviewing this code specifically against Clean Code standards” gives the receiver a clear frame. „This code doesn’t look good” opens the door to every possible interpretation.
- In written communication, avoid ambiguity. You have time to formulate the sentence well. Instead of: „Why is this ticket still open?” write: „Please update the ticket status, we need it for the report.” The intent is clear.
As the receiver
- Analyze contextual cues. Neutral tone and specifics → factual layer. Emotional tone → self-revelation. Commanding → appeal. If a manager says with visible irritation that a feature must be ready by Friday — you’re hearing both an appeal and self-revelation. There’s no relationship layer there, even though it’s easy to project one.
- Ask when you’re unsure. It takes courage, but it’s the most effective method. Instead of guessing, say: „Are you asking me to speed up work on this feature, or is it something else?” One question can prevent weeks of misunderstanding.
- Know your dominant ear. If you know you’re sensitive to criticism, you have a tool: you can pause and ask yourself whether you’re receiving this message through the relationship layer because that’s your pattern or because it’s genuinely there.
- Account for cultural context. In so-called low-context cultures (Poland, most Western countries), intent is communicated directly. In high-context cultures (many Asian countries), meaning is embedded in the surrounding context, the relationship, the shared history. In multinational teams, this makes an enormous difference what sounds like evasiveness to a Polish speaker may simply be a different, equally valid way of communicating.
Final thoughts
The four-ears model isn’t an academic theory it’s a practical tool for understanding why the same words produce completely different reactions depending on the person, the context, and the relationship.
After more than a decade in IT, I can see it clearly: the better the communication in a team, the less time gets spent fighting fires that should never have started.
I’d suggest two things. First think about which is your dominant ear. Second next time you write a code review comment or report a bug, check whether your intent is actually clear to the receiver. Not just to you.
If you’re interested in communication and team dynamics in IT, check out more articles on fireup.pro, including what distinguishes projects from processes and lessons from the AWS Certified Developer Associate exam.
