Backward-Design a Follow-Up
Design a trackable follow-up that checks behavior instead of vague intention.
The lesson promises a check-in but the action is too vague to verify. Kirkpatrick pushes designers to start with behavior and results, then define the evidence a follow-up can reasonably check. The common trap is writing motivational action prompts that sound good but cannot be observed. Name the behavior Specify the work act: "prepare a BATNA before the vendor call." Behavior beats intention because it can be recognized later. Name the evidence Choose a lightweight proof: a prep note, calendar invite, drafted script, or completed checklist. Evidence keeps the follow-up honest without creating surveillance. Write the check Ask, "Did you…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in