Development plan: from competency gap to SMART goal

What is a development plan and why does it often not work?

A development plan describes which competencies someone will develop, which actions are needed for that, and when the result will be evaluated. It is the bridge between insight (where do I stand?) and action (what am I going to do?).

In practice, most development plans do not work. They are drawn up during an annual review, contain vague goals such as "communicate better" or "show more initiative", and then disappear into a drawer until the next review.

This is due to three structural problems. First, the plan is not based on data. Without objective measurement of aptitude and behavior, every goal is an assumption. Second, the plan is not concrete enough. Without measurable criteria, there is no way to test progress. Third, there is no process that keeps the plan alive. Without check-ins, approval and remeasurement, there is no urgency.

A working development plan solves all three. It starts with data from assessments and 360° feedback. It uses the SMART principle to make goals concrete. And it has a governance process that creates commitment from the employee and the manager.

From competency gap to development goal

The starting point of a development plan is the competency gap, the difference between what someone can achieve (aptitude) and what someone shows now (behavior). That gap comes from comparing assessment results with the job profile.

Not every gap is a development goal. The selection depends on three factors. Impact, meaning which competency has the most influence on performance in the current role? Potential, meaning where is the aptitude strongest, so that development has the best chance of success? Energy, meaning where does development fit the motivation and energy level of the employee?

An assessment provides the data for that trade-off. For each competency, it shows the aptitude score (from personality and intelligence) and the behavior score (from feedback or a live assessment). The underlying facets reveal which specific aspects are strong or weak.

• For example: someone scores high on aptitude for "Collaboration" but low on behavior. The facets show that "active listening" and "giving feedback" are the weakest behavioral indicators, while "putting the team's interest above self-interest" scores strongly. The development goal then focuses not on "collaborating better" but specifically on "listening actively and giving constructive feedback in team meetings".

From vague intention to concrete goal

A development goal only works if it is concrete enough to steer by. Not "present better" but "give a structured presentation with a clear key message and room for questions in monthly team updates". That difference determines whether a goal gives direction or disappears into a drawer.

A good goal describes exactly which behavior you want to develop, contains success criteria you can test (for example a behavior score from the next 360° feedback round or an observation by the manager), and is achievable within the available time. An employee who scores 20% on aptitude will not grow to 80% in six months. Realistic goals prevent frustration.

The goal ties in with what the job profile requires and with the employee's personal motivation. And it has a deadline, because without an end date there is no urgency. A typical development period is three to six months, depending on the complexity of the behavior.

AI support in formulating goals

Formulating a good SMART goal is difficult. Most employees have little experience with it. The result is often too vague, too ambitious or not linked to the right competency.

AI can speed up and improve this process. Based on the competency gap, the underlying talent facets, the behavioral indicators and the job context, AI generates a proposal for a SMART goal. Including success criteria, concrete actions and a realistic timeline.

The AI proposal is a starting point, not a finished product. The employee adjusts it, adds personal motivation and makes it their own. The manager assesses whether it is realistic and relevant. AI speeds up the process from hours to minutes and raises the quality, but does not replace ownership.

The strength of AI lies in the context. It knows the competency definition, the behavioral indicators per level, the aptitude and behavior scores and the job requirements. As a result, it generates goals that are specific to this person in this role, not generic templates.

Choosing development actions: what are you actually going to do?

A goal without actions is a wish. Development actions describe what someone is actually going to do to reach the goal. The most powerful actions combine different learning methods.

Most learning happens on the job. Think of "leading the weekly kick-off for the next three months and actively asking the team for feedback afterwards." That is directly linked to the work situation and provides immediate experience. It also helps to learn from others, for example by having a monthly feedback conversation with your manager about the development area. 360° feedback can also play a role here as an interim measurement.

Formal learning, such as a targeted training or workshop, is most effective when combined with application in practice. Following a training without applying what you have learned at work rarely leads to lasting behavioral change.

For each action, you record what will be done, how often, and what the estimated time investment is. That makes the plan concrete and plannable for both the employee and the manager.

Why an approval process makes the difference

A development plan drawn up only by the employee lacks support. A plan imposed only by the manager lacks ownership. The strength lies in the dialogue between the two.

The employee drafts the development goal, possibly with AI support, and submits it to the manager. The manager assesses whether it is realistic and relevant, gives feedback and approves it. That creates a shared commitment and offers a natural moment for the development conversation.

For HR, this process provides an overview. How many employees have an active plan? Which competencies are being developed most? Where are the biggest gaps across the organization? That is valuable input for people analytics and strategic workforce planning.

Tracking progress: check-ins and interim evaluation

An approved plan is the beginning, not the end. Carrying it out requires regular check-ins between the employee and the manager.

A check-in is a short conversation (15-30 minutes) built around three questions. What have you done since the previous check-in? What is going well and what is difficult? What are you going to do in the coming period?

The frequency depends on the complexity of the goal and the preference of the employee and manager. Weekly, every two weeks or monthly are common rhythms.

Along the way, actions are ticked off and progress becomes visible. That gives the employee a sense of progress and gives the manager insight into where support is needed.

If a goal turns out not to be achievable or circumstances change, the plan can be adjusted. A development plan is not a contract but a living document that moves with reality.

Remeasurement: closing the cycle

The ultimate proof that development works is measurable behavioral change. That requires remeasurement with the same instruments that provided the baseline measurement.

After the agreed development period, you measure again. A new 360° feedback round shows whether the behavior has changed in the eyes of colleagues. A new assessment shows whether the competency scores have risen.

The comparison between the baseline and the remeasurement is the hard evidence. Not "I feel it is going better" but "my behavior score on active listening has risen from 45% to 62%".

That remeasurement closes the cycle and at the same time opens the next one. Which competencies have grown? Where is there still room? Are there new priorities? The development plan is updated and the cycle starts again.

For the organization, the remeasurement provides proof that the investment in development pays off. Not as an assumption but as a measurable result. That is the core of data-driven talent development.