How do I get a good score in AI Scenarios?

High scores in AI Scenarios come from showing how you would turn a cultural difference into a better result for everyone, not from picking the "right" culture. Each scenario describes a workplace situation and asks how you would handle it. This guide explains what the scoring looks for and how to write a response that shows your cultural intelligence.

How your response is scored

Your response gets a score from 0 to 100, based on the CultureFlex skills taxonomy. The scoring looks at how well you identify the cultural dynamics at play, and how well your chosen strategy resolves the situation.

Your score places you at one of four proficiency levels:

Level	Name	Score	What it looks like in a scenario response
L1	Aware	0–25	You recognize that a cultural difference is involved and can describe it, but your response doesn't yet turn that into a plan.
L2	Practicing	26–50	You try to adapt, but the response is incomplete, one-sided, or still relies mostly on your own preferred style.
L3	Proficient	51–75	You read all the signals, choose a strategy that fits, and give concrete, well-timed actions that work for both sides.
L4	Strategic	76–100	You use the differences to improve the result for everyone, and shape how the team works in future so the issue is less likely to happen again.

The difference between Practicing and Proficient comes down to two things: whether you treat both sides as having something valuable to offer, and whether your actions follow clearly from your analysis.

Covering all of this takes space, so very short responses rarely reach L3. Aim for a few well-developed paragraphs, but don't pad: extra words only help when they add analysis, a strategy, an action or a reason.

What high-scoring responses do

Strong responses follow the same pattern: analyze the situation, decide on a strategy, apply it with concrete actions, and explain why it works.

Name the dimension and read every signal. Say which Worldprism dimension is at play, such as Explicit–Implicit or Task–Relationship. Then pull together all the clues in the scenario: what people say, what they avoid saying, who stays quiet, and who follows up privately. Silence is information, not agreement.
Recognize your own preference. Say how your own style might shape how you read the situation. For example, "If I lean Explicit, I might take this answer at face value."
See the value on both sides. Explain what each person's approach offers and what need sits behind it, such as protecting face, building trust, or getting clarity. Avoid treating one style as the problem.
Choose a deliberate strategy. Decide whether you will adapt your own style, blend approaches, co-create a way of working with the team, or set a clear rule. Say why that fits this situation, its deadline and its relationships.
Give concrete, well-timed actions. Say what you will do, with whom, in what setting and by when. For example, a private one-to-one before tomorrow's update is stronger than "I would talk to the team".
Include everyone. Account for quiet colleagues, the people who raised concerns, and outside stakeholders such as a client or manager. Protect anyone who told you something in confidence.
Balance adapting with honesty. Adapting to someone's style doesn't mean hiding problems. Strong responses still raise risks clearly with whoever needs to know, in a way that doesn't expose individuals.
Explain the outcome. Finish by explaining how your approach builds trust, improves the work, and meets the goal. Where it fits, mention how you would stop the problem from happening again, such as new team habits or channels.

Common reasons for a lower score

Taking words at face value. Reading "we'll see what we can do" as a yes, or a vague comment as minor, misses what the scenario is signaling.
Assuming silence means agreement. "If they had concerns, they would have said so" usually costs points.
Imposing your own style. Deciding alone because it's faster, or pressing someone for a direct answer in front of the group, solves your problem but not the team's.
Treating one side as wrong. Calling someone cold, slow or evasive, without exploring what their approach offers, makes the response one-sided.
Stereotyping. Explaining behavior only by nationality ("that's how people from X are") rather than by what you observe in the situation.
Staying vague. "Communicate better" or "build trust" without saying how, when and with whom.
Forgetting the goal. A response that handles the relationship but ignores the deadline, the client or the manager is incomplete.
Hiding the problem. Adapting so much that a real risk never gets raised.
Not explaining why. Listing actions without saying how they help.

Worked example

Scenario: You wrote the pricing section of a client proposal due on Friday. In Tuesday's review, one colleague says, "This part is interesting, maybe we can look at it again later." Another looks at the table and says nothing. A third says, "The numbers are fine, but the layout is not clear." The meeting moves on. The team must agree the final version by Thursday afternoon.

Level	Example response	Why it's at this level
L1 Aware	"One colleague seemed unsure and another was quiet, so there may be a difference in communication style. But only one person gave clear feedback, so I'll fix the layout and finalize it on Thursday."	It notices the cultural difference but doesn't act on it, and still treats silence as agreement.
L2 Practicing	"I'll fix the layout, then email the team asking for any other comments by the end of Wednesday."	It adapts a little and stays on schedule, but treats the vague comment as minor and relies on people raising concerns in writing.
L3 Proficient	"'Look at it again later' and the silence suggest unspoken concerns, so this is an Explicit–Implicit situation. Today I'll check in one-to-one with the two colleagues and ask open questions, such as what they'd change if they had more time. I'll fix the layout, share a revised version on Wednesday, and agree final sign-off on Thursday. Private conversations make it safe to raise concerns, so we find problems before the client does."	It reads the signals, names the dimension, uses private conversations that suit implicit communicators, meets the deadline, and explains why it works.
L4 Strategic	Everything in the L3 response, plus: "At sign-off, I'll suggest the team agree a simple feedback routine for future drafts, such as short written comments before each review meeting. That way, concerns come up early whatever people's communication style."	It solves the immediate problem and improves how the team works together in the future.

Quick checklist before you press Score

I named the Worldprism dimension at play.
I used all the signals, including silence and private messages.
I said how my own preference might affect how I read the situation.
I explained what each side's approach offers.
I chose a strategy and said why it fits.
My actions say what, who, where and when.
I included quiet colleagues and outside stakeholders.
Any real risk still gets raised honestly.
I explained how my approach improves trust and results.