Model

Ownership with mandate

"Could you keep an eye on it?" That one sentence is where many changes die a quiet death. Whoever has to guard a way of working after the project needs more than a friendly request: a named role, time to take it on, and the standing to say something.

could you keep an eye on it? week 1 week 5 week 12 the expectation evaporates
Frame 1 · The friendly request

"Could you keep an eye on it?"

Well meant, and predictably without effect. No time freed up, no standing attached, nothing agreed. Three months on, nobody remembers who was going to keep an eye on it.

the quality of this way of working the owner everyone knows whose door to knock on
Frame 2 · The domain

Name what someone guards

Not "keep an eye on it", but: you guard the quality of this way of working. A domain with edges. The owner knows what to watch for, and everyone knows whose door to knock on.

time, in the hours the manager signs off so the role survives the busy weeks
Frame 3 · Time and standing

A role without time is a wish

The manager signs off: the guarding happens in working time and it counts. And the organisation visibly backs the role, so raising something is the agreement talking, not a colleague being difficult.

agreement 1 March agreement 2 review now agreement 3 June agreements that put themselves on the agenda
Frame 4 · The expiry date

No agreement is settled for good

Every working agreement gets a date on which it is looked at again: does this still work, or have we drifted from it, and was there a good reason? Departures come up on their own that way, with nobody telling tales.

manager how is it going with the new way of working? in the meeting that already exists
Frame 5 · The manager

One question, at a fixed moment

Nothing predicts whether behaviour sticks more strongly than whether the direct manager asks about it. Built into a meeting that already exists: no extra meeting, but a steady signal that this is the normal way of working.

the new way of working domain time and standing review date the question small apart, strong together
Frame 6 · The whole

Four anchors under one way of working

A named domain, time and standing, agreements with an expiry date, and a manager who asks about it. Each anchor is small. Together they hold the way of working in place when the attention moves on.

What this is about

After roll-out, someone usually does get asked to follow up on the new way of working. The problem is how that request sounds: informal, in passing, without agreements. An expectation like that evaporates within weeks. This model gives ownership a fixed shape: a named domain, time, standing, and agreements that put themselves on the agenda.

Why the friendly request does not work

"Could you keep an eye on it?" is well meant, and it fails predictably. Not through unwillingness, but through what is missing. No time has been freed up, so following up competes with the ordinary work every day, and loses. No standing is attached, so whoever speaks to a colleague about an old habit does so in a personal capacity and soon feels like the difficult one. And nothing has been agreed about what following up means, so nobody can say whether it is happening or not.

Three months on, nobody remembers who was going to keep an eye on it. That is nobody’s fault. It is the predictable fate of an expectation without a shape.

A named domain

The alternative starts with naming. Not "keep an eye on it", but: you guard the quality of this way of working. That is a domain, with edges. The owner knows what to watch for: is the way of working being followed, are workarounds appearing, do new colleagues find their way into it easily? And everyone knows it is them. Anyone with a question about the way of working knows whose door to knock on. Anyone who sees a problem knows who to report it to.

Often these are the people who helped shape the change. They know the way of working from the inside, and their colleagues know them. The domain turns that informal position into a recognised role.

Time and standing come with it

A role without time is a wish. So the owner’s manager signs off as well: guarding the domain happens in working time, and it counts when someone’s contribution is reviewed. That sounds administrative, but it is the difference between a task that exists and a task that disappears in the first busy period.

Standing does not mean the owner becomes the boss. It means the organisation visibly backs the role: when the owner raises something, that is the agreement talking, not a colleague being difficult. That one difference decides whether anyone dares to raise it.

Agreements with an expiry date

The strongest habit in this model: give every working agreement a date on which it is looked at again. No agreement is settled for good. On the agreed day the team asks itself: does this still work, or have we quietly drifted from it, and did that drift perhaps have a good reason?

That looks like extra work, but it solves two problems at once. Departures come up on their own, at a planned moment, without anyone having to tell tales on a colleague. And agreements that no longer fit get adjusted instead of ignored. A way of working that grows with the work draws no resistance. A frozen one does.

The manager makes the difference

One factor predicts whether new behaviour sticks more strongly than any other: whether the direct manager asks about it. Not checking, asking. A manager who pauses on the new way of working in the weekly meeting now and then, who asks how the new system is going on a walk round the floor, signals without any grand words: this is the normal way of working here.

So we turn those questions into a fixed habit, built into a meeting that exists anyway. It costs no extra meeting. It costs one question, at a fixed moment, from the right person.

How we go about it

We fix the ownership before roll-out, together with the owners themselves and their managers. For each domain it is on paper who guards it, how much time that takes, and when the agreements will be looked at again. That document is half a page, not a handbook. The strength is not in the text, but in the conversation where everyone at the table says yes out loud.

And we build the managers’ questions into existing meetings, so the attention stays without anything being added. Read more about how we work →

When this model helps

At the point where roll-out is near and the question comes up of who takes it on afterwards. Earlier is better: knowing the owners during the design lets them help build what they will later guard. And it helps afterwards too, with a change that is slipping away: naming an owner after all, with time and standing, is the fastest way to get it back on track.

Who guards your new way of working, and do they know it themselves?

In a conversation we look together at how to give your ownership a fixed shape: named, with time, and backed by the managers.