A working map for global teams · click · move · align
In a global team, the same simple question travels easily in one room and hits a hard wall in another. The harm is rarely the disagreement. The harm is that the question never got its real moment — so nothing could move to the next one.
Moving · Moving · Moving — scroll down
A field note on why discussions stall
It looks like a clash of personalities. Look closer and it is a missing slot in time: nobody gave the question a real moment. Many voices, plenty of noise — and at the end, the question itself was still never discussed.
So it cannot close. It cannot move to the next. And the unfinished question begins to burn quietly inside the people who carried it. By the next meeting, the discussion is no longer about the question — it is about the burning.
If there is a question, focus on this one question — not the others, and especially not on the burning inside people.
The discipline is plain: one question at a time, a time box for it, an ending for it. Do that, and the burning no longer has to become the subject — it can become direction.
Five steps. Open one, then take the next. This is a real sequence, not decoration.
If it takes three sentences, it is three questions. Split them and choose one. The sentence you write is the only thing allowed in the room for the next stretch of time.
"Twelve minutes on this question." A question with no time is a question with no owner. Say the time aloud and everyone in the room becomes its keeper.
When the room drifts to another topic — or to a person — name it and park it: "Parked. We come back after this one." Keep the parking list visible to everyone. What is seen does not have to smoulder.
Decided · decided with a date · needs one named person to bring data by a date · consciously dropped. Silence is not an ending. Amazon calls the last mile of this "disagree and commit" — argue honestly, then leave the station together.
Put the ending where the work actually lives — the ticket, the board, the doc, not in someone's memory. A question that is not written did not happen. Only then do you open the next one.
Every point touches several others. Click one: the lines around it light up, and only then does the next choice appear. Stand still and you never really enter the system.
There are no isolated points in an operation. Click one and a few neighbours light up. You may not know what comes next — but the next only appears once you have chosen.
Start by asking: what is the one question I am actually here to answer?
Too many items, too many links. Scope is not a feeling, it is a set of conditions. Open each card: the condition, the threshold people commonly use, and the cost of ignoring it.
With no qualified alternate there is no recovery path. Map it on day one: a dual-source plan, or a risk that is explicitly accepted by a named person. SCOR files this under resilience, not cost — because what you are buying is optionality.
Classic ABC / Pareto classification. Start there and a fraction of your meeting time covers most of the money. Measure the split first; prioritise second. Feeling is not a segmentation.
That gap gets paid for in exactly two currencies: inventory, or apology. Write the gap down as a number and it stops being about whose fault it is.
Compliance is not prioritised, it is required. Taking it out of the priority debate is what makes the rest of the debate clean.
Do not spend live meeting time here. Wrap them in a rule — min/max, standard terms, auto-replenishment — and revisit quarterly. That is not neglect; it is putting attention where the leverage is.
If a topic needs ten people in the room, it is not one question yet. Split it, and give each part one named owner. More collaboration is not better collaboration — the overload research shows it eats your most valuable people first.
A baseline before an opinion. These are commonly reported ranges — treat them as a shape, not a verdict, then benchmark against your own history.
Read the last row twice: adoption is table stakes, value is not. The gap is rarely the model. It is whether a question got discussed, written down, and owned by a named person. An AI-native organisation is first an organisation with clean decision hygiene.
Align at the point, hold at the point — because everyone departs from this station together.
At every possible meeting point, sometimes you simply pass each other by. If you notice one ball that misses everyone, every time, do not start with "difficult to work with". Start by plotting its path.
No regular orbit, no interaction, only the occasional collision — that is not a personality to solve in a meeting. That is a trajectory to make visible. Once it is visible you can align at the next point. Once you align, you can depart together.
How do you define the inner burning? You do not put it out. You give the question its real moment — and the burning turns into direction.
Every number and threshold above comes from the public research and standards below. Verify each against your own baseline.