The United Statesvsthe United Kingdom
アメリカとイギリスUSUK
Seen from the United States: each line below describes the United Kingdom relative to the United States.
Culture Map: eight scales
Erin Meyer's eight scales, sorted by how far apart the United States and the United Kingdom sit, largest gap first.
Filled dot: the United States, where you are looking fromHollow ring: the United Kingdom
Where you will notice the difference4 scales
Communicating
The United Kingdom leaves more to be read between the lines than the United States (2 steps)
The United States −3, the United Kingdom −1, on a line from −3 (Low-context) to +3 (High-context).
Persuading
The United Kingdom wants the theory before the conclusion more than the United States (1 step)
The United States +3, the United Kingdom +2, on a line from −3 (Principles-first) to +3 (Applications-first).
Deciding
The United Kingdom decides by group agreement more than the United States (1 step)
The United States +1, the United Kingdom 0, on a line from −3 (Consensual) to +3 (Top-down).
Trusting
The United Kingdom builds trust through personal relationships more than the United States (1 step)
The United States −3, the United Kingdom −2, on a line from −3 (Task-based) to +3 (Relationship-based).
Where you are close4 scales
Evaluating
The United States and the United Kingdom sit on the same step
The United States 0, the United Kingdom 0, on a line from −3 (Direct negative feedback) to +3 (Indirect negative feedback).
Leading
The United States and the United Kingdom sit on the same step
The United States −1, the United Kingdom −1, on a line from −3 (Egalitarian) to +3 (Hierarchical).
Disagreeing
The United States and the United Kingdom sit on the same step
The United States 0, the United Kingdom 0, on a line from −3 (Confrontational) to +3 (Avoids confrontation).
Scheduling
The United States and the United Kingdom sit on the same step
The United States −1, the United Kingdom −1, on a line from −3 (Linear time) to +3 (Flexible time).
Hofstede: six dimensions
Scores from 0 to 100, sorted by the gap between the United States and the United Kingdom. They describe national averages, not either country's character.
Individualism
The United Kingdom scores 16 points higher than the United States (76 against 60)
The United States 60, the United Kingdom 76, on a line from 0 (Collectivist) to 100 (Individualist).
Uncertainty avoidance
The United Kingdom scores 11 points lower than the United States (35 against 46)
The United States 46, the United Kingdom 35, on a line from 0 (Tolerant of ambiguity) to 100 (Avoids ambiguity).
Long-term orientation
The United Kingdom scores 10 points higher than the United States (60 against 50)
The United States 50, the United Kingdom 60, on a line from 0 (Short-term) to 100 (Long-term).
Power distance
The United Kingdom scores 5 points lower than the United States (35 against 40)
The United States 40, the United Kingdom 35, on a line from 0 (Low power distance) to 100 (High power distance).
Motivation towards achievement and success
The United Kingdom scores 4 points higher than the United States (66 against 62)
The United States 62, the United Kingdom 66, on a line from 0 (Consensus-oriented) to 100 (Decisive).
Indulgence
The United Kingdom scores 1 point higher than the United States (69 against 68)
The United States 68, the United Kingdom 69, on a line from 0 (Restrained) to 100 (Indulgent).
What the sources say, theme by theme
Entries for the United States and the United Kingdom, side by side on wide screens. Each keeps its own confidence label and citations.
Design & quality
United States3 claims
At Google, engineers write a relatively informal design doc before writing code. According to Malte Ubl (2020), the point is not an exhaustive specification but a record of the trade-offs and alternatives considered.
Thin1 source2020us-design-1
Ubl says a design doc should be as long as necessary and as short as possible, and distinguishes it from a heavyweight waterfall-style specification.
Thin1 source2015Datedus-design-2
Meyer places the United States on the applications-first side of the Persuading scale. A book summary describes this as starting from conclusions and examples and favoring the practical how over the theoretical why.
Thin1 sourceus-design-3
United Kingdom3 claims
The GDS Government Design Principles (published 2012, updated 2025) include "Start with user needs," "Do less," and "Iterate. Then iterate again." Iterative development is an official principle of the public sector.
Well attested1 source2025gb-design-1
Point 8 of the GOV.UK Service Standard is "Iterate and improve frequently." It states that a service is never finished and that maintenance such as bug fixes is not enough.
Well attested1 sourcegb-design-2
According to a 2023 NAO report, there have been 11 cross-government digital strategies in the past 25 years. The Police National Computer, introduced in 1974, is still in use.
Well attested1 source2023gb-design-3
Failure & risk
United States2 claims
The Google SRE Book (2016) codifies the blameless postmortem. It identifies contributing causes without blaming individuals or teams and assumes that everyone involved acted with good intentions.
Well attested1 source2016us-failure-1
At F8 in 2014, Zuckerberg changed Facebook's motto from "Move fast and break things" to "Move fast with stable infra." His reason was that at Facebook's scale, the time spent fixing breakage outweighed the gain in speed.
Attested1 source2014Datedus-failure-2
United Kingdom4 claims
The GDS Way incident management standard requires incident reviews to follow a blameless post mortem culture.
Well attested1 sourcegb-failure-1
GOV.UK publishes incident reports, such as one on increased error rates on 5 January 2022. A former GDS staff member wrote in 2018 that publishing them builds trust and an atmosphere where people can learn safely.
Well attested2 sources2022gb-failure-2
In a 2019 blog post, the London fintech Monzo explained that it runs on-call with two people and records every incident. The Pragmatic Engineer warns against "blameless buck-passing," where blame is shifted while claiming to be blameless.
Well attested2 sources2019gb-failure-3
In the Post Office Horizon scandal, testimony that Horizon was "robust" was used despite bugs in the Fujitsu system, and more than 900 people were wrongly convicted. The Court of Appeal found that the Post Office had in effect reversed the burden of proof.
Attested2 sourcesgb-failure-4
Feedback & code review
United States3 claims
According to Meyer, Americans are often taught to wrap negative messages in positive ones (the feedback sandwich). For this reason she places the United States in the middle of the scale for delivering negative feedback.
Attested1 source2014Datedus-feedback-1
A blog explainer on Meyer's evaluating scale notes a common mismatch: Dutch and German colleagues take American praise at face value, while Americans find Dutch and German criticism too harsh.
Thin1 source2016us-feedback-2
A study of more than 70,000 GitHub pull requests from 17 countries (Rastogi et al., 2018) found that pull requests were more likely to be accepted when the reviewer and the submitter were in the same country.
Well attested1 source2018us-feedback-3
United Kingdom3 claims
Meyer writes that the British deliver negative feedback less directly than Americans and far less directly than the Dutch. She describes frequent understatement using downgraders such as "a bit" and "slightly."
Attested1 source2014Datedgb-feedback-1
The Anglo-Dutch translation guide that Meyer cites reads "With all due respect" as "I think you are wrong" and "Very interesting" as "I don't like it." The guide is half a joke, and its authorship is disputed.
Attested2 sources2014Datedgb-feedback-2
A study of 44,000 pull requests across 20 projects that compared acceptance rates with the developer's country HDI (Furtado et al., 2020) placed UK developers in the group with the highest acceptance rates.
Attested1 source2020gb-feedback-3
Hierarchy & decisions
United States2 claims
Meyer classifies the United States as egalitarian but top-down (HBR, 2017). People use first names and are encouraged to speak up, but the boss decides quickly, and the decision can be revisited when new arguments appear.
Attested1 source2017us-hierarchy-1
In the same article, Meyer reports that to Japanese managers an American boss can look flat on the surface yet highly autocratic in how decisions are made.
Attested1 source2017us-hierarchy-2
United Kingdom3 claims
In Meyer's 2017 HBR chart, the United Kingdom sits in the same egalitarian and top-down quadrant as the United States, Canada, and Australia.
Attested1 source2017gb-hierarchy-1
In the public sector, the service assessment against the Service Standard acts as a de facto gate. According to DfE guidance, a service can fail its assessment if it does not publish new source code without a good reason.
Well attested1 sourcegb-hierarchy-2
The NAO (2023) identifies as a problem that many digital decisions in government are made by generalist leaders without technical expertise.
Well attested1 source2023gb-hierarchy-3
Communication & docs
United States4 claims
Meyer places the United States at the most low-context end of the Communicating scale. A book summary describes a preference for saying things explicitly and for repeating and summarizing key points.
Thin1 sourceus-communication-1
According to Bezos's 2017 shareholder letter, Amazon does not use PowerPoint. Meetings start with everyone silently reading a six-page narrative memo, and memos carry no author's name because they come from the whole team.
Well attested1 source2018us-communication-2
According to CNBC (2018), the practice began with a 2004 email from Bezos. He explained that a good four-page memo is harder to write than a 20-page slide deck because the narrative structure forces better thinking.
Attested1 source2018us-communication-3
According to a blog post by Slab, Stripe also rarely uses slides. Meetings begin with silent reading of a memo, followed by comments on the document.
Thin1 sourceus-communication-4
United Kingdom3 claims
According to a book summary, the United Kingdom is on the low-context side of Meyer's Communicating scale but relies on context more than the United States, Canada, Australia, the Netherlands, and Germany.
Thin1 sourcegb-communication-1
"Make things open: it makes things better" is one of the government design principles, and publishing new source code is point 12 of the Service Standard. GDS explained the benefits of coding in the open in a 2017 blog post.
Well attested2 sources2017gb-communication-2
In 2015, Inside GOV.UK published a blog post describing what happens when something goes wrong on GOV.UK.
Well attested1 source2015Datedgb-communication-3
Work & careers
United States5 claims
According to the BLS, median employee tenure in January 2024 was 3.9 years overall, the lowest since January 2002. In the private sector it was 3.5 years.
Well attested1 source2024us-work-1
- BLS: Employee Tenure in 2024 (2024)
At-will employment is the default in every state except Montana. Unless the reason is illegal, either the employer or the employee can end the employment relationship at any time.
Well attested1 sourceus-work-2
According to layoffs.fyi figures cited by TechCrunch, tech layoffs in 2024 exceeded 150,000 people at 549 companies. The peak was 2023, with about 260,000.
Attested1 source2024us-work-3
In the Stack Overflow Developer Survey 2025, 45% of US respondents work fully remote, the highest share among the top responding countries. Median salaries were $200k for engineering managers, $175k for back-end developers, and $138k for full-stack developers.
Well attested1 source2025us-work-4
In Staff Engineer (2021), Will Larson sorts Staff+ individual-contributor roles, which do not require becoming a manager, into four archetypes: Tech Lead, Architect, Solver, and Right Hand.
Attested1 source2021us-work-5
- Will Larson: Staff Engineer (2021)
United Kingdom4 claims
According to the ONS, full-time workers averaged 36.6 actual hours per week in 2024. The figure covers all occupations, not only engineers.
Well attested1 source2026gb-work-1
In the Stack Overflow Developer Survey 2025, 31.9% of UK respondents work fully remote and 25.8% work hybrid leaning flexible. Median salaries were $136,141 for engineering managers and $108,913 for back-end developers, about 60 to 70% of US levels.
Well attested1 source2025gb-work-2
Making 20 or more people redundant requires collective consultation. Consultation must start at least 30 days before the first dismissal for 20 to 99 redundancies, and at least 45 days before for 100 or more.
Well attested1 sourcegb-work-3
In a 2022 four-day week pilot (61 companies, about 2,900 employees), 56 companies continued afterward and 71% of employees reported less burnout. Most participants were small companies, and the pilot was not limited to tech.
Attested1 source2023gb-work-4
Open source & community
United States2 claims
According to Octoverse 2025, the number of US developers on GitHub grew from 10.2 million in 2020 to 28 million in 2025, the most of any country. The US ranks second to India in open source contributors and first in total contributions.
Well attested1 source2025us-oss-1
- GitHub Octoverse 2025 (2025)
The same Octoverse 2025 report says the US, UK, and Canada more than doubled their developer counts from 2020 to 2025, while India and Brazil more than quadrupled. Its 2030 projection puts India ahead of the United States.
Well attested1 source2025us-oss-2
- GitHub Octoverse 2025 (2025)
United Kingdom3 claims
According to Octoverse 2024, the UK has more than 4 million developers on GitHub, up 19% year over year. Octoverse 2025 projects about 11 million by 2030.
Well attested2 sources2025gb-oss-1
- GitHub Octoverse 2024 (2024)
- GitHub Octoverse 2025 (2025)
An estimate by the industry body OpenUK (2023) attributes 27% of the UK tech sector's gross value added in 2022 to open source.
Attested1 source2023gb-oss-2
The public sector has made publishing code the default. The Skills Funding Agency reused GOV.UK's Smart Answers code and finished in under a week work that would otherwise have taken at least two months.
Well attested1 source2017gb-oss-3