# How to Build a Skills Development Plan You Will Actually Use Canonical URL: https://headwayskills.com/knowledge/improve-skills/skills-development-plan/ Markdown URL: https://headwayskills.com/knowledge/improve-skills/skills-development-plan.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving building self-awareness at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer A skills development plan links where you stand to the skills your next goal needs. Follow seven steps to build one, from honest baseline to monthly review. ## Key facts - Title: How to Build a Skills Development Plan You Will Actually Use - Category: Improve Your Skills - Primary skill: Building Self-Awareness - Related skills: Setting Goals, Building Confidence - Primary keyword: skills development plan - Source page: https://headwayskills.com/knowledge/improve-skills/skills-development-plan/ ## What this page covers - A skills development plan links where you stand to the skills your next goal needs. Follow seven steps to build one, from honest baseline to monthly review. - Practical guidance for skills development plan - How this topic connects to Building Self-Awareness ## Detailed explanation A skills development plan is a short working document that connects where you stand today with the skills your next goal requires: which few skills you will build, how you will practice each one, by when, and how you will check that something has changed. It works when you review and adjust it, not when you file it. If yours started life as a form from a manager or a course requirement, you can probably picture how that ends: filled in carefully once, saved somewhere sensible, never opened again. The difference between that plan and one that actually changes how you work comes down to the order you build it in, and to one habit at the end. ## How to build a skills development plan in seven steps The steps below run in sequence, because each one depends on the one before it. You do not need special software or a template; a single page with a heading for each step is enough. Expect the first draft to be rough. A plan is meant to be revised. ### 1. Take stock of your strengths and gaps Everything else in the plan rests on an honest baseline, so start here. Write down [what you are genuinely good at](/knowledge/self-awareness/how-to-identify-your-strengths/), not just competent at: the tasks that go well, that leave you with energy rather than drained, and that produce results other people notice. Then write down the gaps that have shown up in real situations, such as the presentation that lost the room, the deadline estimate that was off twice, or the comment you have heard from more than one person. Your own view has a built-in limit: it cannot see your blind spots. The fix is to check it against other people. Ask two or three people who have seen you work, such as a manager, a colleague, a teacher, or an internship supervisor, one specific, [forward-looking question](/knowledge/self-awareness/questions-to-ask-for-feedback/) each: what is one thing you could do differently over the next few months that would make the biggest difference? Their answers will confirm part of your list and correct the rest. If you would rather begin from something firmer than a gut feeling, the free Job Skills Test gives you [a structured skills baseline](https://assessment.headwayskills.com/) to set beside that feedback, and every gap it surfaces is something you can learn. ### 2. Decide what the plan is for A plan needs a target, or it drifts toward whatever learning happens to be convenient: the webinar your team was invited to, the course a friend recommended. Name the near-term goal the skills should serve. For a final-year student, that might be landing an internship or a first full-time role in a particular field. For someone in their first job, it might be taking on client work, running a small project on your own, or going into your next performance review with something concrete to show. The goal does not have to be a [five-year career plan](/knowledge/setting-goals/career-planning/), and early on it usually should not be. A direction for roughly the next year is enough to make choices. Let your baseline shape it, too: the strengths you found in step one are often a better guide to where you will grow fastest than the job titles other people expect you to want. ### 3. Choose the skills to develop Now compare your baseline with your goal. The skills that belong in the plan are the ones that close the distance between the two: the gap that would actually block the goal, and the strength the goal would reward if you sharpened it further. Everything else can wait for the next version of the plan. Keep the list short. Two or three skills at a time is plenty alongside a full workload or a final year of study; ten skills at once is a wish list, not a plan. Name each skill precisely enough that you could practice it next week. "Communication" is too broad to act on. "Explaining my work clearly in team meetings" or "writing emails that state the main point first" is something you can work on, observe, and get feedback about. ### 4. Turn each skill into a specific goal with milestones A vague intention such as "get better at communication" gives you no next action and no way to tell whether anything has changed. A specific goal with dated milestones does both. For each skill, write what you will be able to do, by when, and the checkpoints along the way. The timeline should be realistic but still a stretch: easy enough that you will start, hard enough that reaching it means something. Keep the horizon short. Emory University's individual development plan template for hematology and medical oncology asks the plan owner to lay out a quarterly timeline for the goals and the development activities that serve them. A quarter is long enough to see real progress and short enough to plan honestly, which matters when you cannot yet know where you will be in two years. A goal like "lead the team's weekly update at least twice before the end of the quarter, and ask for one piece of feedback after each" fits that window well. ### 5. Plan how you will learn each skill This is the step where plans tend to go thin, because development so easily gets equated with courses. In practice, most skill growth at work comes from experience: stretch tasks, repeated practice, and real responsibility. The next-largest share comes from other people, through feedback, coaching, and mentoring. [Formal courses](/knowledge/improve-skills/skills-and-training/) are the smallest contributor. They are useful, but rarely the main engine. So for each goal, write three lines: - The experience: a specific task, project, or responsibility where you will practice the skill, ideally in the job, student job, internship, or project you already have. - The person: someone you will learn from or ask for feedback, such as a colleague who does this well, your manager, a teacher, or a mentor. - The course, if any: only where it fills a gap that experience and people cannot, such as a technical tool you need before you can practice at all. This is also the answer to finding time. Learning built into work you already do costs far less than learning added on top of it. A plan that asks for three extra evenings of study a week tends to collapse in the first busy month; a plan that turns next Tuesday's meeting into practice does not. Stretch tasks are the richest source of learning, but they need sizing. Choose a step one level above what you can do today, not the most ambitious assignment in sight. If your instinct is to volunteer for the hardest thing available to prove you can handle it, you are not alone. One of the young people we interviewed about starting work had advice on exactly that: > Don't be in too much of a hurry — you don't have to be able to do everything from the start. Don't try to be the hero. It's great if you dare to throw yourself into things, but you also have to dare to own your limits. Don't take on tasks you're not equipped for, only to end up not solving them well and beating yourself up for saying yes to something you weren't ready for. That just gets you off to a bad start. She is not arguing against stretching; she values throwing yourself in. The point is the size of the step. A stretch you can just about reach builds the skill. One far out of reach tends to leave you with a poor result and less appetite for the next attempt. ### 6. Bring in your manager or a mentor You can draft a development plan alone or together with your manager, and in many workplaces it is part of the regular performance-review cycle anyway. Either way, bring your manager in early. They shape much of what the plan depends on: which assignments you get, how much feedback you receive, and whether there is room to practice something new. Sharing the plan turns a private intention into an agreed one, and gives you someone who expects to hear how it is going. Be concrete when you ask. Instead of "Can you support my development?", ask for the specific stretch task from step five, for feedback on a particular piece of work, and for a date to look at the plan together. If you are still studying, a teacher, a thesis supervisor, an internship supervisor, or a mentor can play the same role. ### 7. Review, ask for feedback, and adjust A plan that is never reviewed becomes the form that gets filed and forgotten. The safeguard is a fixed rhythm with two loops. The Emory template pairs a personal review every month with a periodic review, quarterly or twice a year, held with a mentor. The monthly check catches slippage while it is still small; the review with another person adds an outside view and a reason to keep going. At each review, look at three things: which milestones you reached, which skills have actually moved, and what still needs work. Use feedback to judge the second one. Ask the people around you about the specific skill you are working on, because the useful question is whether the change is visible to others, not only whether it feels different to you. Then update the plan: move a deadline, swap out a skill that turned out to matter less, add the next milestone. A development plan is not set in stone, and revising it is not a sign that it failed. Revision is how the plan is supposed to be used, which also means your first draft does not need to be perfect. Put the first monthly review in your calendar today, before you have a reason to skip it. ## The skills that keep a plan moving Look at where the seven steps lean hardest: on reading yourself honestly, on knowing roughly what you are building toward, and on following through once the first practice feels awkward. Each of those has a name. **Building Self-Awareness** decides how good your baseline is. It starts with noticing what you are genuinely good at, which shows in how a task goes, how it feels while you do it, and the results it produces. It continues with feedback: asking specific, future-focused questions instead of waiting for an annual review, then listening to understand what is being said before adding your own view and reflecting on it. Without it, a plan targets the skills you assume you lack rather than the ones actually holding you back. **Setting Goals** gives the plan its direction. The skills worth building are the ones that fit your strengths and your work values, not the ones a template lists or other people expect of you. Plan in short horizons of 6 to 18 months rather than a fixed five-year route, and let each round teach you something about where you want to go next. That keeps the plan personal and easy to revise, which is exactly what an early-career plan needs. **Building Confidence** is what turns the plan into practice. Confidence comes from doing, not from feeling ready first: break each goal into small steps, practice at one level before moving up, and decide in advance exactly when and where the first step will happen so it does not slide to next week. Each finished step adds evidence that you can manage the next, slightly harder one. The steps should feel a little uncomfortable, but not so far out of reach that they stall. Your plan's first line is easier to write with evidence behind it. The **free Job Skills Test** scores these three alongside the rest of a **set of twelve work skills**, so you can [decide which skill goes first](https://assessment.headwayskills.com/), knowing that whichever one it points to is a behavior you can build, not a fixed verdict on you. ## A plan built around how you already work You may already be doing parts of this without calling it a plan. If you have ever reread a piece of feedback a week later and finally understood what it was asking of you, or said yes to a task partly because it made you a little nervous, you have already done the raw work of steps one and five. The skills underneath are behaviors, not traits. You can practice them and still work in a way that feels like you, and which ones deserve your attention first depends on where you are starting from, not on a standard list. Left to chance, your development follows whatever work happens to land on your desk, and that matters more with every year your role grows. A one-page plan and a monthly check are enough to take the steering back. What the first draft needs most is an accurate starting point. ## Write the first line of your plan That leaves one thing to do: put something real on the page. The Job Skills Test is a **free** self-assessment of your work skills. It takes about 7 minutes and shows where you stand across all twelve, including the ones that would make the biggest difference to work on now. Consider treating the result as step one of your plan: note the skill it points to, write one milestone for the coming month, and book your first monthly review. ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? A skills development plan links where you stand to the skills your next goal needs. Follow seven steps to build one, from honest baseline to monthly review. ### Which Headway skill does this connect to? This guide connects primarily to Building Self-Awareness. It also relates to Setting Goals, Building Confidence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/improve-skills.md - https://headwayskills.com/knowledge/self-awareness.md - https://headwayskills.com/knowledge/setting-goals.md - https://headwayskills.com/knowledge/confidence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/improve-skills/skills-development-plan/ Preferred summary: "A skills development plan links where you stand to the skills your next goal needs. Follow seven steps to build one, from honest baseline to monthly review." ## Change log - 2026-07-07: Content collection version published.