You Are Not the User

Twenty of the field tools in the online companion at intellectualfrontiers.com now offer their tables as spreadsheet downloads, among them the Who Is the User worksheet, the User Evidence Ladder, the UAT Distance Scale, the Frequency-Friction Matrix and the Product Evidence Brief. Fill them in with your team in a shared sheet instead of retyping a printed table. The tools on screen and in the printed appendix are unchanged.

The twenty-one field tools and three AI prompts left the printed book and are now 27 pages in the online companion at intellectualfrontiers.com, where you can use them with your team. Use the "Who Is the User" worksheet to find out who your user really is. Use the User Evidence Ladder to grade how strong each claim about users is, the UAT Distance Scale to see how far a test was from real use, and the QA versus UAT matrix to stop mistaking one for the other. The complaint-to-hypothesis converter turns a complaint into something you can test. The Frequency-Friction Matrix weighs a workflow by how often it happens and how much friction it carries. The Show-Me interview guide gets people to demonstrate their work instead of describing it. Three prompts help you design AI-assisted acceptance testing, draft alternative prototypes, and turn observations into hypotheses. The printed book keeps a short appendix that says where each tool went.

Competent, caring people can build the wrong software when the information reaching them has passed through a chain of handoffs. A nurse says, "I need to know which patients need my attention," and support, customer success, product, design, engineering and QA each do competent work on that sentence. Months later the nurse gets a status column and says, "This doesn't help me decide who to call." Nobody failed; the design is the problem. This fieldbook treats every internal function as a sensor that reports evidence about users and never a stand-in that speaks as the user, and gives teams the tools to tell the difference. You learn to label every claim about users by how strong the evidence is and how close it came to real use, tell QA from user acceptance testing, turn complaints into testable hypotheses, watch work instead of collecting opinions about it, and weigh a workflow by frequency, friction, economics and clinical consequence. It is for product, design and engineering teams that build B2B and healthcare software.