Induced Hurdles
A pattern Kevin named in himself: his ambitions repeatedly steer him into the hardest technical problem available, and he stays until it's solved. The hurdle is induced by the goal, not encountered by accident.
Kevin's own framing: "There's a pattern in my life I call induced hurdles - my ambitions take me to the hardest technical problems I can find." Source: Cursor transcript, Agent-Machines, 2026-05
The mechanism
Each ambition selects for a harder problem than the last, and each problem looks like a hard ceiling right up until it isn't. OMMC is the recurring example: scaling the organization, hardening the competition portal, and shipping its first real UI each felt like a perceived limiter until it wasn't. The hurdle is the point - it's how capability compounds. Source: Cursor transcript, Agent-Machines, 2026-05
The arc
The pattern threads Kevin's trajectory: building his first agent harness at AWS → founding engineering at Dedalus → Agent Machines as the thing he felt finally ready to "share with the world." Each step was chosen because it was harder, not safer.
Relationship to other positions
Induced hurdles is the engine under several of Kevin's other positions: it's why Bet on Yourself (take the risk now), Forward Deployed (operate where the hardest reps are), and Want It Bad Enough (intrinsic drive through difficulty) all show up together. It's distinct from each - those are about risk, operating mode, and motivation; this is the observation that the difficulty itself is self-selected.
Timeline
- 2026-05-31 | Page created from the Agent Machines YC founder-video transcript, where Kevin coins "induced hurdles" and ties OMMC → AWS → Dedalus → Agent Machines into one identity frame. Source: Cursor transcript, Agent-Machines, 2026-05