This book is for people handed a request to build a system who want to know what problem they're actually supposed to solve.
When the request already names the thing to build, how do you get back to what needs to change?
Chapter 1 starts with what actually arrives: not a problem, but a solution someone has already chosen.
If you'd rather write down the gap between where things are and where they should be than jump to how to build it, start right here with Chapter 1.
Free sample of *The Art of Defining Problems: What Question Should You Really Be Asking?*: the front matter and Chapter 1, "Turning the Request Back Into a Problem: Writing As-Is, To-Be, and the Gap", as PDF and EPUB. The full book is here:
https://buymeacoffee.com/asopitechia/e/581511