How I do product roasts

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