Image by @mirzaie from Unsplash
There is a particular kind of guilt that comes with retiring something. Not ending it in anger, not walking away in a huff — just quietly deciding it is time. Logically, you know it is the right call. Emotionally, it feels like you are admitting defeat.
Think of an old, faithful car. The kind that never once broke down — that got its owner to work, to weddings, to hospital visits and back, without complaint. But somewhere past the two-hundred-thousand-kilometre mark, the maintenance starts outpacing the miles. Parts get harder to find. The mechanic starts greeting the owner with a sigh rather than a smile. And still, letting it go feels like betrayal. As if trading it in means it failed, when really, it did the opposite.
We carry that same guilt into work. The client who has been with us for years but now costs more in patience than they bring in revenue. The project that made sense three strategies ago and somehow still has a standing meeting. The habit — the daily check-in, the approval chain, the reflex to cc everyone — that once solved a real problem and now simply exists, unquestioned. We keep them going not because they still serve us, but because ending them feels like saying they were a mistake.
They were not a mistake. That is the distinction worth sitting with. A thing does not fail by needing to be retired. It fails only if it never did its job in the first place. That old car does not fail at two hundred thousand kilometres — it succeeds, thoroughly and for a long time, and then simply reaches the edge of what it can keep giving. The client relationship that outlives its usefulness was not a bad decision back when it started. The habit that now slows the team down was, at some point, exactly the fix the team needed. Retiring something is not admitting it failed. It is admitting it did its job — completely, and for as long as it could.
But here is where the word "retire" gets misunderstood, and where I think the real conversation lives. We tend to treat retirement as a full stop. A person retires from a job, and we half-expect them to disappear from relevance — to trade purpose for leisure, contribution for quiet. Yet most people who retire well do not stop giving. They mentor. They consult. They show up differently, with more selectivity and less obligation, but they still show up. Retirement, done properly, is not an ending. It is a change in what you are being asked to give.
The same is true at work. Retiring a project does not mean the thinking behind it disappears — often it becomes the foundation for the next one. Retiring a habit does not mean the discipline it built vanishes — it frees that discipline up for something that actually needs it now. And retiring a client relationship does not have to mean disappearing on them, either. You can close a chapter with someone and still hand them onward with care — a referral, an introduction, a recommendation to someone better suited to what they need next. Retiring well is not about severing ties. It is about changing the shape of what you offer, and being honest enough to say so out loud, to the people it affects.
That, I think, is the harder skill. Not noticing when something has run its course — most of us know, quietly, long before we act on it. The harder skill is retiring things without pretending they were worthless, and without disappearing on the people attached to them. A proper retirement has a handshake at the end of it, not a door quietly closed.
So before your next planning meeting, it might be worth asking — not "what should we stop doing," but "what has already done its job, and what do we owe it on the way out?"
