Beauty of second degree probes
Shreyas Prakash
I’ve been noticing this pattern again and again—just about enough to make this pattern a heuristic for my own understanding. “No lie can overcome a second degree probe”
If you probe a lie, just about enough, it reveals itself in due course. At work, I see this all the time. When a statement is just made, in a matter-of-fact way in which it assumes everyone already knows it, and when you ask “why it’s so?”, often, there is an explanation that’s provided to this statement. This is the first line of defense for a lie (or an assumption), and it might most likely exist.
But if you then question the explanation as well, and ask “why is this explanation this way, and why not X?”, you start seeing some cognitive dissonance in action. There apparently is not explanation to the explanation!
Some examples on top of my mind:
For a statement, such as “We need to restructure the team for better efficiency.”
First probe: “Why will this structure be more efficient?”
Response: “Because it reduces communication overhead.”
Second probe: “How exactly does it reduce overhead, and have we measured current communication costs?”
Response: …
Reveals no analysis was done, reveals it’s just a knee-jerk reaction to a directive from a C-level executive.
“Our customers prefer the premium version.”
First probe: “What data shows this preference?”
Response: “Higher conversion rates on the premium product page.”
Second probe: “But isn’t the premium page the default landing page, and how do we know preference versus just path of least resistance?”
Response: …
One might ask, well, it makes sense to do second-degree probes, but why not third-degree or fourth-degree probes?
The short answer here is that one could probe to various deeper levels, but they often don’t pass the test of succinctness, which is highly needed in meetings. You want to question the assumptions deeply, without being too intrusive.
It’s the right level of depth to know if there are any assumptions worth investigating further (perhaps not on the same meeting call, as you don’t want to be dismissed as a modern-day braggart Socrates here)
The moment I realised that this is a good heuristic, I started noticing this pattern everywhere (not just at work). Let’s take even investment advice:
Statement: “Real estate always appreciates over time.”
First probe: “What’s the historical data on that?”
Response: “Look at housing prices over the last 50 years.”
Second probe: “But what about Japan from 1990-2010, or specific regions during economic downturns, and how do we account for survivorship bias in the data?”
Response: “Umm…well…”
The second-degree probe is not a magic wand to shatter inherent assumptions, what it does tell us is that we don’t question our assumptions deeply enough. Sometimes it’s just a castle of glass, waiting for the right question to act as a pickaxe to shatter this whole foundation based on a false premise.
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?