Career roadmaps

Path 01 · 7 stages · 8–10 weeks

Early career foundations

For people in a first or second job, or returning to work after a long absence. The aim is not to make you impressive; it is to make the first year legible, so that effort turns into visible progress rather than quiet frustration.

Objectives

By the end of this path you should be able to:

• Explain how your work connects to what your team is measured on.
• Ask for clarification early, in a way that reads as diligence rather than confusion.
• Write a clear progress update without being asked for one.
• Receive critical feedback without defending, and act on it within a week.
• Keep a running record of your work that makes a review conversation straightforward.

Recommended sequence

1. 1

   Read the room before you change it

   Spend the first stage observing how decisions are actually made, who is consulted informally, and what “done” looks like on your team. Write it down; you will never see it this clearly again.

   Practice: map five people, their role and what they need from you

2. 2

   Understand what the team is measured on

   Ask your manager which two or three numbers or outcomes their own performance is judged against, then work out where your tasks touch them.

   Pairs with: Career planning guide

3. 3

   Ask better questions, earlier

   The costly questions are the ones asked in week six that should have been asked in week one. Learn the pattern: state your understanding, name the gap, propose an answer, ask for confirmation.

   Practice: convert one vague task into three specific questions

4. 4

   Write an update nobody asked for

   A five-line weekly note — done, in progress, blocked, needs a decision. This single habit accounts for much of the difference in how early-career people are perceived.

   Pairs with: Professional writing guide

5. 5

   Take feedback without defending

   Practise the three-step response: thank, restate to check understanding, ask what a better version would have looked like. Save any disagreement for a second conversation.

   Practice: ask one colleague for one specific criticism

6. 6

   Build your evidence file

   A running document of what you delivered, what changed because of it, and who noticed. Fifteen minutes a month; invaluable at review time and when you next apply for anything.

   Pairs with: Career development worksheet

7. 7

   Run your first self-review

   Compare your evidence file with the objectives above. Name one skill to develop next quarter and one thing to stop doing.

   Pairs with: Reflection template

Path 02 · 8 stages · 12–16 weeks

Career change navigation

For people moving to a different field, sector or type of work. Career change fails most often not from lack of ability but from an unclear story and an untested assumption about what the new work is actually like day to day.

Objectives

• Describe your transferable skills in the vocabulary of the target field, not your current one.
• Test the new direction cheaply before committing time or money to retraining.
• Identify the two or three gaps that genuinely block entry, and ignore the rest.
• Explain the change in ninety seconds without apologising for it.
• Build a small, specific network in the target field.

Recommended sequence

1. 1

   Name what you are moving toward, not away from

   “Away from” motivation gets people to start and rarely gets them to finish. Write a one-paragraph description of the work you want, in terms of daily activity rather than job title.

   Practice: describe an ideal Tuesday in the new role

2. 2

   Audit what transfers

   Separate skills into three columns: fully transferable, transferable with translation, and genuinely not transferable. Most people underestimate the middle column badly.

   Pairs with: Career development worksheet

3. 3

   Learn the target field's language

   Read ten job postings and three practitioner blogs or trade publications. Collect the nouns. Using the wrong word for a familiar thing is the fastest way to read as an outsider.

   Practice: build a fifty-word glossary

4. 4

   Sample the work cheaply

   A volunteer shift, a short contract, a shadowing afternoon, a small personal project. The point is to meet the ordinary parts of the job, not the interesting parts.

   Practice: arrange one sampling activity this month

5. 5

   Talk to five people already doing it

   Informational conversations, twenty minutes each, with a specific question you cannot answer from the internet. Ask what they wish they had known and what the worst week looks like.

   Pairs with: Networking guide

6. 6

   Close only the blocking gaps

   After stages 4 and 5, you will know which credentials or skills are genuinely required and which are merely common. Invest in the first list only.

   Practice: rank gaps by whether they block a first interview

7. 7

   Rewrite your story

   A ninety-second account of the change: what you did, what carried over, why this field, what you have already done to prepare. Rehearse until it stops sounding defensive.

   Pairs with: Interview preparation guide

8. 8

   Apply narrowly and review monthly

   Twelve well-matched applications beat sixty scattered ones. Track outcomes by stage so you can tell whether the problem is the résumé, the story or the target.

   Pairs with: Goal tracker

Path 03 · 7 stages · 10–14 weeks

Leadership development

For first-time team leads and those preparing to become one. The central difficulty of a first leadership role is that the behaviours which earned it — doing the work well and quickly — are precisely the ones you now have to stop.

Objectives

• Delegate a whole task, including the judgement calls, rather than handing out instructions.
• Run a one-to-one that is useful to the other person.
• Give corrective feedback early enough that it is still small.
• Make and communicate a decision when the team disagrees.
• Protect your team's attention from avoidable interruption.

Recommended sequence

1. 1

   Redefine your output

   Your output is now the team's output. Write down what you will stop doing personally to make room, and tell your manager what that changes.

   Practice: list three tasks to hand over this month

2. 2

   Delegate outcomes, not steps

   Describe the result, the constraints and the check-in points, then leave the method alone. Handing over steps produces people who need you; handing over outcomes produces people who do not.

   Practice: delegate one task with no method attached

3. 3

   Run one-to-ones the other person owns

   Thirty minutes, their agenda first, your items last, notes kept by both of you. Cancel it and you have told them what it was worth.

   Pairs with: Meeting management guide

4. 4

   Give small feedback early

   The conversation you avoid in week two becomes the formal conversation in month six. Practise a two-sentence version: the specific behaviour, the specific effect.

   Practice: give one piece of corrective feedback within a week

