Stop Celebrating Decimals

You are at 0.4 and there is a slide about it.

Somebody built the chart. The bar moved from the last one. The room claps, and it should, because everyone in it has been working hard, and the number did in fact move.

Nine months later the thing still has not shipped.

The symptoms: what being stuck at 0.4 actually looks like

Some of these you will recognize immediately.

The dashboard is full of progress and nothing has shipped. Every update reports movement. Percent complete, phases entered, milestones passed. None of it is a thing a person outside the building could pick up and use.

Someone has been “almost there” for three quarters. Not lying, not slacking. Genuinely at 0.8 for a very long time, and 0.8 is where the work stopped being interesting.

The team celebrates a milestone nobody outside the room can name. The thing that got celebrated was the internal readiness review that precedes the actual launch, and it got a channel post with emoji on it.

And then the other flavor, which looks nothing like the first three and is the same illness. Someone talks about their practice more than their output. The morning routine, the system, the tooling, the setup. Ask what came out of it last month and the answer takes a while to arrive.

I have been both of these people. The second one is more comfortable and lasts longer, which is the problem with it.

The assessment: questions that separate movement from progress

Four questions. None of them are hostile, only specific enough to be hard to slide past.

What was true in January that is not true now, stated in a sentence a stranger could verify? Not “we made significant progress on the platform.” Something closer to “three customers use it and did not before.” If you cannot produce that sentence, the decimal is measuring your activity rather than the world.

Has this crossed from zero to one for anyone who is not you? Internal progress is real progress, and it is also the easiest kind to manufacture. The test is whether anything left the building.

What would you have to stop doing if the number stopped moving entirely? If the honest answer is nothing, then the number is decorative and everyone has known that for a while.

Are you describing the work or doing it? This one catches the process-romance version. There is a ratio between time spent narrating your practice and time spent executing it, and most people have never measured theirs.

The diagnosis: two ways to lose contact with the outcome

Both root causes look like diligence, and both are errors about the same quantity: how much weight the finish is carrying. One puts too little on it and spreads the payoff across the middle. The other takes the finish off the scale entirely. Most people are somewhere on that line rather than in one of the two boxes, and locating yourself on it is more useful than picking a diagnosis.

The first is metric worship, and its mechanism is that it pays you in advance. If 0.3 came with a slide and 0.5 came with applause and 0.7 came with a post in the channel, then by the time you reach the last stretch the reward has already been collected. That last stretch is the part with no novelty, the tedious integration, the edge cases, the documentation, the thing nobody wants. You arrive at it having already been paid, which is why the end of a project so often feels like working for free. People blame their discipline for that. It is an accounting problem. The same swap shows up when a team adopts someone else’s method and the method starts standing in for the judgment.

A decimal is a position report. It tells you where you are, which is useful, and it says nothing about whether you will arrive.

Worth saying what this looks like when it is going fine, because two failure modes in a row will convince anyone they are sick. The healthy version is unremarkable. You know what you are trying to finish. You can say roughly where it stands without any feeling attached to the number. You are mildly bored by parts of it. Things finish at a rate that would not impress anyone and does add up over a year. If that is roughly your week, you do not have a problem, you have a job you are doing.

The second is process romance, and it runs the same swap in the opposite direction. Here the work becomes a story you tell about yourself. You are a person who gets up at five. You are someone who does the reps. The practice stops being something you do and becomes something you are, and once that conversion happens the practice no longer has to produce anything, because the feeling of working is already doing the job the finished work was supposed to do.

There is a deeper reason it fails, and it took me a while to see it. Work aimed at a real object is corrected by that object. The joint does not fit, the customer does not renew, the test goes red, and you find out you were wrong about something. Work aimed at your own experience of working has nothing correcting it, so it drifts toward whatever feels best, which is how a practice becomes pleasant and useless at the same time.

This is the one that catches serious people, and I want to be careful here because the advice that produces it is mostly good advice. Loving the work beats hating it. Showing up daily beats waiting for inspiration. I have written the trust-the-work version myself, and I would write most of it again.

The correction is narrow. ponos is the Greek word for toil, the effort a thing costs you, and the Greeks treated it as a price you pay instead of a product you accumulate. When the price becomes the product you have started collecting toil, and a person collecting toil will pick the harder path even when a shorter one is available, because the difficulty is what they are actually buying.

