Rewrite a vague improvement into a sprint experiment
Use a worked example to turn retrospective insight into an inspectable experiment.
Vague retro action Behavior plus trigger plus inspection signal The common shortcut is accepting a phrase that expresses team frustration but does not change team behavior. "Communicate better" sounds aligned, yet it has no trigger, no owner, and no observable signal, so it cannot be inspected next sprint. Extract the pain Ask what failure the phrase is trying to prevent. The team says dependencies disappear until the day before release. That is more actionable than "communication." Name the behavior Define what people will do differently and when. A behavior is observable. "Post owner, next decision, and due date before Daily…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in