The Culture Map and International Project Management: Working Across Cultures in Construction
The Culture Map by Erin Meyer is one of the most useful books written about a risk that rarely appears in a risk register: the gap between what was said in a project meeting and what each side believed had been agreed.
At Brisk Group, we deliver construction project management, cost management, planning & project controls, development monitoring and technical due diligence across Romania, the United Kingdom, Moldova and the Gulf region. After ten years and hundreds of projects, one lesson is clear: on international construction projects, cultural misalignment can delay a project long before bad weather does.
Meyer explains why — and gives project managers a practical map for navigating it.
What The Culture Map is about
Meyer’s core argument is simple: people from different cultures communicate, decide, trust, disagree and schedule in systematically different ways.
These differences are rarely random. They are patterns shaped by education, institutions, management traditions and business environments. Once those patterns become visible, they can be managed.
The book organises these differences into eight scales. Every one of them appears, in one form or another, on an international construction project.
The eight scales — translated to the construction site
1. Communicating: low-context vs. high-context
Some cultures expect communication to be explicit, detailed and direct. Others rely more heavily on context, relationship, tone and what remains unsaid.
On a construction project, this distinction matters immediately.
A technical consultant may believe that a decision has been made because it was clearly stated in a meeting. A client or authority representative may understand the same conversation as exploratory, conditional or subject to later confirmation.
The safest protocol in international projects is usually the low-context one: clear minutes of meeting, written confirmations, decision logs, action owners and deadlines in black and white.
Good project management already knows this. Meyer explains why it is non-negotiable.
2. Evaluating: direct vs. indirect negative feedback
Feedback is another cultural interface.
In some environments, technical comments are direct, detailed and unsoftened. In others, criticism is wrapped in diplomatic phrasing. A British consultant may say, “you might want to consider this again” and mean, very clearly, “this is wrong and needs to be corrected.”
A project manager who cannot decode both styles may either take offence where none was intended or miss a warning that was deliberately expressed with restraint.
On design and construction projects, missed feedback can become abortive work, delay, cost exposure or dispute.
3. Persuading: principles-first vs. applications-first
Some professionals want the theory before the conclusion. Others want the recommendation first and the supporting logic afterwards.
This matters in technical reporting, cost advice, design reviews and development monitoring.
A lender may want a concise executive view: what is the risk, what is the exposure, what decision is required?
An engineering team may expect the full technical rationale before accepting the conclusion.
A public authority may require a different structure again.
The same project reality often needs to be translated into different decision formats.
A good consultant does not simply produce information. A good consultant structures information so that each stakeholder can make the right decision at the right time.
4. Leading: egalitarian vs. hierarchical
In some cultures, junior professionals may challenge senior leaders openly in a project meeting. In others, disagreement with hierarchy is more likely to happen privately, indirectly or through a different channel.
This has practical consequences.
A silent meeting is not always an aligned meeting. Sometimes the real issue emerges afterwards, one level down, through a side conversation or a delayed response.
For project managers, the question is not only who attended the meeting. The question is where decisions are actually made, who influences them, and how dissent becomes visible before it affects delivery.
5. Deciding: consensual vs. top-down
Decision-making rhythm differs significantly across international organisations.
In more consensual cultures, decisions may take longer because alignment is built before commitment. Once the decision is made, it tends to hold.
In more top-down cultures, decisions may arrive quickly, especially when senior authority is present. Yet those decisions can shift if the internal hierarchy, commercial pressure or stakeholder context changes.
Cost managers, planners and project directors need to understand this distinction. A fast “yes” and a slow “yes” do not always carry the same delivery risk.
Programme assumptions, procurement sequencing, cash flow forecasts and change control should reflect that reality.
6. Trusting: task-based vs. relationship-based
In some markets, trust is built primarily through performance: deliver what you promised, on time, with clarity and consistency.
In other markets, trust is built through relationship first: time spent together, informal conversations, hospitality, personal credibility and continuity of contact.
Neither model is superior. Both can produce strong professional relationships. The risk appears when one side misreads the other.
A task-based team may see relationship-building as inefficient. A relationship-based team may see purely transactional communication as cold, unstable or insufficiently committed.
International project management requires both: professional reliability and relationship intelligence.
7. Disagreeing: confrontational vs. avoids confrontation
Open disagreement can be productive in some project cultures and damaging in others.
In certain environments, a design workshop is expected to involve challenge, debate and direct technical contradiction. In others, open disagreement may create loss of face, escalation sensitivity or reluctance to speak candidly in front of senior stakeholders.
The project manager’s role is to create the conditions in which problems surface early.
That may mean structured workshops, bilateral conversations, anonymous technical reviews, issue logs, risk registers or formal escalation routes.
On construction projects, a problem raised late is rarely just a problem. It often becomes a claim.
8. Scheduling: linear-time vs. flexible-time
This is the scale every planner feels immediately.
In some project cultures, the programme is treated almost as a contract: sequential, fixed, measurable and highly sensitive to deviation.
In others, time is managed with greater flexibility. Priorities shift, relationships intervene, approvals move through informal channels and dates may be understood as targets rather than commitments.
Planning and project controls exist precisely to close this gap.
Baselines, look-ahead programmes, progress measurement, earned value indicators, dependency tracking and delay analysis give all parties a common reference point.
Without that shared reference, the same programme can mean different things to different teams.
Why this matters for international construction projects
Construction is already a coordination problem.
Developers, designers, contractors, subcontractors, authorities, lenders, tenants and operators all work with different incentives, risk tolerances and decision cycles.
Add three or four national cultures — for example, an international developer, a Romanian general contractor, a Turkish façade subcontractor, a UK-based fund monitoring drawdowns and a Gulf investor with long-term asset ambitions — and the coordination problem becomes more complex.
This is where an independent construction project management consultancy earns its fee.
A project manager fluent in FIDIC is valuable.
A project manager fluent in FIDIC and in the cultural operating systems of everyone at the table is a different asset entirely.
They translate documents. More importantly, they translate intent.
The hidden risk: everyone thinks they understood
One of Meyer’s most useful insights is that cultural perception is relative.
A communication style is never direct or indirect in the abstract. It is direct or indirect compared with another culture.
To a British professional, a Romanian negotiator may seem blunt.
To a Dutch professional, the same Romanian may seem diplomatic.
To a Gulf client, a European consultant may seem too transactional.
To a UK fund, the same consultant may seem appropriately concise.
Effective project managers calibrate to the counterpart, not to themselves.
This is a critical point. Judging another culture through the lens of your own is not neutrality. It is a measurement error.
In international projects, measurement errors are expensive.
What Brisk has learned from international delivery
Brisk Group’s work across Romania, the United Kingdom, Moldova, the Gulf and other international markets has reinforced a practical lesson: technical coordination and cultural coordination cannot be separated.
A design decision is also a communication event.
A cost report is also a trust instrument.
A programme is also a negotiation about time.
A risk register is also a way of making discomfort visible before it becomes conflict.
This is why project governance matters.
Clear reporting, decision logs, scope control, change control, risk registers, meeting discipline, stage gates and escalation protocols are not bureaucratic instruments. They are the infrastructure that allows international teams to work from the same map.
Without that infrastructure, each stakeholder may believe they are following the project correctly, while in reality they are following different assumptions.
What we would push back on
The Culture Map works with national patterns, and patterns can be useful. They can also flatten people.
A Bucharest-educated engineer who spent eight years on London projects may not behave like the “Romanian” point on a cultural chart. A British project director working for a Gulf client may adapt quickly to relationship-based decision-making. A German investor may be highly direct technically and highly diplomatic commercially.
The framework should be used as a first hypothesis, never as a verdict.
On real projects, the individual always matters. The organisation matters. The contract matters. The market context matters. Seniority, sector experience and professional discipline often matter as much as nationality.
The value of Meyer’s book is that it tells you which questions to ask early — ideally on day one, not in month six.
The Brisk verdict
Read it if you manage projects across borders — and in 2026, almost every serious project does.
Capital is international. Developers are international. Design teams, contractors, supply chains and lenders are increasingly international. The construction site is where all of these systems have to physically converge and perform.
Ten years of delivering projects across Romania, the UK, Moldova and the Gulf have taught us that the hardest interfaces on a project are rarely only technical.
They are often between people who are certain they understood each other.
The Culture Map is a manual for that interface.
One step ahead — on every project, in every culture.
FAQ
What is The Culture Map about?
The Culture Map by Erin Meyer is a framework for understanding how cultures differ across eight dimensions: communication, feedback, persuasion, leadership, decision-making, trust, disagreement and scheduling. The book helps leaders and teams work more effectively across international business environments.
Why is The Culture Map relevant to construction project management?
International construction projects bring together clients, consultants, contractors, designers, lenders and authorities from different cultural and professional backgrounds. Misread communication styles, decision-making norms, trust-building expectations and attitudes to schedules can create delays, disputes and delivery risk.
Who should read The Culture Map?
The book is useful for project managers, cost managers, planners, development monitoring professionals, design managers, investors and client representatives working on cross-border construction, real estate and infrastructure projects.
How does cultural misalignment affect construction projects?
Cultural misalignment can affect how teams interpret instructions, raise risks, confirm decisions, challenge technical issues, escalate problems and commit to deadlines. Left unmanaged, these differences can influence programme certainty, cost control, stakeholder confidence and dispute avoidance.
What does Brisk Group do?
Founded in 2016, Brisk Group is a construction project management and cost management consultancy with offices in Bucharest, London and Chișinău. The company provides project management, cost management, construction management, planning & project controls, development monitoring, technical due diligence, design management and related consultancy services across Romania, the United Kingdom, Moldova and international markets.
#ProjectBookshelf is Brisk Group’s ongoing review series of books that matter for construction, project management, cities, systems, leadership and the built environment.
Previous reviews include: How Big Things Get Done by Bent Flyvbjerg and Dan Gardner, The Checklist Manifesto by Atul Gawande, Thinking in Systems by Donella Meadows and The City of Tomorrow by Carlo Ratti.
