Rewrite a retrospective agenda using ORID to move from facts to action.
Rewrite a vague sprint retro so the team can learn from reopened tickets without jumping to blame. ORID: Objective -> Reflective -> Interpretive -> Decisional The common trap is starting with 'What went well and what did not?' That prompt sounds harmless, but it lets people mix observations, feelings, explanations, and solutions all at once. The retro becomes a pile of partially true statements rather than a shared learning path. Objective Ask: Which tickets reopened, when did they reopen, and what handoff notes existed? Facts first reduce defensiveness and keep the team from arguing about memory. Reflective Ask: Where did…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in