LEARN. PRACTICE. GROW.Prepare the question and participation
“How do we convince APS to accept our solution?” already selects a solution and an opponent. In the Horizonte case, a useful question concerns the conditions making work wait and alternatives the group can explore. Explain the purpose, needed information, and decision possible in the session. Provide the question in writing and reflection time before discussion, particularly when participants are working in a second language. The 1-2-4-All technique is an optional reference for collecting perspectives; it is not a Scrum obligation. If remote rooms fail, adapt logistics to achievable participation. Do not record consent from someone unable to hear or respond. Separate idea collection from evaluation against criteria. Hearing a proposal does not require accepting it, but rejecting it before understanding can hide important information. Avoid treating a director’s opening contribution as the session’s consensus result.
Facilitate without fabricating authority
In the Ponte case, the Scrum Master has observability experience and a proposal to reduce alerts. She can contribute if she states when she is presenting her own hypothesis rather than an agreed summary. If needed, another participant can facilitate that part of the comparison. The group may recommend a change, but a vote does not replace the security authority absent in this scenario. Record the recommendation, risks, evidence, and pending decision. When time ends with uncertainty, identify who will clarify it, by when, and where the decision resumes. Extending indefinitely creates no mandate; declaring consensus through fatigue does not either. For impediments shared by multiple teams, find those who participate in and decide about the affected flow. Repeating the same internal action in three retrospectives may simply reproduce missing access to the decision. Facilitation aims to make the next action understandable and possible.
Interpret the result without changing the question
In the Prisma example, there are three days to validation and another five in that stage without overlap. The complete workflow takes eight days. If the dashboard starts ending at validation entry, it shows three, but the user still waits eight. Compare equivalent boundaries and publish the definition change. In a second exercise, an item started Monday at 09:00 and still open Thursday at 09:00 has 72 elapsed hours of age even if it waited 48 for access. In a third, completed times of 1, 1, 1, 1, and 16 have a mean of four and median of one; the sixteen-day item does not disappear because it is inconvenient. These are local calculations on fictional data, not DORA metrics or a deadline guarantee. Retain observations that contradict the hypothesis. If a check created after an incident still accepts the invalid configuration in rehearsal, code delivery does not demonstrate prevention. Reopen effectiveness analysis with an owner and fresh verification.
Horizonte rehearsal with new information
Prepare a 35-minute rehearsal with a facilitator, APS, development, security, and an observer. Use five minutes to define the problem and mandate: the session recommends, while final change authority is absent. Reserve ten minutes to collect perspectives; introduce an APS audio failure and observe whether silence is treated as agreement. During the next ten, present the “eight to three days” chart and then reveal measurement boundaries. The group should revise its conclusion. Use the final ten to close the recommendation, open question, owner, and deadline, and conduct debrief. Produce a note separating facts from interpretations and a record of the pending decision. The observer assesses inclusion, correction when new evidence arrives, mandate boundaries, and follow-up clarity using observation states without an aggregate score. This rehearsal was authored as supervised practice; no human execution or assessment of real people occurred. Conclusions must respect that limit.
HORIZONTE GUIDE | 35 min: 5 + 10 + 10 + 10
Observed problem:
Session question:
Who can recommend / who can approve:
Contributions and participation barriers:
Facts / interpretations / questions:
Previous metric: start ___ finish ___ value ___
New metric: start ___ finish ___ value ___
Conclusion revised with new evidence:
Recommendation / unresolved risk:
Next decision / authority / date:
Action / owner / expected evidence:
Observation: not observed | with help | in rehearsal without help“The metric fell, but the boundary changed. We have not yet demonstrated reduced full-flow time; let us compare the same workflow.”
Common pitfalls
Silence as consent; facilitator opinion as agreement; majority as authorization; changed boundary as improvement; delivered action as demonstrated prevention.
Related topics: Inclusive facilitation · Flow metrics · Incident learning
A useful session produces understood information, a valid decision or an owned next step, and openness to correcting the conclusion.
Reference: 1-2-4-All · Scrum Guide November2020; Kanban Guide May2025; EBM May2024; primary guidance reviewed 2026-09-30