Of Return

This is the step nobody celebrates.

The launch gets a Slack announcement and a shared document and sometimes cake. The delivery gets a retrospective and a case study and a line in the quarterly review. The model going to production gets a ribbon cutting and a screenshot and a brief season of being cited in presentations as evidence that the team delivers.

The return gets nothing.

Nobody schedules it. Nobody owns it. Nobody puts it on the roadmap or the annual planning document or the performance review criteria. The return happens when a practitioner, on a Thursday afternoon that looks like every other Thursday afternoon, decides to pull up the original brief and reread the objective the system was built to optimize and compare it, carefully and honestly, to what the world looks like now.

That practitioner is practicing the discipline at its most complete.

Not at its most visible. Not at its most celebrated. At its most complete. Because the return is where the cycle closes and where the cycle begins again and where the distance between what the system was built to do and what the world now needs is either small enough to close or large enough to require the whole thing to start over, and both of those outcomes are good outcomes, the only bad outcome being the one where no one looks, where the system runs and runs and the distance grows and the organization pays the cost of it quietly and invisibly and without understanding why the decisions downstream feel slightly wrong in a way no one can name.

We are grateful for the return.

We are grateful for the practitioners who make it, who carry the original brief in their heads long after the project has been declared complete and the team has moved on and the model is running in the quiet dark of production. Who ask, without prompting and without reward, whether the thing still makes sense. Who write the memo. Who send it knowing it will create work for people who do not want more work, who send it anyway because the alternative is the Fourth Horseman and they have read the gospel and they know how the Fourth Horseman ends.

The return is not dramatic.

That is why we are grateful for it. The dramatic moments are easy to honor. The ordinary Thursday afternoon when someone decides to look at a system nobody is looking at, to ask a question nobody is asking, to care about something the organization has stopped caring about. that moment is the discipline made flesh. That is what it looks like when the doctrine is practiced rather than performed.

We do not know the names of most of the people who make that return.

We are grateful for them anyway.

Go back.

Ask the question.

That gratitude is what we have to offer, and it is real, and it is enough.

The congregation reads slowly and does not hurry to the next chapter.

The Four Horsemen referenced here are in the book.