The art of asking questions
summary
Concrete guidance on when and how to ask and file bugs: self‑contained written questions with screenshots or short videos, use Slack/Confluence/Jira pragmatically, and apply the Quality Delta to decide which bugs to report. Expect templates (inverted‑pyramid headline + details), soft tactics like Socratic prompts to reveal assumptions, a triage rule to fix or close quickly, and war stories (a costly template migration and a Silk Test snapshot example) showing what worked and what didn’t.
AI-written summary · about
chapters (18)
- 0:00Art of asking questions
- 1:07From reviewer to tester
- 4:18Switching to testing
- 7:09Cost of asking questions
- 10:07Oral vs written questions
- 13:39Who to ask and when
- 15:27Developer communication
- 18:16Structured questions
- 20:42Socratic questioning
- 22:07Mental model of software
- 23:54Arguments for improvement
- 24:58Uneven developer quality
- 26:44Reporting bugs
- 29:14Quality Delta
- 33:49Navigating quality Delta
- 37:46Picking battles
- 38:51Helicopter perspective
- 39:13Q&A
related talks
57mThe art of asking questions
32mThe Art of Asking Questions
32mThe Art of Asking Questions
30mReporting Bugs: Errors Made and Lessons Learned
08mTalk to me! The art of reporting a bug (and handling the feedback)
46mBugs
05mBug Bashing Your Docs
12mBuilding Quality in Legacy Systems - The Art of Asking Questions
