ARCHITECT
Most experts do not lack knowledge. They lack intellectual architecture.
Years of hard-won expertise stay underused, not because the ideas are weak, but because they have never been given a structure that makes them teachable, transmissible and extendable. ARCHITECT is a nine-step method for extracting that knowledge and giving it a form other people can use.
01 · The problem it solves
Expertise that cannot be structured stays trapped in the person holding it.
Expertise that cannot be structured stays trapped in the person holding it. The symptoms are consistent:
- the idea is difficult to state in one clear, defensible sentence
- the expertise is too broad to position for a specific audience
- the insight is rich but has no named framework to anchor it
- the work is stuck in one format when it could support several
- the knowledge was published with no wider strategy behind it
None of these is a knowledge problem. They are all architecture problems.
02 · Why extraction comes first
You cannot allocate work you cannot name.
You cannot allocate work between a human and a machine if nobody can say what the human actually knows.
Every decision about what to delegate, what to verify and what to escalate depends on tacit expertise having been made explicit first. This is where most workflow redesign quietly fails: the knowledge was never extracted, so the allocation is guesswork wearing a diagram.
The same is true of turning expertise into a book, a framework or a teachable method. You cannot codify what has not been recovered. Extraction is upstream work. Everything else waits on it.
03 · Where it sits
Extraction, then design, then augmentation.
First
ARCHITECT
Knowledge extraction. Nine steps. Feeds stage 2, Recover.
Then
Workflow Design Method
Ten stages, Define through Optimise. The Edney Learn operating standard.
Result
AI-augmented practice
An expanded scope of responsible work.
ARCHITECT also feeds the Consultant and Author verticals, which begin from extracted, codified expertise.
Extraction, then design, then augmentation. Attempting the third without the first is the most common and most expensive mistake in this work.
04 · The nine steps
ARCHITECT is an acronym. Each letter names a step.
Each step answers one question.
Articulate
What exactly is being claimed, and what does it defend that others do not?
Recover
What does this expert actually know that has never been written down?
Code
What is the underlying structure, and where are its boundaries?
Hang
Does the argument hold together across every form it will take?
Instrument
What evidence supports this beyond personal assertion?
Transfer
What has to exist for someone else to apply this, not just understand it?
Edit
Is the reasoning coherent, or only the prose?
Certify
Would this hold up to a peer, a practitioner and a sceptic?
Turn
What else can this become without fragmenting?
How each step is run, what it produces and how an engagement is configured are held by Edney Learn.
05 · Architecture first, format second
Begin a level deeper than the output question.
Most approaches begin with the output question. This one begins a level deeper.
The common approach
Decide the format before the idea is clear. Produce more output without a stronger structure underneath. Publish once, with no plan for what follows.
The architectural approach
Clarify the idea before scaling it. Strengthen the framework before publishing it. Design for transfer before chasing reach.
That is the difference between producing more content and building a body of work.
06 · Who this is for
Four kinds of reader.
- Experts with deep knowledge and no named framework yet.
- Scholars whose research needs to travel beyond the academy without losing its integrity.
- Organisations whose critical knowledge lives in a handful of people and has never been documented.
- Professionals approaching AI-augmented work, who need to know what they know before deciding what to delegate.
07 · How it is delivered
Originated by Dr Jim Choo, operated by Edney Learn.
ARCHITECT is Edney Learn’s human-led knowledge recovery and codification method, originated by Dr Jim Choo. Dr Jim Choo teaches and develops its intellectual foundations publicly. Edney Learn owns, governs, productises, delivers and evidences the method.
Within the Edney Learn operating standard it is invoked primarily inside Recover, the second stage of the ten-stage workflow design method. It is also the upstream work behind the Consultant and Author verticals, both of which begin from expertise that has to be recovered before anything can be built on it.
Consultant and Author: Available product familiesAvailability, terms and support are set by Edney Learn.
Where this connects.
The method it feeds, the continuity problem it answers, and the workflows built on it.