Two weeks left. Most of my remaining work is handover, plus a set of conversations about what happens to the systems I built once I leave. That has meant more meetings than usual, which is fitting given this week’s topic. Outside the office, I have been trying to do the last few Stockholm things I keep saying I will get to. The city in late July is quiet and pleasant, and it is a slightly odd feeling to finally have it feel ordinary right as I am about to leave.
Where Sweden sits on the context scale
On the standard low-context to high-context framing, Sweden is usually placed toward the low-context end, near Germany and the Netherlands and not far from the US. My experience is that this is broadly right and also misleading if you take it too literally, because the low-context label describes the content of communication here much better than it describes the delivery.
Where Sweden is genuinely low-context: information is explicit. Meetings have agendas. Written communication says what it means. Instructions, when you get them, are clear and complete, and there is not a lot of hidden protocol about who you are allowed to talk to. Compared to a hierarchical culture, almost nothing about the structure is implicit. I can email essentially anyone in the company directly and that is normal.
Where it is much more high-context than the label suggests: anything involving disagreement, criticism, or refusal. Swedish workplace culture is strongly conflict-avoidant, and the consequence is that negative information gets encoded rather than stated. You almost never hear a direct no. You hear that something is interesting and we should return to it, or that it might be worth checking with someone else first, or you hear a pause. All three of those mean no, and none of them say it.
Silence in particular carries meaning here that it does not carry in American conversation. In the US, a pause is space to be filled, and my instinct was to fill it. Here, a pause is often the whole response, and talking over it means you have just missed the answer.
Miscommunications I have had
I initially over-explained. My emails were long, hedged, and full of context, which is a habit from academic writing and from American professional norms where softening a request is politeness. Here, long emails read as unclear rather than as courteous. The Swedish preference is short and direct, and being brief is not rude. Cutting my messages roughly in half improved their interest noticeably.
Hybrid and asynchronous communication
Our team is not fully in the office every day, and July made that more pronounced because so many people are on vacation at once. Two things stood out.
First, asynchronous communication amplifies the soft-no problem. In person, you can at least read a face. Over a message, a delayed reply is genuinely ambiguous between “I disagree,” “I am busy,” and “I am at a summer house and will deal with this in three weeks.” I learned to save anything requiring an actual decision for a face-to-face conversation and use written messages for status and confirmation only.
Second, the boundary around working hours is real and holds in a hybrid setting. Nobody sends messages at night, and nobody expects a reply outside hours. Coming from a US internship culture where responsiveness is often treated as evidence of commitment, I had to consciously stop sending things at 9pm, because doing so does not read as dedication here. It reads as poor planning, and it puts pressure on people that the culture considers inappropriate.
Professionally, the takeaway is that I now assume I am misreading a culture’s communication norms until proven otherwise, and I test that assumption with concrete, dated questions rather than open ones. That habit travels anywhere.
Vi ses!
