Answer

Default to a private call in first, because most KPI “gaming” starts as confusion, incentive pressure, or fear rather than a mustache twirling fraud plot. Go public only when there is clear evidence, real and immediate harm, repeated behavior after a private reset, or a need to set an organization wide norm quickly. Your goal is not to win an argument about the metric, it is to restore a trustworthy signal while keeping accountability intact.

Calling In vs Calling Out When a KPI Smells Funny

You are not just choosing a conversation style. You are choosing what kind of culture your measurement system creates: one where people surface reality early, or one where they learn to “manage the number.” And once a KPI becomes a political instrument, it stops being a KPI and turns into a weather report written by someone who really wants it to be sunny.

Clarify what problem you’re solving (gaming vs. misunderstanding vs. fear)

Option	Best for	What you gain	What you risk	Choose if
Escalate Internally (Reporting)	Serious misconduct, legal/compliance issues, or when direct approach fails	Formal investigation, organizational support, protection from retaliation	Loss of control over outcome, potential for slow resolution, impact on team morale	Behavior is illegal, unethical, or violates company policy. you lack authority
Call In (with a witness)	Sensitive topics, potential for misinterpretation, or power imbalances	Accountability for both parties, objective perspective, reduces risk of 'he said/she said'	Can feel confrontational, may escalate tension if not handled carefully	You anticipate strong disagreement or need documentation of the conversation
Call In (Private Conversation)	Individual behavior, misunderstanding, or unintentional errors	Preserves relationship, fosters trust, allows for explanation and growth	Perceived inaction, continued behavior if not addressed effectively	Low immediate harm, potential for learning, strong relationship with person
Call Out (Public Correction)	Systemic issues, clear ethical violations, immediate harm, or repeated offenses	Sets public norms, protects others, demonstrates accountability, immediate correction	Public humiliation, defensiveness, damaged relationships, perceived as aggressive	High impact, clear evidence, need for collective awareness, safety is at risk
Call Out (Anonymously)	High personal risk, fear of retaliation, or when direct action is unsafe	Raises awareness without personal exposure, protects your safety	Lack of direct follow-up, difficulty providing context, potential for misinterpretation	Your safety or job is at risk, and you have no other safe avenues

Before you decide private versus public, get crisp on what you think is happening. “Gaming” is a catch all label that can hide three very different problems.

First is misunderstanding. The KPI definition is ambiguous, the data is messy, or different teams interpret the same metric differently. In that case, calling someone out publicly is punishing them for your system’s vagueness.

Second is incentive pressure. The team is doing what the organization implicitly rewards, even if leadership does not love the side effects. This is classic Goodhart’s Law behavior: when a measure becomes a target, it stops being a good measure. The behavior might be rational, not malicious.

Third is fear and bad news concealment. People are worried about repercussions, status, or job security, so they delay, soften, or reframe reality. This is where “everything is green” until the week it is very much not.

Finally, there is deliberate deception. This is rarer than many executives think, but it does happen. When it does, the right response often includes formal escalation, not just a managerial conversation.

Practical tip: Write down, in one sentence, the harm you are trying to prevent. For example: “We are making staffing decisions based on a KPI that may not reflect real customer outcomes.” That sentence should guide how fast you move and how public you need to be.

Decision framework: when to call in privately vs. call out publicly

A good rule is “private for diagnosis, public for standards.” Private call ins are best for figuring out intent, constraints, and incentives. Public call outs, done well, are best for resetting norms and protecting others from harm.

Use a simple rubric with six factors. You do not need a spreadsheet, just an honest read.

Evidence strength: Do you have direct evidence, or just a vibe and a graph that looks odd?
Harm and urgency: Is anyone at risk, is there financial or compliance exposure, or is this mainly a planning accuracy issue?
Scope: Is it one person, one team, or an organization wide pattern tied to how the KPI is defined?
Repetition: First time and plausible confusion versus repeated pattern after coaching.
Power dynamics: Is the suspected actor senior, influential, or in a position to retaliate?
Learning value: Would the broader group benefit from a public reset of definitions and expectations?

Default choice: call in privately when evidence is incomplete, harm is not immediate, and there is a plausible misunderstanding or incentive trap. Shift toward a public call out when evidence is clear, impact is high, behavior is repeated, or you must set a norm for the group right now.

