Most career plans fail quietly. Not because the goal was wrong, but because the plan was a sentence — "move into cloud engineering" — with no evidence behind it and no first action. A year later nothing has changed, and the conclusion drawn is usually "I lack discipline" when the real problem is that the plan was never specific enough to act on.
Short answer: a career plan works when it names a target role, tests that target against the actual job market, identifies the two or three gaps between you and it, picks the cheapest credible route to close them, and reduces the whole thing to something you can do this week. Everything below is that sequence in detail.
1. Assess where you actually are
Start with an honest inventory rather than an aspirational one. Three questions do most of the work:
- What can you evidence? Not what you have been exposed to — what you could demonstrate in an interview or a practical test. "I have used AWS" and "I have built and broken a multi-tier deployment" are different claims.
- What do people ask you for? The tasks colleagues route to you are a better signal of your real strengths than your own self-image.
- What drains you? A plan that walks towards work you dislike is a plan you will abandon, and it is better to find that out now than after two years of study.
Write the answers down. The value is in having a fixed baseline to measure against later, not in the exercise feeling profound.
2. Test the target against real job adverts
This is the step most people skip, and it is the one that saves the most wasted effort. Collect fifteen to twenty live adverts for the role you are aiming at — in your country, at your level, from employers you would genuinely work for. Then read them as data rather than inspiration.
Tally what actually recurs: which tools, which responsibilities, which qualifications appear as requirements versus which appear as "nice to have". You will usually find two or three things named far more often than everything else, and a long tail of technologies mentioned once that you can safely ignore for now.
This converts a vague ambition into a shortlist you can act on. It also occasionally kills the plan outright — which is a good outcome in month one and an expensive one in year two. The method is set out in more detail in how to choose a certification based on job postings.
3. Name the gap — and be precise about its size
Put your inventory next to your tally. The gap between them is your plan. Sort what you find into three buckets:
- Missing knowledge — things you have never learned. These are the slowest to close and usually where a structured course or certification earns its cost.
- Missing evidence — things you can do but cannot prove. These are the cheapest to close: a project, a portfolio piece, a credential that formalises what you already know.
- Missing exposure — things you could learn quickly if someone let you near them. These are often solved inside your current job by volunteering for the right work rather than by studying at all.
Most people over-invest in the first bucket and under-invest in the second. If a hiring manager's doubt is "can they prove it?", another course does not answer the question.
4. Choose the cheapest credible route
There is usually more than one way to close a gap, and they differ enormously in cost and time. A certification, a degree, a side project, an internal transfer and a lower-paid step sideways can all reach the same destination.
Judge each route on four things: what it costs in money, what it costs in months, whether employers in your tally actually recognise it, and what it leaves you with if you stop halfway. A certification you can sit in eight weeks and that appears by name in six of your twenty adverts is a stronger move than a two-year qualification nobody asked for. The trade-offs between the two are worked through in certification versus degree.
5. Reduce it to this week
A plan you cannot start within seven days is a wish. Whatever route you chose, name the first concrete action and put a date on it — book the exam, enrol on the course, message the person who does the job you want, open the editor and start the project.
Then set a review point, roughly quarterly. At each review, ask only two questions: has the market evidence changed, and did I do what I said? A plan that gets revised on evidence is working as intended. A plan that gets revised because the goal felt uncomfortable is usually just avoidance wearing a strategy hat.
The mistake underneath most failed plans
Almost every career plan that stalls does so at step two. It is far more pleasant to research courses than to read twenty job adverts and discover the role you want asks for something you have been avoiding. But the adverts are where the actual requirements live, and a plan built without them is a plan built on guesswork.
Start there, and the remaining four steps mostly write themselves.