Here are key excerpts from our Presence Playbook:
Overview
A culture advisor works only if people use it. The intelligence behind it is rigorous, the deployment is simple, and the answers are useful — but none of that matters if employees don’t know that the advisor exists or don’t think to reach for it when they need it.
This playbook covers five functions: informing employees the agent exists, ensuring the first experience is useful, keeping the advisor visible over time, turning individual learning into collective intelligence, and proactively offering it at high-stakes moments.
The effort is modest. The initial introduction takes an hour to prepare. Ongoing maintenance takes fifteen to thirty minutes per week. The return is an organization where people reach for cultural intelligence instead of acting on misreadings.
Inform
Employees need to know three things: the advisor exists, it is helpful, and here’s the link.
Nothing else. No need to explain the research method. No need to describe the technology. No need to list features.
Experience
People don’t adopt tools because they’re told to. They adopt tools that help them. A culture advisor’s adoption strategy is not communication — it’s quality.
If the first answer is genuinely useful, colleagues will come back for more explanations and advice. If it isn’t, no amount of reminders will change that.
Remind
A nudge is a short piece of cultural content delivered to employees periodically. It is not a newsletter. It is not a lecture. It is one insight, one story, one observation — brief enough to read quickly, interesting enough to remember.
Each nudge ends with an invitation to engage: “Want to explore this further? Ask your culture advisor.”
Example: “Did you know that what your German colleagues call a decision and what your American colleagues call a decision may not be the same thing? In Germany, a decision is final and binding. In the US, a decision is often a direction that can be revisited. This single difference causes more friction than almost any other.”
Team Discussion
A culture advisor answers individual questions. A team discussion turns individual learning into collective intelligence.
When a colleague receives a useful answer from the culture advisor, they can bring it into the team. Paste the response into your Teams channel, your Slack thread, your Yammer group. Add a question: has anyone experienced this? How did it play out on our current project?
The discussion that follows does something the advisor cannot do alone — it connects cultural intelligence to shared experience. Colleagues who would never think to consult the advisor independently get drawn in through the conversation. Real situations get named and interpreted through a cultural lens, in real time, by the people living them.
For Copilot deployments: the culture advisor can be invoked directly inside a Teams channel. A colleague types a question in the channel thread, the advisor responds, and the answer becomes part of the visible discussion. Everyone sees it. The advisor becomes a participant in the conversation, not a separate tool.
The internal champion seeds this. Post a nudge in the channel. Ask a question. Invite colleagues to share their own situations with the advisor and bring the responses back. The habit builds quickly once the first useful exchange happens in public.
High-Stakes Moments
Some moments matter more than others. When teams enter high-stakes cross-cultural situations, the culture advisor should not wait to be discovered. It should be introduced directly to the people who need it most, at the moment they need it most.
What qualifies:
- A new global team has been formed
- A new cross-cultural project launches
- A conflict is brewing within or between teams
- A colleague goes on international assignment
Timing: Before the high-stakes moment begins. Not during. Not after. The value is in preparation.
Proactive Integration
A culture advisor adds the most value before friction occurs — before the meeting, before the trip, before the misreading. Proactive integration makes this happen automatically.
Your company already has systems that know when cross-cultural moments are approaching. HR knows when someone joins a multinational team. Calendars know when someone is meeting with a foreign office. Travel systems know when someone is going abroad. Project tools know when teams span countries.
Connect these systems to a simple workflow: when a trigger event occurs, send the colleague a prompt to consult the culture advisor.
Examples:
“You’ve joined a team with colleagues from Germany and India. Your culture advisor can help you understand how they work. [Start conversation]”
“You’re traveling to Japan next week. Want to prepare for the cultural dynamics? [Ask the advisor]”
“Your project now includes stakeholders from Brazil. Different working styles may apply. [Consult the advisor]”
This is workflow configuration, not software development. Your IT team connects existing systems using tools you already have — Power Automate, Workato, or native integrations. A few days of setup. No custom code.
The result: colleagues receive cultural intelligence at the moment it matters most, without having to remember to ask.
Summary
The effort is small. One launch announcement. One nudge every two weeks. Occasional targeted introductions at high-stakes moments.
Fifteen to thirty minutes per week. Occasional team discussions that turn individual queries into shared learning.
The return is an organization where cross-cultural friction is understood, not endured.
Back to Enterprises.