Building a Cross-Cultural Design Organisation
Sixteen people. Six nationalities. Twelve markets. Zero attrition in eighteen months. This is not a project case study. It is the story of building a team.
Why this matters
Most design leadership case studies describe products. This one describes the people who make products possible. I include it because building a high-performing team across cultural boundaries is the hardest and most consequential thing I do. The design system, the dashboards, the AI training, the product operations framework: all of those exist because this team works. None of them would exist if it did not.
Cross-cultural leadership is not a soft skill you list on a CV. It is a daily practice of navigating different expectations about hierarchy, feedback, communication, conflict, and ambition. Getting it right means people do extraordinary work. Getting it wrong means talented people leave, and you never quite understand why.
The composition
The team spans 16 people across three functions: Product Design, Content Design, and Product Operations. They represent six nationalities and their work reaches 12 international markets, serving over a million learners.
Each cultural context brings a different set of working assumptions. These are not stereotypes. They are patterns I have observed and navigated over years of working in international teams across Europe and the Middle East.
Some team members come from cultures where hierarchy shapes every interaction. Direct feedback from a manager is received as a directive, not an invitation to discuss. Others come from cultures where collaboration is assumed and direct disagreement is welcomed. Some value detailed process documentation. Others work best with broad goals and freedom to find their own path.
The mistake most managers make is choosing one model and applying it uniformly. That approach works when everyone shares the same cultural assumptions. In a team of six nationalities, it fails immediately.
What I did differently
Adapted communication, not people
I do not ask the team to conform to a single communication style. I adjust mine. This is not about performing cultural sensitivity. It is about recognising that the same message lands differently depending on how it is delivered.
Feedback for someone from a culture that values indirect communication requires a different framing than feedback for someone who expects directness. The content of the feedback does not change. The delivery does. This is not compromise. It is precision.
Built psychological safety through structure, not sentiment
Psychological safety is often discussed as though it were a feeling. In practice, it is a set of structural decisions. I created recurring rituals: design critiques with clear rules about how feedback is given, retrospectives where every voice is heard before any conclusions are drawn, and one-to-ones where the agenda belongs to the team member, not to me.
These structures do the heavy lifting. They create predictability. In a cross-cultural team, predictability is safety. When people know what to expect from a critique session, they bring their real work. When they do not know what to expect, they bring their safest work. The difference between those two versions is the difference between a team that grows and a team that stagnates.
Invested in professional growth as retention strategy
I sponsored Nielsen Norman Group and Interaction Design Foundation certifications. I built structured learning paths with milestone checkpoints. Junior designers were paired with senior mentors and given progressively larger scopes of responsibility.
This was not generosity. It was strategy. People stay where they are growing. In a market where competitors recruit aggressively, the most effective retention tool is not a higher salary. It is visible progress toward the career someone wants.
Multiple designers moved from junior to mid-level roles under this programme. The investment paid for itself: hiring a replacement designer costs months. Developing an existing one costs weeks and produces a more loyal, more capable team member.
Created a shared design language
When people come from different design traditions, "good design" means different things. I established shared reference points: a consolidated design system with clear usage rules, documented quality criteria, and regular cross-team reviews where work is assessed against those shared standards rather than individual preferences.
This shared language became the connective tissue. It allowed designers from different backgrounds to give each other meaningful critique. Without it, feedback defaults to personal taste. With it, feedback becomes a professional conversation about whether the work meets the standard the team has agreed on.
What happened
Results
Zero attrition across the entire 16-person team over 18 months. In a competitive market with active recruitment from larger companies, nobody left.
40% efficiency gain in design production, measured against the same period in the prior year.
28% increase in user satisfaction scores across the platforms the team supports.
Multiple junior designers promoted to mid-level roles through structured development paths.
The team transitioned from executing requests to leading full discovery-to-ship cycles independently. Design earned a seat at the product strategy table.
What I learned
The most important thing I learned about cross-cultural leadership is that it is not a special category of leadership. It is leadership done properly. Every team has different communication styles, different expectations about authority, different comfort levels with ambiguity. A six-nationality team simply makes those differences visible rather than allowing them to hide beneath a shared cultural surface.
I also learned that the metrics which matter most in team leadership are the ones that take the longest to produce. Attrition, growth, promotion, cultural cohesion: these are trailing indicators. You cannot optimise for them directly. You can only build the conditions that make them likely, and then wait.
The conditions, in my experience, are simpler than most leadership literature suggests: be clear about expectations, be consistent in how you treat people, be honest in your feedback, and invest genuinely in their growth. The cross-cultural dimension adds nuance to the delivery but does not change the fundamentals.
After thirty years across four countries, this team is the strongest proof of concept for how I lead. Not the design system. Not the dashboard. The people.