PROCESS

Here is How to Build

Design

Principles

What signing is

A design that has been accepted is not yet a process that can proceed. Acceptance is people agreeing it is a good idea. Signing is people formally approving it, putting their name to it, committing that it may go forward. The two are different, and the difference matters.

Signing is the gate between a design and a change. Before the sign-off, you have a design that people like. After the sign-off, you have an approved process that may be built, prepared and run. The signature is what turns agreement into authority. It is the moment the people the process affects formally commit to it, and that commitment is what lets everything downstream happen. Without it, the design has no standing. You cannot ask anyone to build systems, train teams, or change how they work on the strength of a design that was never formally approved, because nothing obliges them to. The sign-off is what creates the obligation.

This is why signing is its own discipline and not a formality. A process that runs without proper sign-off runs on goodwill, and goodwill is thin. The moment something goes wrong, or someone is asked to do something they would rather not, the absence of a sign-off shows. There is no agreement to point to, no commitment anyone made, no record that this was approved. The process unravels, because it was never properly stood up. The sign-off is the foundation that everything after it rests on, and like any foundation, its absence is only felt when the weight comes on.

So signing is the deliberate act of securing formal approval from the people the process affects, before the process goes any further. It is not the end of agreement. It is the conversion of agreement into something committed, recorded, and able to bear weight.

The highest possible standard is to treat signing as the formal commitment that turns an accepted design into an approved process, securing it properly before anything is built, so that everything downstream rests on a real foundation.

Key Takeaway: Acceptance is people liking a design. Signing is people formally approving it, committing that it may proceed. Signing is the gate between a design and a change, and the signature is what turns agreement into the authority that lets building, preparing and running happen. A process that runs without proper sign-off runs on goodwill, and unravels the moment weight comes on it.

Acceptance is agreement. Signing is commitment. Only one can bear weight.

MarvinPro · PROCESS · Here is How to Build · Design · Principles · Discipline 4: Sign · Section: What signing is

MarvinPro | June 2026

marvinpro.com

Sign off the levels as the process matures

A process is not signed off in one act. It is built up in levels, and it is signed off level by level, as it matures.

You saw the levels when you designed. The process is described at L1 (Process Level 1), the broadest view, then in more detail at L2 (Process Level 2), then fully at L3 (Process Level 3), where every step appears, customer, systems, partners and team. Then it becomes department-specific at L4 (Process Level 4), each department's own view, with its swimlanes. These levels do not arrive all at once. They mature, the high-level view first, then the detail, then the department cut. And the sign-off follows that maturing. As each level becomes solid, it is signed off in the stakeholder meetings, starting at L1 or L2 and working down to L4. The sign-off grows with the process, level by level, until the final level is approved.

This matters because signing off the levels in order is what keeps the approval honest. If you tried to sign off the detailed levels before the high-level shape was agreed, you would be approving detail built on an unapproved foundation, and any change to the shape would unravel the detail. By signing off the broad levels first, you fix the shape before the detail is built on it, the same discipline as checking the design holds at its level before driving it down. Each level's sign-off rests on the approved level above it. So the sign-off matures from the top, and by the time L4 is signed off, every level beneath the agreed shape has been approved in turn.

The operational documents the team will actually use, the how-to guides, are a level below this, and they are signed off later, when the process is prepared. This chapter is about approving the process itself, the structure through to L4. Signing the guides comes when you prepare to run. So the sign-off this discipline secures is the approval of the process structure, level by level, ending when L4 is signed off, and that L4 sign-off is the gate. Once it is given, the process is approved and may be prepared.

The highest possible standard is to sign off the levels in the order they mature, from the broad shape down to the department detail, so that each level's approval rests on the approved level above it, ending with the L4 sign-off that approves the process to be prepared.

Key Takeaway: A process is signed off level by level as it matures, in the stakeholder meetings, starting at L1 or L2 and working down to L4. Signing the broad levels before the detailed ones keeps the approval honest, because each level rests on the approved level above it. The operational guides are signed later, in preparation. The L4 sign-off is the gate: once given, the process is approved to be prepared.

A design that is right for today and impossible to extend tomorrow is a bill you have deferred.

MarvinPro · PROCESS · Here is How to Build · Design · Principles · Discipline 4: Sign · Section: Sign off the levels as the process matures

MarvinPro | June 2026

marvinpro.com

Scope is not authority

Here is a hard truth about signing off a process that crosses an organisation: the person who owns the process end to end may not have authority over all the parts it crosses. Scope and authority are not the same thing.

