Trees, Branches, Twigs and Leaves — Mental Models for Writing
Shreyas Prakash
What differentiates a good essay and a great essay? — With a great essay, you can see the larger tree that connects all those branches, leaves, and twigs together into a single unit of a ‘tree’. A bad essay is where you only see the random assortment of leaves and branches. You don’t see the larger tree among the branches.
While listening to one of the podcast episodes from David Perell’s Writes of Passage where he interviews writer-operators to deconstruct their writing process, I noticed the podcast episodes to be very free-flowing, without losing the central theme of the conversation.
And this made the format engaging. In fact, the most boring podcasts I’ve listened to are the ones which start with the premise, and then the supporting arguments, and then the conclusion. That’s not what podcasts/conversations are supposed to be. A conversation has to be fluid. It should not be confined by a specific agenda/bullet points. It’s a discourse, or a ‘meeting’ in the business-sense with specific agenda / bullet points.
After listening to a couple of the episodes, I unearthed Perell’s mental model on how he approaches his interviews with his podcast guests. The tree is the mental model here.
Perell starts with the central theme (the tree), and then goes into the various sub-topics (the branches), goes deeper into the sub-topics of the sub-topics (twigs, leaves), and before it gets more deeper than that, he takes a step back, and directs the user back to the central-theme (the tree). In this way, the viewer/listener is not trapped in some version of a prime-number maze, where they’re not able to see where they are heading. They are still directed back to the tree, and can also capture the gist of what the author is saying. And this is a common pattern among other seasoned podcast hosts such as Joe Rogan, Lex Fridman and others.

And an attempt to progress is by following this principle: Go deep into the sub-topics, suspend, and take a step back and come back to the main topic. You’re the spider, and you are interweaving all the webs. Perell’s approach on podcasting has inspired me to do the same with my writing process. Essays are also supposed to be more ‘loose’ than be ‘rigid’. Even etymology wise, essays originate from the French word ‘essais’ which means an attempt.
So, I can very well add side-notes, callouts, footnotes, and make side-steps throughout my essay, but the reader has to still see the forest among the trees.
The plot should not be lost in the mess. And this is a creative tension worth pursuing.
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?