Model

Standard work and bespoke work

Moving a seam is expensive, and often it is not needed. First make sure fewer cases have to cross the line. What is left after that asks for one of three forms, and which one fits depends on what the seam asks for.

Business Central service standard work, described together deviation needed? and what does it cost? bespoke work form, chosen together fixed point of contact service desk demand or portfolio
Standard work lies across the seam, because both sides described it together. Only the bespoke work crosses over.

What this is about

A seam is the line between two domains of responsibility, and everything that is not standard has to be lifted across it. Where that line comes from and how you tell whether it still serves a purpose is in The seam in the org chart. This piece is about what you do with it.

Three questions go with that. What does this handover protect? What falls through it? And who would have to give something up to move it? The first two tell you which seam to take on. The third decides which form fits.

First, fewer cases that have to cross

Sometimes the cheapest move is not on the seam but beside it. Standard work is what the central function has described together with the business and what can then be carried out. Who carries it out, the unit itself or the function, is part of that description. Everything without such a way of working is bespoke work.

That choice hangs on one condition, and it decides where the work ends up. Described is not yet executable. Whoever does it has to know the way of working exists and has to do it often enough to hold on to it. If something comes up only a few times a year in every unit, it will not land there however well it is described, and it belongs on the side where it does come up often enough.

A deviation is then first a question inside the business itself. Do we want this deviation, and do we know what it costs, in the long run as well? That cost is one more procedure, more variants side by side, and too little repetition to keep all of them in hand. If the answer is yes, it crosses over, and it can still be described afterwards and become standard work.

How the central service arranges itself for that is again an agreement with the business. A fixed point of contact, and with it straight away the question of who stands in during absence and who carries the cost. Or a service desk, or demand, or portfolio. None of those forms moves the seam. They only decide by which route the work crosses it.

When the seam itself is up

If it is only about information, an agreement or a form is the right answer and there is nothing to move. Make the handover fast and predictable then: who decides what, within what deadline, and what route an exception takes. That costs less than setting up a body and it usually works better.

If the same words mean something different on either side, a table with both sides at it helps. On one condition: it works from insight and does not decide what the other side must do. The moment it does that, it raises the demands on the other unit and takes the control capacity away, and then it makes the seam worse rather than smaller.

If somebody has to give something up, one answer holds: move the boundary. Not for the whole organisation, but for the stream the pattern of exceptions points to. Inside that stream both sides sit in the same team and there is no handover left. Outside it everything stays as it was, including the handovers that should stay.

Three forms

Which form fits depends on what the seam asks for. Three are the ones we meet most often.

The seam stays

Deliberate interfaces

Business Central service intake priority delivery

The handovers stay where they are, but each has an owner, a reason and a moment when someone looks back at it. That is the answer when only information has to cross the seam, and it is more often the right answer than moving a boundary. There are no fewer handovers than today, only now someone has chosen them.

The seam shifts

Cutting by layer

Business and central service together deciding escalation delivering

Not the business against the service, but deciding against delivering. Both sides sit together in the layer that decides, and together in the layer that delivers. The seam then runs horizontally, and what falls through it is escalation instead of requests. That helps when the delay sits in the decision making and not in the work itself.

The seam disappears

Cutting by value stream

Business Central service intake one stream, both sides in house SLA

One stream gets both sides in house and has no handover left inside that stream. That is the answer when somebody has to give something up, and it holds for that one stream and not for the whole organisation. Above and below, the seam stays, including the handovers that should stay.

That is deliberately small. One stream can be overseen, the outcome shows within a few months, and if it works you have an example in house instead of a plan. Start with the stream where the most gets stuck and where somebody is willing to give something up. Those two rarely coincide, and where they do, that is where you start.

How we go about it

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 you know which handover pinches and still have to choose what to do about it. Start with the question of whether fewer cases need to cross, because that is the cheapest. If it then turns out that someone has to give up authority, budget or people, it is a design question and not a discussion question. That conversation is no longer about which of the three forms is best.

Which handover or which board exists at your organisation mainly because it has always been there?

In a 30 minute conversation we look at where the seams in your organisation are and which of them still have a reason.