Many PMs are drawn to zero-to-one (explore-stage) work as a concept — but wanting it isn't the same as being suited for it. The Operator archetype in particular tends to underperform badly at zero-to-one, because an Operator's default instincts — wiki pages, OKRs, meetings, executive updates — are exactly the process machinery that a nascent, still-forming initiative doesn't need yet and can be actively harmed by. Doshi: he has 'seen many operators ruin entire teams and entire ... initiatives' this way — not merely underperform, but actively damage the effort.
An Operator can still succeed on a zero-to-one product, but only under specific conditions: recognizing their own limitation as an Operator, deliberately hiring Craftsperson and Visionary counterparts, and actually listening to them on the decisions that matter — rather than overriding them with process.
See Product Leadership Archetypes: Operator, Craftsperson, Visionary, Product Stage as the Primary Fit Factor for Product Leadership, Own-Archetype Hiring Bias (Self-Validation Trap).
The failure mode here isn't a lack of effort, ambition, or quality — Operators dropped into 0-to-1 work often produce genuinely excellent process artifacts (OKRs, wiki pages, executive updates). The problem is that this is the wrong currency at the explore stage, where the product itself hasn't been found yet. Doshi: 'I've seen many operators ruin entire teams and entire sort of initiatives because of this fascination of working on 0 to 1 products' — and 'you are an operator archetype you're going to suck at a 0-to-1 product because you're going to create beautiful Wiki pages.' This reframes the mismatch as a fit problem, not a skill problem, which changes the fix: it isn't for the Operator to become more Craftsperson- or Visionary-like. Instead, the fix is organizational — hire complementary archetypes (Product Leadership Archetypes: Operator, Craftsperson, Visionary: Craftsperson and Visionary) onto the team and actually cede decision authority to them on the important calls, rather than retaining control while adding headcount for cover. Doshi: 'they hire the right counterparts who are crafts people and Visionaries and they actually listen to them on the important things.'
Casey Winters extends this mismatch to new-product staffing specifically: product managers hired after a company has reached PMF typically built their careers optimizing an already-working product, so they usually lack zero-to-one intuition. Founders should not outsource second-product development entirely to these hires — the founder needs to stay personally, substantively involved, echoing why founder conviction predicts second-product success better than resourcing alone.