Underneath both traps sits the same substitution. A story replaced the outcome. In one case the story is about momentum and in the other it is about character, and in both the thing itself quietly stopped being the point.

The treatment: five moves, and the distinction underneath them

Before the moves, the distinction, because without it these five are productivity tips with no spine.

The Stoics separated what is up to you from what is not, and they built the whole system on that line. prohairesis is the faculty of choice, the part that is genuinely yours: what you attend to, what you attempt, whether you sit down today. The outcome sits on the other side of the line. Whether the launch lands, whether the market is in the mood, whether the reviewer had a bad morning.

People misread this as permission. It is the opposite. Once the outcome is off your ledger, the effort is fully on it, and you lose every excuse that depends on circumstances. You do not get to say the quarter was hard. You get to say whether you showed up, and that answer is unambiguous and usually uncomfortable.

Define the one before you start. Write the sentence a stranger could check, and write it on day one, before 0.6 forces the question. If you cannot write it, you are not at 0.4, you are at zero with a lot of activity attached.

Plenty of work has no natural ending, and this is where most advice like mine quietly stops applying. A product is never finished. Neither is a skill, a team, or a piece of writing you could always improve. For that kind of work the move is to define a shippable increment instead of a finish: the smallest version that leaves the building and changes something for someone. Then that increment is your one, and the same rules apply to it.

Report the decimal without celebrating it. Say where you are the way you would read a fuel gauge. Position reports are useful, frequent, and unceremonious. The applause waits for the finish, and it waits every time, including when the finish is late.

Keep the practice boring on purpose. Resist the urge to make it into a system with a name. hexis is the settled disposition that repetition builds, and Aristotle includes something in it that usually gets dropped: the disposition involves taking the right pleasure in the right object. Enjoying the finished joint is the disposition working. Enjoying the routine that produced it is where the substitution starts. The moment your routine becomes interesting enough to explain at length, check whether it is still producing anything.

Celebrate the landing hard. This is the move people skip, and skipping it is how process romance starts. If real completions never get marked, the mind goes looking for meaning in the only place still available, which is the daily effort itself. Mark the finish properly. Take the evening.

One clarification, because the control distinction cuts both ways here. The finish is worth marking as evidence about the effort, not as a verdict handed down by fortune. Unfinished work lets you believe things about how much you actually did; a finished thing settles the question. Two people can do identical work and one gets rained out. That person is owed the same evening and did not get the proof.

Then demote it. The win was a result, it was partly luck, and it is over. Be back in the work the next morning, not three months later. ergon is the characteristic work of a thing, what it is actually for, and yours does not change because one instance of it went well.

The prognosis: what to check this week

Pick the project you would name if someone asked what you are working on.

Can you write the one-sentence version of done, right now, without editing it three times? If it takes more than a minute, that is the finding.

When did you last mark a real completion, as opposed to a milestone? If you cannot remember one this year, you may be running on process alone, regardless of how full the calendar looks.

What did you tell someone about your work this week, and was it about what you made or about how you work? Both are fine. The ratio is the diagnostic.

If the number stopped moving tomorrow and nobody noticed for a month, what would that tell you about what the number was for?

And the one that outranks all of the others: is the one worth reaching? Everything above is a method for arriving, and a method for arriving is indifferent to the destination. You can define done crisply, ship on time, demote the win, return to the practice, and run that loop for thirty years on things that did not deserve any of it. Answer this question first or the rest of it is a very disciplined way to waste a decade.

Final Thoughts

arete is excellence in the doing, and the doing has an object. That is the part both traps lose. Excellence is always excellence at something, aimed at a result that exists outside your own experience of pursuing it, and the moment the pursuit becomes self-sufficient it has quietly stopped being excellence and become a hobby with good posture.

None of which is an argument for outcome obsession, and it is not an argument for serenity either, which I went after a few days ago. The outcome is not yours to control and never was, and hanging your sense of yourself on it makes you a passenger in your own week.

What you own is the showing up, which is smaller than people want and more demanding than it sounds, because it never ends and it never gets a slide. You do the work. When it lands you say so, loudly, and then you put it down. The next morning is the same as every other morning. That is the arrangement, and it stops feeling like a hardship once you quit expecting otherwise.

Go find your 0.4. Ask it what it is waiting for.

Doing the work without narrating it is harder than it sounds, and it goes better with people who will call it when you drift. That is what MasteryLab is for.