Learn CDD · Page 2 of 8

How to write strong competencies

A competency is only as useful as it is well written. Six principles, which spell STRONG, keep yours worth earning and easy to prove.

In this guide Page 2 of 8

Competencies versus everything else

People often confuse a competency with other things in a learning plan. Here's the difference.

Term What it describes Example
Learning activity What the teacher or system does Show a video about VueX in a new VueJS application
Learning objective What the learner will do in the lesson Students will hear about how to use VueX in VueJS applications
Learning outcome What the learner can do after the lesson After the live coding demonstration, the learner will build functional front-end applications using VueX and VueJS
Competency A lasting skill the person holds Build functional user-input-driven front-end applications using VueX and VueJS

Notice how the competency drops the lesson context ("after the live coding demonstration"). It describes the skill itself, so it still means something after the class is forgotten.

Write it from the master's point of view

Learning outcomes often begin "Student will be able to…" (the learner's view). Competencies read as if the person already has the skill: "Repairs a 1cc gasoline-powered engine." Drop the lead-in and start with the verb.

The six STRONG principles

Significant

Valuable, important, worthy.

A strong competency is independently valuable to the widest audience possible, for the longest time possible. It should feel like a goal, not a chore.

Weak

"Signed all HR paperwork."

Better

"Differentiates the merits of 24 and 26 pay-period models."

Weak

"Attended XYZ conference."

Better

"Manages company keys and secrets using HashiCorp's Vault."

Ask: Is this worth someone's time? Would anyone outside this class care that a person has it?

Targeted

Appropriate, leveled, tethered.

A strong competency is intentional about the level of mastery it targets. The verbs you choose set the level. "List five benefits" and "Defend the need for" are very different asks.

A ladder of verbs, using the same subject:

  1. Define basket weaving.
  2. Recognize the five basket styles.
  3. Use a template to weave a basket.
  4. Experiment with different techniques.
  5. Defend the use of baskets over plasticware.
  6. Design a new style of basket.

Another example, same topic at different levels:

  • Understand the purpose of the SOLID principles.
  • Apply the SOLID principles to an object-oriented interface and class.
  • Defend the need for SOLID principles in mobile application development.

Ask: What level of mastery do we really need from this role? Are the verbs matching it?

Reasonable

Reachable, attainable, possible.

A strong competency is within reach of the people it's assigned to. If it's too hard, people won't engage.

Too hard for kindergarteners

"Describe the relationship between illustrations and the story in which they appear."

Reachable

"With prompting and support, describe the relationship between illustrations and the story in which they appear."

Ask: Can the people we'll assign this to actually get there?

Observable

Measurable, provable, evident.

A strong competency can be shown through measurement and evidence. The best ones need about 60 seconds to prove.

Hard to observe

"Feels genuine respect for all co-workers and supervisors."

Observable

"Demonstrates a respectful attitude towards co-workers and supervisors."

Some skills are harder to see, like attitudes and values. There may still be ways to detect them, through consensus or intuition. What matters is that they're measurable at the level you're targeting.

Ask: How would an evaluator know? What would they see?

Narrative

Descriptive, signaling, advertising.

A strong competency tells part of the story of what its holder can do. A resume tries to tell a story about a whole career. A competency tells the story of one skill.

Not narrative

"Pass a written test to demonstrate your readiness to care for dolphins."

Narrative

"Teach tricks and special behaviors to dolphins of all varieties." / "Design a nutrition plan for a healthy and active adult dolphin."

Ask: If an employer read only this line, would they know what this person can do?

Granular

Right-sized, balanced, focused.

A strong competency balances value against size. Too large and it becomes impossible to attain or measure. Too small and it loses its value.

Too big

"Lists the leaders of all countries for the past 100 years."

Right-sized

"Lists the leaders of Honduras for the past 100 years."

Too big

"Rebuilds all engine parts from a Cummins diesel V12 engine."

Right-sized

"Cleans the cylinder block of a diesel engine." / "Detects damage and imperfections in a diesel cylinder block."

Too big? Try these questions: Can you split it into two or three? Is it a compound statement? Is the target too broad? Is it too difficult?

Putting the six together

A strong competency is valuable, targeted at the right level, reasonable to achieve, measurable, right-sized, and tells part of the holder's story.

Before and after:

A typical training outcome
After the live coding demonstration, the learner will build functional user-input-driven front-end applications using VueX and VueJS.
Becomes a STRONG competency
Build functional user-input-driven front-end applications using VueX and VueJS.

Types of competencies

Competencies can be about:

  • Skills and knowledge, which are easier to measure
  • Attitude, behavior, leadership, motives and values, which are harder to measure

Both matter. Start with what you can measure confidently. Add the harder ones when you have a good way to observe them.

Putting CDD to work?

You can run it yourself, bring us in to help, or use a tool that fits. We're glad to talk through any of it.

Start a conversation