This really clicked for me—especially the idea that "the code is the same everywhere, but the meaning is not."
On the Korean company example though, I found myself stopping earlier. “Desire individualism” is a phrase I wouldn’t act on without pushing back. Even at the level of what’s actually being emphasized. What does that actually look like in user behavior in Korea? When does it show up, and when doesn’t it?
It made me wonder if part of the gap isn’t just cultural framing, but how quickly teams accept ambiguous language in briefs—especially under time pressure. If it can’t be translated into concrete behavior in that market, it feels like we’re already designing on assumptions.
Curious how you’d pressure-test language like that in a fast cycle.
Thanks for spotlighting this, Susan. This is exactly the operational layer the essay points toward but doesn't fully develop. And I think you're right that the gap isn't only cultural framing. It's also velocity.
"Desire individualism" survived because the brief was moving fast — it was an 8-week sprint and I was brought in two weeks after kickoff — and the language felt universal enough that we didn’t stopto translate it into observable behavior in that market. The brief itself was highly detailed and specific in its directives, which made it easier to trust the framing without questioning the cultural assumptions embedded in it.
How I'd pressure-test it now: before the brief leaves the room, every key phrase gets a behavioral translation for each market. Not "what does this mean?" but "what does this look like when someone actually does it?" If the answer is different in Seoul and SF, the brief is carrying an assumption that needs to be named before it ships.
The fast cycle problem is real though. Most teams don't have time for that interrogation, which is why the assumptions survive. As I became more experienced and senior, interrogating the brief immediately became second nature and we've been more successful.
That might be the deeper structural issue: the cosmotechnics gap doesn't just exist between cultures. It exists between the speed of production and the speed of understanding.
The gap also tracks with what we know from decision-making research: under time pressure, people default to heuristics and “good enough” interpretations rather than interrogating assumptions. As you say, the brief doesn’t just move fast—it actively protects its own framing.
Which makes your point even sharper: without an explicit step to translate language into observable behavior per market, the system is set up to reproduce its own blind spots.
This really clicked for me—especially the idea that "the code is the same everywhere, but the meaning is not."
On the Korean company example though, I found myself stopping earlier. “Desire individualism” is a phrase I wouldn’t act on without pushing back. Even at the level of what’s actually being emphasized. What does that actually look like in user behavior in Korea? When does it show up, and when doesn’t it?
It made me wonder if part of the gap isn’t just cultural framing, but how quickly teams accept ambiguous language in briefs—especially under time pressure. If it can’t be translated into concrete behavior in that market, it feels like we’re already designing on assumptions.
Curious how you’d pressure-test language like that in a fast cycle.
Thanks for spotlighting this, Susan. This is exactly the operational layer the essay points toward but doesn't fully develop. And I think you're right that the gap isn't only cultural framing. It's also velocity.
"Desire individualism" survived because the brief was moving fast — it was an 8-week sprint and I was brought in two weeks after kickoff — and the language felt universal enough that we didn’t stopto translate it into observable behavior in that market. The brief itself was highly detailed and specific in its directives, which made it easier to trust the framing without questioning the cultural assumptions embedded in it.
How I'd pressure-test it now: before the brief leaves the room, every key phrase gets a behavioral translation for each market. Not "what does this mean?" but "what does this look like when someone actually does it?" If the answer is different in Seoul and SF, the brief is carrying an assumption that needs to be named before it ships.
The fast cycle problem is real though. Most teams don't have time for that interrogation, which is why the assumptions survive. As I became more experienced and senior, interrogating the brief immediately became second nature and we've been more successful.
That might be the deeper structural issue: the cosmotechnics gap doesn't just exist between cultures. It exists between the speed of production and the speed of understanding.
The gap also tracks with what we know from decision-making research: under time pressure, people default to heuristics and “good enough” interpretations rather than interrogating assumptions. As you say, the brief doesn’t just move fast—it actively protects its own framing.
Which makes your point even sharper: without an explicit step to translate language into observable behavior per market, the system is set up to reproduce its own blind spots.
Thanks, a stimulating and insightful read!