Here is the reference table that helps many leaders choose the least bad option in the moment.

After the table, here are the controls worth naming explicitly.

Escalate Internally (Reporting): Use when the issue crosses into policy, legal, or serious ethics territory.

Call In (Private Conversation): Your default for first contact, especially when facts and intent are still unclear.

Call Out (Public Correction): Use to reset norms and prevent harm, not to vent frustration.

Call In (with a witness): Use when power dynamics or disagreement make documentation and neutrality important.

Common mistake: Leaders “call out” a team in a staff meeting because the KPI looks suspicious, then discover later the data pipeline changed or a definition drifted. What to do instead is to privately verify first, then publicly reset the metric and expectation without pinning blame on an unproven narrative.

Establish facts without creating fear: verification steps

You want to verify without turning the workplace into an interrogation room. Think “triangulation,” not “gotcha.”

Start with the KPI definition and data source. Ask: what exactly counts, when is it counted, and who can influence the counting? Many gaming problems are really definition problems.

Then look for divergence between leading and lagging signals. If the KPI is improving but customer complaints, churn, quality defects, or cycle time are not, you may be seeing metric theater.

Use sampling. Pull a small set of underlying records and trace them end to end. Sampling is powerful because it is fast, concrete, and less accusatory than “I think you are lying.”

Get a second perspective from a neutral partner. This can be analytics, finance, operations, or an internal audit function, depending on your context. In ethical risk situations, follow internal reporting guidance and preserve documentation.

Practical tip: Document your observations in a “facts only” note with timestamps and sources. Avoid interpretive language like “they are gaming.” Use language like “conversion rate increased 18 percent while qualified lead volume decreased 22 percent, and three sampled deals show backdated stage changes.”

How to call in privately: conversation structure and scripts

A strong private call in has structure. It is kind, direct, and specific. It separates the person from the behavior and makes it safe to tell the truth.

Start with intent and stakes. “I want to make sure our numbers are a reliable guide for decisions. Right now I see a mismatch and I need your help understanding it.”

Share observations, not accusations. “Over the last two weeks, the KPI improved sharply, but the downstream outcomes did not move. I also saw a pattern in a small sample of records that I want to walk through.”

Invite their explanation with real curiosity. “What am I missing? What pressures or constraints are you dealing with? How are you interpreting the metric definition?”

Map incentives out loud. “If we only reward this KPI, what behaviors does it encourage? Are we unintentionally encouraging shallow wins?” This often surfaces the real issue: people are optimizing exactly what leaders celebrate.

Ask directly for correction and for the bad news version. “If the KPI is overstating performance, I need us to correct the reporting and share the true picture. What is the most honest way to represent this for the next review?”

Close with an agreement and a follow up date. “Let’s agree on the corrected definition and a short plan to validate the next two reporting cycles. We will review it together next Friday.”

If you suspect defensiveness, add a safety line. “I am not here to punish someone for being in a tough spot. I am here to make sure we are not steering the company with a broken compass.”

Who should attend? Usually just you and the owner of the KPI. Add a witness if there is a power imbalance, a history of conflict, or you need a clean record of what was said.

How to call out publicly without shaming: structure and scripts

Public corrections should be about standards and learning, not character. Your job is to protect the team’s ability to speak truth, while also making it clear that manipulating metrics is not acceptable.

Start by naming the norm. “We use KPIs to learn and decide, not to win. If a metric is not reflecting reality, we will fix the metric and the behavior.”

Share what you know, narrowly and factually. “We found that the current definition of X allows outcomes that look like improvement without improving customer results. We are addressing it.”

Avoid naming individuals unless it is necessary for safety, ethics, or repeated misconduct that requires transparency. In most business cases, you can keep it behavior level: “We saw patterns of misclassification” rather than “Alex did this.”

State the new expectation. “Starting this week, we will report X alongside Y, and we will sample underlying records monthly. If anyone sees pressure to misreport, raise it immediately.”

Give a safe channel for concerns. “If you are not comfortable raising it in the room, bring it to me, HR, compliance, or the established reporting channel.” This aligns with ethical callout guidance that emphasizes raising concerns without retaliation.

A simple public script that works: “We are resetting how we measure this because the current KPI can be optimized in ways that do not help customers. Thanks to everyone who surfaced questions. The goal is accuracy, not blame.”

