Public draft 0.1.0 · open for comment
What if every cohort got a better program than the last?
The Education Development Lifecycle (EDLC) is a proposed ten-stage model for how education material is developed, released, delivered and improved. It starts from the standard and writes the assessment before the content. Every stage ends in a review, and what delivery teaches flows back into design.
One loop, not a project with an end date
Stages 1 to 8 design and release a program. Stages 9 and 10 run it with real learners and feed what is learned back into the standard and the plan. The return path is the point: improvement becomes routine, not a one-off evaluation.
- Discover — Who is this for, and what do they need?
- Specify — What exactly must a learner be able to do?
- Architect — How will every outcome be taught and assessed?
- Scaffold — Is the shape of the whole package right?
- Test-first — What evidence will show the learner can do it?
- Build — What does a learner need to succeed at those assessments?
- Orchestrate — Can this be delivered in the time and modes we have?
- Validate and release — Is it fit for use, and which version is going out?
- Deliver and observe — How is the program performing with real learners?
- Improve — What did we learn, and where does each change go?
The problem it answers
Most learning programs are built once, audited occasionally and improved rarely. After release they drift: examples age, standards are revised, trainers patch gaps informally, and the evidence of how learners actually performed seldom reaches the people who designed the program.
Specification first
Every program traces to an explicit learning standard, regulated or authored in-house.
Evidence before content
Assessment is designed before learning materials, so content exists to enable demonstrated outcomes.
Gates at every stage
Detail grows stage by stage, and each stage is reviewed while errors are still cheap to fix.
Traceable end to end
Every task, content block and session traces to the outcome it serves, and back again.
Versioned releases
Every cohort receives an identifiable version, so results can be tied to what was delivered.
Close the loop
Findings from delivery and validation become change requests that re-enter the lifecycle.
Who it is for
The stages and artefacts are the same everywhere. How strict each gate is depends on where you work: regulation sets the strictness of a gate, not whether the stage exists.
Vocational providers
Existing review and validation requirements already supply several of the gates. The EDLC extends them into delivery and improvement.
Universities and schools
Subjects and units treated as living programs with an owner, versions and evidence from each offering.
Workplace learning
Corporate academies applying the same stages with lighter gates and their own capability standards.
Independent experts
A craft or discipline taught online, specified and improved with the same loop.
A draft, tested in the open
The EDLC is a proposal. Its claims have not yet been tested empirically, and its practitioner grounding comes mostly from one sector in one country. We invite designers, trainers, researchers and regulators to test, challenge and improve it.