Who Owns This? Fixing Handoffs Between Teams

Who Owns This? Fixing Handoffs Between Teams

"Who is dealing with this?"

It is a simple question, but in a growing service business it can be surprisingly difficult to answer.

A customer sends a request.

Sales passes it to operations.

Operations passes it to the delivery team.

Someone needs information from accounts.

The customer then calls again because nobody has updated them.

Everyone has done something.

But somewhere between those people, the work has stopped moving.

This is what makes handoff problems difficult to spot.

The problem is not always that someone is doing a bad job.

The problem is often that responsibility becomes unclear as the work moves from one person or team to another.

A handoff is more than passing something on

Consider a simple example.

A customer accepts a quotation.

The salesperson emails the details to the operations team.

The salesperson considers the job handed over.

Operations assumes they have everything they need.

The delivery team is waiting for operations to confirm the start date.

Nobody has clearly said who is responsible for contacting the customer.

The work has been passed around, but nobody is clearly carrying it.

That is the difference between passing work and handing over ownership.

A good handoff should make it clear what is being passed, who receives it, and what happens next.

Find the handoffs in one workflow

You do not need to map the whole business.

Pick one workflow where delays or confusion happen regularly.

For example:

• A new customer being onboarded
• A quotation becoming a job
• A maintenance request moving to an engineer
• A customer complaint being escalated
• An invoice being raised after work is completed
• A cancellation being processed

Write down the steps from beginning to end.

Then circle every point where the work moves from one person or team to another.

Those are your handoffs.

Now look at each one and ask:

What exactly is being handed over?

Who receives it?

What are they expected to do?

When do they become responsible?

How does the previous person know the handoff is complete?

You may find that some of these questions have no clear answer.

"I sent it" is not the same as "it's handed over"

This is one of the easiest traps.

Someone sends an email and considers their part finished.

But sending information does not necessarily mean the next person has accepted responsibility.

Imagine a team member sends:

"Please see the attached customer details. Can you take this forward?"

What does "take this forward" mean?

Does the other person need to call the customer?

Create a job?

Check the information?

Schedule the work?

Confirm the booking?

There is room for different interpretations.

A better handoff makes the expected next step clear.

For example:

"The customer has accepted the quotation. Operations now owns the job. Please confirm the start date with the customer by Thursday."

That is much easier to act on.

Look for the "in-between" work

Some of the biggest gaps happen when nobody owns the work between two obvious steps.

For example:

Sales → Operations

Who checks that the customer information is complete?

Or:

Operations → Delivery

Who confirms that the job is ready?

Or:

Delivery → Accounts

Who confirms that everything needed for invoicing has been recorded?

The teams on either side may each have a clear responsibility.

The problem is the space between them.

That space is where work can sit.

Watch for these five warning signs

When reviewing a handoff, look for:

1. "I thought they were doing it"

If you hear this regularly, ownership is probably unclear.

2. People chasing each other for updates

A little chasing is normal.

If people regularly need to ask, "What's happening with this?", the process may not make status or ownership clear enough.

3. Work sitting in shared inboxes

A shared inbox can make information visible to everyone while making responsibility visible to nobody.

4. Personal spreadsheets or trackers

These can be useful, but they may also indicate that the main process does not give people enough visibility.

5. Customers becoming the reminder system

If customers regularly need to call or email again to find out what is happening, look at what happens internally after the previous step.

The customer should not have to manage the handoff for you.

Make ownership clear at the point it changes

You don't necessarily need a complicated responsibility system.

At each important handoff, define three things:

Owner: Who is responsible now?

Next action: What do they need to do?

Timing: When does it need to happen?

For example:

Owner: Operations coordinator
Next action: Confirm the customer's preferred installation date
Timing: Within one working day

That is often enough to remove a lot of uncertainty.

The exact wording will depend on the business.

The important thing is that the person taking ownership knows that they have taken ownership.

Don't create more meetings to solve a handoff problem

A common response to poor handoffs is to add meetings.

Another meeting is created so that sales can update operations.

Then another meeting is needed because operations needs to update delivery.

Sometimes meetings are necessary.

But before adding one, ask:

What information or decision is missing from the current process?

If the problem is that nobody knows who owns the next step, another meeting may simply create another place to discuss the same problem.

A clearer handoff may solve it without adding more time to everyone's week.

Your systems should support the handoff

This is where your existing tools can become useful.

If you already have a CRM or operations system, it may be able to show:

• Who owns the work
• Current status
• Next action
• Important information
• Outstanding tasks
• When the work was last updated

But the system can only help if the process has been decided first.

There is little value in adding another status called "Pending Operations" if nobody knows what that status actually means.

The tool should support the handoff, not become another thing people have to manage.

Try this with three recent examples

Pick three pieces of work that recently got stuck between teams.

For each one, write down:

1. Who owned it before the handoff?
2. What exactly was handed over?
3. Who was supposed to own it afterwards?
4. What was the next action?
5. How was that action communicated?
6. How did the previous person know the handoff was complete?
7. Where could someone see the current status?
8. What did the customer experience while this was happening?

Now look for the same gap appearing more than once.

If three different examples all stop at the same handoff, you probably have a process problem rather than three separate mistakes.

Fix the handoff before fixing everything around it

You may discover that the solution is very simple.

Perhaps the handoff needs a clear owner.

Perhaps one piece of information needs to be captured earlier.

Perhaps the next action needs to be recorded somewhere everyone can see.

Perhaps two teams need to agree what "ready" actually means.

Or perhaps the existing system needs to be configured differently.

Sometimes automation can help too.

But first, make the handoff clear.

A good process does not require people to constantly ask:

"Who is dealing with this?"

They should be able to see who owns the work, what needs to happen next, and when it needs to happen.

When that becomes clear, work has a much better chance of moving from one person to the next without getting lost in between.

Tell us where work is getting stuck.