You now have one-year access to UC.
You’re out
You no longer have access to UC.
Interviews
I have given many talks over the years. It never occurred to me that they could or should be recorded. Here are a few:
Collaborate Effectively
Affect Companies
Wrong Thinking
Global Companies
Back to About.
You’re in !
Congratulations. You now have one-year access to UC.
You’re out
You no longer have access to UC.
IT Deployment
This brief is for the IT team setting up the deployment. It sets out what you receive, what your team does, and what we need from you to confirm the fit.
In short: two files loaded into your existing AI environment, nothing installed, nothing connected back to us.
What you receive
Two components, delivered as files you hold. First, the cultural intelligence: a plain-language knowledge base your AI draws on, currently covering Germany, the United States, and fifteen business topics.
Second, the behavioral instructions: a system-prompt layer that tells your AI when and how to use that knowledge. Nothing else is installed.
How it runs
Both components run inside the AI environment you already operate. There is no separate system to buy, host, or connect, and no infrastructure to set up.
Understand Culture is not connected to your environment and receives no data from it. Your people’s questions, messages, and documents never leave your systems.
What your team does
Scoped to the starting group, a single administrator:
- Creates a dedicated assistant, project, or agent for the group.
- Loads the cultural-intelligence document, a single consolidated file, as its knowledge source.
- Places the behavioral instructions into the instruction or system-prompt field.
- Grants access to the intended colleagues, which is also the basis for billing.
- Runs a short test with realistic scenarios to confirm the AI surfaces the right material.
Effort and who is needed
On platforms with a projects, assistants, or agent layer — for example Claude for Enterprise, ChatGPT Enterprise, Microsoft Copilot, Google Gemini or Vertex, or Amazon Bedrock — setup is a one-person, roughly one-day task, and that person needs administrator rights rather than deep engineering.
In most of these environments the intelligence can sit in the assistant’s context as a single document, so on these platforms that is all it takes.
Only where a platform requires the knowledge to be chunked into a retrieval (RAG) index does the setup call for your AI-platform engineers and more time. The hands-on work is a person-day.
Allow separately for any security or governance review your own process requires, which can add calendar time the technical work does not.
Security and data
Because everything runs inside your environment and nothing is sent to us at UC, the deployment stays within your existing data-residency and security boundaries.
There is no external data flow to review, no vendor connection to secure, and no telemetry or licence check that reports back to us.
It works as a set of files you hold rather than a service you send work to. Your team can verify this directly rather than take our word for it.
What we need from you to scope it
So that we can confirm the fit and effort, please tell us: (1) which AI environment the teams use, (2) whether that environment can hold a single knowledge document in its context or requires chunked retrieval, and (3) the audience and the approximate number of colleagues to be given access.
Commercials
The price is €250 per user per year — a user being a colleague who has been given access to the cultural intelligence. You pay for those colleagues and no one else.
Access is scoped by your administrators, team by team, so you begin as small as you wish and widen from there. Billing is quarterly in arrears. Full commercial terms are set out separately. This brief is for technical scoping.
Support and updates
When we improve or extend the intelligence, you receive the new version and your team loads it the same way. Where helpful, we adapt the behavioral instructions to your specific platform so the cultural layer triggers reliably.
Back to How to begin.
How to deploy.
Our intelligence runs inside the AI environment you already have — whichever one that is, whether Copilot, Claude, Gemini, Bedrock, or your own internal model.
UC is not tied to any single AI provider, so it fits the environment you already run and moves with you if that ever changes.
There is no separate system to buy, install, or operate. There is no API-connection. Your own IT team does the setup.
There are two parts to load. The first is the cultural intelligence, the knowledge base your AI will draw on. The second is the instructions, which tell your AI when and how to use that knowledge.
Your IT team places intelligence and instructions into your AI environment. From that point, your AI has a cultural layer, and it can see what it could not see before.
When we add to or improve the intelligence, you receive the new version and your IT team loads it the same way.
Access to the cultural layer is then granted to the colleagues who need it.
Back to Companies.
“I’m fired!”
Germany. United States. Feedback.
Aaron, an American, is a first-rate engineer and manager. Sent to Germany on a three-year delegation, his job was to increase technical knowledge transfer, integrate critical processes, and build a cross-Atlantic organization based on transparency and trust. A very tall order.
After the first year came his formal feedback discussion with his German boss, Martin. The employer, a German multinational, takes such evaluations seriously — they shape compensation and career path. Central to the process is self-evaluation: you measure yourself against the goals you set a year earlier with your team lead. Aaron is focused, understated, not one to put himself front and center. If anything, he is overly self-critical.
From Aaron’s side, the year had gone well — surprisingly well. Reflecting beforehand, he felt he had an honest read on where he’d done well and where he hadn’t. Martin, a few years older, also a first-rate engineer, was grateful to have Aaron on his team and saw the year as a strong one: with few exceptions, and those in less critical areas, Aaron had more than met the ambitious goals they’d set. Martin was looking forward to an even better second year.
So both walked in expecting the same thing. Both had a B+ in mind. It should have been a meeting of minds.
The meeting. Aaron listened carefully, respectful of Martin as a fellow engineer and his superior, looking forward to agreeing on the year and setting goals for the next. But he left confused, almost shocked, in a daze. I’ll be fired within six months, he thought. How could I have been so wrong about myself?
It took days for Aaron to steady himself. Self-doubt swamped him. Was he out of touch with reality? Had he misunderstood the goals? Were his achievements over twelve months actually average, mediocre, worse?
What Aaron heard. Martin had focused almost entirely on Aaron’s weaknesses. There weren’t many, but Martin found them, and dwelt on them. There was so little said about the positives, about the real progress — and there had been real progress.
Information now flowed between Germany and the US. Two of the three key engineering processes were nearly fully integrated. There was a new Teamgeist. Aaron was respected by his German peers, and had even learned enough German for basic conversation.
To Aaron, hearing mostly about shortcomings, the message was clear and devastating: he had failed.
What Martin meant. Martin left puzzled too. Aaron had seemed distracted, disengaged, and when it came to setting next year’s goals he had little to offer. Strange. That’s not the Aaron I know. Personal problems? Homesick? The grey German winter?
What Martin could not see was this. He had voiced his satisfaction — early, and once. “You’ve done very good work, Aaron. No goal has gone unmet. You’re a strong member of my team.”
Any German in the room would have caught it: that is high praise from Martin. Aaron got a B+ — a strong grade in a culture where nobody is perfect, where there is always room to improve, where an A is truly rare, and rarer still from Martin.
Having said the positive once, Martin saw no reason to repeat it. Why dwell on what already works? So he moved to what he considered the valuable part of the conversation: how Aaron could go from B+ to A-, steadily, systematically, in the few areas where he could stretch further.
To Martin, this was respect — you invest detailed attention in your strongest people. To Aaron, it felt like nitpicking, like being told everything that was wrong with him.
For Martin, it was a pleasure — a capable person to develop. Aaron was exactly the kind of engineer a German boss wants to mentor. All of that stayed hidden from Aaron. And Aaron’s reaction stayed hidden from Martin.
They continued to work well together for two more years. But they were never again on the same wavelength. Two more formal reviews, and dozens of smaller feedback exchanges, and Aaron always felt a little off balance with Martin. Martin sensed it, but could never quite name it, much less address it. They succeeded, and senior management saw it. But they could have gone far higher.
Neither did anything wrong by their own culture’s rules. Both did everything wrong by the other’s. And neither could see it.
What went wrong
What feedback is for. For Americans, feedback reinforces. You lead with strengths, name what’s working, and build motivation — criticism comes carefully wrapped. For Germans, feedback corrects. You concentrate on weaknesses, on what can still improve, because that is where the value is. Praise is given once, plainly, and not repeated.
What a grade means. An American B+ sits in a scale where high grades are common and encouragement is expected. A German B+ sits in a scale where perfection is unreachable, an A is rare, and a B+ is genuinely strong. The same letter meant “you’re in trouble” to one and “you’re excellent” to the other.
The missed signal. Martin praised Aaron — once, early, sincerely. In American terms that single sentence was far too little to register as approval. Aaron never heard it as the strong endorsement it was. And Martin, having said it, never imagined it hadn’t landed.
Why neither fixed it. Aaron didn’t raise his distress — to him the review had spoken for itself. Martin didn’t probe the disengagement beyond wondering about the weather. Each read the other through his own rules, and the gap quietly stayed open for three years.
What their AI could have seen
Aaron and Martin had no way to read each other in that moment. Their company’s AI would have.
With cultural intelligence embedded, the AI each of them already used could have surfaced what neither could see — for Aaron, what a German B+ actually means and what Martin’s brief praise actually signaled; for Martin, that an American hears mostly-criticism as mostly-failure.
Not in a training a year earlier. In the moment, inside the tools they already worked in, available to both — an American in Germany and his German boss alike. The misunderstanding that shadowed three years could have been dissolved shortly after the review.
What did it cost?
The company will never see an invoice for this. But consider what it lost — and only you can put real numbers to your own version of it.
The lost partnership. Aaron and Martin could have become true strategic partners, inspiring each other and the whole organization. Instead they merely worked well. What is that gap — between good and what they could have been — worth on an organization that size?
The reduced performance. For two more years Aaron performed while “always a bit off balance.” What does a capable person operating below their real capacity cost, over two years?
The near-miss. Had the misread been sharper, Aaron might have felt unjustly judged and cut a three-year delegation short. What would ending that posting at eighteen months have cost — the knowledge transfer unfinished, the integration stalled, the replacement found and flown out?
The pattern. Now count the Aaron-and-Martin situations in your own company — capable people on both sides of a review table, reading the same words to mean opposite things. What does a year of quietly demotivated talent cost, when no one ever learns why?
Back to Three Reasons.
Monitor the value.
Because our cultural intelligence runs on your own AI platform, its use shows up in that platform’s reporting.
Your IT people set up your dashboard. There you can see how often cultural help is provided, which countries and topics are addressed, and which teams benefit.
None of this is something we add. It is your platform’s own reporting, in your own environment, showing you what is already there. We install nothing that watches, and we ask for nothing your platform does not already provide.
That picture is useful in its own right. It shows you where cross-cultural friction occurs in your organization and where it might make sense to extend access further.
This is monitoring for your benefit, not ours. It has nothing to do with what you are billed, which follows only from who has access.
Back to Companies.
Game Day
Germany. United States. Persuasion.
Mark works in the U.S. for a German company — an automotive supplier from the Stuttgart area, a hundred years old, ten thousand employees, €1.75 billion in revenue. It supplies not just VW and Mercedes but GM, Ford, and Chrysler.
First-rate technology, clear structure, a real drive to innovate. Mark came up through engineering and supply chain, then moved into sales and marketing, and is now Vice-President for North America.
The opportunity. Mark and his top people saw a serious market opening. Detroit was interested — GM, Ford, Chrysler — while the German carmakers were more reluctant. The project meant modifying one of the company’s best-selling products, which meant significant investment and close cross-Atlantic collaboration.
Mark’s team did it right, American style. They pinned down the market demand through customer discussions. They took it to engineering, who saw the potential and signed on. They refined the business case and brought it to the finance people, who weren’t convinced — so the team worked three straight days on the numbers until even the skeptics were on board. Engineering, yes. Finance, yes.
Game day in the U.S. Now they needed the North American board. Mark assembled his presenters and built the argument with care. For four straight weeks they worked, meeting Saturdays to tighten and rehearse, recruiting colleagues to play skeptical board members, pizza every Saturday night. Intense, and genuinely fun.
On the day, they won. The critical questions came, there were moments they nearly lost one powerful board member, they ran well over time. During breaks they huddled over laptops, redoing calculations, pulling in experts to answer detailed questions. High tension, but they stayed consistent and cohesive — and that cohesion convinced the board.
A few issues stayed unresolved, and that was fine with everyone. Innovation involves risk. At the end of the marathon, the North American CEO broke into a grin: “Great work, team. We’re behind you 100%. I’ll get you a date to present in Germany. But remember — our German colleagues will do their best to find the weaknesses in your plan. Dress warmly, as they’d say.”
Out in the hall, the team cheered and slapped backs. Mark pumped his fist. Yes. Let’s celebrate.
How they’d won. Every round had made the team more confident and more personally identified with the project. And Mark can sell — emotion and inspiration balanced with facts, on the principle his father drilled into him: sell yourself first, then your product or service. Risks were never called problems — consciously, deliberately, they framed problems as opportunities. “Always look for the silver lining.”
Every report and meeting mixed hard data with stories and war stories from past projects, told by people who could make them come alive — one engineer was so good at simplifying the complex they called him the Great Simplifier. Mark kept everyone focused on the future, literally counting slides to make sure the future outweighed the past.
The innovation had to feel like a leap, even where it was incremental. Colleagues joked he should have gone into politics or advertising — a bit of a Don Draper. And on the weak points, Mark took a frankly American line: if the audience doesn’t ask the hard question, we’re not obliged to volunteer our weaknesses. Let them pull it out of us. Caveat emptor.
Game day in Germany. The presentation to the parent board, and the meetings afterward with engineering, quality, sales, and commercial, did not go well. Some went very poorly. By noon on day two the team was unsettled and didn’t know why. They even began to suspect the Germans opposed the project simply because it came from the U.S.
They did what had worked at home — worked day and night, answered unanticipated questions, reached out to every possible supporter on both sides of the Atlantic. The Germans listened patiently and sincerely. None would commit to anything. Every meeting felt like a battle: argument, counter-argument, fact, counter-fact, experience, counter-experience.
By Thursday the team was physically and emotionally spent, with only minor meetings left and no time even for the sightseeing their hosts kept recommending. At breakfast Mark asked for odds. The team said fifty-fifty. They flew home Friday feeling defeated.
The answer came two weeks later. The German board thanked them for a motivating and at times very interesting presentation. They saw many positive aspects. The project would not be funded.
Neither side did anything wrong by its own culture’s rules. Both did everything wrong by the other’s. And the Americans never saw it coming.
What went wrong
Sell yourself, or step aside. Mark’s whole method — sell yourself first, put heart and soul on display, carry the room with conviction — is how you persuade in America. Germans are taught the opposite: be objective, separate self from substance, let the argument speak for itself.
So the very energy that won the U.S. board made the Germans wary. They read the self-selling as show over substance, even as an attempt to distract from weak arguments.
Opportunities, or problems. Mark’s team framed every risk as an opportunity and spoke relentlessly positively. Germans expect the word problem when there is one — not “challenge,” not “issue.” The relentless optimism didn’t reassure them. It made the team look naive, and made the Germans suspect that difficulties were being hidden.
Show your weak points — or be caught hiding them. Mark’s “let them pull it out of us” was, to the Germans, close to dishonest. They are proud Schwachstellenanalytiker — weak-point analysts. They spotted the soft spots early, waited for the Americans to address them, and grew suspicious when they didn’t. What Mark saw as normal salesmanship, they saw as withholding, perhaps even deception.
A sales pitch, or the start of a process. In America a strong presentation asks for the decision, and can win it. In Germany a presentation begins the decision process — it doesn’t end it. Mark pushed for a yes. The Germans deliberately gave no reaction, because for them it was far too early to signal anything. The push for closure itself looked unserious.
A leap, or continuity. The team sold the project as a bold leap into the future. Germans value continuity and careful, incremental change, and worried the Americans hadn’t defined the starting point clearly enough — that they’d rush off in the wrong direction, and move the company off a path it had held for two decades.
The bottom line: to the Germans, Mark and his team did not come across as competent. Brilliant, energetic, likeable — and not competent by German standards. The pieces without the whole. Stückwerk.
What their AI could have seen
Mark’s team had no way to know that the approach which won America would lose Germany. Their company’s AI could have.
With cultural intelligence embedded, the AI the team already used could have shown them, as they built the German presentation, that Germans persuade and are persuaded differently — that self-selling reads as show, that unnamed risks read as concealment, that a presentation in Germany opens a decision rather than closing it.
Not in a seminar years earlier. In the moment, as they prepared, inside the tools they already worked in — and available to their German counterparts too, who might have seen that the Americans’ optimism was enthusiasm, not evasion.
The same opportunity. Presented once for America, once for Germany, each on its own terms. It might have survived four days in the Stuttgart area.
What did it cost?
The company will never see an invoice for this. But consider what it lost — and only you can put real numbers to your own version of it.
The lost business. Detroit wanted this innovation. Had the project been funded, and had the German OEMs followed — as they might have — this was the payoff, the real return, at a company doing €1.75 billion a year. What is a conservatively estimated share of that opportunity, forgone, worth?
The stakeholders who backed it. A U.S. board committed to this “100%” and put its credibility behind it to the German parent. When Germany said no, what did that cost the standing of the American leadership who championed it — and their appetite to bring the next opportunity forward?
The stakeholders who watched. Detroit’s OEMs saw the German board reject an innovation they wanted. Will they now expect less from this supplier, and take the next idea elsewhere? What is that erosion of a customer relationship worth, over the years it shapes?
The people. Mark and his best people poured themselves in and flew home defeated, fully backed at home and rejected abroad. What does that cost in their motivation, their next initiative, their reasons to stay — and in every colleague who watches how it turned out?
The pattern. Now count the Game Days already unfolding in your own company — capable people persuading brilliantly by their own culture’s rules, and failing by the other’s. What does a year of them cost, in opportunities won at home and lost across the border?
Back to Three Reasons.