One tasteful line of humor can defuse tension: “We are not here to make the dashboard happy, we are here to make the business healthy.”

Hybrid approach: private first, then public reset (most common)

Most real situations benefit from a two step sequence.

Step one is a private call in to understand what happened, correct the record, and decide whether it is a people issue, a definition issue, or an ethics issue.

Step two is a public reset that shares what the organization needs to know: updated definitions, added counter metrics, a verification mechanism, and a clear norm about truth telling. You do not need to share who made the mistake unless the wider group must understand a specific accountability decision.

Timing matters. Do the private call in quickly, ideally within days, so the story does not spread as rumor. Do the public reset after you have the facts and a concrete change to announce. Public meetings should not be live investigations.

Fix the system: make KPIs harder to game and easier to trust

If a KPI is easy to game, it will be gamed, even by good people on a bad week. The fix is rarely “try harder,” it is better measurement design.

Use a pair of metrics: one primary KPI plus a guardrail. For example, if you push for speed, add quality. If you push for volume, add customer outcome. This makes shallow optimization less attractive.

Define the metric like you would define a contract. Specify inclusion, exclusion, timing, and ownership. Publish a one page definition and revisit it quarterly.

Add light auditability. This can be as simple as monthly sampling, or a requirement that key status changes have a note and timestamp. You are not building a surveillance state. You are making the number explainable.

Balance quantitative reviews with narrative. In performance reviews and business reviews, require a short “what changed and why” explanation. People are less likely to hide bad news when they can explain the story and the plan.

Practical tip: Decouple compensation or status from a single metric when possible. Multi factor evaluation reduces the pressure that drives gaming.

Accountability without fear: consequences, coaching, and escalation

Accountability works best when people know the difference between an honest mistake and a deliberate deception.

If it is an honest error or misunderstanding, coach and clarify. Fix definitions, train the team, and add a check.

If it is negligent reporting, set a performance expectation and a deadline. “You own the integrity of this metric. Here is the corrected process. We will review compliance in two cycles.” Document it.

If it is deliberate deception, escalate. In many companies this means HR, compliance, legal, internal audit, or a formal reporting path. Guidance on reporting unethical behavior and whistleblowing emphasizes documentation, using appropriate channels, and protecting against retaliation.

The key is to keep fear out of truth telling, but not to remove consequences for dishonesty. People can handle high standards. They cannot handle unpredictable punishment for bringing bad news.

Hard cases: senior leaders, high performers, and cross team impacts

Senior leaders: Power changes everything. If the suspected gaming involves someone senior, assume retaliation risk is higher and direct confrontation may be unsafe or ineffective. Use a witness, involve a neutral function, or use internal escalation channels. If your organization has a speak up process, use it.

High performers: The temptation is to look away because the person “delivers.” Do not. High performers who bend metrics teach everyone else that integrity is optional. In the private call in, acknowledge performance while being firm: “Your results matter, and so does the truth about how we measure them.”

Cross team impacts: When one team’s KPI feeds another team’s work, gaming becomes a contagion. Handle these in a joint forum focused on definitions and interfaces. A public reset is often appropriate, but still avoid naming and shaming. Focus on shared standards and shared data.

If you misjudged: repairing trust after a false alarm

Sometimes you will suspect gaming and be wrong. How you handle that moment determines whether people will ever trust you with early bad news again.

Own the error quickly. “I raised a concern about the KPI based on patterns I saw. After review, the data shows it was caused by a definition change, not misreporting. That is on me for not verifying before escalating.”

Thank the people who helped clarify. This signals that transparency is rewarded.

Fix the root cause anyway. If you were wrong because the metric definition was unclear, or because the dashboard lacks context, improve it. A false alarm is still a signal that your measurement system is fragile.

Finally, reset the relationship privately with the people affected. “I am sorry for the stress this caused. Next time I will start with a private check and a shared review of the raw data before drawing conclusions.”

If you want one operational takeaway: start private, verify fast, and then go public only to reset norms and systems. Do not overcomplicate the conversation. Overcomplicate the measurement design instead, because that is where the real leverage lives.

Sources

Last updated: 2026-03-30 | Calypso

When you suspect a team is gaming a KPI (or hiding bad news), how do you decide whether to call in privately versus call out publicly? (Calling In vs Callinging