Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Just as cybersecurity teams use "red teams" to find system vulnerabilities, organizations should assign individuals a role to discover how key metrics can be manipulated. This exposes weaknesses in the goal-setting system before they are exploited unethically for personal or team gain.

Related Insights

Before committing to an outcome, teams should ask: "If we achieved this number via methods I'd be embarrassed to see in a news headline, is it a worthy goal?" This simple thought experiment acts as a powerful, practical guardrail against unethical tactics.

NFL CSO Cathy Lanier frames red teaming not as a "gotcha" exercise to find holes, but as quality assurance for security standards. It tests whether the processes you've implemented are truly effective and being executed correctly, revealing weaknesses in both design and implementation.

Like basketball coaches who make players analyze game film to spot momentum shifts, business leaders can use 'what-if' teams. By regularly gaming out hypothetical market shifts or competitor actions, they train the organization to recognize and seize real opportunities when they arise.

To expose vulnerabilities, run a "murder board" offsite. Task your team with a simple goal: if you were a new, well-funded competitor, how would you kill our company? This exercise forces brutal honesty, counters a culture of overly positive "optics," and reveals weaknesses before the market does.

When setting large goals, like an annual ARR target, don't just assign the number. Provide a rubric of expectations and require your team to develop and present their execution plan. This fosters ownership and allows for course correction before work begins.

Setting rigid targets incentivizes employees to present favorable numbers, even subconsciously. This "performance theater" discourages them from investigating negative results, which are often the source of valuable learning. The muscle for detective work atrophies, and real problems remain hidden beneath good-looking metrics.

To ensure rigorous vetting of ideas, create an environment of friendly competition between teams. This structure naturally motivates each group to find flaws in the other's thinking, a process that might be socially awkward in a purely collaborative setting. The result is a more robust, error-checked outcome.

Intense pressure to hit goals corrupts data-driven cultures. Teams may block improvements to A/B testing tools if accurate results threaten a 'win'. This pathology extends to shipping features solely to meet a deadline, with a plan to delete the code immediately after the performance review cycle ends.

When teams are singularly focused on hitting a number (e.g., engagement, account openings), they may rationalize unethical methods, as seen with Facebook's platform issues and Wells Fargo's fraudulent accounts. The relentless pursuit of a metric can justify evil outcomes.

To make outcome goals safer, supplement each objective with explicit constraints or "red lines." For example, pair "Increase signups by 20%" with "without increasing new user support tickets by more than 5%." This builds ethical and operational guardrails directly into the goal itself.

Use Cybersecurity's "Red Teaming" Concept to Proactively Game Your Own Goals | RiffOn