The intellectual territory
Transformative Learning Architecture
What is actually designed at the personal, professional and institutional levels, and what is merely inherited and then blamed on the individual.
01 · Definition
What it is.
Transformative Learning Architecture is the deliberate design of the conditions under which experience becomes judgment. It treats capability development as an architectural problem of structures, sequences, constraints and feedback, rather than a motivational or content problem.
What it helps you see
Which conditions in a workplace or institution actually produce judgment, who designed them, and what happens when nobody did.
What it is not
A curriculum, or a maturity model. It is not a scale you score against.
02 · The central problem
Provision is designed. Conditions are inherited.
Organisations design provision carefully: catalogues, platforms, pathways, budgets. They almost never design conditions: what work gets allocated to whom, what struggle is preserved, what is reviewed, what is escalated, what is safe to get wrong. Provision is visible and procurable. Conditions are invisible and free, so they are inherited from operations.
Capability then tracks the inherited conditions rather than the designed provision, which is why learning investment and capability outcomes correlate so weakly.
03 · Theoretical foundations
What this work builds on.
This is not a new discovery dressed as one. It stands on established traditions and should be judged against them.
- Transformative learning and perspective transformation
- Self-directed and self-regulated learning
- Situated learning, legitimate peripheral participation and communities of practice
- Cognitive apprenticeship and deliberate practice
- Community of inquiry research on presence and affective outcomes
- Curriculum theory, particularly the distinction between intended, enacted and experienced curriculum
The contribution claimed here is architectural framing and the AI-era extension, not the underlying learning theory.
04 · Three levels of architecture
What is actually designed at each level.
Nobody, explicitly
Attention, sequence, difficulty, reflection and the decision about what to stop doing.
A body or employer
What counts as competence, how it is assessed, and which work is considered delegable.
Operations, by accident
Workload, review, tolerance for error, and what is actually rewarded rather than stated.
The characteristic failure is designing at one level and expecting the other two to comply.
05 · Human capability in the AI age
The conditions that built judgment are being removed.
Professional judgment has historically been a by-product. It accumulated because juniors did work that was slow, effortful and reviewed. The first draft, the initial analysis, the rough plan: that is exactly the work now most easily delegated to a model.
The immediate effect is welcome: faster output, less drudgery. The structural effect is that the apprenticeship mechanism has been quietly disconnected, and no replacement has been designed. This is an architecture problem, and it is the reason the AI-native distinction matters.
How far the evidence goes. This is an argument about mechanism, not a measured finding. It has not been tested longitudinally, the size and timing of any such effect is unknown, and it should be read as a hypothesis worth designing against, not as an established outcome.
06 · Professional applications
Where this applies to a profession.
Two professions are examined publicly on this site because they make the problem unusually legible: education, where the professional is expected to model judgment while their own conditions erode, and project work, where a plausible plan has never been cheaper and a sound one has never been harder to distinguish.
- The AI-Native Educator: public teaching
- The AI-Native Project Professional: public teaching
07 · Institutional applications
Where this applies to an institution.
Institutions usually arrive with one of two needs: a question they want investigated, or a capability they want built. The first is a research collaboration. The second is implementation work. They run differently and it helps to know which one you are starting.
08 · Research agenda
What is not yet known.
- Which conditions actually predict judgment transfer, as opposed to satisfaction or confidence?
- Can workflow-level governance substitute for the apprenticeship work that AI has absorbed?
- What institutional conditions predict whether capability work survives contact with operations?
- Can capability be described developmentally without implying a rank or a verified competence?
09 · Implementation
From territory to working practice.
Designing conditions is not a workshop. It means examining how work is currently allocated, what gets reviewed and what does not, where difficulty is productive and where it is merely expensive, and then rebuilding the workflow so capability is a by-product of the work again rather than an afterthought.
That is what Edney Learn builds.
Project Manager: Pilot · Author and Consultant: AvailableThe Project Manager offer is at pilot stage. Author and Consultant are available product families. Participation, terms and evidence are governed by Edney Learn.
Originated by Dr Jim Choo. Operated by Edney Learn.
Discuss a research or scholarly collaboration.
Public research collaboration, scholarly interpretation and invited speaking are handled directly.