Flipping questions on its head

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