# Lessons from Firefox and Twitter - Alan Byrne (Product Leader, Mozilla) Page: https://stenobird.com/podcast/the-product-experience-1156837/lessons-from-firefox-and-twitter-alan-byrne-product-leader-mozilla Text version: https://stenobird.com/podcast/the-product-experience-1156837/lessons-from-firefox-and-twitter-alan-byrne-product-leader-mozilla.md Podcast: [The Product Experience](https://stenobird.com/podcast/the-product-experience-1156837) Published: 2026-02-18T06:00:00+00:00 Episode link: https://www.buzzsprout.com/1797429/episodes/18691889-lessons-from-firefox-and-twitter-alan-byrne-product-leader-mozilla.mp3 Audio file: https://www.buzzsprout.com/1797429/episodes/18691889-lessons-from-firefox-and-twitter-alan-byrne-product-leader-mozilla.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/the-product-experience-1156837/episodes/lessons-from-firefox-and-twitter-alan-byrne-product-leader-mozilla Duration seconds: 2165 ## Resource Alan Byrne, Product Leader for Mozilla’s Firefox extensions ecosystem, argues that the best product work is less doctrine and more judgement. In conversation with LRandy Silver, he breaks down why prioritisation frameworks like RICE and MoSCoW often masquerade as science while quietly embedding subjectivity—and why he prefers writing clear “what and why” statements over chasing false precision. From his experience at QuickBooks and Twitter, Alan explores when PRDs are genuinely valuable (com... ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/the-product-experience-1156837/episodes/lessons-from-firefox-and-twitter-alan-byrne-product-leader-mozilla/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/the-product-experience-1156837/lessons-from-firefox-and-twitter-alan-byrne-product-leader-mozilla.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.