How I do product roasts

13 Jul 2024

Shreyas Prakash headshot

Shreyas Prakash

Product roasts are the best way to enhance one’s sensibility around building better products. It’s called a “roast” because it often involves a no-holds-barred, brutally honest critique of the product’s features, design, user experience, and overall value proposition.

In the spirit of ‘everything is a remix’, I’ve liberally forked, remixed and adapted a set of questions from industry leaders like Manas Saloi and Julie Zhou, to create my own tailored questionnaire for a product roast.

I run this through a new product or even a feature I would like to dig deeper into.

Strategy, Distribution and Market

  • If I was the PM for a product, how would I grow it?
  • What is the GTM of this product?
  • How big is this market?
  • Is the app a leader in this category?
  • Where does the product fit into the larger ecosystem of other companies/competitors? Where are they in this landscape?

Understanding the company and the larger context

  • What are the other products which the company creates? How does this product fit into the larger ecosystem?
  • What’s the culture and DNA of the brand?
  • What is the tone and voice of their brand? Any hints being dropped from their company blogs?
  • Any news from seekingalpha, perplexity, techcrunch, crunchbase on the company status
  • what is the vision the executives from the company are pitching in global platforms/podcasts/round-tables etc?

Playstore

  • Is the name unique? is it memorable?
  • What is written in the About section? Is it too generic? Do they talk about the value prop in terms of JTBD?
  • How do the screenshots look like?
  • What are the metrics shown on the playstore page?
  • Do I see it running ads on its competitor pages?
  • What has been their approach for the description? Is it just a bunch of keyword stuffing? Written description using reviews of their users to show social proof?
  • How is the page different from its competitors?

Positioning

  • What do I think about its positioning? Has the positioning been consistent across other touchpoints?
  • Is there a crisp and consistent description of the product across their playstore page, app?
  • What is A, B and C, but not D for this product? What are the things they say they do, and the things they say they don’t? And the things they say they do, but don’t?

Onboarding

  • How frictionless is the onboarding process? Any identifiable barriers?
  • Is signup mandatory?
  • Can you skip the onboarding process?
  • What is asked in the onboarding process?
  • How quickly can you get to the meat of the product? Get gratification by completing the task I hired for? Measure both by the number of steps as well as the time taken
  • What is the developer optimising for in the signup flow?
  • What are the decisions in the onboarding that might affect the FTUE?
  • Are they talking about features or jobs?

First Time User Experience

  • How does the app feel? What emotions does it raise?
  • Is the FTUE overwhelming? Does it meet my expectations?
  • If I have to describe this app to others, how will I do that in less than 8 words? Will I use the same thing highlighted by the product team on the playstore page/app?
  • Is the experience a straight line?
  • What is absurd/supernormal about it?
  • If I was the PM designing this FTUE, what data would I collect to personalise the experience?
  • What are the hypothesis I have that I would test as a PM?

Jobs to be done

  • What are the main jobs a user might have been hired this product for?
  • What does the JTBD force diagram look like for this app?

Defensibility

  • What is the moat?
  • How is the app increasing the switching cost?
  • How is it decreasing switching cost if I am thinking of switching over from other apps?

Building trust and reliability

  • What are the trust indicators in the product?
  • How is the app reducing customer anxiety?
  • Is there any social proof?
  • How does the user know it is a legit business?

