Alpha-Beta People and Process Design
Borrow finance's alpha/beta to decide where you want upside and where you want boring reliability.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 93%
A framework for matching people and process to the job. Alpha is outsized upside; beta is volatility. Some product areas and hires should be high-alpha (creative, risky, 0-to-1); others should be low-beta (predictable, reliable). The core insight: process exists solely to lower beta, and its unavoidable cost is suppressing alpha, so apply it surgically.
Origin
MacInnis imports the investing concepts of alpha (outperformance vs an index) and beta (volatility), then maps them onto people (e.g. 'Dennis Rodman' high-alpha types) and product surfaces. He developed it while reforming how Rippling builds product over his first ~11 months as CPO.
Core principles
- 01Alpha = outsized return above the default; beta = volatility/unpredictability.
- 02Processes in a business exist for the sole purpose of lowering beta.
- 03Every process has a hidden cost: it suppresses alpha.
- 040-to-1 work needs alpha; mature/mission-critical work (e.g. payroll) needs low beta.
- 05There is room on every team for one high-alpha 'nut job' — but only where you can afford the volatility.
How to run it
- 1
Classify the surface
Decide whether a product area or project needs alpha (novel angle, big upside) or low beta (reliability, no aberration). Payroll = low beta; a new 0-to-1 bet = alpha.
Pro tip Ask: if this thing is merely reliable but unremarkable, is that a win? If yes, it's a low-beta surface.
- 2
Match the person to the surface
Hire high-alpha people for high-alpha surfaces and low-beta operators for reliability-critical surfaces. A candidate can be excellent yet wrong-fit if their alpha/beta profile mismatches the role.
Pro tip Use it to decode a gut 'no': 'I liked him, but this is a high-alpha area and he's a low-beta person.'
Watch out Alpha and beta tend to be correlated in people; the pure 'high alpha, low beta' unicorn rarely exists.
- 3
Apply process as a beta dial, not a default
Add just enough process to lower beta where you want predictability, and consciously withhold it where you need alpha. Sometimes 'just a touch,' sometimes 'very clear rigid process.'
Pro tip Before adding any process, name exactly which volatility it removes and which upside it will cost.
Watch out Blanket process kills alpha across the board; that's how you get a reliable but mediocre product.
In the wild
Rippling 'badly' wants its payroll product to be very low beta — no unpredictability or aberration — so the team willingly accepts more process there.
→ Reliable money movement; process cost is worth it.
After a good conversation MacInnis can feel a candidate is strong yet wrong for a specific product, and the alpha/beta lens names why: high-alpha product, low-beta person.
→ Converts intuition into a communicable, defensible hiring decision.
Common mistakes
Adding process everywhere
Process lowers beta but suppresses alpha; applying it uniformly strangles the creative, high-upside parts of the org that needed volatility to win.
Putting a low-beta operator on a 0-to-1 bet
Reliable execution can't manufacture the non-obvious angle a new market needs; the surface stays mediocre.
Is it for you?
Best for
Product and eng leaders deciding where to standardize vs where to protect creative latitude, and hiring managers translating gut fit into words.
Not ideal for
Environments where every surface is genuinely safety-critical; there's little alpha to protect.
From the transcript
“processes processes in a business exist for the sole purpose of lowering beta. Processes are for decreasing volatility in the output of the system.”
“The the the downside of a process is that it suppresses alpha.”
“this is a high alpha product area, and he's a low beta person. Valuable, but definitely not the right fit for this.”
From the episode
10 contrarian leadership truths every leader needs to hear
Matt MacInnis (Rippling)