On my first project as a team lead, I got two verdicts on exactly the same behaviour.
For a long time I thought one of those verdicts was right and the other wrong. Only much later, sitting in a chair in Seoul wearing a white cape, did I understand that this was the wrong question.
Two verdicts on the same behaviour
My project lead found me “too rigid”. I protected my scope and my team, and extra work didn't get past me for free.
My manager thought that was exactly right. A project's scope is there to be protected.
Same behaviour. Two people. Two opposite verdicts.
One wanted to stay in the client's good books. The other wanted extra work to be paid for.
Neither of them was unreasonable. They were simply looking from a different interest. For the project lead, my behaviour was a brake on the client relationship. For my manager, it protected the margin and the team. What one saw as a problem, the other saw as a strength.
At the time it mostly felt confusing. Should I become more flexible? Or hold the line? Each verdict pulled me in a different direction, and each verdict was about me.
A white cape in Seoul
Last month in Seoul, I sat in a white cape at a colour analysis that had been on my bucket list for a while.
The consultant laid one piece of fabric after another under my face and let the fabric do the work. With one colour I went pale and looked tired. With the next, my eyes suddenly looked bright.
What struck me: even my mood and my energy moved with it.
My result was Autumn Mute. Warm, muted, low contrast. My worst type is Winter Bright, vivid and sharp, which looks stunning on someone else.
My face didn't change. Only what was underneath it.
The face doesn't change, the fabric does
That's what happened on that first project. I wasn't too rigid, and I wasn't really right either. Two people held a different fabric under the same face.
It helps to pull this apart into three layers.
The behaviour
What someone actually does. I said no to extra work without an agreement. That is observable, and both people judging me would probably agree on it.
The fabric
The interest, the role, the norm or the culture the behaviour is held against. The client relationship. The project's margin. What counts as normal, polite or professional in a country or an organisation. You almost never see this layer, because the person judging rarely names it, even to themselves.
The verdict
What finally gets said. “Too rigid.” “Exactly right.” “A bit harsh.” This is the only layer you hear, which is why it's the layer you tend to respond to.
At Seemotion I call the gap between behaviour and verdict the Interpretation Gap. What sits inside it is the fabric. As long as it stays invisible, every verdict seems to be about you.
Meant as neutral, received as harsh
Later, as a project manager, I gave feedback to my Indian counterpart. Neutral, in my eyes. Balanced, the way a Dutch person means it.
The response was: “a bit harsh”.
Same words. Different fabric underneath.
Here the fabric isn't an interest but a cultural norm. In the Netherlands, feedback that comes directly and without much softening often counts as honest and respectful. You take the other person seriously by just saying it. In many other work cultures the bar sits elsewhere. There, softening, context and timing are how you show the relationship matters. What was balanced to me came out as harsh against that standard.
Erin Meyer describes this in The Culture Map as the evaluating scale: how directly or indirectly negative feedback is given. The Netherlands sits at the direct end. That doesn't make Dutch people blunter by character. It means the fabric a Dutch person uses to judge themselves differs from the fabric many colleagues elsewhere use to judge them.
Why the conversation turns to the person
I see it again and again in international teams. At home, people call the same manager clear. In another team, blunt. And then the conversation is about the manager. It should be about the fabric.
That is no accident. People have a strong tendency to attribute someone else's behaviour to character and to underestimate the circumstances. In social psychology this is called the fundamental attribution error. With someone from another culture the tendency grows, because you don't experience your own standard as a standard. It just feels like the way things are.
The result in teams is predictable. A difference in style becomes a personality trait. “She's direct” becomes “she's blunt”. “He protects his scope” becomes “he's rigid”. Once the label hangs on the person, the solution moves to the person too. Someone has to become softer, more flexible, less Dutch. While nobody has looked at which standard was being used.
It works in both directions. The person receiving the verdict plays along too. When I heard “too rigid”, I wondered whether I needed to change. I didn't wonder which interest my project lead was looking from. I responded to the verdict, not to the fabric.
Learning to see the fabric
You don't always get to choose the fabric you're judged under. But you can learn to see it.
Next time someone calls you too rigid, or a bit harsh, ask yourself one question before you change anything: what fabric is this person holding under your face?
Three questions help make that fabric concrete.
- What is this person trying to achieve? A good client relationship, a healthy margin, calm in the team. The verdict often says more about that goal than about you.
- What is normal for this person? What level of directness, what way of saying no, what pace. A verdict is always a comparison with something.
- Who else is judging me, and with which fabric? If two people judge you in opposite ways, you haven't found a mistake. You've found two standards.
That doesn't mean you never adjust. Sometimes adjusting is exactly right. If you know your Indian colleague reads softening as respect, you can choose to package your feedback differently without changing the content. The difference is that you're choosing consciously, instead of letting the last verdict you heard decide your behaviour.
And as a leader you can shift the conversation in your team. Not: who is right about this colleague? But: which standards are we using here, and which have we forgotten to say out loud?
What do you do that one team calls clear and another calls blunt?