Transfer and Promotion Journeys: The Moves That Fall Through Cracks

Internal moves are oddly neglected. A promotion or transfer gets a celebratory email and then half of it quietly doesn't happen, the new title lands but the pay change is forgotten, or the person keeps their old system access into a role that shouldn't have it. A journey makes the whole move land cleanly.

Sequence every consequence of the move

A transfer isn't one change, it's a cascade, new manager, new cost centre, new access, possibly new pay, new location. A journey sequences all of it so nothing gets celebrated and then forgotten.

Handle the access change both ways

A move often means new access needed and old access removed. The removal is the bit that gets forgotten, leaving people with permissions from a role they've left. Build both directions into the journey.

Get the pay and effective dates right

A promotion usually carries a pay change effective a specific date. The journey should ensure that change is made and dated correctly, not left for someone to remember after the fact.

Real scenario: a client promoted someone who kept access to their old team's sensitive data for months, because the move updated the title but nobody removed the old permissions. A journey would have handled the removal automatically. We built transfer and promotion journeys covering the full cascade, access both ways, pay, dates. Moves stopped falling through the cracks. Celebrate the promotion, but land the whole thing.