Intellectual Frontiers

Twenty-One Blank Field Tools, in the Order the Chapters Introduce Them

Every tool in this book has a blank, reusable version on these pages, in the order the chapters introduce them. Each one starts with a line saying when to reach for it and names the chapter that runs it on a worked example. Fill in one copy per workflow or claim, and keep it next to the decision it informed. The three AI prompts the book introduces are in the prompt library.

  1. Trace Where the Need Changed Meaning Along the Handoff Chain

  2. Ask Which of Five Parties “the Customer” Means

  3. Weigh What Each Function Sees Well and Systematically Misses

  4. Find Which Testing Question Was Actually Answered

  5. Do Not Treat a QA Pass as Proof That Users Can Do the Job

  6. Say How Far a Tester Was From the Person Who Does the Job

  7. Attach an Honest Label to Any UAT Result From a Non-User

  8. State How Strong the Evidence Is Before a Claim Drives a Decision

  9. Put a Product Change on One Page With Its Evidence

  10. Count the Behavior Before Arguing About It

  11. Keep the Pain and Test the Diagnosis in Each Complaint

  12. Observe How the Task Is Really Done

  13. Interview for What People Did

  14. Turn “Easy to Use” Into Things You Can Measure

  15. Rank Workflows by Frequency and Friction to Choose What to Fix First

  16. Check What a Change Does Beyond the One Screen

  17. Put a Number on What a Change Does to One Unit of Work

  18. Split “the User” Into the Kinds of People the Workflow Serves

  19. Get Working Alternatives in Front of Real Users Within Days

  20. Run the Monthly Product Review on What Users Did

  21. Check That No Stand-In Did a User’s Step