Systems Thinking for Testers
summary
Argues that many testing failures come from treating projects linearly instead of as interacting systems, and shows how to spot root causes by mapping variables, boundaries and feedback loops rather than chasing symptoms. Recommends concrete practices: use mind maps, flowcharts and fishbone diagrams to visualize dependencies, apply 5W1H questions to uncover hidden assumptions, weigh explicit trade-offs (cost vs quality vs time), and consult the tools listed at untools.co.
AI-written summary · about
chapters (4)
- 0:00Introduction
- 1:11Defining systems
- 2:57Applying systems to testing
- 5:28Practical tips and conclusion
related talks
31mHans Borjesson: The Unique Holistic Perspective of the Software Tester
37mTransforming Testing from a Task to a Strategic Mindset
49mThe Secret to Successful Testing
34mHelping Testers Add Value to Agile Projects
01h 48mTutorial - PRAGMATIC TESTING - WHAT TO DO WHEN YOUR WORLD IS MESSY
01mRethinking testing and risk within complex systems
28mYour Testing Strategy is broken - lets fix it!
44mEnhancing your Testing Skills with "Mindset Tools"