Insights are not just a salad of facts

Shreyas Prakash headshot

Shreyas Prakash

What is an insight?

An insight for Elon was: “The most entertaining outcome was the most likely’. His tweet suggests that he believes in taking risks and embracing the unknown, rather than playing it safe.

For Maya Angelou, the renowned poet and civil rights activist, it was: “People will forget what you said, but people will never forget how you made them feel”. A perspective on the impact of emotional connections.

Some of these insights challenge norms and encourage a re-evaluation on how we look at the world.

Getting insights however is not so easy.

We cannot just pluck insights from a tree and serve it on a platter.

As Chris Kocek states in his book, The Practical Pocket Guide to Account Planning, “Contrary to popular belief, there is not a mythical tree inside our offices from which we pluck insights on a daily basis.”

For individuals like Elon and Maya Angelou, it likely required a wealth of life experiences spanning years to distill such profound wisdom into concise statements.

Insights play a pivotal role in shaping the direction of a project, product, or even an entire company. Their significant return on investment is why companies prioritize investing in insights. While it’s impossible to replicate the depth of insights derived from decades of lived experiences, alternative approaches through design research methods can lead to valuable insights.

Let’s understand the shape of an insight by how the design research methodology ships insights. A typical design research cycle looks like this:

**You’ve got a problem or a question that needs solving. It could be creating something new or making an existing thing better.

First, you gather clues. You talk to people who might know something about the problem or have experienced it themselves. You listen to their stories, ask them questions, and take notes.

Next, you look for patterns. You analyze all the information you’ve collected and start seeing common themes or trends.

It’s like connecting the dots in a big picture. This helps you uncover insights and understand what really matters to the people involved.

Eventually, this becomes a process to churn out insights on a consistent basis within an organisation. There is a navigation from data, information, knowledge, INSIGHT and finally, wisdom.**

An insight is not just a statement. On the contrary, it is everything else but the statement. It’s the reasoning behind that statement. Insights are stories conveyed in a succinct way to help us with sensemaking.

Why do they help us with sensemaking? Why can’t all the data captured through all the interviews and literature studies be enough?

Picture this: 111111111111111…(million digits)

You’re brain finds it easy to store it (even if it’s around a million digits). You’ve been able to find the pattern here. A repetition of the number one. A million times.

But now, imagine this: 100010…(million digits)

You’re not able to make a head or tail of this information. You are not able to find patterns anywhere and are stuck.

Eventually you slice and dice the data, segment and start seeing some patterns emerging from what seemed like a random salad of 1s and 0s.

This is the process which design research adopts. Except that instead of 1s and 0s, you are trying to slice and dice transcriptions, anecdotes, statements, reports .

Insights help compress data in a beautiful way as you can clearly see the ‘why’ behind them. It ultimately has the shape of a story.

Your brain is a sprawling library of information. Stories, however, are the VIP section—easily accessible and constantly on your mind. And stories are wired into our very essence. We’re storytelling chimpanzees.

They captivate us, stick in our memory, and stand the test of time because they tap into the core of what it means to be human—our emotions, experiences, and the universal themes that connect us all.

Insights are arrows that cut through all the noise. They’re not just a salad of facts.

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

Read more

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