The short version
Competency-Driven Development (CDD) is a way of developing people that starts with the skill, not the class. You write down the skills your organization depends on as clear statements called competencies. Then you let everything else flow from them: how people learn, how they prove it, how they're recognized, and how leaders see the whole picture.
Lectures, courses and videos still have a place. They just stop being the goal. The competency leads, and the learning activities serve it.
Why it matters
Most learning systems report who attended a class or finished a course. That tells you very little. Attendance doesn't mean growth, and training a person on a skill doesn't mean they learned it.
Training programs usually fall short in a few predictable ways:
- Employees can find courses but struggle to match them to the skills they actually need.
- Training isn't tied to the organization's values and strategy, so it can't support them.
- Almost nobody celebrates "class completion," so real achievements go unnoticed.
- Leaders can't see which skills are concentrated in the company and which are missing.
CDD is built to fix those things.
What a good system does
At minimum, any learning and development system should:
- Guide people to skills. Make learning targets, resources and pathways easy to find.
- Align with the organization. Connect to vision, mission, values and strategy.
- Transform teams. Produce measurable results in skills, productivity and confidence.
- Drive culture. Become a real driver of how the organization works.
- Celebrate achievement. Recognize people when they gain a skill.
- Nurture skills. Use methods that help people keep what they learn.
- Report capability. Tell leadership where skills are strong and where they're thin.
The parts of CDD
Competencies sit at the center. Eight parts grow out of them.
1. Evaluations
People prove mastery in a way that fits the skill: a timed project, an interview with an expert, a team review, on-the-job observation. Read more about evaluations →
2. Inclusive learning experiences
People learn in different ways, with or without a teacher. Mentoring, practice, reading, apprenticeship, job shadowing and trial and error all count. Learn more →
3. Transferable skills
If someone already has a skill, they prove it and move on. It doesn't matter where they picked it up: a past job, school or life. No repeating classes they don't need.
4. Self-paced learning
Nobody moves ahead until they've shown mastery, and nobody is held back by the pace of a class. Faster learners move on. Others take the time they need.
5. Learning pathways
Skills are arranged by difficulty and by audience (a role, team or department), so the next skill is always clear. Think of them like grade levels at school.
6. Digital credentials
Earned skills become portable digital badges that follow the Open Badges standard. About badges →
7. Skill reporting
Once skills are proven and recorded, leaders can see where skills are concentrated and where the gaps are. That's a metric most organizations don't have.
8. A repeatable process
The first implementation is the heavy lift. After that, you can run the same process whenever the business needs new skills. No new system required. See the process →
What a competency is
A competency is a clearly written skill statement, such as:
Build functional user-input-driven front-end applications using VueX and VueJS.
It isn't a lesson plan, a goal for a class, or a list of topics covered. It describes what a person can do. Competencies can cover skills and knowledge, which are easier to measure, and also attitudes and behaviors, which are harder to measure but still valuable. How to write good ones →
Why people care about competencies
- They work even when training doesn't. If someone can prove the skill, it doesn't matter how they learned it.
- They guide planning, teaching and assessment. Everyone is aiming at the same target.
- They show preparedness and trustworthiness. A proven skill tells employers and teammates what they can rely on.
- They contribute to careers. Each one tells part of a person's story.
Where CDD came from, and our role
Grow Strong is a steward of CDD. That means we care for the method, teach it to the public, and want to see it used widely. You're welcome to implement it on your own. We encourage that. If you'd like a hand building or running a system, you're welcome to invite us in. And if CertifyHub is the best tool for your team, we hope you'll use it. If another tool suits you better, use that.