Insights are not just a salad of facts
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
2026
2025
- Legible and illegible tasks in organisations
- L2 Fat marker sketches
- Writing as moats for humans
- Beauty of second degree probes
- Read raw transcripts
- Boundary objects as the new prototypes
- One way door decisions
- Finished softwares should exist
- Essay Quality Ranker
- Export LLM conversations as snippets
- Flipping questions on its head
- Vibe writing maxims
- How I blog with Obsidian, Cloudflare, AstroJS, Github
- How I build greenfield apps with AI-assisted coding
- We have been scammed by the Gaussian distribution club
- Classify incentive problems into stag hunts, and prisoners dilemmas
- I was wrong about optimal stopping
- Thinking like a ship
- Hyperpersonalised N=1 learning
- New mediums for humans to complement superintelligence
- Maxims for AI assisted coding
- Personal Website Starter Kit
- Virtual bookshelves
- It's computational everything
- Public gardens, secret routes
- Git way of learning to code
- Kaomoji generator
- Style Transfer in AI writing
- Copy, Paste and Cite
- Understanding codebases without using code
- Vibe coding with Cursor
- Virtuoso Guide for Personal Memory Systems
- Writing in Future Past
- Publish Originally, Syndicate Elsewhere
- Poetic License of Design
- Idea in the shower, testing before breakfast
- Technology and regulation have a dance of ice and fire
- How I ship "stuff"
- Weekly TODO List on CLI
- Writing is thinking
- Song of Shapes, Words and Paths
- How do we absorb ideas better?
2024
- Read writers who operate
- Brew your ideas lazily
- Vibes
- Trees, Branches, Twigs and Leaves — Mental Models for Writing
- Compound Interest of Private Notes
- Conceptual Compression for LLMs
- Meta-analysis for contradictory research findings
- Beauty of Zettels
- Proof of work
- Gauging previous work of new joinees to the team
- Task management for product managers
- Stitching React and Rails together
- Exploring "smart connections" for note taking
- Deploying Home Cooked Apps with Rails
- Self Marketing
- Repetitive Copyprompting
- Questions to ask every decade
- Balancing work, time and focus
- Hyperlinks are like cashew nuts
- Brand treatments, Design Systems, Vibes
- How to spot human writing on the internet?
- Can a thought be an algorithm?
- Opportunity Harvesting
- How does AI affect UI?
- Everything is a prioritisation problem
- Now
- How I do product roasts
- The Modern Startup Stack
- In-person vision transmission
- How might we help children invent for social good?
- The meeting before the meeting
- Design that's so bad it's actually good
- Breaking the fourth wall of an interview
- Obsessing over personal websites
- Convert v0.dev React to Rails ViewComponents
- English is the hot new programming language
- Better way to think about conflicts
- The role of taste in building products
- World's most ancient public health problem
- Dear enterprises, we're tired of your subscriptions
- Products need not be user centered
- Pluginisation of Modern Software
- Let's make every work 'strategic'
- Making Nielsen's heuristics more digestible
- Startups are a fertile ground for risk taking
- Insights are not just a salad of facts
- Minimum Lovable Product
2023
- Methods are lifejackets not straight jackets
- How to arrive at on-brand colours?
- Minto principle for writing memos
- Importance of Why
- Quality Ideas Trump Execution
- How to hire a personal doctor
- Why I prefer indie softwares
- Use code only if no code fails
- Personal Observation Techniques
- Design is a confusing word
- A Primer to Service Design Blueprints
- Rapid Journey Prototyping
- Directory Structure Visualizer
- AI git commits
- Do's and Don'ts of User Research
- Design Manifesto
- Complex project management for product
2022
2020
- Future of Ageing with Mehdi Yacoubi
- Future of Equity with Ludovick Peters
- Future of Tacit knowledge with Celeste Volpi
- Future of Mental Health with Kavya Rao
- Future of Rural Innovation with Thabiso Blak Mashaba
- Future of unschooling with Che Vanni
- Future of work with Laetitia Vitaud
- How might we prevent acquired infections in hospitals?