In a multi-day workshop involving several teams, we developed a shared roadmap, concrete changes to the workflow, and a larger number of possible actions. Topics that had previously been discussed separately—or not at all—could be addressed openly. Communication between the teams became more direct and dependable during the workshop itself.
By the end, owners and deadlines had been agreed. That is more than a collection of good ideas. Even so, the impact is not determined at the moment when a card is placed on a wall or an outcome is documented. It is determined in the weeks that follow, when day-to-day work, new requirements, and familiar patterns begin competing for attention again.
Clarity in the workshop is not yet change
A workshop can create a shared perspective, enable decisions, and release energy. But it cannot anticipate how well an agreement will work in everyday practice. Some decisions still require alignment with people who were not in the room. Some actions turn out to be too large. And sometimes only practical application reveals that an agreement was understood differently.
We therefore began by distinguishing between the outcomes: What has been decided? What remains open? And what requires alignment with others? For the selected next steps, we documented not only the topics, but also owners, initial actions, deadlines, and review dates.
A good workshop outcome does more than describe what should happen. It creates a path for bringing the outcome into day-to-day work.
Four weeks of transfer in the daily
For the following four weeks, the daily is deliberately adapted as well. The workshop outcomes are regularly brought back to mind and connected with current work. This is not a full repetition of the workshop or an additional round of actions, but a focused question: Which of these outcomes matters for our collaboration and next steps today?
During this period, I continue to support the transfer. Together with the Product Owner, I work to integrate the outcomes into the existing workflow, observe their effects, and refine them where necessary. At the same time, I help the team follow through on the agreed topics, responsibilities, and deadlines.
This support is not intended to take responsibility away from the team. It creates additional focus for a limited period until the new agreements have been tested in everyday work and the team can decide what it wants to continue independently.
Do not overload the daily with another ritual
Agile routines in particular can become ends in themselves. Adding another item to the daily does not improve collaboration by itself. The adaptation is therefore designed as a time-limited experiment. It has a concrete purpose, a manageable duration, and a defined point at which its effects will be reviewed together.
What matters is not whether the modified daily was conducted exactly as planned. What matters is whether agreements remain visible, obstacles are raised earlier, and responsibility can actually be taken. If the routine does not contribute to those outcomes, it needs to be changed or ended again.
What makes a transfer phase binding
- Distinguish between outcomes: What has been decided, what remains open, and what requires alignment outside the team?
- Make responsibility specific: The first step is owned by one person, not by “the team.”
- Limit the actions: Not every insight immediately becomes additional work. A deliberate “not now” protects the team from a new backlog of measures.
- Use existing routines: Outcomes are revisited where day-to-day work is already coordinated.
- Observe the impact: Agreements can be improved on the basis of practical experience.
- Set a limit on the support: After four weeks, the team decides what remains, what needs to be adapted, and what is no longer required.
A transfer phase does not simply extend the workshop. It connects its outcomes with the reality in which they need to hold up. That is where it becomes clear whether a good conversation leads to sustainable change.
Questions for your own practice
- Which outcomes from our last workshop are still visible in day-to-day work?
- Does every important next step have one person responsible for it—including an initial action and a deadline?
- Which existing routine could support the transfer without becoming an additional end in itself?
- What would tell us in four weeks that something has actually changed?