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. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
  2. How I started building softwares with AI agents being non technicalagentic-engineering
  3. Legible and illegible tasks in organisationsproduct
  4. L2 Fat marker sketchesdesign
  5. Writing as moats for humanswriting
  6. Beauty of second degree probesdecision-making
  7. Read raw transcriptsknowledge
  8. Boundary objects as the new prototypesprototyping
  9. One way door decisionsproduct
  10. Finished softwares should existproduct
  11. Essay Quality Rankerobsidian
  12. Export LLM conversations as snippetsbrowser-extension
  13. Flipping questions on its headinterviewing
  14. Vibe writing maximswriting
  15. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  16. How I build greenfield apps with AI-assisted codingai-coding
  17. We have been scammed by the Gaussian distribution clubmathematics
  18. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  19. I was wrong about optimal stoppingmathematics
  20. Thinking like a ship
  21. Hyperpersonalised N=1 learningeducation
  22. New mediums for humans to complement superintelligenceai-coding
  23. Maxims for AI assisted codingai-coding
  24. Personal Website Starter Kitai-coding
  25. Virtual bookshelvesaesthetics
  26. It's computational and AI everythingai-coding
  27. Public gardens, secret routesdigital-garden
  28. Git way of learning to codeai-coding
  29. Kaomoji generatorsoftware
  30. Copy, Paste and Citecuriosities
  31. Style Transfer in AI writingai-coding
  32. Understanding codebases without using codeai-coding
  33. Vibe coding with Cursorai-coding
  34. Virtuoso Guide for Personal Memory Systemsmemory
  35. Writing in Future Pastwriting
  36. Publish Originally, Syndicate Elsewhereblogging
  37. Poetic License of Designdesign
  38. Idea in the shower, testing before breakfastsoftware
  39. Technology and regulation have a dance of ice and firetechnology
  40. How I ship "stuff"software
  41. Weekly TODO List on CLIcli
  42. Writing is thinkingwriting
  43. Song of Shapes, Words and Pathscreativity
  44. How do we absorb ideas better?knowledge
  45. Read writers who operatewriting
  46. Brew your ideas lazilyideas
  47. Vibescreativity
  48. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  49. Compound Interest of Private Notesknowledge
  50. Conceptual Compression for LLMsai-coding
  51. Meta-analysis for contradictory research findingsdigital-health
  52. Beauty of Zettelswriting
  53. Proof of workproduct
  54. Gauging previous work of new joinees to the teamleadership
  55. Task management for product managersproduct
  56. Stitching React and Rails togetherai-coding
  57. Exploring "smart connections" for note takingknowledge
  58. Deploying Home Cooked Apps with Railssoftware
  59. Self Marketing
  60. Repetitive Copypromptingwriting
  61. Questions to ask every decadejournalling
  62. Balancing work, time and focusproductivity
  63. Hyperlinks are like cashew nutswriting
  64. Brand treatments, Design Systems, Vibesdesign
  65. How to spot human writing on the internet?writing
  66. Can a thought be an algorithm?product
  67. Opportunity Harvestingcareers
  68. How does AI affect UI?design
  69. Everything is a prioritisation problemproduct-management
  70. Nowlifestyle
  71. How I do product roastsproduct
  72. The Modern Startup Stacksoftware
  73. In-person vision transmissionproduct
  74. How might we help children invent for social good?social-design
  75. The meeting before the meetingmeetings
  76. Design that's so bad it's actually gooddesign
  77. Breaking the fourth wall of an interviewinterviewing
  78. Obsessing over personal websitessoftware
  79. Convert v0.dev React to Rails ViewComponentsrails
  80. English is the hot new programming languagesoftware
  81. Better way to think about conflictsconflict-management
  82. The role of taste in building productsdesign
  83. World's most ancient public health problemsoftware
  84. Dear enterprises, we're tired of your subscriptionssoftware
  85. Products need not be user centereddesign
  86. Pluginisation of Modern Softwaredesign
  87. Let's make every work 'strategic'consulting
  88. Making Nielsen's heuristics more digestibledesign
  89. Startups are a fertile ground for risk takingentrepreneurship
  90. Insights are not just a salad of factsdesign
  91. Minimum Lovable Productproduct
  92. Methods are lifejackets not straight jacketsmethodology
  93. How to arrive at on-brand colours?design
  94. Minto principle for writing memoswriting
  95. Importance of Whytask-management
  96. Quality Ideas Trump Executionsoftware
  97. How to hire a personal doctor
  98. Why I prefer indie softwareslifestyle
  99. Use code only if no code failscode
  100. Personal Observation Techniquesdesign
  101. Design is a confusing worddesign
  102. A Primer to Service Design Blueprintsdesign
  103. Rapid Journey Prototypingdesign
  104. Directory Structure Visualizercli
  105. AI git commitscli
  106. Do's and Don'ts of User Researchdesign
  107. Design Manifestodesign
  108. Complex project management for productproducts
  109. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  110. Pedagogy of the Uncharted — What for, and Where to?education
  111. Future of Ageing with Mehdi Yacoubiinterviewing
  112. Future of Equity with Ludovick Petersinterviewing
  113. Future of Mental Health with Kavya Raointerviewing
  114. Future of Tacit knowledge with Celeste Volpiinterviewing
  115. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  116. Future of unschooling with Che Vanniinterviewing
  117. Future of work with Laetitia Vitaudinterviewing
  118. How might we prevent acquired infections in hospitals?digital-health
  119. The soul searching yearsentrepreneurship
  120. Design education amidst social tribulationsdesign
  121. How might we assist deafblind runners to navigate?social-design