Writing Development Action Items That Actually Get Done

The review ended three weeks ago — and nothing has happened

The conversation went well. The manager and the employee agreed on two or three things to work on. Someone wrote them down in the notes column of the review form — or in a follow-up email, or in a shared doc that now lives three folders deep in Google Drive. Nobody set a due date. Nobody named who would find the training resource. Nobody scheduled a follow-up.

By week two, both parties have moved on to the next urgent thing. The development plan is not abandoned out of bad faith; it is abandoned because it was never designed to survive contact with a busy quarter.

This is one of the most common failure modes in performance management, and it is almost entirely structural. Vague intentions dressed up as goals do not get done. Concrete development action items — with an owner, a resource, a milestone, and a due date — have a fighting chance.

This article gives you a practical framework for writing action items that close the loop between the skill-gap report and actual skill growth, and for tracking them so they do not die between review cycles.

---

Why most development plans stall before they start

A development plan that reads "improve communication skills" is not a plan — it is a category. No one knows what done looks like. No one knows who is responsible for making it happen. And because it is so broad, it is easy for both the employee and the manager to feel vaguely guilty about it without taking any concrete step.

The structural problem has three parts:

Ambiguity of outcome. Without a defined target behavior or a specific competency level to reach, the employee cannot self-assess progress and the manager cannot give useful feedback. "Better at communication" could mean anything from delivering clearer status updates in Slack to presenting to the board.

Ambiguity of action. Even if the outcome is clear, "work on it" is not an action. What specifically will the employee do? Read a book? Attend a workshop? Shadow a colleague? Present a draft recommendation at the next team meeting? Each of these takes different time, costs different money, and produces different evidence of progress.

No accountability structure. If neither the employee nor the manager has a specific task on their calendar or in their task manager tied to this goal, it will be displaced by anything that does have a deadline.

Research on career development consistently shows that lack of visible advancement opportunity is one of the top reasons employees leave — Pew Research Center found that 63% of those who quit in 2021 cited no opportunities for advancement (Pew Research Center, 2022). The irony is that most organizations genuinely want to invest in their people; the gap between intention and outcome is almost always execution, not intent.

---

The anatomy of a well-formed development action item

A well-formed development action item answers four questions before anyone leaves the room.

1. What competency or skill gap is this addressing? Anchor the action item to a specific gap identified in the skill-gap report. "Scored a 2 on 'Structures communication for the intended audience' at the Associate level; target is a 3 by Q3 review" is a precise origin. It connects the action to a defined standard rather than to a subjective impression.

2. What is the specific action? Use an action verb and name the deliverable or the activity:

• Completes the "Structured Communication for Practitioners" course on [platform] by [date]
• Delivers a written project brief to the team at the April 14 standup, incorporating manager feedback within one week
• Shadows a senior analyst on one client presentation in Q2 and submits a one-paragraph reflection

Each of these is observable. Either it happened or it did not.

3. Who owns it — and who supports it? The employee owns the action. The manager owns the support condition (budget approval, calendar time, introduction to a mentor, feedback on the deliverable). Both sides need an explicit task. When only one party has a task, the other party becomes a blocker without realizing it.

4. What is the due date, and what does "done" look like? A specific date beats a quarter. "By April 30" beats "Q2." And "done" is a concrete artifact: the course certificate is uploaded, the brief is delivered, the reflection is submitted. Without an artifact, "done" becomes a matter of interpretation at the next review.

---

Translating gap-report scores into action items

If you are running structured evaluations against a defined career framework, your skill-gap report tells you exactly where each employee sits relative to their current level's expectations and, if you have defined the next level, where the gaps are to get there.

The translation from score to action follows a straightforward logic:

Gap severity	Score delta	Suggested action type
Foundational gap	Scored 1–2 on a must-have competency for current level	Structured learning + supervised practice with short feedback loop
Developmental gap	Scored 3 on a competency; target is 4 for advancement	Stretch assignment + peer or senior exposure + deliverable
Awareness gap	Scored 2–3 on an emerging competency for next level	Exposure and observation; no performance expectation yet

A few practical notes on this table:

