Portable Playbook · Framework

The Hastings Inversion

Auditing Process for Mediocrity Insurance

Section IX · CROSS-CUTTING PLAYBOOKS: THE TALENT RAID · The Talent Raid

The process manual that protects you from the bottom 20% is experienced as an insult by the top 20%, and the top 20% are the ones with options.

How It Works

Every quarter, take the complete process inventory: every standing meeting, every approval chain, every review cycle. For each, ask two questions. First: if everyone on this roster were excellent, would we still need this? Second: who specifically is this designed to catch?

When Reed Hastings analyzed Pure Software's decline, he did not ask "how do we hire better?" He asked: what systemic conditions caused our best to leave? The answer was that rules created to compensate for mediocre hires drove out the excellent ones. The implementation step most leaders skip: after identifying the process, remove it silently for one quarter and measure what happens. If nothing breaks, the process was insurance against a risk that no longer exists. If something breaks, you have identified an individual, not a process problem.

How to Use This Today

Any organization with a growing process manual.

Run the Hastings Inversion this quarter: pull your complete process inventory. Every standing meeting, every approval chain, every review cycle, every sign-off requirement. For each, answer two questions. First: if everyone on this roster were excellent at their job, would we still need this process? If the answer is no, the process exists to compensate for someone's inadequacy. Second: who specifically is this process designed to catch? Name them. If the person has already left the company, you are running a process whose original justification departed years ago. The scar tissue remains. The specific implementation step most leaders skip: after identifying a process that exists for a person rather than a principle, remove it silently for one quarter and measure what happens. Do not announce the removal. Do not ask for permission. Just stop enforcing it and track the results. If nothing breaks, the process was insurance against a risk that no longer exists. If something breaks, you have identified an individual performance problem that was hiding behind a process, and now you can address the individual rather than taxing the entire team.

Post-acquisition integration.

The acquirer's processes will be experienced as insults by the target's best talent. Those are the people who will leave first, because excellent people have options and a low tolerance for bureaucracy they perceive as pointless. Before imposing any process on the acquired team, run it through the Hastings filter: "If everyone on this team were excellent, would we still need this?" If the answer is no, you are about to install a mediocrity tax on a team that was acquired precisely because it was not mediocre. The specific cost: every process you impose that the target's A-players consider beneath them accelerates their departure timeline by approximately the time it takes them to update their LinkedIn profile. That timeline is measured in weeks, not months.

The failure signature is specific: you conduct the audit and conclude that every process is necessary. If that is your conclusion, you have not conducted the audit. You have defended the status quo.