The usual career change is a clean break: leave the old field, take a course, and apply for entry-level roles in the new one. It feels decisive. It also throws away most of what made you employable.

The two axes

Every role is a function in an industry. A finance manager in healthcare is a function — finance — and an industry — healthcare.

Move one and you keep a claim on the other. A finance manager moving to finance in logistics brings ten years of finance. A finance manager moving to product in healthcare brings ten years of healthcare context.

Move both and you are competing against people who have one of them, with a story rather than evidence. That is the move that costs a level and a pay cut, and it is the one most people attempt because the new thing looks maximally different from the old one.

The bridge role

The practical route is a step that uses your old axis and requires some of the new one.

Someone moving from consulting into a product company takes a role where client-facing skill is the requirement and product exposure is the reward. A year later, the second move is internal, cheaper and easier, because the evidence now exists.

Two moves of one axis each is usually faster than one move of two, even though it looks slower on paper.

What actually transfers

More than people assume, and it needs naming to be usable. Judgment about people, running a process, writing clearly, managing stakeholders, diagnosing what is actually wrong — these carry across almost everything and are rarely listed because they feel generic.

Make them specific. "Managed stakeholders" is generic. "Ran a migration across four teams that disagreed about priorities" is evidence. See career capital.

A worked example

An accountant with eight years at a hospital system wants to work in software. Applying straight for product manager jobs at tech companies means competing with people who already have product experience, on the strength of a certificate. The likely result is a junior title and a pay cut, if an offer comes at all.

Split into two moves, it looks different. First, a finance role at a company that sells software to hospitals: her healthcare finance experience is the qualification, and she now sits next to the product team. Eighteen months later she moves into product, working on the billing features she already understands. Each step kept one axis steady, and neither meant starting over.

Test before committing

Do a version of the new work before making it your job — a project inside your current role, a small piece of paid work, a conversation with three people doing it. Most career changes that fail were changes into an imagined version of the job. See revealed preference.