A leader can be given the end-to-end scope of a process, responsibility for the whole of it, from the first step to the last, while sitting in just one part of the organisation. The process runs through their own area, and then through others, after another department, a different function, a separate reporting line. Over their own area they have authority. Over the others they have only their scope, the responsibility for the whole, without the power to direct the parts that belong to someone else. They own the end-to-end, but they cannot command most of it. This is extremely common, because processes cross organisational boundaries while authority stops at them. The end-to-end owner sits somewhere, and wherever they sit, the process leaves their authority long before it leaves their scope.

This gap between scope and authority is the central difficulty of signing off a cross-organisation process. To get the process signed off, the end-to-end leader needs the approval of the department leaders whose areas the process crosses, and over most of them they have no authority. They cannot sign on those leaders' behalf, and they cannot make them sign. They can only bring them to it, the way a design is brought to acceptance, through the picture, the reasoning, and the relationships built earlier. So securing sign-off across a process is rarely an exercise of authority. It is an exercise of persuasion and trust across boundaries the owner does not control, and the wider the process spreads across the organisation, the more of its sign-off lies outside the owner's authority.

It helps to see this clearly rather than resent it. The end-to-end leader who expects to command the sign-off will be frustrated at every boundary. The one who understands that scope is not authority approaches it differently, gathering the department leaders' agreement one relationship at a time, knowing that the signature of someone you do not control is given, not taken. The authority gap is not a failure of the role. It is the shape of the role, and working within it is the discipline.

The highest possible standard is to understand that end-to-end scope does not carry authority over the whole, and to secure the sign-off of the department leaders the process crosses through reasoning and trust rather than expecting to command it.

Key Takeaway: A leader with end-to-end scope owns the whole process but often has authority only over their own part of the organisation. Scope and authority are not the same, and the process leaves the owner's authority long before it leaves their scope. So securing sign-off across the boundaries is an exercise of persuasion and trust, not command, because the signature of a department leader you do not control is given, not taken.

You can be given the scope of the whole and the authority of only a part. The signature you cannot command, you must earn.

MarvinPro · PROCESS · Here is How to Build · Design · Principles · Discipline 4: Sign · Section: Scope is not authority

MarvinPro | June 2026

marvinpro.com

The process no one owns

If a process with one end-to-end owner is hard to sign off, a process with no owner at all is harder, and it is more common than it should be. Some processes float between areas, belonging fully to none of them.

A process can run through two departments and sit clearly inside neither. Each department sees part of it and treats that part as someone else's responsibility at the edges. The whole, the thing that crosses between them, belongs to no one. And a process that belongs to no one does not get signed off, because there is no one whose job it is to secure the sign-off. It simply sits. Worse, it does not sit still, because work keeps arriving. The backlog of the unowned process grows, the problems in it go unsolved, and everyone can see it getting worse while no one is responsible for fixing it. Compartmentalised ownership, whether by department, or by the split between global and regional, or between a centre and its markets, leaves these floating processes in the gaps between the compartments, and the gaps are exactly where no authority reaches.

What resolves it, when it resolves, is someone choosing to own it. Not being given it cleanly, there is no one to give it, but stepping into the gap because the work is there and growing and no one else will. Often this is a leader who already owns other things, who takes on the floating process on top of a full load, not because it is theirs by right but because the cost of its remaining unowned is too visible to ignore. That choice, to own the unowned, is what makes the sign-off possible at all, because now there is someone whose job it is to secure it. Until someone owns it, no amount of meetings or goodwill moves it, because securing a sign-off is work, and work without an owner does not get done.

So the unowned process is a particular failure of sign-off, and it is worth naming because it is so often mistaken for a people problem or a priority problem when it is really an ownership problem. The process is not stuck because the department leaders are difficult or because it is unimportant. It is stuck because no one owns getting it signed off. Give it an owner, even one who takes it on themselves, and it can move. Leave it ownerless, and it stays in the gap, its backlog growing, until someone steps in or it becomes a crisis.

The highest possible standard is to recognise a process that floats unowned between areas, and to see that it will not be signed off until someone owns it, even if that means a leader choosing to take on the unowned work because the cost of leaving it is too high.

Key Takeaway: Some processes float between areas and are owned by none, and an unowned process does not get signed off, because no one's job is to secure it, while its backlog grows. Compartmentalised ownership leaves these processes in the gaps where no authority reaches. What resolves it is someone choosing to own the unowned work, often a leader already carrying a full load, because until there is an owner, the sign-off does not get done.

A process that belongs to no one is signed off by no one. Its backlog grows in the gap until someone steps in.

MarvinPro · PROCESS · Here is How to Build · Design · Principles · Discipline 4: Sign · Section: The process no one owns

MarvinPro | June 2026

marvinpro.com

When ownership is unclear, sign-off can stall

When ownership of a process is clear, sign-off is hard but it moves. When ownership is unclear or contested, sign-off can stall, and the stall has a shape worth knowing, because if it runs long enough it ends in a worse place than where it began.

