So you think a new tool will help? Here are some things to remember
summary
Research claims a set of practical heuristics that ask why do we need this tool, who is it for, and where will it be used, and validates them with 12 heuristics, case studies, and over 3,000 data points (230+ survey participants, 6 industry case studies). A usable framework lives in a GitHub repository under GPL3; concrete stories (Anna, Bill, Cam) show tools often don’t solve root problems and that conversations, context checks, ROI and decommissioning plans decide success.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:27Tool shelfware problem research
- 3:15Initial research questions
- 6:03Heuristics for tool selection
- 9:15Validating heuristics framework
- 12:09Case studies
- 16:49Why tools fail
- 20:21Stakeholder mapping
- 23:08Tool usage context
- 26:16Autonomy in tool design
- 28:24Tool maintenance and ROI
- 31:38Using heuristics effectively
- 33:43Future plans
related talks
25mHeuristics to help you design, build, and choose test tools
36mIf, when and how? - Strategies towards web-based tooling
15mPut On Your Product Hat When Championing an Internal Tool
39mHacking usability
48mHAMMERS AND NAILS
38mFrom Conversation to Software
47mStop Building Useless Software
23mUsing Data to Bridge Product and Engineering Teams