Where teams misread each other
At work the stakes of a misread are concrete: a missed deadline that everyone thought was agreed, feedback nobody noticed, a colleague who quietly checked out. Most of it comes down to a handful of recurring situations.
Feedback
The same criticism can be a routine note or a career-ending signal, depending on the code. Upgraders (US, often UK) strengthen positive words and soften negatives; downgraders (Netherlands, Germany, Israel, France) do the opposite.
- Before giving feedback to someone from a different code, ask how they like to receive it.
- When receiving it, ask for the one thing to change: "If you could change one thing, what would it be?"
- In indirect cultures, give negative feedback 1:1, never in front of others.
Meetings and decisions
Is a meeting the place to decide, or to rubber-stamp what was agreed beforehand in hallways? Is silence agreement? Is the boss's opinion the end of the debate or the start?
- End every meeting with: who does what by when — said out loud and written down.
- Collect opinions before the most senior person speaks.
- For quieter colleagues, ask for input in writing afterwards.
"Yes" and deadlines
"Yes" can mean agreement, commitment, or just "I heard you". "By Friday" can be a promise or an aspiration. When the codes differ, both sides feel let down on Friday.
- Replace "Can you do this?" with "What would you need to get this done by Friday?"
- Ask for a check-in halfway, not only at the deadline.
Email and chat
Written messages strip tone, so everyone reads them through their own code. Short replies look curt to relationship-oriented readers; long, warm openings look like filler to task-oriented ones.
- If a message feels rude, reread it assuming a direct code. It usually reads fine.
- If it matters emotionally, call instead of writing.