Unfinished is not about doing less, shipping sloppy work, or pretending quality does not matter. It is about the harder professional truth: good work can still disappear if it enters a room it was never built to survive.
Before We Begin
This book is for the person I was in year one.
Not year one of design, or product management, or strategy, or whatever discipline brought you here. Year one of working inside a complex organisation and discovering, quietly, without anyone naming it, that the skills you had been trained on were not quite the skills the job required.
You were not wrong about the skills. The design was good. The research was solid. The analysis was thorough. The work was, by every measure you had been given, exactly what it was supposed to be.
And something kept not working.
Not always. Not every project. But often enough that the pattern became impossible to ignore. Work that you knew was good, work your peers confirmed was good, work your manager praised, work that passed every internal review, reaching a room you had never been in and not surviving it.
If you have felt that specific exhaustion of doing everything right and watching it not matter, this book was written for you.
The Room You Were Never In
I once watched twelve months of work disappear in an afternoon.
Not because the work was bad. Everyone said it was good. My manager said so, my peers said so, the people who had been close to it from the beginning said so. The prototype was thorough. The research behind it was solid. The team had given it everything they had.
And then it reached a room none of us had ever been in. A room with one person in it. A person none of us had ever studied, never spoken to, never tried to understand. A person whose name appeared in the brief as the final approver but who had been, in every practical sense, completely invisible to us for twelve months.
The VP rejected it.
Not with a long explanation. Not with a list of things to fix. Just: no. This is not what we need.
The work disappeared. The project was shelved. The team went back to their desks. Within a few weeks everyone had moved on to something else, carrying the weight of twelve months quietly, without anyone naming what had actually gone wrong.
I was junior enough to watch without being responsible. Senior enough to understand that something had failed that had nothing to do with the quality of the work.
We knew everything about what citizens needed from an intranet. We knew nothing about what the VP needed from us.
What The Work Had To Survive
For a long time I did what most people do. I worked harder. I made things more thorough. I added more research, more detail, more evidence. I refined. I polished. I told myself that if the work was good enough, complete enough, defensible enough, it would survive.
It did not always survive.
The problem was not the work. The problem was that I had been trained to design for one kind of user, the person who would use the product, and never taught to study the system the product had to survive before it could reach that person.
The decision-maker was a user I had never researched. The organisation was a context I had never mapped. The question of what version of the work could realistically enter the room had never appeared in any course I had taken, any book I had read, any mentor I had learned from.
The Four Questions
This book gives you four questions to ask before you design, write, recommend, or build anything. They sit in the space between the craft of doing the work and the room the work has to survive.
- Who actually decides? Not who commissioned the work. Who has the real power to say yes or no when the moment that matters arrives?
- What do they actually need right now? Not what the brief says. What pressure is the decision-maker under, and what would make the work feel useful, credible, and safe enough to back today?
- What can this system actually absorb? Not what it should be able to receive. What can the organisation genuinely take in, given its history, workload, fears, and current capacity for change?
- What is the smallest version that can enter the room? Not the ideal solution. The earliest useful version that can survive the real situation and begin a real conversation.
These questions will not tell you everything. They will tell you enough to stop building blind.
Stay Unfinished
Stay Unfinished is not permission to lower the bar. It is the recognition that the system your work has to survive is alive. It changes, responds, grows, resists, and keeps becoming something slightly different from what it was the last time you looked.
The practitioner who stays unfinished is not the one who never completes anything. They are the one who understands that completion is not the goal. Landing is.
Enjoyed the sample? Get the book on Amazon → Buy Unfinished