You are The Articulator.

The Recognition

You have begun to write it down. After years of doing the work — building the judgment, internalizing the standards, developing the instincts — you are starting to make explicit what was previously felt. You are drafting playbooks, naming frameworks, articulating the principles behind the choices you have been making automatically. The tacit is becoming explicit. The instinctive is becoming instructional.

This is harder than you expected. The things you do without thinking turn out to be surprisingly difficult to describe. When you try to write down how you make a particular kind of decision, you discover that the decision involves twelve factors you had never named, integrated in ways that resist simple description. You write a draft. You read it. It does not quite capture what you actually do. You revise. It is still not quite right. You realize that articulating expertise is itself a craft, and you are not yet expert at it.

You have also discovered something the methodology predicts: the act of articulation deepens your own understanding. Writing the playbook forces you to confront what you actually know versus what you merely feel. Parts of your practice that you assumed were settled turn out, on close examination, to be vague. Other parts you assumed were vague turn out to be more precise than you thought. The map you are drawing is teaching you about the territory you have been operating in for years.

The Underlying Mechanic

The methodology describes a knowledge conversion cycle: tacit knowledge (personal, instinctive, embedded in practice) must be externalized into explicit knowledge (documented standards, annotated examples, quality criteria) before it can be transmitted. The Articulator is doing the externalization work — the necessary first step before any meaningful delegation or scaling can occur.

The bias that most affects this phase is the curse of knowledge. Once you have internalized a skill, you lose the ability to imagine what it is like not to know it. Your explanations skip steps that are obvious only to you. Your standards omit criteria so fundamental you cannot conceive of someone not applying them. The drafts you are writing probably feel adequate to you and would feel incomplete to anyone trying to use them. This is not a personal failing. It is the structural difficulty of making transmissible what has become unconscious.

The delegation paradox is also active here. Effective delegation requires more understanding from the delegator, not less. When you do work personally, unconscious competence is sufficient. When you delegate or document, unconscious competence is useless — the person or system receiving the work needs explicit criteria, clear standards, articulated reasoning. The process of making knowledge transmissible is the process of confronting what you take for granted. This is why articulation is genuinely educational for the articulator, even though it feels like documentation work.

The Tension

The tension you navigate is between completeness and action. The articulation could always be more thorough. Every framework you write reveals additional dimensions that could be specified. Every standard you draft suggests three more standards that should be drafted alongside it. The work expands as you do it, and there is no natural stopping point — only the choice to ship the current version and learn from how it is used.

This is one of the methodology's harder boundaries. The Articulator who waits for completeness produces beautiful, never-released documents. The Articulator who ships too early produces standards that fail in use and have to be reworked. The middle — release a version, learn from application, revise based on real use — is what produces transmissible knowledge that compounds. The transmission is the goal, and transmission requires release. Completeness is not the goal in itself.

The Gift

What you have, that the unarticulated expert does not, is knowledge that begins to travel. Once your understanding is externalized, it can be shared, scaled, deployed by others, encoded into AI workflows, used as the basis for training. Your impact stops being capped by your personal hours. The years of accumulated experience finally become an asset that compounds outside you.

This is one of the most consequential transitions available in the methodology. Most experts never make it. They die with their understanding still tacit, and the field is poorer for it. The Articulators are the ones who leave the work easier for the next generation than it was for them — which is, in a real sense, the highest form of contribution a practitioner can make.

The Next Move

In the next 14 days, build the annotated example library for one specific area of your practice. Not a framework. Not a checklist. A collection of real work — three to five concrete examples — annotated to show what makes each one excellent, acceptable, or inadequate, and why. Each annotation should explain the reasoning behind the assessment, not just the assessment itself. Examples beat frameworks. Annotated examples beat descriptive examples.

The trap most Articulators hit on this move is writing more frameworks before building the example library. Frameworks are easier to write — they feel like real expertise compressed into elegant form. They are also harder to use without examples, because the framework only works when you can match new situations to the prototypes embedded in your understanding. The examples are the prototypes. Without them, the framework is abstract. With them, the framework becomes operational.

This is one move from your free assessment. The full Personal Profile reveals your six-domain resource map with attention to which dimensions are being depleted by the articulation work versus which are being built, your Trust Formula scores with focus on how externalized knowledge changes the dynamics of all three factors, the bias-specific warnings for the Articulator phase (curse of knowledge, Dunning-Kruger at the expert end, IKEA effect), and the 90-day sequence that turns the first example library into the infrastructure for actual delegation. If a single move is useful, the full diagnostic is where the real work happens.