Episode Details

Blaine Billingsley is a Member of Technical Design Staff at OpenAI whose path into the field ran through music composition, spare-change website work at college, and a decade across Gmail, Airbnb, YouTube and Slack. At OpenAI he was hired to work on Presence, then redirected to solve a more immediate problem: making ChatGPT genuinely useful as a daily tool for designers. Working with a single engineer, he built the ChatGPT product design plugin — a bridge between the raw power of Codex and the day-to-day workflow of product teams. In this conversation with Randy Silver, he talks about what design actually means when your interface is a text box, why volume beats perfection in an age of infinite iteration, and why the fundamentals of good product thinking are more durable than the tools used to apply them.

Key takeaways

— The designer's job at an AI company has shifted from pixels to outputs. Deciding what "good" looks like, building the criteria to evaluate it, and heuristically assessing results is now a core part of the role — one that didn't exist in the same form at Gmail or Slack.
— LLMs don't replace structured creativity techniques; they scale them. The crazy eights exercise squeezes eight ideas from a room of people in eight minutes. A well-directed ChatGPT session can return 80 in the same window, alone, while you're at lunch.
— Volume beats perfection. The best way to make a pot isn't to try to make the best pot — it's to make a thousand pots. That logic now applies directly to prototyping: generate at scale, stay unattached, and find the nugget in the noise.
— Evals are closer to synthetic user research than quality assurance. The hardest part isn't building the rubric — it's correctly anticipating what people will actually try to do. Show it to one more person and your assumptions will immediately break.
— The second 80% problem hasn't gone away. Getting to a working prototype is dramatically faster; getting that prototype to production is still gruelling — and becomes harder still when platform direction shifts mid-sprint.
— Small teams with AI assistance need to protect the rituals that keep them aligned. When two people can each produce a week's worth of work in an afternoon, parallel drift becomes the real collaboration risk.
— Role boundaries are dissolving, but specialisations still matter. The question is less "what is your title" and more "what does the band need right now, and can you play that part?"
— Experience brings judgment; freshness brings juice. The best work often comes from junior designers unconstrained by years of accumulated assumptions — and both things need to be in the room.

Chapters 

• (00:00) Introduction
• (01:14) Blaine's background: from music composition to product design 
• (02:32) What design means at OpenAI 
• (04:21) The ChatGPT product design plugin 
• (06:12) Deciding what to build: the early exploration 
• (10:05) Structured creativity and LLM-powered ideation 
• (13:37) Volume over perfection: the thousand pots approach 
• (16:13) Designing as a two-person team 
• (20:29) What is the job now? 
• (23:33) Evals as synthetic user research 
• (27:08) Testing at scale when you can't know your users 
• (30:15) How they actually did the research 
• (33:01) The second 80%: from prototype to production 
• (35:06) Staying aligned without roadmaps 
• (38:19) Demo: the product design plugin 
• (44:52) When a prototype isn't ready to ship 
• (48:26) Design sprints, reimagined 
• (49:27) Advice for joining an AI-first product team 
• (52:17) The jazz analogy: experience, freshness and your role in the band 

Featured Links

• ChatGPT for Work: https://openai.com/chatgpt 
• Codex: https://openai.com/codex 
• Figma: https://figma.com