There's a lot of noise about the future of the PM, designer, and engineering trio. Here's how OpenAI is resolving it:
I chatted with Ryan Lapopolo to get an inside look at OpenAI. Here's what he revealed: every role on the team got more specialized.
PMs write PRDs in markdown that Codex compiles directly into shipped pull requests. A documentation tree, test harness, and review agents handle the translation that used to require sprint planning and three standups. One PM shipped a complete "skill library" feature in under a week without a single engineer sync.
Designers ship full UI with instrumented noop backends. They call it the "painted door" pattern. Real users click real buttons, real data flows back, and engineering knows exactly what deserves investment before building a single API. When one designer got annoyed about curly quotes, he vibe coded a build-failing test. Typography has been perfect across the entire app ever since.
Engineers write constraints. Package boundaries that make spaghetti dependencies structurally impossible. Review agents with architectural personas. Build-failing tests that encode the team's taste into every future PR. The codebase grades itself.
Everyone comes together in one shared repo. The relay race between PM, design, and engineering collapsed into a harness where every commit compounds everyone's judgment.
Don't just listen to me. Hear it from the frontier:
Ryan Lapopolo, OpenAI: youtube.com/watch?v=8su…
Aparna Dhinakaran, Arize: open.spotify.com/episod…
Ed Bayes, OpenAI: news.aakashg.com/p/ed-b…
Jacob Brill, OpenAI: news.aakashg.com/p/jake…