We scan new podcasts and send you the top 5 insights daily.
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.
Saying 'no' to product ideas is often contentious. At GitHub, the process is simplified by first 'seeking the truth'—rigorously assessing if an initiative aligns with the team's definition of success. If it doesn't, the 'no' becomes an objective, logical conclusion rather than a subjective or political decision.
To avoid ethical slippery slopes, project the outcome of a small compromise over time. Exaggerating a claim by 2% for better results seems harmless, but that success creates temptation to push it to 4%, then 8%. This compounding effect pushes you far from your original ethical baseline before you notice.
Before a major initiative, run a simple thought experiment: what are the best and worst possible news headlines? If the worst-case headline is indefensible from a process, intent, or PR perspective, the risk may be too high. This forces teams to confront potential negative outcomes early.
Simply stating a goal, like "increase sales by 15%," is insufficient for autonomous teams. Leaders must also articulate the "anti-vision"—the negative outcomes to avoid, such as eroding customer experience. This rich context provides clearer guardrails and a more nuanced understanding of the mission.
The "IKEA Check" is a three-question framework to fight personal bias. 1) Does my conviction come from my work or from evidence? 2) Would I fund this if it weren't my idea? 3) What is my confidence level before and after feedback? This forces a more objective assessment.
When faced with an ethically questionable directive, refusing outright can be career-limiting. A more effective strategy is to research and propose an alternative product that solves the same underlying business problem in a more responsible way, thereby redirecting the conversation.
Instead of adding more goals, use a three-part filter to audit them. A goal must support your nervous system (peace), meaningfully advance the business (profit), or align with your desired impact (purpose). This ruthless audit eliminates energy-draining tasks that were never truly yours.
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.
This simple question serves as a powerful, ongoing framework for evaluating project ROI. It forces teams to continually ask if the required effort (the "squeeze") is justified by the expected outcome (the "juice"), especially when facing scope creep or unexpected resource demands.