“Is it supposed to feel like this, or did I just lose a piece of my soul in the faculty lounge?” I asked the radiator, which hissed back in a way that felt suspiciously like a critique of my lesson plan. I didn’t realize my colleague was standing behind me until I heard her cough. Getting caught talking to yourself is a professional hazard when you spend 48 hours a week teaching middle schoolers about digital citizenship. You start to treat every object as a potential student, hoping the inanimate ones will at least stay on task. But the truth is, I wasn’t just talking to the radiator; I was mourning a handoff. I had just spent 18 minutes trying to explain to a parent why their child’s data had been ‘transferred’ between three different school platforms, losing the student’s history and half of my sanity in the process.

Most organizations think of a handoff as a technicality. It is the moment Sales passes a lead to Support, or when a developer pushes code to the QA team. We treat these moments as logistics, as if we are just moving a box from one shelf to another. But we are wrong. The handoff is the moral center of an institution. It is the exact point where you find out if a company actually cares about the person on the other end of the transaction, or if they just care about getting the task off their own desk. Most large-scale frustration in the modern world is born in these gaps, these tiny, airless spaces between specialties where no single human feels fully responsible and the user’s experience gets chopped into 8 unidentifiable pieces.

Take Elena. Elena is a fictional customer, but she lives in the hearts of anyone who has ever had to repeat their name and problem 18 times in a single afternoon. Her journey starts in Sales. Sales is a dreamscape. It is filled with people who listen, who promise that the software will solve her problems, and who offer 28 percent discounts if she signs by Friday. But once the ink is dry, Elena is handed off. She is catapulted across a canyon into the arms of the Implementation team. But Implementation didn’t get the notes from Sales. They don’t know Elena has a deadline in 8 days. They don’t know that her previous system crashed in 2018 and she’s still traumatized by data loss. To them, she is just ticket #4888.

This is where the character of the organization is revealed. If the salesperson truly cared about Elena, they would have ensured the transition was seamless. They would have walked across the hall-or the virtual Slack channel-and personally ensured that Implementation understood the nuances. But in most places, that doesn’t happen. Why? Because the salesperson has already been paid. Their KPI is met. Elena is no longer their problem. This is a form of institutionalized indifference. It is a belief that as long as my department’s numbers look good, the fact that the customer is currently screaming into a void is irrelevant.

I see this in my classroom every day. Teaching digital citizenship isn’t just about telling kids not to bully each other on the internet. It’s about the ethics of the handoff. When you share a piece of information, you are handing off a piece of someone else’s reality. If you don’t care what the next person does with it, or if you don’t provide the context necessary to handle it with care, you are failing as a citizen. We are raising a generation of kids who are being taught by the corporate world that the goal is to ‘ship it’ and let someone else deal with the fallout. I once spent 58 minutes trying to explain to a group of eighth graders why a ‘broken link’ in a research paper is actually a breach of trust. They thought I was being dramatic. I told them that a broken link is a handoff that failed. You promised them a destination and instead you gave them a brick wall.

“The handoff is where the soul of the work either survives or is quietly smothered by a lack of ownership.”

This lack of ownership is a contagion. It starts at the top and trickles down until everyone is just a cog in a machine that produces nothing but confusion. I’ve seen it in healthcare, where a specialist hands a patient back to a general practitioner with 188 pages of notes that no one has the time to read. I’ve seen it in government, where you are told to go to Window 8, only to find that Window 8 closed in 1998 and the person now sitting there only handles parking tickets, not building permits. Every time this happens, the underlying message to the human being on the receiving end is: ‘You are not worth the effort of coordination.’

