Execution used to be the bottleneck. At Juno, taste is the bottleneck — the PM is the person who decides what "a trip that feels right for this family" actually means, in the places the Memory agent can't.
Most PMs were never bottlenecked by execution. They were bottlenecked by taste and judgment. Team capacity functioned as a governor that prevented bad ideas from shipping. Remove that governor and you discover who was driving and who was just steering.
We hire operators. On day one, this PM prototypes the onboarding flow in Claude Code in an afternoon — not a Figma, not a PRD, a clickable v0 the team reacts to. They write their own evals in Braintrust, read a LangSmith trace without asking for help, and move fluently across the eight layers from foundation models to strategy. They are craftspeople with model uncertainty: they can write the sentence "Juno is 90% sure this villa fits all nine of you — here's what we couldn't verify" and know why that sentence builds more trust than a confident lie. Above all, they have taste — the judgment to decide what "a trip that feels right for this family" means when the agent can't, in the moments that earn the second booking.
Builds a new first-trip onboarding flow in Claude Code before standup. Clickable v0 live by 11am.
Writes 24 evals against last month's first-trip failure logs. Each one becomes a regression test the Memory agent has to pass.
Ships the new onboarding to 10% of traffic. No sprint ceremony. Posts a 90-second Loom walking through the change + eval deltas.
Reviews overnight traces in LangSmith. Spots that Matching is under-weighting accessibility on first trips. Writes the fix themselves. Engineer cleans up before lunch.
Calls three Sarah-type users who hit the failure mode. Rewrites the uncertainty copy live. Ships by 4pm.