5. 5

   Decide when the room is split

   Consultation is not consensus. Say how the decision will be made, gather input, decide, and explain the reasoning to the people whose view did not prevail.

   Pairs with: Critical thinking guide

6. 6

   Handle the difficult conversation

   Preparation, a private setting, a factual opening, silence after it, and an agreed next step in writing. Difficulty is reduced by structure, not by charisma.

   Practice: script an opening line and rehearse it aloud

7. 7

   Build the team's operating rhythm

   A weekly planning point, a written update, and a monthly retrospective. Rhythm removes the need for constant coordination and gives quieter people a predictable place to speak.

   Pairs with: Meeting agenda template

Path 04 · 6 stages · 6–8 weeks

Communication skills

The shortest path we publish, and the one that pays back fastest in almost any role. It treats writing, speaking and listening as three parts of one skill: making it easy for another person to act on what you know.

Objectives

• Open any message with the decision, request or conclusion.
• Choose the right channel for the message, and stop escalating by volume.
• Explain a technical matter to a non-specialist without condescension.
• Deliver a ten-minute talk with a clear spine and no read-aloud slides.
• Listen in a way that changes what you do next.

Recommended sequence

1. 1

   Lead with the point

   Put the conclusion in the first two lines and the reasoning below it. Readers who need detail will scroll; readers who do not are already served.

   Practice: rewrite three sent emails, top-down

2. 2

   Match the channel to the message

   Decisions and disagreements belong in conversation; records, requests and detail belong in writing. Most communication friction is a channel error rather than a wording error.

   Pairs with: Professional communication guide

3. 3

   Edit for the skim

   Cut a third. Break long paragraphs. Make every request explicit, with a name and a date attached. Ambiguous requests are the main cause of work that never happens.

   Practice: reduce a long message by 30 percent

4. 4

   Explain without jargon

   Practise the ladder: one sentence for anyone, one paragraph for an interested colleague, one page for a specialist. Choose a rung deliberately rather than defaulting to the deepest one.

   Practice: explain your current project three ways

5. 5

   Build a talk from the audience backwards

   Decide what they should do differently afterwards, then work back to three points that get them there. Slides last, always.

   Pairs with: Presentation skills guide

6. 6

   Listen for the thing not said

   Summarise back before responding, ask one clarifying question before disagreeing, and notice which topic the other person keeps returning to.

   Practice: summarise before replying, for one full day

Path 05 · 7 stages · 9–12 weeks

Project coordination

Written for the very large number of people who hold a piece of work together without a project title, a methodology certificate or any formal authority over the people involved.

Objectives

• Write a one-page brief that stops scope arguments before they start.
• Sequence work so that dependencies surface early rather than at the deadline.
• Track progress in a form other people will actually read.
• Escalate a risk while it is still cheap to fix.
• Close a project properly, including what should be done differently next time.

Recommended sequence

1. 1

   Write the one-page brief

   Purpose, scope, explicitly out of scope, decision-maker, key dates, known risks. The “out of scope” line prevents more trouble than all the others combined.

   Pairs with: Project one-pager template

2. 2

   Identify who decides what

   List every decision the project needs and name one person for each. Shared decisions without a named owner are how projects stall politely for weeks.

   Practice: draft a decision list with owners

3. 3

   Sequence backwards from the date

   Start at the deadline and work backwards, marking every point where you depend on someone outside your control. Those points are your real schedule.

   Practice: mark all external dependencies

4. 4

   Track in one place, visibly

   One list, one status vocabulary, one update rhythm. The tool matters far less than the fact that everyone looks at the same version.

   Pairs with: Weekly planner

5. 5

   Escalate early and unemotionally

   State the issue, the impact, what you have already tried, and what you need. Early escalation reads as competence; late escalation reads as a surprise.

   Practice: write an escalation note for a current risk

6. 6

   Run useful checkpoints

   Short, scheduled, with a written agenda and a decision to make. A checkpoint that only reports status can be an email instead.

   Pairs with: Meeting agenda template

7. 7

   Close and review

   Confirm delivery in writing, hand over what continues, thank people specifically, and record two things to change next time.

   Pairs with: Reflection template

Path 06 · 6 stages · Ongoing

Continuous learning

A path about the practice of learning itself. Most professional study fails for structural reasons — no schedule, no narrowing, no review — rather than from any shortage of motivation.

Objectives

• Choose subjects based on the work in front of you rather than general interest.
• Hold a modest weekly study commitment through a busy quarter.
• Use spacing and retrieval rather than rereading.
• Keep notes you will genuinely revisit.
• Review honestly every quarter and drop what is not working.

Recommended sequence

1. 1

   Pick one subject for the quarter

   Narrow enough to finish, connected to something you will use within a month. “Better communication” is not a subject; “writing project updates” is.

   Practice: write the subject as a single testable sentence

2. 2

   Book the time before you find the material

   Two fixed sessions of forty-five minutes a week, in the calendar, treated like a meeting with someone else. Material is abundant; protected time is not.

   Pairs with: Weekly planner

3. 3

   Learn by retrieval, not rereading

   After each session, close the page and write what you remember. The discomfort of the blank page is the mechanism; recognition while rereading feels like learning and mostly is not.

   Practice: five-minute recall note after each session

4. 4

   Apply it inside seven days

   Find the smallest real task that uses the new idea. Applied once, badly, beats understood perfectly and never used.

   Practice: name the task before you start studying

5. 5

   Keep notes in your own words

   One page per subject, rewritten as understanding improves. Copied notes are a record of reading; rewritten notes are a record of thinking.

   Pairs with: Reflection template

6. 6

   Review each quarter and choose again

   What did you actually use? What did you abandon and why? Then select the next subject with that evidence in hand.

   Pairs with: Goal tracker