Here is how the stall tends to go. Ownership is not held steadily but passes back and forth, picked up by one area, then set down, then claimed by another, like a light changing. No one holds it long enough to drive the sign-off through. Sometimes a group is formed to solve it together, a task force drawn from the areas involved, and the group struggles, because a group of people none of whom owns the outcome is a group that can discuss but not decide. The task force may fail to deliver, for the same reason the process was stuck in the first place: shared responsibility with no single owner is no responsibility at all. And while this goes on, months pass. A sign-off that should have taken weeks can run half a year, and the process sits unapproved while its backlog grows and the situation slides from a problem toward a crisis.

If it does reach a crisis, the resolution is often worse than a timely sign-off would have been. Under pressure, leadership may appoint someone to own it quickly, often someone who does not know the process deeply and must learn it under time pressure, and whose brief is to solve the immediate crisis rather than to design well. They get it signed off, but it is a sign-off shaped by urgency, fixing the present problem and not scoping the future, missing the forward-looking design that a standing owner would have built in. So the cost of the stall is not only the months lost. It is a process signed off in haste that will need redesigning sooner than one signed off properly would have.

Behind all of this is a simple dynamic worth understanding. Stakeholders agree more readily when there is an accountable owner, because the owner carries the responsibility and, if it goes wrong, the failure. The department leaders can sign knowing that the owner is the one accountable for the outcome, which frees them to agree. When there is no owner, that reassurance is gone. Every stakeholder is partly on the hook and none is fully in control, so each is cautious, and caution from everyone is how a sign-off stalls. The owner does not just drive the sign-off. The owner's accountability is what makes the others willing to give their signatures at all.

The highest possible standard is to recognise that unclear ownership puts a sign-off at risk of stalling, with the cost of months lost and a crisis-driven approval that scopes only the present, and to see that an accountable owner is what makes stakeholders willing to sign in the first place.

Key Takeaway: When ownership is unclear, sign-off can stall: ownership passes back and forth, a task force without a single owner fails to decide, and months pass while the backlog grows. If it reaches a crisis, a hurried owner may be appointed who fixes the present without scoping the future. Stakeholders sign more readily when an accountable owner carries the risk and the failure, so the owner's accountability is what makes the others willing to sign.

Shared responsibility with no single owner is no responsibility at all. That is how a sign-off stalls.

MarvinPro · PROCESS · Here is How to Build · Design · Principles · Discipline 4: Sign · Section: When ownership is unclear, sign-off can stall

MarvinPro | June 2026

marvinpro.com

Securing the sign-off

Knowing who must sign and why it matters is one thing. Actually getting the signatures is another, and it comes down to two things: reaching the right people, and recording what they approve.

The right people are the department leaders whose areas the process crosses, together with the stakeholders who approve the higher levels as the process matures. The end-to-end leader secures each of their sign-offs, and where the leader lacks authority over an area, this is done the way a design is accepted, through the picture, the reasoning, and the relationships built earlier. When a meeting of everyone together is the way to reach agreement, that is where the levels are signed off. But when the collective route stalls, agreement can still be reached one leader at a time, in individual sessions, each department leader brought to the sign-off on their own terms. The signatures add up to the same approval, gathered singly rather than all at once. The training function is among those who sign, because training material is reviewed and approved too. Where there is an end-to-end owner, the training sign-off sits under them. Where there is none, the training function becomes another stakeholder whose approval must be secured.

Recording the sign-off is the second half, and it is what makes the approval durable. A sign-off that lives only as a verbal agreement in a meeting is a sign-off that can be denied later. So each level's approval is documented, with who approved it and when. This can be as simple as the approval captured on the process map with the email thread that records it, a working method that holds. A more robust way is a formal digital sign-off system, where each level is signed electronically, leaving a clear and durable record of who approved what and when. Whatever the form, the principle is the same: the sign-off is recorded, per level, so that when the process is questioned later, and it will be, there is a record to point to. An approval you cannot show is an approval you may have to win again.

So securing the sign-off is the practical close of this discipline: reach every department leader and stakeholder whose approval the process needs, collectively where that works and individually where it does not, and record each level's approval so it holds. Done well, you end with every level approved through L4, documented, and a process that is now ready to be prepared.

The highest possible standard is to secure the sign-off of every department leader and stakeholder the process needs, collectively or one at a time, and to record each level's approval with who gave it and when, so the sign-off is durable and can be shown when the process is later questioned.

Key Takeaway: Securing the sign-off comes down to reaching the right people and recording what they approve. The right people are the department leaders whose areas the process crosses and the stakeholders for the higher levels, reached collectively when that works and individually when it stalls, with the training function among them. Each level's approval is recorded, with who and when, from the process map with its email thread to a formal digital sign-off system, so the approval is durable and can be shown when the process is later questioned.

