The role of taste in building products

24 Jan 2024

Shreyas Prakash headshot

Shreyas Prakash

If we take Marc Lou, a familiar figure within the Twitter Indiehacking circle. He’s garnered attention for openly sharing his journey as a product builder. This transparency has piqued interest in his projects well before their launch, as followers have grown to appreciate his distinctive approach.

A notable instance of this was the excitement around his AI logo generator, which swiftly climbed to the top spot on Product Hunt. Despite its remarkable simplicity, the product captured the audience’s attention, largely because the audience already understood the creator’s taste.

Unlike indie hackers, and other product builders, companies do prioritise rigorous A/B testing and data-driven decision-making. As the projects involve larger teams, and processes, they subscribe to the philosophy of ‘letting the data do the talking’.

Take this snippet from Flo Health’s Medium blog here for example. Each and every feature is rigorously tested and experimented before going live.

Flo experiments dashboard as shown on their Medium blog. While this is the status quo, Indie hackers have normatively taken a different route.

People are considering taste and sensibility, despite the fact that taste is one of the hardest things to talk about. We now have more people building something “because it’s tasteful”, and maybe not as evidence based as it could be.

Brie Wolfson describes this inexplicability in his essay on Taste—

When I ask people what they mean by “taste,” they’ll stumble around for a bit and eventually land on something like “you know it when you see it,” or “it’s in the eye of the beholder.” I understand. Words like taste are hard to pin down, perhaps because they describe a sensibility more than any particular quality, a particular thing. We’re inclined to leave them unencumbered by a definition, to preserve their ability to shift shapes. But I don’t think we have to. And for the past several months, I haven’t been able to resist the urge to try to articulate taste.

This comes, in part, from a place of wanting to be precise — now that the term is such a frequent and varied part of our lexicon, it runs the risk of losing its meaning.  But I also believe taste is something we can and should try to cultivate. Not because taste itself is a virtue, per se, but because I’ve found a taste-filled life to be a richer one. To pursue it is to appreciate ourselves, each other, and the stuff we’re surrounded by a whole lot more. So, how to wrap my arms around this term in a way that captures its spirit without flattening it?

I can’t think of a piece of writing that does this more effectively than Susan Sontag’s “Notes on ‘Camp.’” In her words, “a sensibility is one of the hardest things to talk about… To snare a sensibility in words, especially one that is alive and powerful, one must be tentative and nimble. The form of jottings, rather than an essay (with its claim to a linear, consecutive argument), seemed more appropriate for getting down something of this particular fugitive sensibility.” 

Consider the approach of Linear, a company that diverges from the data-dominated decision-making model. Linear emphasizes the importance of taste and opinion in validating ideas and assumptions, rather than relying solely on A/B testing and metrics. This approach is about trusting one’s gut in a product’s readiness for launch, based on qualitative feedback and iterative improvements.

With certain projects, we might pull up specific data or metrics to see if the data gives us any more insights, but it’s not the way we make decisions. We don’t do A/B tests. We validate ideas and assumptions that are driven by taste and opinions, rather than the other way around where tests drive decisions. There is no specific engagement or other number we look at. We beta test, see the feedback, iterate, and eventually we have the conviction that the change or feature is as good as it can be at this point and we should release it to see how it works at scale. — Karri Saarinen, CTO of Linear__

This perspective is shared by Jason Fried, Co-Founder of 37 Signals (makers of Basecamp and Hey). Fried challenges the notion that everything must be A/B tested, questioning the practicality and relevance of ‘statistical significance.’

I am not driven by data, or I don’t have different P&Ls for each product in a way where we’re looking at them very carefully. It’s in total, collectively, are we making more money than we spend? That’s the only thing we ultimately look at, whether or not this product is more profitable than that product, and this is behind that, it’s all the things we do. It’s all the things we do. I don’t even think you can actually draw lines back to everything and go, “That was worth it. That wasn’t worth it.” What is the value of saying thank you to somebody? Would you want to A/B test that and, if it turned out that it was worse to say thank you to somebody, would you not do that? No, you would do it because it’s still the right thing to do. — Jason Freid, Basecamp

He argues for a more holistic view of success, focusing on overall profitability rather than the minutiae of individual product performance. Yet, the essence of ‘taste’ remains somewhat enigmatic. It involves an understanding of what makes a project or product resonate, balancing quality, appeal, and budget.

But there are some great examples showcasing this. Apple’s approach to sustainability reporting exemplifies this. Apple provided a new spin to the boring 10-page report format, focusing instead on a creative ad campaign outlining their efforts in a smart, eye-catchy fashion. They could have done the same thing in a more convenient format, but they chose to do it differently.

Apple provided a new spin to the boring 10-page report format, focusing instead on a creative ad campaign outlining their efforts in a smart, eye-catchy fashion.

As Brent Schlender describes in “Becoming Steve Jobs,” Apple’s resurgence from near-bankruptcy was driven by Jobs’ ability to harness ‘trusted auteur directors’ to realize a singular vision. Airbnb’s Brian Chesky also embodies this concept of taste. His 15-year journey in developing a nuanced understanding of both the demand and supply sides of Airbnb’s service has culminated in a distinct, qualitative essence that defines the brand.

Taste is nothing but intuition translated to action.  It’s your System 1 in action. A firefighter immediately notices thick smoke billowing from the house. All the years of training and experience has honed his instincts, and snap-second judgements. In split seconds, the firefighter is deciding on calls to backup, begin immediate entry, as well as identify escape routes to rescue victims.

Taste is nothing but intuition translated to action.

Who should steer the course of a product’s development – data-driven product managers or visionary auteurs? Should the focus be on relentlessly testing every modification and feature addition, or should we trust in the guidance of these auteur directors to fulfill their promise of impeccable taste?

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

Read more

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