Was it worth it?

It was a rather good party. Meat platters, fish platters, cheese platters. Decent wine, good beer, posh tea, and the lovely glow of a job done. The product had shipped – on time, a tad over budget, at a quality everyone could live with – and after nine long months the team had earned the right to enjoy themselves. So they did.

The trouble arrived a few weeks later, in a spreadsheet. The finance team, tidying up the numbers, went looking for one figure in particular and came up empty: the value that nine-month project had actually realised. Not the cost – the cost was easy. The value. The thing the whole endeavour had been for. It simply wasn't there to be found.

This is one of the most common traps in any kind of work. We confuse the shipping of a thing with the arrival of the value it was meant to bring – and they are not the same event, often not even close. Plenty of work gets shipped, on time and on budget and meeting every reporting standard going, and the value it was supposed to produce is nowhere to be found. The launch event that was tremendous fun and generated not one sales lead. The marketing campaign that drove just three people into the funnel. The software platform built to make real money that sat unused, gathering operational costs and then dismantled the following year, at more expense. The book that took two years of evenings and reached two people.

And here's the part I want to be careful about. None of that is the real mistake. Ideas are bets. No idea arrives fully formed with a guaranteed return stapled to it; you invest your money and your finite time, energy and attention, and sometimes the value shows up and sometimes it doesn't.

That's not new news – it's the nature of doing anything worthwhile. The actual mistake, the one that costs the most, came a few weeks after the party. Because once the celebrating was done and finance had come up empty, the team did something remarkable in its very ordinariness: they picked up the next idea and set off down exactly the same road to shipping it. Nobody stopped. Nobody turned around and asked the one question that mattered – was it worth it? – and, more importantly, nobody stayed long enough to learn from the answer.

That question is likely one of the most powerful there is, and in my experience it is almost never asked – not before the work starts, not after it ends. Was it worth doing? Not whether it shipped on time. Not whether the launch went smoothly, or the workshop got good scores, or the party was money well spent. Whether the value the work was actually for turned up – and, if it didn't, what that has to teach us.

None of which is a business problem, incidentally, which is where most writing on this goes wrong. It's a human one, and it belongs as much to the novelist as to the finance team. The writer Henry James, thinking about how to judge a work of art, proposed three useful questions, and they are very nearly perfect: What was the artist trying to achieve? Did they achieve it? Was it worth achieving?

Ask those of a painting or a poem and they hold. Ask them of a marketing campaign, a change programme, a two-year novel, a solo maker's first product, and they work just as well – because underneath, all of it is the same act. You had an idea, you spent something precious to make it real, and at some point it's worth knowing, honestly, whether the spending paid off.

James's questions almost never get asked, and it's rarely carelessness. It's often that nobody was super clear, at the start, about what value they were actually chasing – so there's no honest way to judge, at the end, whether it arrived. Because "value" isn't one thing. Sometimes what you're after is money: did it sell. Sometimes it's simply that a thing now works that didn't work before. And sometimes – this one trips everyone up – the entire point of the work was to learn something: a test, a pilot, a first novel, a small experiment. In which case "did it succeed" is the wrong question altogether. An experiment that comes back with a clean, useful no and changes what you do next is worth ten that end in a shrug and get quickly filed. Designing a experiment, with the goal of learning, as though it were a delivery of revenue, then judge it as a delivery, and you'll call it a flop when it was actually a gift. Be honest at the outset about which kind of value you're chasing, and the judging at the end becomes more realistic.

The reason we skip the judging is partly human, and slightly unsettling. The work is done, the budget is spent, the next thing arrives, everyone moves on, likely because reflecting on the work may make us realise we've spent a lot of our money, and finite resources, on something that didn't work – and that hurts. People feel that. We often don't want to face that reality. To know, that maybe, it wasn't really worth it. It's easier just to keep moving ahead, potential knowing, deep down, that this year might be exactly like the last. But asking that questions, was it worth it, as painful as it may be to lean into, actually prevents, if we learn from what we find, a repeat of the same thing again this year.

And the fix is remarkably cheap. It's the willingness to ask three questions before you begin – what am I actually trying to achieve here, which kind of value am I chasing, and, most bravely, is this worth doing at all – and three more when it's done: did the value I was after actually arrive, what did I genuinely learn, and would I do this again, or never again? That's it. No framework, no software, no away-day. Just the discipline of closing the loop that almost everyone leaves open.

Sometimes the honest answer will be no – it wasn't worth it. That answer is not the mistake. Not learning from it is. Reflection isn't an event you schedule once and forget – a post-mortem, a lessons-learned slide deck filed for audit purposes and never reopened or used. It's an ability, and like any ability it compounds: the people and the teams who do it well abandon the doomed ideas sooner, repeat the good patterns on purpose, and build judgement across the years rather than merely stacking up more activity. They get wiser, not just busier.

Which brings me back, interestingly, to the platters. There was nothing wrong with the party – celebrating shipped work is a fine and human thing. The mistake was everything that didn't happen after it: the turning-around, the honest question, the minutes of learning that would have made the next nine months worth more than the last.

Whether you're running a company or writing a book alone at a kitchen table, the work that compounds into something isn't the work that ships the most. It's the work that, every so often, stops long enough to ask whether it was worth it – and is brave enough to believe the answer.