A development plan fails when the person isn't convinced of the path and the leader doesn't stay close enough to notice. Periodic feedback isn't enough: it takes dated milestones, an honest conversation about conviction, and — if it doesn't appear — agreeing on another exit in time.
What was the plan?
An internal support role (assets, licenses, equipment) had a clear path to grow toward Compliance Officer or Security Analyst, supported by improving endpoint security tooling. Courses were defined and regular feedback was given.
What went wrong?
The person wasn't convinced about changing roles or taking on more responsibility. Daily operations always won out over reviewing their progress. They never completed the training, disengaged from the role, and ended up leaving for performance during a restructuring.
The uncomfortable part of this case isn't that it ended badly — it's that the signals were there the whole time. The plan looked impeccable on paper: defined courses, regular feedback, a clear destination. What was never there was a direct conversation about whether the person wanted that destination.
What should have been done differently?
Concrete milestones with dates, so a stalled plan shows up in weeks instead of months. A frank conversation about conviction and, if it doesn't appear, an agreed exit in time. And in hiring, assess demonstrated interest in the growth path, not just the skills for the entry-level role.
Signals that a development plan is stalling
Courses or deliverables get postponed without a new date. The person avoids talking about the next role or new responsibilities. And the progress review always loses to the day's operations. None of those three signals is conclusive on its own; all three together, sustained over weeks, are a diagnosis.
Frequently asked questions
How often should a development plan be reviewed? With short, dated milestones (every 2–4 weeks, for example), not only in long periodic evaluations.
Is it a failure of the leader or of the person? Usually both: the person needs conviction, and the leader needs to detect early when it isn't there.
Related article: what the numbers didn't explain — until I askedRelated article: when one person's departure almost cost us the accountRelated article: the overtime nobody seesIn this topic
View the full topicQuick answerDetail
Why does a talent development plan fail?
A development plan fails when the person isn't convinced of the path and the leader doesn't stay close enough to notice. Periodic feedback isn't enough: it takes dated milestones, an honest conversation about conviction, and — if it doesn't appear — agreeing on another exit in time.
Written and reviewed by Rogelio Barajas González — certified Lead Auditor ISO 27001:2022 and ISO 9001:2015, with direct experience in SOC 1 Type 2 and SOC 2 Type 2. Founder of Barajas Advisory.
Company names, people, and some minor identifying details have been generalized to protect the confidentiality of the organizations involved. The facts, figures, and lessons narrated remain faithful to what happened.
Verify his credentials on LinkedIn:linkedin.com/in/rogelio-barajas-gonzalezLast updated: September 2026
This is one of nine real cases
Cicatrices de Nube — do you want the rest of the stories?
All nine documented cases —FinOps, Release Management, Service Delivery, Compliance, and AI governance— with a self-assessment checklist per chapter and an overall scorecard.
Download the free playbook