Odyssey Planning

Odyssey planning turns one career question into three deliberately different futures. The point is not to predict the future. The point is to make trade-offs visible before a single job description, course, or side project pulls you off course.

Use it when a user asks "what should I do next?", considers a major role change, or faces a tempting JD that would require real learning investment.

The three-path map

Build three paths, not one:

1. Base path: the stable compounding route. It preserves the user's most important life constraint while deepening career capital.
2. Stretch path: the selective advancement route. It pursues a bigger role, platform, or scope only when the upside is worth the added load.
3. Option path: the high-upside route. It is explored through low-cost experiments until evidence justifies more risk.

The names can change by user, but the logic should stay distinct. Do not make three versions of the same plan.

Start with the non-negotiable

Ask what the user least wants to sacrifice before designing paths. Common anchors:

• cash-flow stability
• family or caregiving time
• location stability
• health and energy
• autonomy
• upside and ambition

Then rank paths against that anchor. A glamorous option that violates the user's non-negotiable is not the primary path. It can remain an option path with trigger conditions.

Forecast three to five years

For each path, write a short forecast:

• Year 1: what the user would actually do next, not a vague aspiration.
• Year 3: what credible traction looks like.
• Year 5: what identity, market position, and lifestyle the path could produce.
• Risks: what can quietly break the plan.
• Signals: what evidence would make the path stronger or weaker.

Keep the forecast honest. The hub should not turn every path into a motivational story.

Convert gaps into learning investments

When a JD exposes gaps, do not turn the JD into a study syllabus. Sort the gaps by career return:

• Must learn: missing gatekeeper skills that block credible entry into the target role.
• Useful to understand: topics the user must evaluate, manage, or discuss, but does not need to own as an expert.
• Not now: adjacent topics that would pull the user away from stronger career capital.

This prevents single-job-description drift. The goal is to invest in skills that compound across many plausible futures.

Design a learn-by-doing project

Replace generic learning lists with a bounded project. A strong project has:

• one real workflow
• a small but complete dataset or scenario
• visible artifacts: README, demo, evaluation notes, failure cases
• a clear skill map: what it proves, what it does not prove
• a resume boundary: what can be claimed now, what must wait for real deployment

Prefer four-to-eight-week projects. Long enough to produce evidence, short enough to avoid becoming a second job.

Keep resume boundaries honest

The hub separates learning, experiments, and proven experience:

• Already evidenced: can be used in resumes and interviews.
• Project in progress: can be tracked in todo.md or a portfolio, but should not be overclaimed.
• Not yet claimable: should stay out of formal resumes until there is evidence.

This is especially important for senior roles. Overclaiming expert-level ability in a new stack damages credibility faster than admitting a focused learning plan.

Suggested hub outputs

When an Odyssey plan is completed, save the outputs in the private career hub:

• career/odyssey/YYYY-MM-DD-plan.md for the three-path forecast.
• jobs/market-watch/YYYY-MM-DD-<role>-gap.md for JD-specific gap analysis.
• todo.md for selected experiments and evidence-gathering tasks.
• changelog.md when a plan, experiment, or portfolio artifact is completed.

Avoid writing private family, compensation, medical, or employer-sensitive details into public docs. If the generated hub stores them, mark the file as sensitive.