Who Is Your Internal Customer? Three Questions That Fix Handoffs

I talk a lot about the external customer. The external customer buys our product or service, pays the bills, and keeps us in business. I support that focus completely.

But if all we ever talk about is the external customer, we are going to struggle internally. There is another customer that matters just as much, and most people in your building have never been asked to identify theirs.

What an internal customer is

Your internal customer is the person, team, or department that needs your work in order to do their work.

If production needs a schedule from planning, production is planning's internal customer. If accounting needs paperwork from operations before it can send an invoice, accounting is operations' internal customer. If the next shift needs good notes from the current shift, that next shift is an internal customer too.

Notice the timeframe. This is not about the product lifecycle, whether that is four days or seven months or two years before your company gets paid. This is about today. What is someone doing today that affects somebody else today?

If people do not know who their internal customer is, that is a problem. If they know and do not care, that is a bigger problem.

Question one: who is my internal customer?

I work through three questions with teams, and this is the first.

Look at what happens after your work leaves your hands. Who gets it next? Who depends on it? Who gets stuck if you are late? Who has to fix it if you make a mistake?

That person or team is your internal customer. For most people the answer is obvious once they are asked, and the striking thing is how rarely anyone has asked.

Some people will identify more than one, and that is worth knowing too, because it tells you where a single delay propagates in several directions at once.

Question two: what does my internal customer need from me?

I do not want to guess at this, so I ask directly. What do you need from me to do your job well?

The answers are usually more specific than expected. They may need the information sooner. They may need it in a different format. They may need fewer mistakes in it, or more notice when something changes.

Here is the part that surprises people. You can follow your process exactly and still make somebody else's job harder. The process was designed around your department's convenience, and nobody checked it against the person receiving the output.

That is why I want the people doing the work talking to each other, rather than everyone assuming the handoff is working because nobody has complained.

Question three: how do we talk when the handoff is not working?

This is the one that changes an operation.

I do not want one department complaining about another department behind closed doors. That conversation happens constantly in most companies and it resolves nothing, because the people who could fix the problem are not in the room.

What I want instead is a direct conversation covering five things: what was missing, what was late or wrong, what problem it caused, what needs to happen next time, and who owns the fix.

That last item is the one most often skipped. A handoff conversation without a named owner is a venting session with better manners.

Why most problems live between the jobs

A lot of what goes wrong at work happens between jobs, not inside them.

One person believes the work is done. The next person is still waiting for what they need. Both are being reasonable from where they are standing, and the gap between them is where the delay, the rework, and the frustration accumulate.

Individual departments can each be performing well while the organization performs badly, because nobody owns the space between them. That is why fixing this rarely requires people to work harder. It requires the handoff to be visible and owned.

Our piece on communication working agreements covers how to make those expectations explicit, and when every decision escalates covers what happens when ownership of the gap is never settled.

The three questions on one handoff

Take a shift handover, because almost every operation has one and almost every operation has trouble with it.

Question one. The outgoing shift's internal customer is the incoming shift. Obvious once stated, and yet handover notes are very often written as a record for management rather than as a briefing for the people who need them.

Question two. Ask the incoming crew what they actually need. The answers tend to be concrete: which machine was behaving oddly and in what way, what was tried, what is half-finished and where it stands, which order the customer moved, what to watch in the first hour. That is a different document from a list of what was completed.

Question three. When the handover fails, the two crews rarely speak, because they are never in the building at the same time. So the conversation has to be deliberately created, with someone owning the fix, or the same gap repeats indefinitely while both crews privately conclude the other one is careless.

The same exercise works on any handoff in the business. Planning to production. Sales to operations. Operations to accounting. Maintenance to the line.

We five-star everything except work

Here is something I put to rooms. Raise your hand if you have given a five-star review in the last six months. Or left a review that was not five stars.

Almost every hand goes up. We rate the delivery driver, the restaurant, the app, the hotel. We do it constantly and without being asked.

So why do we not do that at work? Why do we not do it between departments, where the quality of what we hand each other actually determines whether the business runs?

I am not proposing a rating system. I am proposing that the same instinct we apply everywhere else is missing in the one place it would do the most good.

Build the workflow, do not rely on goodwill

Asking the three questions once produces a good conversation. Asking them regularly changes how the place runs.

That means a workflow rather than an intention. Is my department supplying what our internal customer needs? That question should be asked on a routine basis, with a route for raising it when the answer is no, and a habit of stopping to schedule the conversation rather than working around the gap for another month.

When a handoff breaks, stop and ask what is not being provided. Get the two groups together. Agree the fix and who owns it. Then check back, because a fix nobody revisits tends to last about six weeks.

What this changes for a supervisor

For the people running shifts and departments, this reframes a part of the job that usually gets handled by instinct.

A supervisor who thinks in terms of internal customers plans the end of the shift differently. The notes get written for the person who has to use them at six in the morning, rather than as a record that something was done. The unfinished item gets flagged rather than left to be discovered. The change that affects two other departments gets communicated before it lands on them.

It also changes how they read a complaint. When another department pushes back, the instinct is defensive, because the process was followed. Thinking in terms of internal customers turns that into information. Something we produced did not work for the person who received it, and we would rather know.

None of this requires new authority. It requires the supervisor to see one step past the boundary of their own area.

The idea underneath all of this

What I am really describing is servant leadership applied to the ordinary flow of work.

If the only reason you show up is to move your own work forward and clear your own hurdles, that is the problem. The alternative is asking how you help others and how you put other people in a position to succeed.

People sometimes hear that and worry they are not looking after themselves enough. My experience is the opposite. When you consistently put others first at work, you tend to get what you deserve, and you get it the right way.

The internal customer question is simply the practical version of that idea. It turns a value into something a person can actually do on a Tuesday.

The point of all of it

The goal is to make the handoff better, so the next person can do their job without chasing information, correcting mistakes, or waiting on something they should already have had.

When people start thinking about whoever gets their work next, something changes in how the place feels. You stop having a set of departments that happen to share a building, and you start having a team.

So the three questions, one more time. Who is my internal customer? What do they need from me? Have I actually asked them?

Frequently Asked Questions

What is an internal customer?

The person, team, or department that needs your work to do their work. If production needs a schedule from planning, production is planning's internal customer. If the next shift needs good notes from this one, that shift is an internal customer too.

How do I identify my internal customer?

Look at what happens after your work leaves your hands. Who gets it next, who depends on it, who gets stuck if you are late, and who has to fix it if you make a mistake. That is your internal customer, and some people have more than one.

Can I follow my process correctly and still cause problems?

Yes. Processes are usually designed around the producing department's convenience and never checked against the person receiving the output. That is why the two groups need to talk rather than assume the handoff works because nobody complained.

What should a conversation about a broken handoff cover?

Five things: what was missing, what was late or wrong, what problem it caused, what needs to happen next time, and who owns the fix. Without a named owner it is a venting session rather than a resolution.

Why do departments perform well while the company performs badly?

Because most problems live between jobs rather than inside them. One person believes the work is finished, the next is still waiting, and nobody owns the space between them where the delay and rework accumulate.