The Body of Work
One question, pursued through connected frameworks.
How do the conditions for professional capability get designed, and what happens to those conditions when the work that used to build judgment is handed to a machine?
01 · The thesis
Capability is a design problem, not a motivation problem.
The standard explanation for weak professional development is that people lack discipline, time or incentive. That explanation survives because it is cheap. The stronger explanation is that the conditions which convert experience into judgment are almost never designed. They are inherited from whatever the institution happened to build for other reasons.
When those inherited conditions are good, capability appears to develop naturally and we credit the individual. When they are poor, capability stalls and we blame the individual. In both cases the architecture did the work and went unexamined.
Transformation is not a feeling. It is a designed outcome, and someone is always the designer, usually by default.
02 · Three levels of architecture
The same problem, at three scales.
Personal
The curriculum of one person’s becoming. Mostly unowned, mostly implicit, and increasingly outsourced to whatever a recommendation system serves next.
Professional
What a profession treats as competence, how it assesses it, and which parts of the work it considers safe to delegate.
Institutional
What an organisation actually rewards, measures and protects, which is frequently not what its capability framework says.
The levels are not independent. A personal learning system built inside a professional standard that rewards output volume will produce output volume. Designing at one level while ignoring the others is the most common failure in this work.
Explore by topic
Prefer to enter through a question?
The Body of Work shows how the frameworks connect. If you are looking for a particular problem instead, the Topic Hubs gather the relevant essays, books, frameworks, research and video around six recurring questions.
03 · The frameworks
Five connected frameworks and implementations.
Ideas you can explore
Transformative Learning Architecture
The territory. The deliberate design of the conditions under which experience becomes judgment, at personal, professional and institutional levels.
The Self-Curriculum
The personal layer, and the foundational text. How adults design their own transformation in the age of AI.
PAPER
ForthcomingIn final typesetting; estimated publication October 2026.
Philosophy, Attitude, Process, Education, Resource. A framework for identifying what is actually constraining growth.
SALAD
ForthcomingNot yet published. No publication date is confirmed here.
Standard, Awareness, Learning, Action, Delivery. A framework for turning a need for change into progressive value.
AI-Native Professional Capability
The nine capability domains, and the public argument about accountable human–AI work.
Turning the ideas into practice
The ideas above are free to read and use. Building them into how an organisation actually works is a different job, and Edney Learn does it: the ten-stage workflow design method, ARCHITECT, the capability profile, and the role-specific workflows, pilots, workshops and coaching that come from them.
04 · ARCHITECT
Knowledge recovery and codification.
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.
The intellectual problem ARCHITECT addresses is that most professional knowledge is tacit, distributed and undocumented at exactly the moment someone tries to design a workflow around it. You cannot allocate work between a human and a machine if nobody can say what the human actually knows.
ARCHITECT is a nine-step knowledge extraction method that feeds Recover, the second stage of the workflow design method below.
05 · Method
The Edney Learn Workflow Design Method.
What the method is for. It takes a workflow that people run by habit and turns it into one that can be reasoned about: what the work must produce, what only a human can decide, where the output gets checked, and what has to be escalated rather than absorbed. The result is a workflow someone else can pick up, audit and improve.
The canonical description, and every operational detail, belongs to Edney Learn.
- 01Define
- 02Recover
- 03Map
- 04Allocate
- 05EngineerEscalation control
- 06GovernEscalation control
- 07Test
- 08Validate
- 09Document
- 10Optimise
Stage 2, Recover, is where ARCHITECT is invoked. Escalation is a mandatory control inside Engineer and Govern, marked above. It is not a separate stage, and it does not renumber the ten.
Originated by Dr Jim Choo. Operated and governed as an operational method by Edney Learn.
06 · Current research direction
Where the work is being tested.
This is an early research programme. There is a peer-reviewed publication record in online learning and community of inquiry, and a developing agenda on capability, judgment and workflow governance. The frameworks here are conceptual and have not been established as measurement models.
Where does this apply to your work?
Four routes, depending on what you do.