This case is entirely constructed. The weeks, the exchanges and the numbers illustrate one possible sequence. Six weeks is neither a required duration nor a promise that a team will be transformed.
A small team handles the welcome for people attending training sessions. Jo and Lina work at two different sites. They are already convinced that handing files over better is worth doing, but they can neither change access rights nor commit to a purchase. Their manager, Samira, can authorise a trial procedure. Nora, a colleague from another activity, offers bounded help with a review.
The request and the backing agreed
Jo makes a concrete request:
We propose trying a handover sheet for ordinary sign-ups at one site. We keep the current controls. We need forty-five minutes of preparation each, and fifteen minutes of review at the end of each week where a case came up. We propose pushing back the visual redesign of the welcome sheet. Samira will decide with us after the first observations.
Samira accepts that remit and the work displaced. She refuses, however, general access to the other site’s files: some of that information is not needed for the trial. Jo and Lina do not copy those files elsewhere to get round the refusal.
Nora sets out her help:
I can give thirty minutes to review a fictional case with you in week 2. I’ll look at whether the recipient understands the next action. I approve neither the access rights nor the business procedure. After the review, my commitment ends, unless we agree something new.
That is useful backing with no hierarchical power and no new permanent obligation.
The log of decisions and results, filled in
| Moment | Fact examined | Decision and next step |
|---|---|---|
| Week 1 | Of six recent handovers we can reach, three had needed a clarification about the next action. | Choose an ordinary remit; note the load and the exceptions too. No numeric target is imposed. |
| Week 2 | Nora cannot tell who confirms receipt in the fictional case. | Add “handover accepted by” and the contact if it gets stuck. The two peers test reading it remotely. |
| Week 3 | Of four new handovers, two need a clarification. One recipient has no access to the linked document. | Pause that case and have Samira handle the access. The other cases stay inside the authorised remit. |
| Week 4 | The recipient of the paused case gets the access and accepts the handover. The sheet covers one exception badly. | Resume the ordinary case; keep the usual route for exceptions. Do not widen the sheet. |
| Week 5 | Of five ordinary handovers, one needs a clarification. Preparation stays light according to both users, with no precise measure. | Keep this version one more week; ask the recipients for feedback too. |
| Week 6 | The recipients we asked identify the next action better. A doubt remains about absences and the total cost. | Keep the small remit, name a cover arrangement, and plan a review next cycle. Stop the detailed weekly record. |
These periods hold few cases and are not directly comparable. The numbers show observations to discuss, not proof that the sheet caused a general improvement. The paused case counts in the record of limits; it is not erased to make the account look better.
The six-week account
- What was done: a sheet, some attempts, a peer review, and one access clarified for one file.
- What was observed: the recipients we asked find the next action more easily; questions persist in some cases.
- What is still unknown: the total time saved, the effect on exceptions, and whether it holds during an absence.
- Cost: preparation and feedback took the agreed slots; one piece of formatting was deferred. Nora finished her contribution after the review.
- Decision: keep the sheet for ordinary cases, name a cover arrangement, and check that point next cycle. No roll-out to the second site for now.
- Responsibilities: Lina maintains the template with Samira’s agreement; Jo flags difficulties in use; Samira handles access and rules on the load. They revisit those commitments if one of them no longer has the capacity.
The meeting held and the document written are not the results on their own. What matters is what people can now do better, with the limits still in view.
If the environment stays closed
Here the refused access made a bounded alternative possible. That is not always the case. If the manager also refuses the trial, Jo can ask which constraint is in the way and propose a smaller version, with no new data and no change to the process.
An ally can help shape that proposal or find the right person to ask; they do not supply the missing authorisation. After a clear and sustained refusal, Jo does not chase indefinitely and does not move the work into his evenings. He notes what is still blocked, asks whether the original commitment has to be adjusted, and pauses the trial. He can choose another piece of learning inside his remit, or review his options with someone he trusts.
For a new team, starting with a fictional case helps make the words and the roles understandable. Between peers or at a distance, a shared note and agreed feedback can replace a meeting, if people can reach the material. With no sponsor, peers can examine an authorised case; any change to shared work waits for the agreement it needs.
The backing, log and account templates let you take this approach up. The session format offers a discussion around the cards.