The Business Culture Spectrum
National culture is deep, unconscious, and largely unchanging, and the diversity it brings is what makes global teams strong. Business culture sits on top: the observable practices that shape how a team actually works together day to day. That's the layer we measure, and the layer where teams can adapt.
The philosophy
Most cross-cultural work in business either tries to change what can't be changed, or ignores the layer where the friction actually happens. We do the opposite. We leave the deep layer alone, because it's not broken, and because its diversity is a source of strength. And we make the surface layer explicit, so teams can talk about it and adapt where it helps them work better together.
The observable ways a team gets work done. How meetings run. How feedback lands. How decisions get made. How ownership works. How planning happens. These are learned, adjustable, and vary from team to team even within a country.
Adaptable · Observable · Where friction shows up
Business practices are shaped by national culture, but they're not the same thing. Two teams from the same country can operate very differently.
The unconscious values people absorb from the society they grew up in. Power distance, individualism vs. collectivism, time orientation, tolerance for uncertainty. These form early, run deep, and are largely unchanging in adulthood.
Deep · Unconscious · Diverse, and that's a strength, not a problem to solve
Every dimension is a spectrum between two legitimate ways of doing business. There is no "right" side. There is only whether your team's ways of working are shared, understood, and fit for what you're trying to do.
We don't try to flatten out the deep cultural differences people bring. We work at the surface, where the team can decide together how it wants to run meetings, give feedback, and make decisions.
Most cross-cultural friction is invisible until named. When a team sees where its members sit on each dimension, and how those positions collide, the "he's being difficult" story becomes "we have a different default here: let's decide what to do about it."
The five dimensions
Each dimension is measured on a 0–10 spectrum from one business culture to another. Both ends are legitimate. Most teams sit somewhere between the poles, with a lean one way or the other. Where the team sits, and how tightly it clusters, is the actual profile.
How the team builds and extends trust. Whether trust starts from the working relationship itself, or from what people deliver.
You earn trust here by being present, being known, and building a personal connection over time. The working relationship IS the personal relationship.
You earn trust here by delivering what you said you would. New colleagues get benefit of the doubt from day one, the hire itself was the vetting.
Delivery-culture colleagues are read as cold, transactional, or uninterested in the person. Relationship-culture colleagues are read as slow, inefficient, or "not focused on the work". Both are misreadings, the underlying practice is different, not the intent.
How the team carries meaning. How direct feedback is, and whether it's delivered explicitly or through context.
Feedback is wrapped, softened, and given through hint, tone, silence, or story. Reading between the lines is not optional. It's how the team communicates.
Feedback is direct, specific, and on-the-record. The team's cultural default is that clarity is a form of respect: people should hear the real message.
Explicit-culture colleagues read indirect communication as evasive or dishonest, and miss the real message. Context-culture colleagues read direct feedback as aggressive, disrespectful, or a personal attack. This is the single most-cited source of cross-cultural friction in the workplace research.
How decisions actually get made. Whether the shape is set in advance by role, or worked out live in the room through open contribution.
Real decision-making happens in 1:1 conversations before the meeting. The meeting itself confirms what's already been shaped. Junior disagreement is possible, but expressed diplomatically.
Decisions get shaped in the meeting itself, through open discussion. Speaking up is expected at every level. Direct challenge to seniors is normal and welcomed as long as the argument is good.
Contribution-led colleagues get frustrated by "another meeting to ratify what's already been decided in someone's office". Role-led colleagues get unsettled by public disagreement with seniors, and by decisions being reopened once made. Both sides frequently walk out of the same meeting believing very different things were agreed.
Whose name is attached to a piece of work: who it is given to, how much that person can decide alone, who is named for the credit and for a missed target, and who explains it to senior management.
New work goes to the leader, who shares it out. Someone given a piece of work checks the larger calls first. A missed target is discussed as a team or a process question. What this protects is the individual: nobody is left standing on their own.
The owner decides most things themselves and tells the leader what they decided. Their name is on the work when it goes well and when it does not. What this buys is clarity: everyone knows who to go to, and people are developed and rewarded for what they actually did.
A team that names owners will ask who is responsible and not get an answer it can use, and may keep pressing for a single name, which can look like an attempt to single someone out. A team where the work belongs to the group experiences the naming of individuals as exposure rather than clarity, and may be slower to raise a problem that would identify someone. Both readings are reasonable from inside.
How the team handles uncertainty: how much has to be clear before it is ready to start, and what happens when the work does not go to plan. The same unfinished brief is enough for one team to begin and not enough for another.
The questions are settled before the work starts. An unclear brief goes back for answers, and a written plan is prepared, often with approval, before anyone begins. When something unexpected happens, the team pauses and re-plans that part before continuing.
The team's default is that unknowns are things you discover, not things you resolve first. Adjusting course is normal, expected, and often the point.
Plan-and-execute colleagues read the iterative style as chaotic, unprofessional, or making it up as they go. Iterate colleagues read the plan-first style as slow, inflexible, or stuck in preparation while the world moves on. Sector matters here too, the same person might be plan-first in one context and iterate-first in another.
How we measure it
The assessment is short, but it's carefully designed. Items are written in the third person (observing how the team behaves, not how the respondent wants to appear), rated on a five-point scale with a "not enough opportunity to observe" option, and validated with an attention check to filter out inattentive responses. The result is a team profile you can trust to reflect what's actually happening.
Run the Business Culture Assessment with your team. Get an honest, statistically grounded profile, and the conversation that unlocks better collaboration.
Book an intro call → Explore country profiles