Map development moves by risk and proof
Evaluate development moves by how much proof they create versus how much exposure they carry.
Exposure / risk Lower Higher Proof of next-level readiness Avoid Low proof · High exposure Examples include oversized stretch assignments with vague authority. They feel bold but generate messy data and avoidable damage. Sweet spot High proof · High enough challenge A defined workstream, visible decision forum, or recommendation section with sponsor support. This is where most targeted stretch design should live. Starter reps Low proof · Low exposure Shadowing, observation, or internal rehearsal. Useful as preparation, but not enough by themselves to prove readiness. Use selectively High proof · Low exposure Rare but valuable moments where a learner can…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in