Skip to main content

Rebuild a retro with ORID

Structure a retrospective question flow with ORID so the team learns before deciding.

curiosity-at-work5 min read

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…

Read the full lesson

Sign up free: one personalized lesson every day, matched to your role and goals.

← Back to library

Contact us