Flipping questions on its head

02 May 2025

Shreyas Prakash headshot

Shreyas Prakash

A cardinal sin when it comes to design research is when some one asks a leading question. If you’re interviewing a consumer of Pepsodent toothpaste, you should almost never, ever, ever, ask “How much do you enjoy using Pepsodent toothpaste?”. That’s a leading question, and the answers you might get from this question are usually loaded with confirmation bias. It would be more along the lines of ‘what they think you might want to hear’, rather than ‘what they actually think/feel/do’.

This guiding principle of interviewing without asking leading questions applies to various facets: market research for F&B brands, company interviews, philosophy debates, and even some negotiations. The thumb rule here is to start initiation and ask more generic open-ended questions such as “How does your day in your life look?”, and then gradually narrow down some topics based on what the end-user wants to say/express.

More recently, I’ve created a variation of the the ‘leading question’, and flipped it on it’s head. I call it as the ‘non leading leading question’. I can’t think of a better term without convoluting the crux of what this does: Let me illustrate this 4D chess move with an example.

Let’s say I want that there is a restructuring in your company, and you are being moved to a new team and a new project. Your expectation is that the new team/project is much more ambitious/chaotic, highly charged and even (stressful) at times. (This is counter-intuitive and not what everyone would want). But you are hell-bent on wanting to work in such an environment, and the mythical “work-life” balance is not something you are considering it as much. How do you then gauge if this new team/project is ambitious/chaotic through a series of questions?

What I would do in such situations is to pull up the “non leading leading question” card.

I would ask — “Would there be good work life balance in the new team?”. The natural expectation for the manager here would be to say that there is good work-life balance. It’s not against the grain, and it’s not counter-intuitive. But by doing so, you reveal the true nature of the new team. The inverse of the inverse question has helped you reveal how this team works, in other words, the question has achieved it’s purpose.

The manager thinks this is a leading question (as they think you’re inclined towards changing your role into a new team where there is better work-life balance, but you’re not revealing your cards entirely and playing a bluff here)

If for the same question, “Would there be good work life balance in the new team?”, the manager says, “Actually, Shreyas, you know what, this is a mission-critical project, and a lot of dependencies to get the right outcome.” Even in this case, this question has achieved it’s purpose. You are now being posted into a more ambitious, growth-oriented team hungry for shipping fast, and moving at break-neck speed. This is what you want!

On the contrary, if I had asked — “Would there be too much stress in the new team?”, there might be a risk of getting a lot more smoke signals which make the response unclear.

This was one specific example, but there could be more situations where such non-leading leading questions can be leveraged.

