The handover problem in small teams

Every small team has a version of this conversation. A customer calls, the person who normally handles them is away, and whoever answers has to say some variation of “let me find out and come back to you.”

It sounds minor. It is not, for two reasons. The customer learns that the relationship is with a person rather than with the business. And the business learns nothing, because the context that was missing is still missing tomorrow.

Why “write better notes” does not work

The standard response is to ask people to document more. This fails predictably, for a reason worth naming: the person with the context has the least incentive to record it. They already know it. Documentation is pure cost to them and pure benefit to a colleague who may never need it.

Any system that depends on someone doing unrewarded work at the moment they are busiest will decay. It might hold for a month. It will not hold for a year.

The systems that work are the ones where the record is a by-product of doing the job, not an extra step after it.

Context is not notes

Part of the problem is that “context” gets treated as a summary somebody writes. In practice, the things a colleague needs are more specific:

• What did we last say to them, and when?
• What stage is this at?
• What did they buy before, and what did it cost?
• What is outstanding on their side?
• Is anything overdue?

None of those are prose. All of them are structured facts that a system can hold without anyone writing a paragraph.

Where the record should live

The distinction that matters is between a record attached to a person and a record attached to a customer.

Email is attached to a person. It is a private log of one employee’s side of a relationship. It cannot be handed over — forwarding a thread transfers some of the words and none of the structure.

A unified inbox on the contact record inverts that. The conversation belongs to the customer, so it is visible to whoever opens the record. Nothing has to be transcribed, because nothing was ever in a private place.

The same is true of the deal. A visible pipeline means “where are we with them?” is a thing you look at rather than a thing you ask. Stages are shared state, not a status someone carries in their head.

Reduce how often the question is asked

Handovers get easier when there are fewer status questions to begin with.

A large share of inbound customer contact is not a request — it is a check. Is it done? When are you coming? Did you get my file? Each one costs an interruption and, during a handover, a moment of visible uncertainty.

Giving clients a portal where they can see status and files removes the question rather than answering it faster. That is a better trade than any amount of internal documentation, because it takes the load off the team entirely.

What good looks like

You have solved this when the following is true: someone who has never spoken to a customer can open their record and, within a minute, know the stage, the last exchange, what is outstanding and what happens next — without asking a colleague.

That is a low bar in principle and an uncommon one in practice. It is worth testing directly. Pick a customer at random, hand the record to someone who has never dealt with them, and ask them to explain the situation back to you.

Whatever they cannot tell you is what currently lives in somebody’s head. That is your actual exposure, and it is the same exposure whether the person is on holiday or has just resigned.

The compounding version

There is a longer-term reason to care, beyond covering absences.

A business where context lives in records can grow by adding people. A business where context lives in individuals grows by cloning individuals, which nobody knows how to do. The first can hire; the second can only stretch.

The handover problem is not really about handovers. It is an early, cheap signal of whether the business is structured to get bigger.