Not only IT. HR, procurement, finance, legal and facility know the same break with the business, and every trade has invented a role for it: the HR business partner, the account manager, the delivery manager, the business controller. Five handovers can be a design or a scar. The difference lies in four questions.
Five stitches hold the seam together, and more keep being added.
What this is about
Many central services recognise the same thing. Whatever is not standard gets stuck, and the answer to that is another meeting. That meeting solves the problem of the moment. It does not close the break between the business and the central service, and it can drive the two further apart, away from the reason that service was set up in the first place. What is left is a seam: two domains of responsibility, each with its own way of working.
The drawing above is not wrong. Five handovers can be exactly the right number. How many there are is not the question. Four questions do count, and they are about the design rather than the number. Did anyone choose them? Is it known, per handover, what it protects? Does anyone ever look back at it? And when a new situation turns up, is another such handover reached for without thinking?
If those four are in order, it is an interface somebody designed. If one is missing, it is not a scar yet, but it is on its way to becoming one.
The same seam, other services
The seam is usually described as something between the business and IT. That is where the term comes from, and it is where most organisations feel it first. It is not the only place.
In HR the business partner is usually not appointed to think along about how the work is divided. The role is a fixed point of contact for a department, and should make the line more capable in what HR has put there. Only nowhere does it say when that has been achieved. No date has been agreed on which the role ends, HR does not like letting go of the tie with the department, the department can no longer do without it by then, and the partner is an HR specialist on a permanent contract. So the partner draws up the vacancy text and the job description every time. The line manager does it too rarely to build any routine, and so calls the partner, who finds it hard to say no. The vacancy has a date, how the work gets divided does not, and that is why the vacancy wins every time.
How does that go in your organisation, with a dismissal, with pay, with a change to working hours?
Who drafts it, who decides on it, and who gets called the moment it is not standard?
At the four other services it looks different and the same thing happens.
Outside the agreement
Procurement
A team buys on its own, outside the framework contract, from a supplier who is not in it yet. Procurement is not involved and often sees it first on the invoice. Sometimes for better terms, often because nobody knew the framework contract. The agreement sits with procurement and the budget with the business, and whoever holds the budget can buy without needing anyone. That is why more oversight changes little.
Two loyalties, one diary
Finance
The controller sits on the steering group to help think through an investment choice, and three days later a consolidation close is waiting. Both belong to the role, and they do not have the same owner. The close belongs to finance, which also decides on the controller's diary. The thinking belongs to the business, which has no say over it. So the thinking gives way, and not because anyone considers it less important.
The waiting time belongs to nobody
Legal
The contract sits three weeks waiting for review, and meanwhile the supplier cannot sign. Nobody owns those three weeks. Legal measures its lead time from the moment the document is picked up, the business counts from the day it was sent, and the queue in between appears in neither figure. That is why adding capacity does not help either. What nobody sees as part of their own responsibility stays lying between the two.
The same report, time after time
Facility
Work is carried out to a standard that nobody in the team helped draw up. What goes wrong afterwards comes in as a report, and that report is logged neatly. The reason it keeps coming back is not. Whoever can adjust the standard does not hear the problem, and whoever hears the problem cannot adjust the standard. The result is a list that grows and a standard that stays as it is.
Every trade looks at it differently. In procurement it has a name: maverick buying, purchasing outside the agreement. In IT a whole discipline has grown around it, business relationship management, with its own training courses and a specialist module of its own in ITIL 4. In HR and finance there are terms for the complaint but not for the phenomenon underneath, and there it is simply called the business partner never getting to the real work. None of the trades recognises it as the same organisational phenomenon, and so every service thinks it is their problem and looks for the answer inside their own boundary.
The seam does not stop at the outer edge
So far the line has run between a central department and the business. Inside that department the same line lies a few more times. An IT department of any size has architecture, applications, and infrastructure and operations, each with its own way of working and its own authority. Whatever has to pass between those teams crosses a seam. Each of those teams also has a plan of its own, so delivering the plan of one depends on the willingness of the others, while nothing obliges them to put it before their own.
These are the same three cuts, one level down. Architecture, applications and operations side by side is a cut along function. And the question whether you could cut around a stream instead holds there just as much as it does at the outer edge.
These seams are yours to draw. That holds more than you might think for the line towards the business as well, because the intake form, the demand board and the SLA were usually devised by the department rather than imposed by the business. They made its own work manageable, and at the time that was a defensible choice. Whoever drew them can redraw them.
One imbalance underneath
In all five the decision sits somewhere other than where the work ends up.
The demand comes from elsewhere. The capacity to do something about it has been taken away.
The demand lands in one place, while the authority, the knowledge or the capacity to resolve it sits somewhere else. Whoever gets the demand then looks for a way around it, escalates, or waits. Anyone does that when they are responsible for something without the means to resolve it.
Which of the three is missing also decides what helps. If the knowledge is missing, training is enough. If the capacity is missing, it is a question of staffing. Only when the authority sits elsewhere is it a design question, and then neither a course nor an extra pair of hands changes anything.
It is also why more oversight yields so little. Oversight works on the will, and the will is not the problem.
Where a seam comes from
Some seams were drawn on purpose. At a time when departments depended on each other far less, many organisations went for operational excellence: cutting costs by standardising, reusing what was there, and making the best possible use of the available capacity. A central service with its own entrance belongs to that. It is a defensible design, and for many organisations it was the right one at the time.
When the work sits inside the business, there is usually no seam. It appears as soon as a team is taken out of it and starts serving the rest of the organisation.
Procurement is the clearest example of that. One function buying for the whole needs fewer people than every entity separately, and whoever pools the volume gets a better price than whoever calls on behalf of one department. On top of that, not every entity has to build the competence itself. Those three reasons still hold today, and they do not go away because a seam comes with them.
Most seams did not come about that way. They grew. A service was added, a department split, a merger brought two structures together, somebody took work over because there happened to be time. Nobody ever drew that line and nobody ever approved it.
The consequences are the same, whether the seam was drawn on purpose or simply grew. It is still there, but has probably never been looked at again since. Who drew it does not matter. The question is whether it still serves anything.
A reason can also move house. Fifteen years ago the weight sat with the technology choice. A new website was built in Drupal, and having that decision sit with IT saved the organisation a lot of money and trouble. Today the weight sits more with privacy and security, and that seam defends itself. The old one is usually still lying there, around a choice nobody needs to guard any more.
What falls through
A seam has a price, and it is paid mostly by whoever has to deal with the exceptions. Everything that is not standard ends up in the seam. A new instrument. A project that has to take priority. A departure from what was agreed. Each of them an exception to what the organisation was optimised for. Someone has to lift them over the seam by hand.
That lifting takes time. Every seam brings its own people, priorities and decision making. So what lands in it does not fall straight through. First it sits there.
What happens when the organisation moves
That price stays bearable as long as both sides keep roughly the same pace. That stops the moment the business changes how it works in order to keep meeting what its customers ask.
The seam is stretched. The existing agreements no longer suffice, exceptions pile up, and the distance between the two sides grows.
Both sides then stop seeing each other's interests and needs. The business sees a service that says no. The service sees a stream of exceptions to a way of working that exists for a reason. Both readings are honest. Neither is complete.
From that moment the same words mean something different on either side. An urgent request, a simple change, a finished result. A handover that takes too long, you can speed up. But that does not help here, because the two sides mean different things.
Why we patch instead of moving the seam
The answer is nearly always another body. A steering committee. A list of approved exceptions. A review board. Each of them arrives to make the handover run better, and each of them becomes part of how the organisation works.
A body that puts the right people around one table does real work, and for some seams it is the right answer. The difference lies in when the two options deliver something.
A new board is quick. The board sees the pain, shortly afterwards there is a board, and the organisation looks as though it can respond. Changing how teams and departments work together takes far longer, and it needs someone who keeps saying month after month why it was started. That attention usually fades before the work is finished. Then the change gets stuck halfway.
So it becomes another patch. A stopgap delivers something too, as long as the attention lasts. It just does not move the seam.
A table added every year, and the opening is still as wide at the bottom as at the top.
Add a body every year and after five years you have five tables and the same line.
How many coordinating bodies have been added around this one handover in the past five years?
And which of them has ever been disbanded since it was set up?
A temporary solution that stays in place acquires an interest of its own over time. A body has members for whom it is a seat at the table. A role has a contract. Nobody agrees in advance when it ends, and by the time someone asks the question, the other side can no longer do without it. Removing the patch therefore takes something away from someone. That is what makes it hard, quite apart from whether it is a good idea.
The seam is a choice, even when nobody made it
What nobody revisits is the seam itself.
Take the teams you have today and cut them three different ways.
The teams and the people stay the same, only the boundary sits somewhere else each time. That changes what gets stuck between the teams as well.
The line stands vertical
Cut by function
The usual arrangement. The business on one side, the central service on the other, and everything that crosses the line calls for a handover. The request that is not standard gets stuck, because neither side has a place for it. The gain is depth of craft and scale, and that gain is real.
The line tilts
Cut by layer
Not the business against the service, but those who decide against those who carry out. Both sides then sit together in the same layer. What falls through changes with it. No more requests, but escalations. That is a different complaint, and different people voice it.
The line disappears within the stream
Cut by value stream
You bring the skills and the responsibilities together around the same result. Part of the handovers disappears, another part shifts to the boundary between two streams, and work falls through there again. Specialists also end up scattered, and have to keep finding each other in another way.
Where you put the line decides what has to cross a boundary every day.
That makes the seam in your organisation not a fact but a consequence. That is something other than a mistake, and it is also something other than untouchable.
Moving a seam is expensive. It takes months, it touches who decides what, and it takes people out of a place they have become good at. That is a reason to look carefully at which seam you take on, and not a reason to leave every one of them alone.
Not every handover should go
Not every handover is a patch. Some are there on purpose and have to stay.
Handovers that stay
Whoever needs something does not award the contract themselves, wherever the amount or the risk warrants it. Otherwise the same person chooses what is bought and from whom.
Whoever books an invoice does not approve it themselves. Two pairs of eyes, so that one mistake is not enough.
Whoever administers a system does not grant themselves rights in it. Otherwise nobody can check afterwards who was allowed to do what.
Whoever processes personal data has to be able to point to who is responsible for it. That is a legal duty and not an internal agreement. What is required is that the ownership stays identifiable, not that a handover is built around it.
Risk, compliance and internal audit do not report to the department they check. Whoever checks their own work checks nothing.
In regulated environments certain independence requirements are also explicitly imposed. Which ones exactly depends on the activity and on the framework that applies to it. Where they apply, the question is not whether the handover stays, but how quickly it runs.
Those handovers have one thing in common: the judgement loses its value as soon as the same party does both sides. The separation has to stay there, because it protects that very judgement.
Then ask one thing. Is an independent judgement needed here, does a conflict of interest have to be ruled out, do you have to be able to show who is responsible, or does impartiality have to be guaranteed? If so, the handover stays, and it is at most about how quickly it runs. If not, it is design, and then the question may be asked.
There is a second brake, and it is about scale. A central service with its own entrance is not wrong because it is central. Do not look only at the difference between standard and exception, but above all at how much work the exceptions add up to. If most requests fit the standard, nine in ten say, that standard is doing its work and the seam is cheap. Where that ratio sits exactly differs per service, and it is not a norm. The problem starts once the exception has become the ordinary case. Then what the organisation treats as the exception is the work itself.
Three questions about one seam
The first four questions say whether a handover was designed on purpose. These three help you decide what to do with it. Does your operating model still support the way the organisation has to work today?
1
What does this handover protect?
Sometimes it protects something that still holds: that somebody other than the requester judges, that not everyone can reach all the data, or that it is clear who is responsible. Sometimes it only protects the efficiency of the past: one place that pools the work, and one way of doing it. That second one was right once, and may not be any more.
2
What falls through it?
Put the exceptions of the last few months side by side. Do they keep coming from the same department, or are they always about the same kind of request? If there is a pattern in them, that pattern tells you where the line sits wrong. If there is no pattern, it was simply busy, and then there is nothing to move.
3
Who would have to give something up to move it?
This is the most important of the three, and usually the one asked last. If nobody has to give anything up, a better agreement or a smoother exchange may be enough. If someone does have to give up authority, budget, people or the certainty that their own figures keep adding up, you have to arrange the organisation itself differently. And that is exactly what no meeting resolves, because every member of that meeting is held to account by their own department once the meeting is over. Then the answer is a team or a moved boundary, and the answer to this question tells you straight away why the seam still sits where it sits.
Which form fits
The first two questions tell you which seam to take on. The third decides which form fits.
Sometimes the cheapest intervention is not on the seam but beside it, by making sure fewer cases have to cross. What remains after that calls for one of three forms: the handovers stay where they are but are chosen, the cut moves to deciding against carrying out, or it disappears within a single value stream, for the work that fits in that stream.
We start from your strategic plan and from how work and information run through your organisation today. From that follows where the seams are and which of them still have a reason. We make the design with a group from your own people, because whoever has to carry a change helps design it.
We do not fill roles and we do not take work over. We stop when the new way of working is the ordinary way of working. Read more about how we work →
When this helps
This helps when every proposal that departs from the standard gets stuck somewhere, and the answer to that is another meeting every time. And above all when you are about to set up a new body. Work through the three questions above first, because they tell you whether that body is the answer or the next patch. If you cannot tell which of the two it is, that already says something. A handover that was once designed can be explained.