Product and Design

  • What are the interactions I like?
  • What do I hate?
  • Do I like the information architecture?
  • What are the things I can copy in my own products?
  • Is there some interactions, some visual elements which do not map to the convention? Any that follow industry standards that other apps don’t?
  • Does the product design align with the frameworks I have learned over the years? Where does it deviate from the norm?
  • Now that i have used the product, what are the metrics I think the PM should be measuring?
  • What do I think the north star of the product is?
  • What are the experiments I would run?
  • Does the app experience tie back to what was promised in the playstore?

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Home is where the feeling of home residesreflections
  2. Notes on doing most good, doing some good, and living goodphilanthropy
  3. Notes on Londontravel
  4. 18 key ideas from reading Henrik Karlsson this monthwriting
  5. Stop arguing, and start drawing circles togethermathematics
  6. The whole world is just the snake eating its own tailmental-models
  7. Life lessons and hot takes from my 30slifestyle
  8. Building a skill for coherent science illustrationsscience
  9. My agentic engineering workflow (step by step)agentic-coding
  10. Hammock driven developmentagentic-coding
  11. Peculiar ways number three fits into our funny little brainsmental-models
  12. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  13. Authority in the guise of evidencecritical-rationalism
  14. Map is not the territoryphilosophy
  15. Self hypnosis as a manifestation ritualmeditation
  16. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  17. How I prepare for tough negotiations nowadaysnegotiation
  18. When should we steelthread somethingproduct-development
  19. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct
  20. Healthy conflict in teams have a tipping pointteam-building
  21. How I deslopify AI writingwriting
  22. How I started building softwares with AI agents being non technicalagentic-coding
  23. Read raw transcriptswriting
  24. Legible and illegible tasks in organisationsproduct
  25. L2 Fat marker sketchesdesign
  26. Writing as moats for humanswriting
  27. Beauty of second degree probesdecision-making
  28. Boundary objects as the new prototypesprototyping
  29. One way door decisionsproduct
  30. Finished softwares should existproduct
  31. How I periodically rank my rough draftsobsidian
  32. Flipping questions on its headinterviewing
  33. Vibe writing maximswriting
  34. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  35. How I build greenfield apps with AI-assisted codingagentic-coding
  36. We have been scammed by the Gaussian distribution clubmathematics
  37. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  38. I was wrong about optimal stoppingmathematics
  39. Thinking like a shipmental-models
  40. Hyperpersonalised N=1 learningeducation
  41. New mediums for humans to complement superintelligenceagentic-coding
  42. Maxims for AI assisted codingagentic-coding
  43. Virtual bookshelvesaesthetics
  44. It's computational and AI everythingagentic-coding
  45. Public gardens, secret routesdigital-garden
  46. Git way of learning to codeagentic-coding
  47. Style Transfer in AI writingagentic-coding
  48. Understanding codebases without using codeagentic-coding
  49. Vibe coding with Cursoragentic-coding
  50. Virtuoso Guide for Personal Memory Systemsmemory
  51. Writing in Future Pastwriting
  52. Publish Originally, Syndicate Elsewhereblogging
  53. Poetic License of Designdesign
  54. Idea in the shower, testing before breakfastsoftware
  55. Technology and regulation have a dance of ice and firetechnology
  56. How I ship "stuff"software
  57. Writing is thinkingwriting
  58. Song of Shapes, Words and Pathscreativity
  59. How do we absorb ideas better?knowledge
  60. Read writers who operatewriting
  61. Brew your ideas lazilyideas
  62. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  63. Compound Interest of Private Noteswriting
  64. Conceptual Compression for LLMsagentic-coding
  65. Meta-analysis for contradictory research findingsdigital-health
  66. Proof of workproduct
  67. Gauging previous work of new joinees to the teamleadership
  68. Task management for product managersproduct
  69. Beauty of Zettelswriting
  70. Stitching React and Rails togetheragentic-coding
  71. Exploring "smart connections" for note takingwriting
  72. Deploying Home Cooked Apps with Railssoftware
  73. Repetitive Copypromptingwriting
  74. Questions to ask every decadejournalling
  75. Balancing work, time and focusproductivity
  76. Hyperlinks are like cashew nutswriting
  77. Brand treatments, Design Systems, Vibesdesign
  78. How to spot human writing on the internetwriting
  79. Can a thought be an algorithm?product
  80. Opportunity Harvestingcareers
  81. Everything is a prioritisation problemproduct
  82. How I do product roastsproduct
  83. The Modern Startup Stacksoftware
  84. In-person vision transmissionproduct
  85. How might we help children invent for social good?social-design
  86. The meeting before the meetingmeetings
  87. Design that's so bad it's actually gooddesign
  88. Lessons learnt interview prepping for product rolesinterviewing
  89. Obsessing over personal websitessoftware
  90. English is the hot new programming languagesoftware
  91. Better way to think about conflictsrisk-management
  92. The role of taste in building productsdesign
  93. Dear enterprises, we're tired of your subscriptionssoftware
  94. Products need not be user centereddesign
  95. World's most ancient public health problemsoftware
  96. Pluginisation of Modern Softwaredesign
  97. Let's make every work 'strategic'consulting
  98. Making Nielsen's heuristics more digestibledesign
  99. Startups are a fertile ground for risk takingentrepreneurship
  100. Insights are not just a salad of factsdesign
  101. Minimum Lovable Productproduct
  102. Methods are lifejackets not straight jacketsmethodology
  103. How to arrive at on-brand colours?design
  104. Minto principle for writing memoswriting
  105. Importance of Whytask-management
  106. Quality Ideas Trump Executionsoftware
  107. Why I prefer indie softwareslifestyle
  108. Use code only if no code failscode
  109. Self Marketing
  110. Personal Observation Techniquesdesign
  111. Design is a confusing worddesign
  112. A Primer to Service Design Blueprintsdesign
  113. Rapid Journey Prototypingdesign
  114. Visualise detailed file structures on CLIcli
  115. Do's and Don'ts of User Researchdesign
  116. Design Manifestodesign
  117. Complex project management for productproducts
  118. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  119. Pedagogy of the Uncharted — What for, and Where to?education
  120. Future of Equity with Ludovick Petersinterviewing
  121. Future of Ageing with Mehdi Yacoubiinterviewing
  122. Future of Tacit knowledge with Celeste Volpiinterviewing
  123. Future of Mental Health with Kavya Raointerviewing
  124. Future of unschooling with Che Vanniinterviewing
  125. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  126. Future of work with Laetitia Vitaudinterviewing
  127. How might we prevent acquired infections in hospitals?digital-health
  128. The why to endure any howentrepreneurship
  129. Design education amidst social tribulationsdesign
  130. How might we assist deafblind runners to navigate?social-design