An approval you cannot show is an approval you may have to win again. Record who signed, and when.

MarvinPro · PROCESS · Here is How to Build · Design · Principles · Discipline 4: Sign · Section: Securing the sign-off

MarvinPro | June 2026

marvinpro.com

A real example

A process leader held the end-to-end ownership of a process that floated between two areas of the organisation. It belonged fully to neither, and for a long time it had been owned by no one. The work kept arriving, the backlog kept growing, and there was no solution in sight. The leader already owned other areas, a heavier load than the other leaders carried, and took this floating process on anyway, not because it was theirs by right but because the work was there and no one else would own it.

From the start, the difficulty was the gap between scope and authority. The leader owned the process end to end, but sat in one part of the organisation and lacked full authority over the others it crossed. Over those areas the leader had the responsibility for the whole and the power to direct none of it. And the ownership itself was never stable. It was picked up and set down, claimed and released, passing back and forth like a light changing, never held by anyone long enough to be driven through. At one point a task force was formed to resolve it together, and the task force was unable to deliver, because a group in which no one owns the outcome can discuss but cannot decide. Months went by this way. The sign-off that should have been straightforward ran for around half a year while the backlog grew.

What finally moved it was not authority and not the group. It was the leader securing the sign-off one party at a time, in individual sessions, on the strength of the original design, which had been sound all along. The delay had never been a fault in the design. It was the absence of stable ownership and the gap in authority. The leader, who was closest to the true end to end and saw the whole as no one else did, brought each party to the sign-off individually, and gathered the approvals that the collective route had failed to produce.

The other thing that made it work was a partnership already in place. The leader worked closely with another leader whose ownership covered the area the floating process most needed to join with, and the two had already worked together on another area, where their responsibilities overlapped. That earlier shared work had built the trust between them, and it was that trust, not any reporting line, that let them span the full end to end together. With the sign-off secured and the two of them covering the whole between them, the process was successfully implemented. The argument over who should own it was never won on paper. The work got done because someone chose to own it and someone they already trusted helped them carry it.

The signature that resolved it was given to a relationship, not to a role. The trust had been built long before it was needed.

MarvinPro · PROCESS · Here is How to Build · Design · Principles · Discipline 4: Sign · A real example

MarvinPro | June 2026

marvinpro.com

Sign

Signing is the formal approval that turns an accepted design into a process that may proceed. Acceptance is agreement; signing is commitment, the signatures of the people the process affects, putting their name to it and creating the obligation that lets everything downstream happen. A process that runs without proper sign-off runs on goodwill, and unravels the moment weight comes on it. So you sign off the levels as the process matures, from the broad shape at L1 or L2 down to the department detail at L4, each level resting on the approved level above it, until the L4 sign-off gives the gate that approves the process to be prepared.

The difficulty of signing a process that crosses an organisation is that scope is not authority. A leader can own the whole end to end and have authority over only their own part of it, so securing the sign-off of the department leaders the process crosses is an exercise of persuasion and trust, not command, because a signature you cannot compel is given, not taken. Harder still is the process that floats between areas owned by no one, whose backlog grows in the gap until someone chooses to own it. And where ownership is unclear or contested, the sign-off can stall, ownership passing back and forth, a task force unable to decide, months lost, until in the worst case a crisis forces a hurried owner who fixes the present without scoping the future. Behind it all is one dynamic: stakeholders sign more readily when an accountable owner carries the risk and the failure, so the owner's accountability is what makes the others willing to sign at all.

Securing the sign-off, in the end, is reaching the right people and recording what they approve. You bring each department leader and stakeholder to the sign-off, collectively where that works and one at a time where it does not, the training function among them, and you record each level's approval, who gave it and when, from the process map and its email thread to a formal digital sign-off system, so the approval is durable and can be shown when the process is later questioned. Done well, every level through L4 is approved and documented, and the process is ready for what comes next.

You can now secure the sign-off of a process. You understand signing as the formal commitment that turns an accepted design into an approved process, you sign off the levels as they mature from L1 to L4, you see that end-to-end scope does not carry authority over the whole, you recognise the unowned process and the stall that unclear ownership brings, and you secure the signatures of the department leaders and stakeholders, collectively or one at a time, recording each level's approval so it holds. The process is seen, designed, and now approved through L4. Next, it must be made ready: turned into the guides the team will use, built, tested, and prepared, before it can run.

You cannot prepare what has not been approved. Sign it off, level by level, and record who signed, so the approved process can be made ready to run.

MarvinPro · PROCESS · Here is How to Build · Design · Principles · Discipline 4: Sign · Chapter Outcome

MarvinPro | June 2026

marvinpro.com

Think Simple.