Back to blog
9 min readKoru Team

Career path planning when your work history is messy

Find plausible career paths in a nonlinear work history, compare them with a decision matrix, and choose the smallest useful test.

career-planningcareer-developmentprofessional-development

A messy work history does not need a better story first. It needs a better diagnosis. Ignore job titles for an hour and look for the problems, decisions, and responsibilities that followed you from role to role. Those repetitions are the raw material for your next career direction.

Career path planning, in this situation, means doing four things: finding the strongest threads in your past work, translating them into possible role families, comparing those paths, and running a small test before you commit. You are not trying to prove that every move was intentional. You are deciding what your experience supports now.

For example, a move from support to operations to implementation may look scattered on a CV. Underneath the titles, the same person may have spent years fixing customer handoffs. That thread could support customer operations, implementation leadership, enablement, or product operations. The useful question is not "Which title explains my whole career?" It is "Which direction has the strongest evidence, and what would I need to test next?"

This article helps you answer that question. Once you have chosen a direction, the personal career development plan can turn it into a longer plan.

Start with evidence threads, not titles

The National Career Development Association describes career development as an ongoing process shaped by information about yourself, the world of work, fit, and action. That framing leaves room for a career that changes shape. It also puts the burden on current evidence rather than a tidy retrospective story.

An evidence thread is a type of work that keeps reappearing even when the setting or title changes. It might be a problem people trust you to solve, a decision you repeatedly own, or a group you often help.

Reading titles

"I moved from teaching to training to customer education. I have changed direction three times."

Reading evidence

"I keep turning complex material into instruction people can use. The audience changed; the work did not."

Look for verbs before nouns. "Analyst," "coordinator," and "manager" tell you where someone sat. "Investigated," "translated," "negotiated," and "built" tell you what they can do.

Build three path hypotheses

Use this worksheet to turn past work into possible directions. Work across rows rather than completing one role at a time. Repetition is easier to see when similar evidence sits together.

Evidence-thread worksheet
PromptWhat to captureExample
Repeated problemA problem you have solved in more than one role or project.Customer information gets lost between teams.
Repeated actionWhat you actually did when that problem appeared.Mapped the handoff, clarified ownership, rewrote the process.
Outside signalWhat other people asked for, noticed, or trusted you to own.Support and Product asked me to mediate recurring issues.
ConditionsThe setting where you did the work well and wanted more of it.Cross-team work with an unclear process and a visible outcome.
Role familiesTwo or three markets that pay for this pattern of work.Customer operations, product operations, implementation.
Do not polish the language yet. "Made confusing things usable" is a better starting note than a borrowed phrase such as "strategic knowledge enablement." If your examples are hard to recall, use the weekly career journal template to rebuild the raw material.

Aim for three path hypotheses. One gives you nothing to compare. Ten usually means the evidence thread is still too broad.

See how the same method produces different paths

The method should work outside one neat office-career example. These three histories point in different directions because the repeated work is different.

Work historyEvidence threadPlausible paths

Support specialist → operations generalist → implementation lead

Finds broken customer handoffs and turns them into workable processes.

Customer operations, implementation, product operations.
Teacher → trainer → customer education contractor

Turns complex material into instruction for different levels of knowledge.

Customer education, enablement, learning design.
Research assistant → content strategist → insights coordinator

Finds patterns in scattered information and makes them useful to decision-makers.

Research operations, customer insights, knowledge management.
These are hypotheses, not conclusions. A plausible label still has to survive contact with real job descriptions and real work. CareerOneStop's career tools are one place to compare occupation language, common tasks, and training requirements.

Compare the paths instead of choosing by instinct

Now score each path from 0 to 3 against five criteria. The score is not a verdict. It forces you to make your assumptions visible.

CriterionQuestion03
Evidence strengthHow much specific past work supports this path?No clear exampleSeveral strong examples
AccessCan you observe or try this work soon?No practical accessCan test it now
Market languageDo employers describe this work consistently?Unclear or rareEasy to find and compare
Interest

Do you want more of the daily work, beyond the appeal of the title?

Mostly attracted to statusWould choose more of the work
Proof gapCan you build the missing proof without a blind leap?Large, inaccessible gapSmall, testable gap

Create one column for each hypothesis and total the scores. Then read the reasons behind the number. A path with strong evidence but low interest may be easy to enter and miserable to sustain. A path with high interest but no access needs exploration before it deserves a plan.

If two paths score closely, keep both. Your next step is a test designed to separate them.

Decide what kind of move this is

The score should lead to one of four honest outcomes:

  1. 01

    Continue

    Your past work already supports the direction, market language is clear, and the missing proof is small. Choose a project or responsibility that makes the pattern more visible.

  2. 02

    Make an adjacent move

    Your evidence transfers, but employers use different language or expect one unfamiliar part of the work. Talk to people in the role and test that missing part before applying broadly.

  3. 03

    Treat it as reinvention

    Interest is real, but your current evidence does not support the move yet. That is not a reason to abandon it. It means the path needs training, a portfolio, volunteer work, shadowing, or a more junior entry point.

  4. 04

    Park it for now

    Evidence, access, and interest are all weak. Keep the note if you want, but stop spending planning time on it until something changes.

Calling every change a natural next step is comforting but unhelpful. A reinvention has a different cost and timeline from an adjacent move. Name it correctly so you can plan for the work it requires.

Run the smallest test that can change your mind

Do not build a 90-day plan for an idea you have never touched. Start with the cheapest test that could make one path more or less credible.

UncertaintyUseful testEvidence to keep
I do not understand the daily work.Interview two people in the role using the same five questions.

Repeated tasks, tradeoffs, frustrations, and entry requirements.

I do not know whether my experience transfers.

Compare ten job descriptions and annotate where your examples match.

Common language, supported requirements, and missing requirements.

I have never done one core part of the role.Take on a small project, shadow the work, or produce a sample.

Output, feedback, decisions made, and what felt different from expectation.

Two paths still look equally good.Run one short test for each using the same decision criteria.

What you learned, what became easier, and which assumptions failed.

Once a path survives a small test, turn it into a 90-day development plan. That is the point where a longer commitment becomes useful rather than ceremonial.

Keep the evidence, including what did not work

Career decisions get distorted when you remember only the polished result. Keep the job-description notes, conversations, sample work, feedback, and reasons a path lost strength. That record helps you distinguish a bad week from a repeated signal.

Koru's role in this method is straightforward: it gives you a place to capture work evidence while it is fresh and review the patterns later. A document or spreadsheet can do the same job. What matters is keeping enough detail to answer four questions:

  • What did I try?
  • What did the work require from me?
  • What evidence became stronger or weaker?
  • What will I continue, change, or stop?
If the chosen path begins to support a promotion case, use how to ask for a promotion with evidence. If it requires deliberate skill-building and manager support, move to the personal career development plan. Your work history does not have to form a ladder. It does have to give you something concrete to test.