I’d used this in a more recent interview I’d taken. To one of the candidates, I’d asked — ‘How do you ensure that you do ethnographic studies for all your projects?’ (what I expect here is them calling out the bluff, that it’s impossible to do extensive user research for all projects as in reality you’re dealing with tradeoffs of time/effort/complexity etc). Again, the non-leading leading question acts as an inverse-of-an-inverse.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Life lessons and hot takes from my 30slifestyle
  2. Building a skill for coherent science illustrations
  3. My agentic engineering workflow (step by step)agentic-coding
  4. Every darn thing is a kekulean loop if you notice itdesign-thinking
  5. Hammock driven developmentagentic-coding
  6. Peculiar ways number three fits into our funny little brainsmental-models
  7. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  8. How I write essays in 2026writing
  9. Authority in the guise of evidencecritical-rationalism
  10. Map is not the territoryphilosophy
  11. Self hypnosis as a manifestation ritualmeditation
  12. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  13. How I prepare for tough negotiations nowadaysnegotiation
  14. When should we steelthread somethingproduct-development
  15. Learning and re-learning my mother tongue in Malayalam
  16. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct
  17. Healthy conflict in teams have a tipping pointteam-building
  18. How I deslopify AI writingwriting
  19. How I started building softwares with AI agents being non technicalagentic-coding
  20. Read raw transcriptswriting
  21. Legible and illegible tasks in organisationsproduct
  22. L2 Fat marker sketchesdesign
  23. Writing as moats for humanswriting
  24. Beauty of second degree probesdecision-making
  25. Boundary objects as the new prototypesprototyping
  26. One way door decisionsproduct
  27. Finished softwares should existproduct
  28. How I periodically rank my rough draftsobsidian
  29. Flipping questions on its headinterviewing
  30. Vibe writing maximswriting
  31. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  32. How I build greenfield apps with AI-assisted codingagentic-coding
  33. We have been scammed by the Gaussian distribution clubmathematics
  34. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  35. I was wrong about optimal stoppingmathematics
  36. Thinking like a shipmental-models
  37. Hyperpersonalised N=1 learningeducation
  38. New mediums for humans to complement superintelligenceagentic-coding
  39. Maxims for AI assisted codingagentic-coding
  40. Virtual bookshelvesaesthetics
  41. It's computational everythingtrends
  42. Public gardens, secret routesdigital-garden
  43. Git way of learning to codeagentic-coding
  44. Style Transfer in AI writingagentic-coding
  45. Understanding codebases without using codeagentic-coding
  46. Vibe coding with Cursoragentic-coding
  47. Virtuoso Guide for Personal Memory Systemsmemory
  48. Writing in Future Pastwriting
  49. Publish Originally, Syndicate Elsewhereblogging
  50. Poetic License of Designdesign
  51. Idea in the shower, testing before breakfastsoftware
  52. Technology and regulation have a dance of ice and firetechnology
  53. How I ship "stuff"software
  54. Writing is thinkingwriting
  55. Song of Shapes, Words and Pathscreativity
  56. How do we absorb ideas better?knowledge
  57. Read writers who operatewriting
  58. Brew your ideas lazilyideas
  59. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  60. Compound Interest of Private Noteswriting
  61. Conceptual Compression for LLMsagentic-coding
  62. Meta-analysis for contradictory research findingsdigital-health
  63. Proof of workproduct
  64. Gauging previous work of new joinees to the teamleadership
  65. Task management for product managersproduct
  66. Beauty of Zettelswriting
  67. Stitching React and Rails togetheragentic-coding
  68. Exploring "smart connections" for note takingwriting
  69. Deploying Home Cooked Apps with Railssoftware
  70. Repetitive Copypromptingwriting
  71. Questions to ask every decadejournalling
  72. Balancing work, time and focusproductivity
  73. Hyperlinks are like cashew nutswriting
  74. Brand treatments, Design Systems, Vibesdesign
  75. How to spot human writing on the internetwriting
  76. Can a thought be an algorithm?product
  77. Opportunity Harvestingcareers
  78. How does AI affect UI?design
  79. Everything is a prioritisation problemproduct
  80. How I do product roastsproduct
  81. The Modern Startup Stacksoftware
  82. In-person vision transmissionproduct
  83. How might we help children invent for social good?social-design
  84. The meeting before the meetingmeetings
  85. Design that's so bad it's actually gooddesign
  86. Lessons learnt interview prepping for product rolesinterviewing
  87. Obsessing over personal websitessoftware
  88. English is the hot new programming languagesoftware
  89. Better way to think about conflictsconflict-management
  90. The role of taste in building productsdesign
  91. Dear enterprises, we're tired of your subscriptionssoftware
  92. Products need not be user centereddesign
  93. World's most ancient public health problemsoftware
  94. Pluginisation of Modern Softwaredesign
  95. Let's make every work 'strategic'consulting
  96. Making Nielsen's heuristics more digestibledesign
  97. Startups are a fertile ground for risk takingentrepreneurship
  98. Insights are not just a salad of factsdesign
  99. Minimum Lovable Productproduct
  100. Methods are lifejackets not straight jacketsmethodology
  101. How to arrive at on-brand colours?design
  102. Minto principle for writing memoswriting
  103. Importance of Whytask-management
  104. Quality Ideas Trump Executionsoftware
  105. Why I prefer indie softwareslifestyle
  106. Use code only if no code failscode
  107. Self Marketing
  108. Personal Observation Techniquesdesign
  109. Design is a confusing worddesign
  110. A Primer to Service Design Blueprintsdesign
  111. Rapid Journey Prototypingdesign
  112. Visualise detailed file structures on CLIcli
  113. Do's and Don'ts of User Researchdesign
  114. Design Manifestodesign
  115. Complex project management for productproducts
  116. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  117. Pedagogy of the Uncharted — What for, and Where to?education
  118. Future of Ageing with Mehdi Yacoubiinterviewing
  119. Future of Tacit knowledge with Celeste Volpiinterviewing
  120. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  121. Future of Equity with Ludovick Petersinterviewing
  122. Future of work with Laetitia Vitaudinterviewing
  123. Future of Mental Health with Kavya Raointerviewing
  124. Future of unschooling with Che Vanniinterviewing
  125. How might we prevent acquired infections in hospitals?digital-health
  126. The why to endure any howentrepreneurship
  127. Design education amidst social tribulationsdesign
  128. How might we assist deafblind runners to navigate?social-design