Flow States and High Stakes: How a human performance optimizer does agentic coding

The “traditional” engineering org chart is a relic of a time when code was the primary bottleneck. For technical founders today, the challenge has shifted from managing human velocity to orchestrating agentic systems and defending product taste.

In a recent Founder to Fortune conversation, Clayton Kim, CTO of FlyKitt and professional aerial acrobat, broke down how he transitioned from managing dozens at Wayfair to running a “wizard-led” team of three that outpaces traditional squads.

The Death of the Middle Manager

Clayton’s thesis is clear: the industry is over-correcting toward a flattened organization. The “middle management” layer—those whose primary output is consensus—is being rendered obsolete by agentic workflows.

For the technical founder, this means:

* Hiring “Wizard Architects”: You need ICs (Individual Contributors) who can manage five simultaneous Claude Code sessions, making high-level architectural trade-offs rather than just writing functions.

* The Soft-Skill Paradox: As technical tasks are offloaded to agents, the value of cross-functional “buy-in” and “commanding a room” skyrockets. Your best engineer must now be your best communicator.

“Taste” as the Only Defensible Moat

When any PM can “vibe-code” a functioning prototype, feature parity becomes instant. Clayton argues that taste—the ability to manifest a cohesive, delightful design opinion—is the only thing preventing your product from becoming generic “AI slop”.

* Regulatory Complexity: In industries like health-tech (FlyKitt’s domain), the moat isn’t the feature; it’s the underlying legal and insurance infrastructure that an LLM can’t replicate.

* Human Behavior Psychology: AI coaches fail because they lack social accountability. Clayton’s insight: “People will ignore a notification, but they won’t ignore a Navy SEAL on a Zoom call”.

The Tactical Hack: Lock Picking and Flow State