• Do not write action items for every gap at once. Three well-supported items completed beats eight items abandoned. Prioritize the gaps that matter most for the employee's current-level performance first, then advancement.
• Match the action type to the gap type. A foundational gap in a current-level skill probably needs more structure and shorter feedback loops than a stretch toward the next level.
• If a competency gap is large enough that it raises a performance question rather than a development question, that is a separate conversation — one that requires its own documentation. Development action items are for the growth trajectory, not for managing underperformance.

For a fuller walkthrough of how to evaluate employee career readiness against a defined framework before writing any action items, that piece covers the evaluation side in detail.

---

Writing the action items: worked examples

Here are three before-and-after examples across different job families. The "before" is the kind of entry that survives most review conversations. The "after" is a well-formed development action item.

Example 1 — Software engineer, mid-level

Before: "Work on code review skills."

After: "Leads the code review on at least two PRs per sprint for Q2, following the team's documented review checklist. Submits a brief written reflection on one review to the engineering manager by June 15. Manager will share the review checklist and confirm PR assignment process by April 7."

---

Example 2 — Account manager, associate level

Before: "Improve client communication."

After: "Writes and sends one proactive status update email to an assigned client account each week for eight weeks (April–May). Manager reviews the first three drafts and provides feedback within 48 hours. Employee and manager assess pattern at the June 1 check-in."

---

Example 3 — People operations coordinator, targeting a senior individual contributor level

Before: "Learn more about HR data and reporting."

After: "Completes the HRIS analytics module in [platform] by May 31 and produces one summary dashboard of Q2 headcount metrics for the department review. Manager secures platform access by April 10."

Each "after" version has an action verb, a named deliverable, a date, an employee task, and a manager support task. None of them require a budget conversation before they can be written down.

---

The tracking cadence that keeps action items alive

Writing good action items is necessary but not sufficient. The system that keeps them alive is a light, regular cadence — not another heavy process.

At the 30-day mark: A five-minute check-in (this can be folded into an existing 1:1) to confirm the employee has the resources they need and that nothing has blocked the first step. This is the moment to catch blockers before they become excuses.

At the midpoint: A brief status update — not a formal review, just a written note in whatever system you track development: green (on track), yellow (delayed but recoverable), red (blocked, needs intervention). The employee writes it; the manager reads and responds within a week.

At the next review cycle: The action items become part of the evaluation evidence. Was the deliverable completed? What did the employee learn? Did the gap move? This connects development back to the career framework and to the evaluation process that started the cycle.

The career conversations that happen between reviews are where most of this cadence lives. If managers and employees are having regular, documented career conversations, action-item check-ins fold in naturally. If they are not, the check-in cadence is a good forcing function to start.

---

What a trackable development action item looks like in a system

Whether you are tracking in a spreadsheet today or in dedicated software, the minimum fields for each action item are:

• Competency targeted (linked to the framework)
• Action description (specific, verb-forward)
• Employee task and due date
• Manager support task and due date
• Status (not started / in progress / complete / blocked)
• Evidence artifact (what the employee will submit or produce)
• Outcome at review (did the gap close?)

Without these fields, action items cannot be reviewed meaningfully at the next cycle, and you lose the feedback loop that tells you whether your framework's competency definitions are actually achievable and well-calibrated.

Career Ladder Builder's evaluation workflow is built around this loop: you define competency standards in your career framework, evaluate employees against them, generate a skill-gap report, and track development action items with status and evidence — all inside the same system, so the gap report and the action items stay connected rather than living in separate spreadsheets. You can explore how the full workflow is designed on the features page, or read more about building the career ladder that makes gap-based action items possible in the first place.

---

A concrete next step

The first action item worth writing is for yourself: before the next round of reviews, draft a template with the six fields above and share it with your managers. Even a shared Google Sheet with those columns is better than free-text notes. The structural discipline comes from the fields, not the tool — though a 14-day free trial of Career Ladder Builder will show you what it looks like when the gap report and the action items live in the same place, connected to the framework that defined the gaps.

Development does not stall because people do not care. It stalls because the hand-off from review to action to follow-up was never designed. Design it once, and it runs.