Article
Hidden Dynamics of Global Teams

The screen on the floor: do what I asked vs do what I meant

Raymond Honings 1 June 2026
A presentation screen on the floor in the corner of a château room, invisible past the front rows.
Summary

Global teams often give you exactly what you asked for, and it still does not land the way you meant it. The cause is not resistance but the gap between do what I asked and do what I meant. In low-context cultures intent lives in the words, in high-context cultures it lives in the room and the relationship. The fix is simple: stop asking for the thing, ask for the outcome.

Key Insights
  • A team can execute exactly what you asked and still miss the outcome, because you assumed your intent traveled with the words instead of saying it out loud.
  • In low-context cultures intent lives in the words, in high-context cultures it lives in the room and the relationship. Where the two meet, the words get followed and the meaning gets lost.
  • The practical shift is to stop asking for the thing and start asking for the outcome, plus the open question of how to reach it here.
A large screen sitting on the floor in the corner of a room, far out of the audience's line of sight.
Exactly what I asked for. Not what I meant.

The team did everything I asked. That was the problem.

There was a screen on the floor, in the corner, where nobody past the second row could see it. And it was exactly what I had asked for.

The screen on the floor

We were running an event in a château in France. I needed a large screen in the room for a talk. The site crew was French, hired in, and we had always worked well with them. So I asked for a screen.

They brought one. Exactly as I asked.

There it was. Large, neat, on time. And completely useless, because it sat on the ground in the corner, and the moment the room filled up it was invisible from the third row back. Nobody had done anything wrong. A screen had been asked for, a screen had been delivered. The instruction had been carried out to the letter.

I had asked for a screen. What I actually wanted was a screen people could watch. Those are not the same request. I just never said the second part out loud, because where I come from, it goes without saying. A screen exists to be looked at, so why would you spell that out. Except I should have spelled it out, because that second part is exactly where it went wrong.

That gap is the thing I keep coming back to.

Why the team did nothing wrong

Because the team did nothing wrong. They built exactly what I named. The miss was mine. I gave them the words, and assumed they came with my intent attached.

Here is the core. Do what I asked and do what I meant are not the same thing, and almost never spoken as two separate things. The first is the literal request: the screen, the slide, the report, the thing I name. The second is what I want it to achieve: the room that can see, the decision that gets made, the problem that goes away. In my head those two are one. They arrive together, they feel like the same thing. But I only say one of them out loud. So the other person hears half, and fills in the rest with their own assumption about what I mean.

Why do I only say the first? Because the second is so obvious to me that it becomes invisible. My intent does not feel like information I have to transfer, it feels like context that is simply already there. And that is the trap: the very things that go without saying for you are the things you do not say, and therefore the things the other person never gets.

This is the part that should matter if you lead an international team. You ask for input. You get input. You ask for a plan. You get a plan. Everyone says yes. The room nods. And two weeks later you are standing in front of a screen on the floor, wondering why something so clearly agreed on did not land the way you pictured it.

It is not resistance. It is not low effort. It is not a lack of ownership either. It is that do what I asked and do what I meant are two different instructions, and only one of them gets spoken.

I gave them the words, and assumed they came with my intent attached.

High context, low context

Anthropologist Edward Hall described the distinction between high-context and low-context communication decades ago. Erin Meyer built it out in The Culture Map into a practical tool for anyone working across cultures. The core is simple, and painfully recognizable once you see it.

In a lower-context culture, you put the intent in the words. What is said is what counts. Explicit, literal, self-contained. You would rather over-explain than under-explain, and good communication means an outsider could understand the message without knowing the history behind it. The words carry the load, all of it, on their own.

In a higher-context culture, the intent deliberately does not live fully in the words. It lives in the room, in the relationship, in what everyone already knows. The words point at a meaning you are expected to fill in yourself. Over-explaining there feels almost insulting, as if you do not trust the other person to grasp the rest on their own. The message sits between the lines, in the tone, in what is deliberately left unsaid.

Neither is better. Both work fine, as long as everyone at the table uses the same packaging. They only collide at the line between them. And the collision is treacherous, because it makes no noise. When someone who puts intent in the words asks something of someone who looks for intent in the room, this happens: the words get followed faithfully, and the meaning the speaker assumed came with them stays behind. Both of them are doing exactly what their culture considers good behavior. And it looks like alignment the whole way down.

It is not in a country, it is in the assumption

The tempting move is to read this as a list of countries. That is not how it works. I have seen the same thing in Seoul, in Munich, in Mumbai. Different language, different room, different crew, but always the same movement: I specified the thing, assumed the intent traveled with it, and found out it had stayed behind the moment I left. The shape changes, the mechanism does not.

