Recall responses to retrospective anti-patterns that block adaptation.
"Retros do not change anything." Say "Fair. Let's choose one change small enough to run next sprint and define how we will know it worked." Arguing that retros matter ignores the evidence of past non-follow-through. It validates the concern and narrows to inspectable adaptation. "We are too busy for improvement work." "That is exactly why we need one constraint to reduce drag, not five extra tasks." Busy teams often skip the work that would make them less busy. It reframes improvement as capacity recovery. Blame frame or system frame? System frame creates safer candor. Retro close rule Owner, trigger, evidence.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in