Reader · no content
No body text on file.
Open the original to read the full piece.
OpenAI Codex lead on the new shape of product work | Andrew Ambrosino
Brief
The episode centers on Andrew Ambrosino, product and engineering lead for OpenAI’s Codex desktop app, and how large language models are reshaping product work. Ambrosino traces Codex’s trajectory — started in November, shipped the desktop app in February — and cites striking adoption numbers from the host: a 6x usage increase since January and over 5 million weekly active users, with nearly 100% of OpenAI employees using the app weekly. That adoption revealed a larger organizational shift: implementation is no longer the scarce resource, so individuals across disciplines are building prototypes rapidly. The consequence, Ambrosino says, is an explosion of parallel experiments (“90 different explorations”), which makes curation and what he calls taste — the ability to pick, frame and integrate the best ideas — the central product skill.
Andrew pushes back on the binary claim that PRDs are dead: documents and prototypes both have precise roles. Documents remain the right medium for early-stage clarity; prototypes are useful for interaction and stress‑testing — but polished prototypes can mislead stakeholders into believing work is production-ready. He explains why AI is still limited for design: design is harder to grade, depends on culture and novelty, and requires tying visual choices into code abstractions — problems that current models and training-feedback loops haven’t fully solved. The conversation moves into org design: the Codex group shows role overlap (engineers who design, designers writing code), a “zone defense” approach for product coverage, and hiring for high-agency, high-taste builders. Operationally, planning has shortened — long-range plans are intentionally fuzzy because model capability timelines change outcomes (Ambrosino notes the same product shape performed very differently depending on model improvements between months).
Practically, Ambrosino describes product features and workflows he and his team dogfood: an in-app browser, computer control (automating local UI steps), connectors and extensions (e.g., a Premiere Pro extension used by the team’s videographer to edit via Codex), and automated daily briefs that scan Slack/pull requests. His vision is not a monolithic editor but a desktop home base that orchestrates best-in-class tools, surfaces common personal workflows as primitives (memory, automations), and lets users both run tasks inside the app and hand off to specialized apps as needed. Lenny and Andrew mostly agreed on the new emphasis on curation and taste, while diverging from simplistic takeaways about the death of roles or design processes — both argued for nuance and picking the right medium and discipline for the problem at hand.
Why it matters
Since January Codex usage grew 6x and the app now has over 5 million weekly active users; internally at OpenAI 'nearly 100%' of employees use Codex weekly (podcast intro, Lenny).
Key details
- Andrew Ambrosino: implementation has become cheap — teams now often skip lengthy PRDs and jump to prototypes, producing what he described as '90 different explorations' for the same idea; the scarce skill is now curation and 'taste' (deciding what to fold into product and how to present it).
- Ambrosino argues documents are still essential for product clarity (when the problem is vague) while prototypes are right for interaction testing — but prototypes can over-anchor because they look production-ready even when they're exploratory.
- Andrew: frontier AI models are still weak at design because design is hard to grade, requires cultural/novelty judgment, and needs an abstraction layer tying visual decisions to code — models will improve but those human judgment aspects remain challenging.
- Team structure on Codex: role overlap/collapse is common — Andrew estimates the core team is 'double digits' of engineers, roughly half that in designers, and a few product people; hiring prioritizes high-agency, high-taste 'builders' rather than strict role boundaries.
- Product planning shifted: short‑term work gets more precision; long‑range plans stay intentionally hazy. Andrew says the same Codex product shape would have failed in November but succeeded when released in February because model capability improved in the interim.