The real problem, then, is not the other person, and not a particular nationality. It is the assumption that your way of packing meaning is universal. Where I come from, it goes without saying. That without saying feels like a property of the world, when it is a property of my own context. And it is precisely that without saying that does not cross the culture line.

The illusion of alignment

The most dangerous part of this mechanism is that it looks like agreement at every moment. Nobody says no. Nobody frowns. The words check out, the nods check out, the plan checks out on paper. You get no signal that something is off, until the thing is built and you see it with your own eyes.

That is what makes it so hard to catch. You see a conflict coming, because it announces itself. A misunderstanding about what a word means looks identical to understanding from the outside. The same nod, the same yes, the same calm. You cannot hear the difference between the two, because they sound exactly alike. The difference only becomes audible in the outcome, and by then it is too late to steer.

And the reflex afterward is almost always wrong. You start specifying harder. More detail, more words, more instruction. It feels logical: if the message did not land, I must not have made it clear enough. But you are adding more to exactly the channel that failed to carry the intent. You did not have too few words, you had the wrong layer. More instruction about the thing sharpens the instruction and does not improve the outcome, because the outcome was never a problem of word count.

Ask for the outcome, not the thing

So here is what I started doing, after the screen.

I stopped asking for the thing. I started asking for the outcome. Not "bring a screen," but "I need everyone in this room to be able to see the slides from their seat. How do we do that here?"

That last sentence does the work. How do we do that here. It hands over the intent explicitly, it pulls out the second instruction I used to swallow and puts it on the table. And it gives the other person room to bring their own context, the context I cannot see from my seat. I name the result. They know better than I do what is possible in that room, which wall, which height, which stand is available. I supply the intent, they supply the execution.

It feels slower. You name an outcome, you ask an open question, you wait for an answer instead of a yes. But it is not slower. It is just more visible up front. The work you do here is exactly the work you would otherwise have to do two weeks later, when the thing is in the wrong place and you start over. A leader notices the difference not in the speed of the conversation, but in what happens after it: fewer surprises, fewer redo's, fewer moments standing in front of a screen on the floor.

It is the difference between a screen, and a screen people can watch.

The trick is not more words. The trick is the right kind of words. Put the outcome in the question instead of the execution, and leave the execution to the people who know the room you do not.

A Take-Home Message
  • When an international team delivers exactly what you asked and it still misses, the miss is usually yours: you packed your intent into words that did not carry it.
  • Do what I asked and do what I meant are two instructions. Say the second one out loud.
  • Ask for the outcome, not the thing, and add: how do we do that here? That gives both your intent and their context a place to land.
References
  1. Meyer, E. (2014). The Culture Map: Breaking Through the Invisible Boundaries of Global Business. PublicAffairs. link
  2. Lewis, R. D. (2006). When Cultures Collide: Leading Across Cultures. Nicholas Brealey Publishing. link

Frequently Asked Questions

What is the difference between high-context and low-context communication? +
In low-context communication, intent lives explicitly in the words: what is said is what counts. In high-context communication, intent lives in the room, the relationship and shared knowledge, and the words are a pointer you are expected to fill in yourself. Both work fine inside their own context and collide at the line between them.
How do I know if a misunderstanding is cultural or just an unclear instruction? +
That distinction matters less than it seems. In both cases the fix is the same: you did not make the outcome explicit and assumed it traveled with the task. Whether the distance is cultural or personal, asking for the result instead of the thing closes both gaps.
Why does specifying harder not help? +
Because you are adding more to exactly the channel that already failed to carry your intent: the literal instruction. You sharpen the task, not the outcome. The other person still follows the words without the intent you assumed was inside them. What helps is a different kind of question, not more words.
How do you ask for the outcome without micromanaging? +
By doing the opposite of micromanaging. You name the result you need and leave the execution to the other person, with an open question like how do we do that here. You supply the intent, they supply the context and the solution you cannot see from your own position.
Does this only apply to international teams? +
It shows up most sharply across cultural lines, because that is where the assumptions sit furthest apart. But the same mechanism plays out between departments, disciplines, and even two people from different backgrounds. Anywhere you assume something goes without saying, the intent can disappear in transit.
Raymond Honings
About the author

Raymond Honings

Raymond is the founder of Seemotion. He works with managers and leadership teams across cultures, helping them build self-reliant teams that perform under pressure. Over the past years he has worked with more than 1,000 managers worldwide. Today most of his work takes place in Asia, mainly in Korea, Taiwan, China and Japan.