The Mario Meeting

Rands uses a recurring peer — "Mario," a Senior Director — to illustrate how senior leaders misunderstand the compensation cycle. In any given summer, two budgets move simultaneously: this year's raise budget (locked a year ago, now being allocated in Talent Planning) and next year's budget (being built in strategy, product planning, and finance meetings).

Talent Planning divides a fixed pile of money across four performance buckets (Exceptional, Strong, Fine, Needs Work) with constraints on how many people fit in each bucket and a compensation range per bucket. These constraints enforce a curve — which managers are routinely told doesn't exist, but always does. The Lake Wobegon effect (every manager believes their team is above average) is why the constraints are needed.

Mario treats Talent Planning as a budget negotiation, arguing for more dollars. The correct forum was the Product Planning meetings months earlier, where strategy connects to features to headcount to cost. Mario never attended those — "I'm not a product guy" — and so missed the only window where budget can actually be influenced. The article's core warning: no one will explain this system to senior leaders; they're expected to figure it out themselves, and arguing about budget during Talent Planning signals a profound misunderstanding of how the business works.