[{"data":1,"prerenderedAt":59},["ShallowReactive",2],{"/en/answer-library/when-you-suspect-a-team-is-gaming-a-kpi-or-hiding-bad-news-how-do-you-decide-whe":3,"answer-categories":35},{"id":4,"locale":5,"translationGroupId":6,"availableLocales":7,"alternates":8,"_path":9,"path":9,"question":10,"answer":11,"category":12,"tags":13,"date":15,"modified":15,"featured":16,"seo":17,"body":22,"_raw":27,"meta":28},"274418a6-aa92-4d87-b762-40d71c0aa7a2","en","c62299cd-ea3a-48d4-bc80-4e77105d2e19",[5],{"en":9},"/en/answer-library/when-you-suspect-a-team-is-gaming-a-kpi-or-hiding-bad-news-how-do-you-decide-whe","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","## Answer\n\nDefault 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.\n\n# Calling In vs Calling Out When a KPI Smells Funny\n\nYou 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.\n\n## Clarify what problem you’re solving (gaming vs. misunderstanding vs. fear)\n\n| Option | Best for | What you gain | What you risk | Choose if |\n| --- | --- | --- | --- | --- |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n\nBefore 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.\n\nFirst 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.\n\nSecond 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.\n\nThird 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.\n\nFinally, 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.\n\nPractical 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.\n\n## Decision framework: when to call in privately vs. call out publicly\n\nA 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.\n\nUse a simple rubric with six factors. You do not need a spreadsheet, just an honest read.\n\n1) Evidence strength: Do you have direct evidence, or just a vibe and a graph that looks odd?\n\n2) Harm and urgency: Is anyone at risk, is there financial or compliance exposure, or is this mainly a planning accuracy issue?\n\n3) Scope: Is it one person, one team, or an organization wide pattern tied to how the KPI is defined?\n\n4) Repetition: First time and plausible confusion versus repeated pattern after coaching.\n\n5) Power dynamics: Is the suspected actor senior, influential, or in a position to retaliate?\n\n6) Learning value: Would the broader group benefit from a public reset of definitions and expectations?\n\nDefault 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.\n\nHere is the reference table that helps many leaders choose the least bad option in the moment.\n\nAfter the table, here are the controls worth naming explicitly.\n\nEscalate Internally (Reporting): Use when the issue crosses into policy, legal, or serious ethics territory.\n\nCall In (Private Conversation): Your default for first contact, especially when facts and intent are still unclear.\n\nCall Out (Public Correction): Use to reset norms and prevent harm, not to vent frustration.\n\nCall In (with a witness): Use when power dynamics or disagreement make documentation and neutrality important.\n\nCommon 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.\n\n## Establish facts without creating fear: verification steps\n\nYou want to verify without turning the workplace into an interrogation room. Think “triangulation,” not “gotcha.”\n\nStart 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.\n\nThen 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.\n\nUse 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.”\n\nGet 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.\n\nPractical 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.”\n\n## How to call in privately: conversation structure and scripts\n\nA 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.\n\nStart 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.”\n\nShare 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.”\n\nInvite their explanation with real curiosity. “What am I missing? What pressures or constraints are you dealing with? How are you interpreting the metric definition?”\n\nMap 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.\n\nAsk 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?”\n\nClose 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.”\n\nIf 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.”\n\nWho 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.\n\n## How to call out publicly without shaming: structure and scripts\n\nPublic 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.\n\nStart 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.”\n\nShare 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.”\n\nAvoid 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.”\n\nState 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.”\n\nGive 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.\n\nA 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.”\n\nOne tasteful line of humor can defuse tension: “We are not here to make the dashboard happy, we are here to make the business healthy.”\n\n## Hybrid approach: private first, then public reset (most common)\n\nMost real situations benefit from a two step sequence.\n\nStep 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.\n\nStep 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.\n\nTiming 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.\n\n## Fix the system: make KPIs harder to game and easier to trust\n\nIf 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.\n\nUse 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.\n\nDefine the metric like you would define a contract. Specify inclusion, exclusion, timing, and ownership. Publish a one page definition and revisit it quarterly.\n\nAdd 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.\n\nBalance 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.\n\nPractical tip: Decouple compensation or status from a single metric when possible. Multi factor evaluation reduces the pressure that drives gaming.\n\n## Accountability without fear: consequences, coaching, and escalation\n\nAccountability works best when people know the difference between an honest mistake and a deliberate deception.\n\nIf it is an honest error or misunderstanding, coach and clarify. Fix definitions, train the team, and add a check.\n\nIf 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.\n\nIf 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.\n\nThe 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.\n\n## Hard cases: senior leaders, high performers, and cross team impacts\n\nSenior 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.\n\nHigh 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.”\n\nCross 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.\n\n## If you misjudged: repairing trust after a false alarm\n\nSometimes you will suspect gaming and be wrong. How you handle that moment determines whether people will ever trust you with early bad news again.\n\nOwn 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.”\n\nThank the people who helped clarify. This signals that transparency is rewarded.\n\nFix 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.\n\nFinally, 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.”\n\nIf 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.\n\n### Sources\n\n- [Calling In vs. Calling Out for Tough Conversations](https://www.pipedrive.com/en/blog/calling-in-vs-calling-out)\n- [The Ethical Callout: Raising Concerns Without Retaliation](https://productiveconflict.us/ethical-callout-raising-concerns-without-retaliation/)\n- [Reporting Unethical Behavior in the Workplace: A Guide for Leaders](https://www.complianceresource.com/blog/reporting-unethical-behavior-in-the-workplace-a-guide-for-leaders/)\n- [A guide on when, where, and how to blow the whistle safely](https://www.journalofaccountancy.com/issues/2023/jul/when-where-and-how-to-blow-the-whistle-safely.html)\n- [How to Speak Up About Ethical Issues at Work](https://hbr.org/2015/06/how-to-speak-up-about-ethical-issues-at-work)\n- [How to call bullshit on something](https://personalmath.substack.com/p/how-to-call-bullshit-on-something)\n- [When Feedback Crosses the Line](https://www.hbr.org/2026/03/when-feedback-crosses-the-line)\n- [The do's and don'ts of calling out the rotten egg in your team (when they're your senior)](https://outlign.co/blog/the-dos-and-donts-of-calling-out-the-rotten-egg-in-your-team-when-theyre-your-senior)\n\n---\n\n*Last updated: 2026-03-30* | *Calypso*","decision_systems_researcher",[14],"calling-in-vs-calling-out-for-tough-conversations","2026-03-30T10:06:50.177Z",false,{"title":18,"description":19,"ogDescription":19,"twitterDescription":19,"canonicalPath":9,"robots":20,"schemaType":21},"When you suspect a team is gaming a KPI (or hiding bad","Calling In vs Calling Out When a KPI Smells Funny You are not just choosing a conversation style.","index,follow","QAPage",{"toc":23,"children":25,"html":26},{"links":24},[],[],"\u003Ch2>Answer\u003C/h2>\n\u003Cp>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.\u003C/p>\n\u003Ch1>Calling In vs Calling Out When a KPI Smells Funny\u003C/h1>\n\u003Cp>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.\u003C/p>\n\u003Ch2>Clarify what problem you’re solving (gaming vs. misunderstanding vs. fear)\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Option\u003C/th>\n\u003Cth>Best for\u003C/th>\n\u003Cth>What you gain\u003C/th>\n\u003Cth>What you risk\u003C/th>\n\u003Cth>Choose if\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Escalate Internally (Reporting)\u003C/td>\n\u003Ctd>Serious misconduct, legal/compliance issues, or when direct approach fails\u003C/td>\n\u003Ctd>Formal investigation, organizational support, protection from retaliation\u003C/td>\n\u003Ctd>Loss of control over outcome, potential for slow resolution, impact on team morale\u003C/td>\n\u003Ctd>Behavior is illegal, unethical, or violates company policy. you lack authority\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Call In (with a witness)\u003C/td>\n\u003Ctd>Sensitive topics, potential for misinterpretation, or power imbalances\u003C/td>\n\u003Ctd>Accountability for both parties, objective perspective, reduces risk of 'he said/she said'\u003C/td>\n\u003Ctd>Can feel confrontational, may escalate tension if not handled carefully\u003C/td>\n\u003Ctd>You anticipate strong disagreement or need documentation of the conversation\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Call In (Private Conversation)\u003C/td>\n\u003Ctd>Individual behavior, misunderstanding, or unintentional errors\u003C/td>\n\u003Ctd>Preserves relationship, fosters trust, allows for explanation and growth\u003C/td>\n\u003Ctd>Perceived inaction, continued behavior if not addressed effectively\u003C/td>\n\u003Ctd>Low immediate harm, potential for learning, strong relationship with person\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Call Out (Public Correction)\u003C/td>\n\u003Ctd>Systemic issues, clear ethical violations, immediate harm, or repeated offenses\u003C/td>\n\u003Ctd>Sets public norms, protects others, demonstrates accountability, immediate correction\u003C/td>\n\u003Ctd>Public humiliation, defensiveness, damaged relationships, perceived as aggressive\u003C/td>\n\u003Ctd>High impact, clear evidence, need for collective awareness, safety is at risk\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Call Out (Anonymously)\u003C/td>\n\u003Ctd>High personal risk, fear of retaliation, or when direct action is unsafe\u003C/td>\n\u003Ctd>Raises awareness without personal exposure, protects your safety\u003C/td>\n\u003Ctd>Lack of direct follow-up, difficulty providing context, potential for misinterpretation\u003C/td>\n\u003Ctd>Your safety or job is at risk, and you have no other safe avenues\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch2>Decision framework: when to call in privately vs. call out publicly\u003C/h2>\n\u003Cp>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.\u003C/p>\n\u003Cp>Use a simple rubric with six factors. You do not need a spreadsheet, just an honest read.\u003C/p>\n\u003Col>\n\u003Cli>\u003Cp>Evidence strength: Do you have direct evidence, or just a vibe and a graph that looks odd?\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>Harm and urgency: Is anyone at risk, is there financial or compliance exposure, or is this mainly a planning accuracy issue?\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>Scope: Is it one person, one team, or an organization wide pattern tied to how the KPI is defined?\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>Repetition: First time and plausible confusion versus repeated pattern after coaching.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>Power dynamics: Is the suspected actor senior, influential, or in a position to retaliate?\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>Learning value: Would the broader group benefit from a public reset of definitions and expectations?\u003C/p>\n\u003C/li>\n\u003C/ol>\n\u003Cp>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.\u003C/p>\n\u003Cp>Here is the reference table that helps many leaders choose the least bad option in the moment.\u003C/p>\n\u003Cp>After the table, here are the controls worth naming explicitly.\u003C/p>\n\u003Cp>Escalate Internally (Reporting): Use when the issue crosses into policy, legal, or serious ethics territory.\u003C/p>\n\u003Cp>Call In (Private Conversation): Your default for first contact, especially when facts and intent are still unclear.\u003C/p>\n\u003Cp>Call Out (Public Correction): Use to reset norms and prevent harm, not to vent frustration.\u003C/p>\n\u003Cp>Call In (with a witness): Use when power dynamics or disagreement make documentation and neutrality important.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch2>Establish facts without creating fear: verification steps\u003C/h2>\n\u003Cp>You want to verify without turning the workplace into an interrogation room. Think “triangulation,” not “gotcha.”\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Ch2>How to call in privately: conversation structure and scripts\u003C/h2>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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?”\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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?”\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch2>How to call out publicly without shaming: structure and scripts\u003C/h2>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Ch2>Hybrid approach: private first, then public reset (most common)\u003C/h2>\n\u003Cp>Most real situations benefit from a two step sequence.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch2>Fix the system: make KPIs harder to game and easier to trust\u003C/h2>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>Define the metric like you would define a contract. Specify inclusion, exclusion, timing, and ownership. Publish a one page definition and revisit it quarterly.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>Practical tip: Decouple compensation or status from a single metric when possible. Multi factor evaluation reduces the pressure that drives gaming.\u003C/p>\n\u003Ch2>Accountability without fear: consequences, coaching, and escalation\u003C/h2>\n\u003Cp>Accountability works best when people know the difference between an honest mistake and a deliberate deception.\u003C/p>\n\u003Cp>If it is an honest error or misunderstanding, coach and clarify. Fix definitions, train the team, and add a check.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch2>Hard cases: senior leaders, high performers, and cross team impacts\u003C/h2>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch2>If you misjudged: repairing trust after a false alarm\u003C/h2>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>Thank the people who helped clarify. This signals that transparency is rewarded.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.”\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch3>Sources\u003C/h3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https://www.pipedrive.com/en/blog/calling-in-vs-calling-out\">Calling In vs. Calling Out for Tough Conversations\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://productiveconflict.us/ethical-callout-raising-concerns-without-retaliation/\">The Ethical Callout: Raising Concerns Without Retaliation\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://www.complianceresource.com/blog/reporting-unethical-behavior-in-the-workplace-a-guide-for-leaders/\">Reporting Unethical Behavior in the Workplace: A Guide for Leaders\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://www.journalofaccountancy.com/issues/2023/jul/when-where-and-how-to-blow-the-whistle-safely.html\">A guide on when, where, and how to blow the whistle safely\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://hbr.org/2015/06/how-to-speak-up-about-ethical-issues-at-work\">How to Speak Up About Ethical Issues at Work\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://personalmath.substack.com/p/how-to-call-bullshit-on-something\">How to call bullshit on something\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://www.hbr.org/2026/03/when-feedback-crosses-the-line\">When Feedback Crosses the Line\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://outlign.co/blog/the-dos-and-donts-of-calling-out-the-rotten-egg-in-your-team-when-theyre-your-senior\">The do's and don'ts of calling out the rotten egg in your team (when they're your senior)\u003C/a>\u003C/li>\n\u003C/ul>\n\u003Chr>\n\u003Cp>\u003Cem>Last updated: 2026-03-30\u003C/em> | \u003Cem>Calypso\u003C/em>\u003C/p>\n",{"body":11},{"date":15,"authors":29},[30],{"name":31,"description":32,"avatar":33},"Lucía Ferrer","Calypso AI · Clear, expert-led guides for operators and buyers",{"src":34},"https://api.dicebear.com/9.x/personas/svg?seed=calypso_expert_guide_v1&backgroundColor=b6e3f4,c0aede,d1d4f9,ffd5dc,ffdfbf",[36,40,44,48,52,55],{"slug":37,"name":38,"description":39},"support_systems_architect","Arquitecto de Sistemas de Soporte","Estos temas deben mantenerse sólidos en diseño de soporte, lógica de escalamiento, enrutamiento, SLA, handoffs y esa realidad incómoda donde el volumen sube justo cuando la paciencia del cliente baja.\n\nEscribe como alguien que ya vio automatizaciones romperse en la capa de escalamiento, equipos confundiendo chatbot con sistema de soporte y retrabajo nacido por ahorrar un minuto en el lugar equivocado. Queremos tips, modos de falla, humor ligero y ejemplos concretos de LatAm: retail en México durante Buen Fin, logística en Colombia con incidencias urgentes, o soporte financiero en Chile con más controles.\n\nStorylines prioritarios:\n- Qué debería corregir primero un líder de soporte cuando sube el volumen y cae la calidad\n- Cuándo enrutar, resolver, escalar o hacer handoff sin perder el hilo\n- Cómo equilibrar velocidad y calidad cuando el cliente quiere ambas cosas ya\n- Dónde los hilos duplicados y el ownership difuso vuelven ciego al soporte\n- Qué conviene mirar por sucursal además del conteo de tickets\n- Qué señales aparecen antes de que un desorden de soporte se vuelva evidente",{"slug":41,"name":42,"description":43},"revenue_workflow_strategist","Sistemas de captura, calificación y conversión de leads","Estos temas deben mantenerse fuertes en captura, calificación, enrutamiento, agendamiento y seguimiento de leads, incluyendo esas fugas discretas que matan pipeline antes de que ventas y marketing empiecen su deporte favorito: culparse mutuamente.\n\nEscribe como un operador comercial que ya vio entrar leads basura, promesas de 'respuesta inmediata' que empeoran la calidad y automatizaciones que solo ayudan cuando la lógica está bien pensada. Queremos tono experto, práctico, con criterio y enganche real. Incluye ejemplos de LatAm: inmobiliaria en México, educación privada en Perú, retail en Chile o servicios en Colombia.\n\nStorylines prioritarios:\n- Qué leads merecen energía real y cuáles necesitan un filtro elegante\n- Qué hace que el seguimiento rápido se sienta útil y no caótico\n- Cómo enrutar urgencia, encaje y etapa de compra sin volver la operación un laberinto\n- Dónde WhatsApp ayuda a capturar mejor y dónde empieza a fabricar basura\n- Qué conviene automatizar primero cuando el pipeline pierde por varios lados a la vez\n- Por qué el contexto compartido suele convertir mejor que solo responder más rápido",{"slug":45,"name":46,"description":47},"conversational_infrastructure_operator","Infraestructura de mensajería y confiabilidad de flujos de trabajo","Estos temas deben sentirse anclados en operaciones reales de mensajería, de esas que ya sobrevivieron reintentos, duplicados, handoffs rotos y ese momento incómodo en el que el dashboard 'crece' bonito... pero por datos malos.\n\nEscribe para operadores y líderes que necesitan confiabilidad sin tragarse un manual de infraestructura. El tono debe sentirse humano, experto y útil: tips que ahorran tiempo, errores comunes que rompen métricas en silencio, humor ligero cuando ayude, y ejemplos concretos de LatAm. Sí queremos referencias específicas: una cadena retail en México durante Buen Fin, una clínica en Colombia con alta demanda por WhatsApp, o un equipo de soporte en Chile que mide por sucursal.\n\nStorylines prioritarios:\n- Cuándo las métricas por sucursal se ven mejor de lo que realmente se siente la operación\n- Cómo conservar el contexto cuando una conversación pasa entre personas y canales\n- Qué conviene corregir primero cuando la operación de mensajería empieza a sentirse caótica\n- Dónde la actividad duplicada distorsiona dashboards y confianza sin hacer ruido\n- Qué hábitos devuelven credibilidad más rápido que otra ronda de heroísmo operativo\n- Qué significa de verdad estar listo para volumen real, sin discurso inflado",{"slug":49,"name":50,"description":51},"growth_experimentation_architect","Sistemas de crecimiento, mensajería de ciclo de vida y experimentación","Estos temas deben demostrar entendimiento real de activación, retención, reactivación, mensajería de ciclo de vida y experimentación de crecimiento, sin caer en discurso genérico de 'personalización'.\n\nEscribe como alguien que ya vio onboardings quedarse cortos, campañas de win-back volverse intensas de más y tests A/B concluir cosas bastante discutibles con total seguridad. Queremos contenido específico, útil y entretenido, con tips, errores comunes, humor ligero y ejemplos de LatAm: ecommerce en México durante Hot Sale, educación en Chile en temporada de admisiones, o fintech en Colombia ajustando journeys de reactivación.\n\nStorylines prioritarios:\n- Cómo se ve un primer momento de activación que de verdad da confianza\n- Cómo diseñar reactivación que se sienta oportuna y no desesperada\n- Cuándo conviene pensar primero en disparadores y cuándo en segmentos\n- Qué experimentos merecen atención y cuáles son puro teatro de crecimiento\n- Cómo el contexto compartido cambia la retención más que otra campaña extra\n- Qué suelen descubrir demasiado tarde los equipos en lifecycle messaging",{"slug":12,"name":53,"description":54},"Investigación, Diseño de Señales y Sistemas de Decisión","Estos temas deben convertir señales, conversaciones y eventos por sucursal en decisiones confiables sin sonar académicos ni técnicos por deporte.\n\nEscribe como un asesor con experiencia real, de esos que ya vieron dashboards impecables sostener conclusiones pésimas. Queremos criterio, tips accionables, algo de humor ligero y ejemplos concretos de LatAm. Incluye referencias específicas: una operación en México que compara sucursales, un contact center en Perú con picos semanales, o una cadena en Argentina donde los duplicados maquillan el rendimiento.\n\nStorylines prioritarios:\n- Qué números por sucursal merecen confianza y cuáles son puro ruido bien vestido\n- Cómo detectar señal sucia antes de que una reunión segura termine mal\n- Cuándo confiar en automatización y cuándo todavía hace falta criterio humano\n- Cómo convertir evidencia desordenada en insight útil sin maquillar la verdad\n- Qué suelen leer mal los equipos cuando comparan sucursales, conversaciones y atribución\n- Cómo construir una cultura de señal que sirva para decidir, no solo para presentar",{"slug":56,"name":57,"description":58},"vertical_operations_strategist","Temas de autoridad específicos por industria","Estos temas deben mapearse de forma creíble a cómo opera cada industria en la práctica, no sonar genéricos con un sombrero distinto para cada sector.\n\nEscribe como una estratega que entiende que clínicas, retail, bienes raíces, educación, logística, servicios profesionales y fintech se rompen cada una a su manera. Queremos voz experta, práctica y entretenida, con tips vividos, tradeoffs claros y ejemplos concretos de LatAm. Incluye referencias específicas: clínicas en México, retail en Chile, real estate en Perú, educación en Colombia, logística en Argentina o fintech en México y Chile.\n\nStorylines prioritarios por vertical:\n- Clínicas: qué mantiene la agenda viva cuando los pacientes no se comportan como calendario\n- Retail: cómo sostener la calma cuando sube la demanda y baja la paciencia\n- Bienes raíces: cómo se ve un seguimiento serio después de la primera consulta\n- Educación: cómo hacer más fluida la admisión cuando recordatorios y handoffs dejan de pelearse\n- Servicios profesionales: cómo mantener claro el intake y las aprobaciones cuando el pedido se enreda\n- Logística y fintech: qué mantiene los casos urgentes bajo control sin frenar el negocio",1775310169060]