Create a ladder-gap map with behavior, current evidence, missing proof, and next experiment.
Mika wants Staff Engineer, but her goal is phrased as "more influence and bigger architecture scope," which is not yet a plan. Ladder-gap map: target behavior -> current evidence -> missing proof -> work experiment -> review date The common trap is listing broad senior-sounding traits without separating what is already proven from what still needs evidence. Target behavior Select one ladder phrase: "creates leverage across teams through reusable technical direction." One phrase prevents the plan from spreading across every possible Staff expectation. Current evidence Write the proof already visible: checkout design review improved one team's API consistency. Current evidence…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in