Beauty of second degree probes

Shreyas Prakash headshot

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

  1. How I started building softwares with AI agents being non technical

2025

  1. Legible and illegible tasks in organisations
  2. L2 Fat marker sketches
  3. Writing as moats for humans
  4. Beauty of second degree probes
  5. Read raw transcripts
  6. Boundary objects as the new prototypes
  7. One way door decisions
  8. Finished softwares should exist
  9. Essay Quality Ranker
  10. Export LLM conversations as snippets
  11. Flipping questions on its head
  12. Vibe writing maxims
  13. How I blog with Obsidian, Cloudflare, AstroJS, Github
  14. How I build greenfield apps with AI-assisted coding
  15. We have been scammed by the Gaussian distribution club
  16. Classify incentive problems into stag hunts, and prisoners dilemmas
  17. I was wrong about optimal stopping
  18. Thinking like a ship
  19. Hyperpersonalised N=1 learning
  20. New mediums for humans to complement superintelligence
  21. Maxims for AI assisted coding
  22. Personal Website Starter Kit
  23. Virtual bookshelves
  24. It's computational everything
  25. Public gardens, secret routes
  26. Git way of learning to code
  27. Kaomoji generator
  28. Style Transfer in AI writing
  29. Copy, Paste and Cite
  30. Understanding codebases without using code
  31. Vibe coding with Cursor
  32. Virtuoso Guide for Personal Memory Systems
  33. Writing in Future Past
  34. Publish Originally, Syndicate Elsewhere
  35. Poetic License of Design
  36. Idea in the shower, testing before breakfast
  37. Technology and regulation have a dance of ice and fire
  38. How I ship "stuff"
  39. Weekly TODO List on CLI
  40. Writing is thinking
  41. Song of Shapes, Words and Paths
  42. How do we absorb ideas better?

2024

  1. Read writers who operate
  2. Brew your ideas lazily
  3. Vibes
  4. Trees, Branches, Twigs and Leaves — Mental Models for Writing
  5. Compound Interest of Private Notes
  6. Conceptual Compression for LLMs
  7. Meta-analysis for contradictory research findings
  8. Beauty of Zettels
  9. Proof of work
  10. Gauging previous work of new joinees to the team
  11. Task management for product managers
  12. Stitching React and Rails together
  13. Exploring "smart connections" for note taking
  14. Deploying Home Cooked Apps with Rails
  15. Self Marketing
  16. Repetitive Copyprompting
  17. Questions to ask every decade
  18. Balancing work, time and focus
  19. Hyperlinks are like cashew nuts
  20. Brand treatments, Design Systems, Vibes
  21. How to spot human writing on the internet?
  22. Can a thought be an algorithm?
  23. Opportunity Harvesting
  24. How does AI affect UI?
  25. Everything is a prioritisation problem
  26. Now
  27. How I do product roasts
  28. The Modern Startup Stack
  29. In-person vision transmission
  30. How might we help children invent for social good?
  31. The meeting before the meeting
  32. Design that's so bad it's actually good
  33. Breaking the fourth wall of an interview
  34. Obsessing over personal websites
  35. Convert v0.dev React to Rails ViewComponents
  36. English is the hot new programming language
  37. Better way to think about conflicts
  38. The role of taste in building products
  39. World's most ancient public health problem
  40. Dear enterprises, we're tired of your subscriptions
  41. Products need not be user centered
  42. Pluginisation of Modern Software
  43. Let's make every work 'strategic'
  44. Making Nielsen's heuristics more digestible
  45. Startups are a fertile ground for risk taking
  46. Insights are not just a salad of facts
  47. Minimum Lovable Product

2023

  1. Methods are lifejackets not straight jackets
  2. How to arrive at on-brand colours?
  3. Minto principle for writing memos
  4. Importance of Why
  5. Quality Ideas Trump Execution
  6. How to hire a personal doctor
  7. Why I prefer indie softwares
  8. Use code only if no code fails
  9. Personal Observation Techniques
  10. Design is a confusing word
  11. A Primer to Service Design Blueprints
  12. Rapid Journey Prototyping
  13. Directory Structure Visualizer
  14. AI git commits
  15. Do's and Don'ts of User Research
  16. Design Manifesto
  17. Complex project management for product

2022

  1. How might we enable patients and caregivers to overcome preventable health conditions?
  2. Pedagogy of the Uncharted — What for, and Where to?

2020

  1. Future of Ageing with Mehdi Yacoubi
  2. Future of Equity with Ludovick Peters
  3. Future of Tacit knowledge with Celeste Volpi
  4. Future of Mental Health with Kavya Rao
  5. Future of Rural Innovation with Thabiso Blak Mashaba
  6. Future of unschooling with Che Vanni
  7. Future of work with Laetitia Vitaud
  8. How might we prevent acquired infections in hospitals?

2019

  1. The soul searching years
  2. Design education amidst social tribulations
  3. How might we assist deafblind runners to navigate?