Structure a retrospective question flow with ORID so the team learns before deciding.
The team's retro jumps straight to fixes after a sprint miss. The first proposed solution is "make standups longer," but no one has named the pattern. ORID: Objective -> Reflective -> Interpretive -> Decisional The common trap is asking "What should we change?" first. That feels action-oriented, but it lets the most available complaint choose the solution before facts and meaning are clear. Objective Ask: What happened in the sprint that anyone can verify? This creates shared ground: four stories entered QA late, two acceptance criteria changed, one dependency arrived Friday. Reflective Ask: Where did the work feel most surprising…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in