Poetic License of Design
Shreyas Prakash
Let’s say you have to make slides for tomorrow’s big meeting. Your boss wants five strategy points on one slide. You know that’s too much to be put on one slide, but it’s being insisted. “This gives a complete picture of our strategy”. “We can’t split it up.”
You think there is another way. You spread these points across five clean slides, one point per slide, and you still receive a pushback. They worry it waters down their message. You’re stuck between what works and what your bosses want.
In my current worldview, I would err on the side of clarity.
Ideas are only as good as our ability to communicate them. We might have the best possible product strategy, and it still needs the messenger to have delivered the message right, for the reader to chew and digest it.
So, I would pull a magic trick up my sleeve. I call it the ‘Poetic UX license’. This is inspired by poetic license, a popular literary tool often used by the legends to deviate from conventional tools of language in certain situations. Take Shakespeare. When he wrote “Friends, Romans, Countrymen, lend me your ears,” he left out the “and” to make it sound better. Or think about “Treasure Island,” where the author used fake pirate talk like “shiver me timbers” to make the story feel more real.
Just like writers can break grammar rules to make their writing stronger with poetic license, designers can break presentation rules to make ideas clearer using a similar, poetic license of design. The goal isn’t to follow rules—it’s to make sure people understand.
Here’s what I mean: Instead of cramming five points into one messy slide (too dense) or spreading them across five slides (too long), why not merge them into three clear points on one slide? It’s like finding the sweet spot between too much and too little.
Think about it this way: most people only remember about 10% of what they see in a presentation. If that’s true, we should make those few takeaways count. Three strong points stick better than five rushed ones.
In this example, you might have the best strategy in the world, but it’s worthless if no one gets it. It’s like having a great joke but messing up the punchline—the delivery matters as much as the content. This isn’t about cutting corners. It’s about making ideas shine through.
Sometimes you have to break the rules to create clarity. And clarity comes from subtraction, not addition.
I will always pick clarity over completeness. And good clarity comes from subtraction, not addition.
The ability to create clarity when there’s no shortage of chaos, opinions, and competing priorities is a rare skill.
In any reasonably competent company, this skill alone will help take you quite far, fairly quickly.
Concretely, this means creating clarity on the main problems,…
— Shreyas Doshi (@shreyas) January 13, 2025
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?