It is a radical act to care about what happens after you are finished. It requires a level of empathy that isn’t easily measured in a spreadsheet. It means looking at the person you are handing the task to-not just the task itself-and asking, ‘What do you need from me to be successful?’ It means acknowledging that the job isn’t done until the person on the other end is whole. This is why brands that prioritize coherence are so rare and so beloved. They understand that the experience must be a single, unbroken thread. Whether you are dealing with a complex software implementation or something as fundamental as pet nutrition, the principle is the same. You cannot have a high-quality product if the delivery of that product is a disorganized mess. For example, the reason people trust a service like Meat For Dogs is because there is a perceived coherence in the mission; the care put into the product must be matched by the care in how it reaches the bowl. If the handoff between the source and the consumer is broken, the quality of the source becomes irrelevant.

We often hide behind ‘process’ to avoid the emotional labor of a good handoff. We say, ‘I followed the protocol,’ or ‘I filled out the form correctly.’ But protocol is a floor, not a ceiling. You can follow every rule in the company handbook and still leave a customer feeling abandoned. I remember a time in 2008 when I was working for a different school district. We had a student transferring in with severe allergies. The paperwork was perfect. It had 8 signatures and was filed in 18 different folders. But nobody actually talked to the cafeteria manager. The handoff was technically complete, but the human connection was missing. It was only because a teacher happened to be talking to herself in the hallway-much like I do now-and mentioned the student’s name that the manager realized they needed to change the menu for the day. That ‘accidental’ communication saved a child’s life, but it shouldn’t have been accidental. It should have been the moral priority.

When we treat handoffs as administrative moments, we are choosing efficiency over humanity. We are saying that the speed of the transaction is more important than the quality of the relationship. But in the long run, this is a losing strategy. The cost of a bad handoff is astronomical. It’s the cost of churn, the cost of rework, and the cost of a damaged reputation. More importantly, it’s the cost of the internal culture. When employees see that their colleagues don’t care about making their lives easier, they stop caring too. The ‘not my job’ attitude is the terminal stage of a culture that has failed its handoffs.

I’ve made this mistake myself. More times than I care to admit, I’ve sent a curriculum update to the board of directors without explaining the ‘why’ behind the changes. I assumed they would just get it. Then, when they came back with 68 questions that felt like attacks, I realized I hadn’t handed off the information; I had thrown it at them and run away. I had been so focused on my own 188-item to-do list that I forgot the people on the other side were human beings with their own pressures and constraints. I apologized, which felt like swallowing a bag of 88 rusty nails, but it was necessary. You have to admit when you’ve left a gap for someone else to fall into.

“True professionalism is the refusal to leave a mess for the next person, even when nobody is watching you clean it up.”

So, how do we fix the handoff? It starts with a shift in perspective. We need to stop seeing ourselves as individuals with tasks and start seeing ourselves as links in a chain. A link doesn’t exist for itself; it exists to connect two other things. If the link is strong but the connection is loose, the chain is useless. We need to build ‘overlap’ into our processes. In a relay race, the runners don’t just throw the baton at each other; they run together for a few meters to ensure the transfer is smooth. Organizations need to do the same. Sales needs to sit in on the first Support call. Developers need to watch QA test their code. Teachers need to talk to the radiator-or anyone else who will listen-about the needs of the students they are passing on to the next grade.

It’s about 8 percent more work to do a handoff correctly, but it saves 88 percent of the headache later on. We have to stop treating context as a luxury. Context is the oxygen of a functioning organization. Without it, everything dies. When you give someone a task, give them the history, the emotion, and the goal. Tell them why it matters. Tell them what the person before you did, and what the person after them expects. If we can’t do that, then we aren’t really working together; we’re just standing in the same building, passing the same mistakes back and forth until the lights go out.

I eventually finished my conversation with the radiator and went back to my desk. I realized I needed to redo that student’s data transfer myself, manually, instead of relying on the automated system that had already failed twice. It took me another 48 minutes, and I missed my lunch break, but when I was done, the history was there. The context was there. The next teacher who looked at that file wouldn’t see a series of 108 disconnected data points; they would see a child with a story. It wasn’t my ‘job’ to fix the software’s mistake, but it was my responsibility to the handoff. And in the end, that is the only thing that actually matters. If you can’t care about the space between you and the next person, you aren’t really doing the work at all.