Competence standards are the most foundational and most neglected element of certification program design. They define what qualified actually means — precisely enough to be assessed, defended, and enforced.
Without standards, a certification program is a training program with a badge attached. With strong standards, it becomes something the market can trust: a credential that means the same thing every time it's issued.
What Competence Standards Are
Competence standards are explicit statements of what a practitioner must know, be able to do, and be able to judge in order to be considered qualified to deliver a method. They answer the question: what does qualified actually mean?
Standards are not learning objectives. Learning objectives describe what a training program intends to teach. Standards describe what a practitioner must be able to demonstrate — regardless of how they learned it.
This distinction matters: a certification that is purely a record of what the training covered is measuring curriculum exposure, not competence. Standards decouple the credential from the training pathway and anchor it to actual capability.
Three Components of a Competence Standard
- 01Knowledge standards — what a practitioner must understand. The concepts, principles, frameworks, and information that underpin competent practice. Knowledge standards are the foundation — necessary but not sufficient for competence.
- 02Skill standards — what a practitioner must be able to do. The observable behaviors, techniques, and capabilities that constitute effective delivery. Skill standards describe performance, not just understanding.
- 03Judgment standards — what a practitioner must be able to discern and decide. The contextual reasoning that separates expert from novice application of the same method. Judgment standards are the hardest to write and the most important to get right.
Most certification programs write knowledge standards only — describing what practitioners must know, not what they must be able to do or decide. This produces credentials that test comprehension rather than competence.
Why Standards Are Hard to Write
Competence standards are hard to write for the same reason methodology documentation is hard: they require making implicit expertise explicit. The founder knows what qualified practice looks like — but articulating it in terms precise enough to assess is different from knowing it.
The specific challenges:
- Vagueness — standards written at too high a level of abstraction ('demonstrate professional judgment') that can't be assessed consistently
- Over-specification — standards written at too granular a level that capture steps but miss the judgment required to apply them
- Founder-centrism — standards that describe how the founder delivers the method rather than what a qualified practitioner must be able to do
- Training bias — standards written to match what the training program covers rather than what the job actually requires
What Good Standards Look Like
A well-written competence standard is:
- Observable — it describes something that can be seen, heard, or read in a practitioner's work
- Assessable — it can be evaluated with reasonable consistency by a trained assessor
- Meaningful — it reflects something that actually matters for effective practice, not just something that's easy to measure
- Bounded — it's clear about scope, so practitioners know what is and isn't within the standard
A standard that says 'understands the principles of the method' is not assessable — understanding is invisible. A standard that says 'can identify which of the method's three diagnostic phases applies to a given client scenario and articulate the criteria for that selection' is observable and assessable.
The test of a good competence standard: can two trained assessors independently evaluate a candidate against it and reach the same conclusion? If not, rewrite it.
The Standards Development Process
The most effective way to develop competence standards is through a structured process with multiple inputs:
- 01Start with the job — what does an expert practitioner actually do? Observe delivery, review work products, map the decisions practitioners make. Standards should reflect practice, not curriculum.
- 02Involve subject matter experts — people who know the method deeply and can articulate what distinguishes strong from weak practice. Standards written by one person reflect one perspective; panels surface what's truly essential.
- 03Draft against observable performance — for each standard, ask: how would we know if a practitioner met this? If the answer requires inference rather than observation, the standard needs to be rewritten.
- 04Validate with practitioners — test draft standards against real practitioners at different levels of experience. Do the standards distinguish between novices and experts? If experienced practitioners and beginners score the same way, the standards aren't capturing what matters.
Standards Are Living Documents
Competence standards should be reviewed and updated periodically as the method evolves, as the field changes, and as experience with the assessment reveals gaps or over-specifications. A governance process for standards revision is part of what makes a certification program durable.
When standards change significantly, credential holders need to know — and may need to demonstrate continued competence under the updated standard. This is one of the core governance functions: managing how the standard evolves without invalidating what existing certified practitioners earned.
