Hello! 👋
It's Thursday, 14th May 2026. Welcome back to Bold Efforts!
Most jobs end twice. There is the official ending: a resignation, a last day, a round of farewells. And there is the real ending, which happened earlier, quietly, in a moment nobody thought to mark. The second one is the one that shaped you.
At every job you have ever left, there was a last genuinely good day. You probably cannot name the date, but you could reconstruct it if you tried: the last meeting where the team worked as it was supposed to work, the last afternoon a project still felt like something being built rather than something being maintained, the last time you left the building feeling the work was worth the effort. You did not know that day was ending as it happened. The next morning arrived, everything looked the same, and the calendar kept moving.
The official last day came later. It came with paperwork, a farewell lunch, a card signed in the hallway, a round of LinkedIn posts celebrating the next chapter. It is this date that HR systems record, that notice periods count toward, that employment histories reflect. It is the date everyone uses.
But the ending was already behind you. At most jobs, the gap between the last genuinely good day and the official last day is measured in months. At some, years. Inside that gap something real was lost, and the professional world has almost no mechanism for acknowledging it.
The first reason is structural. Organizations are built to track documented states, not experiential transitions. An HR system records a hire date and a termination date. A project management system records a start and an end. Everything between those markers is assumed to be continuous. There is no field in any management software for the day a team stopped working as it was designed to work, or the quarter when a project was last genuinely alive. The things that actually shape a person's experience of work do not appear in any system. So when someone leaves, what the organization processes is a change in status. What it cannot process is what happened in the years between.
The second reason is cultural. There is an approved script for leaving a job, and it is essentially mandatory regardless of how the job actually ended. The language is always the same: grateful for the opportunity, learned so much, excited for what comes next. Your next employer is searching your name. Former colleagues need to believe your departure does not indict them. Your own professional standing requires a certain frame. The incentives produce the script. But the script makes honest acknowledgment impossible, because you cannot grieve publicly in a register that requires optimism. There is no professional vocabulary for "this team was something real and I am sad it is ending." The experience gets repackaged, optimism gets performed, and what was actually lost disappears into your career history stripped of its texture.
The cost of this runs in two directions.
For the individual, it accumulates as residue. Most people who have worked for a decade carry something they cannot easily identify: a guardedness with new teams before those teams have proved themselves, a hesitation to invest fully in a project before it has survived its first real test, a reflexive distance when asked to believe in something new. This reads as experience, sometimes as wisdom. Often it is the weight of endings that were never allowed to close. You cannot fully arrive at the next thing while you are still half inside a previous thing that was never permitted to finish. Grief, when it has nowhere to go, does not evaporate. It becomes the atmosphere.
For organizations, the cost is different but larger. When people leave performing mandatory optimism, the honest signal disappears with them. The departing person does not say: this project failed because the decision-making was broken at a level above mine. They do not say: this manager has driven out four good people in two years and none of us said so publicly because we needed the reference. They say they are grateful for the experience. The manager hears gratitude from every exit. The pattern never gets named. The same conditions reproduce in the next hire, and the one after that.
Organizations have spent decades building systems to measure employee engagement, predict attrition, and analyze exit data. Almost none of it captures the real ending, because the real ending happened before anyone thought to measure anything.
The reason this problem resists structural fixes is that the norms around professional exits are not careless. They are load-bearing. Mandatory optimism protects reputations, preserves references, and keeps former colleagues from having to process a public accounting of what went wrong. Ending ceremonies are brief because organizations need people to keep working, including the people who remain after someone leaves. The system is not broken. It is working exactly as designed, which is why it produces this outcome so consistently.
What the system cannot do is distinguish between a departure and a loss. A departure is a status change. A loss is something that was real and is now gone, and the going deserves to be marked as such. The farewell party handles the departure. Nobody handles the loss.
What remains is a private accounting that most people never quite make. The last good day at every job was real. The team that worked, the project that mattered, the period when the work was worth the effort: these things ended, and they ended before the paperwork said they did. Calling them endings rather than transitions is not sentimental. It is accurate. And accuracy, here, is the beginning of actually being able to set something down.
The farewell party marks a departure. However, the loss happened earlier, in a room that no longer exists as it was, in a week that nobody thought to notice. Thank you for reading.
Best,
Kartik
I write Bold Efforts every week to think clearly about where work and life are actually headed, not where headlines say they are. If you want these essays in your inbox, you can subscribe here.