Royal Army College

Lesson Overview

A course exists, fully, only when it is run. Up to this point the systems approach has been design work: the need analysed, the objectives written, the course designed, the materials developed. All of that is potential, a course on paper, and the stage where the paper course becomes a real one, delivered to real learners by real instructors, is implementation. It is the stage most easily neglected by designers, who can feel the job is done when the design is finished, and yet it is where a sound design either proves itself or reveals the gaps that only contact with reality exposes. This lesson is about putting a course into service: preparing to run it, trialling it before committing to it, running it as designed, and handing it over so it can be run again well by others.

The governing truth of implementation is that a design rarely survives first contact with a real course unchanged, and the wise designer plans for that rather than being surprised by it. A timing that looked right on paper runs long; an explanation that was clear to the designer confuses the class; a sequence that seemed logical leaves a gap; a resource assumed available is not. None of this means the design was bad; it means a design is a prediction, and predictions meet reality at implementation. So a course is implemented in a way that catches these things safely, ideally through a trial or pilot run before it is rolled out in full, and then refined, so that the gap between the course as designed and the course as delivered is found and closed early, on a small scale, rather than discovered after the course has produced a year of graduates who did not quite get what they needed.

This is the knowledge layer. It teaches you how a course is prepared for service, trialled, run as designed, and handed over, so that you understand how a designed course becomes a delivered one. The actual running of a course, the instruction, the assessment, the day-to-day supervision, is the work of TRG 301, TRG 310, and TRG 320, performed in person and signed off; this lesson is the designer's and the course manager's view of putting a course into service and keeping it running true to its design. Read this to know how a course is implemented; the delivery itself is mastered in the instructional courses.

By the end you will be able to explain why implementation is a real and distinct stage and why a design rarely survives first contact, prepare a course for service (instructors, materials, resources, audience, programme), trial a course before full roll-out, run a course true to its design, and hand a course over so others can run it well.

Key Terms

Implementation: the stage of the systems approach in which a designed course is put into service and delivered to real learners; the design made real.
Trial (pilot) run: a first, controlled running of a course on a small scale, to prove the design and find its faults before full roll-out.
Roll-out: the full deployment of a course into normal service once it has been trialled and refined.
Course as designed vs as delivered: the distinction between the course on paper and the course actually run, the gap between which implementation finds and closes.
Instructor preparation: the training, briefing, and standardisation of the instructors who will deliver the course, so they teach it as designed and to the standard.
Training audience: the learners a course is run for, whose starting level, numbers, and needs the implementation must match (as the analysis assumed).
Course programme: the worked-out timetable of a running of the course, sequencing lessons, practicals, and assessments against the available time and resources.
Handover: the passing of a course from its designer to those who will run it, with the materials, instructions, and standard needed to run it well.
Course manager: the person responsible for running a particular delivery of a course, holding its programme, resources, instructors, and standard together.
Refinement: the controlled adjustment of a course after trial or early running, to close the gaps between design and delivery without losing the design's integrity.

Why implementation is a real stage

It is tempting to think a course is finished when it is designed, and that running it is mere administration, but this underrates implementation badly. Implementation is where the design meets the three things it could only assume on paper: real learners, who arrive at a different starting level or in different numbers than expected; real instructors, who must understand and deliver the design rather than the designer holding it all in their own head; and real conditions, the actual time, rooms, equipment, and weather, which never quite match the plan. A design is a set of predictions about how teaching will produce learning; implementation is where those predictions are tested against reality, and reality always has something to say.

This is why a design rarely survives first contact unchanged, and why a good designer treats the first running not as the simple execution of a finished thing but as the final, decisive part of the design process. The timing that overran, the explanation that confused, the practical that needed more time, the assessment that was too hard or too easy, these are not failures but discoveries, the design telling the designer where its predictions were wrong so they can be corrected. A designer who takes early running as feedback improves the course quickly toward what actually works; one who treats the design as finished and blames the instructors or the students when it does not run smoothly learns nothing and leaves a flawed course in service.

The practical conclusion is that implementation is planned and watched as deliberately as design, and built to surface and absorb the inevitable gaps. The chief tool for that is to try the course before committing to it fully, which is the trial run, and to prepare everyone and everything so the running is fair to the design, which is implementation's preparation. Both follow.

Preparing a course for service

Before a course is run, it is prepared, and the preparation is what gives the design a fair chance to work. A course launched with unready instructors, missing materials, or a mismatched audience will run badly regardless of how good the design is, and its faults will be wrongly blamed on the design. Preparation covers a handful of things.

The instructors are prepared, which is the most important and most neglected part. The people who will deliver the course must understand its design, its objectives, and its standard, and must be able to teach it as intended, not as each privately prefers. This means briefing and, where needed, training the instructors on the course, and standardising them so they teach and assess to one standard, exactly as TRG 310 standardises assessors. A course is only as good as its delivery, and its delivery depends on instructors who own the design.

The materials and resources are ready and complete: the lesson materials, the training aids, the assessment instruments, and the physical resources, equipment, rooms, ranges, ammunition, the course needs, all confirmed available for the running, not assumed. A course that stops because a resource the design required is not there has failed in preparation, not design.

The training audience is matched to what the analysis assumed: the learners arrive at the starting level the course was designed for (with prerequisites confirmed, as the catalogue requires), in numbers the course can handle, and prepared for what is coming. A course designed for one audience and run for a very different one, more or less prepared, more or fewer, will not work as designed, and the mismatch is corrected before the course runs, not discovered during it.

The programme is worked out: the actual timetable for this running, sequencing the lessons, practicals, and assessments against the real available time, instructors, and resources, with sensible slack for the things that always overrun. The programme is the design realised as a runnable schedule, and the course manager holds it.

   PREPARING A COURSE FOR SERVICE  (give the design a fair chance)

   INSTRUCTORS      understand the design, objectives, and standard;
                    trained and STANDARDISED to teach and assess alike
                    ......... the most important, most neglected part
   MATERIALS &      lessons, aids, assessments, equipment, rooms,
   RESOURCES        ranges, all confirmed AVAILABLE, not assumed
   TRAINING         starting level, prerequisites, and numbers MATCH
   AUDIENCE         what the analysis assumed
   PROGRAMME        the real timetable for this running: lessons,
                    practicals, assessments, with slack for overruns

   A badly prepared course runs badly whatever the design, and the
   design gets the blame. Prepare so the design can prove itself.

Trialling before roll-out

Because a design rarely survives first contact, a new or substantially changed course is, wherever possible, trialled before it is rolled out in full: run once on a small, controlled scale to prove the design and find its faults before committing the whole training effort to it. The trial run is the systems approach's safeguard against fielding a flawed course at scale, and it is the cheapest possible place to find a design's problems, on one small course rather than after a year of full deliveries.

The trial is run as close to the real thing as possible, with a representative audience and the actual materials and instructors, precisely so that it surfaces the real gaps. It is watched closely, with the designer present or fully informed, and everything that does not work as predicted is captured: the timings that were wrong, the explanations that confused, the sequence gaps, the assessment that misfired, the resource that fell short. Then the course is refined in light of the trial, the gaps between design and delivery closed, before it is rolled out into normal service. Crucially, the refinement closes the gaps without losing the design's integrity: it corrects what reality showed to be wrong, but it does not let the course drift away from its objectives in the process, which is the discipline that links to the standards governance of Lesson 09.

Where a full trial is not possible, and in a small force it sometimes is not, the same logic is applied in miniature: the first running is treated explicitly as a trial, watched and captured and refined, rather than assumed to be the finished article. The principle holds either way: prove the course small before betting the training effort on it large, because the cost of finding a flaw in a trial is a little time, and the cost of finding it after a year of graduates is a year of capability that was not quite there.

Running it true to the design, and handing it over

Once prepared and trialled, a course is run, and the designer's and course manager's concern shifts to running it true to the design. A course's value lies in delivering its objectives to its standard, and that is lost if, in delivery, it quietly drifts: instructors teaching their own version, the standard creeping up or down, parts skipped under time pressure, the assessment softened. Running it true means the instructors deliver the designed course to the designed standard, the course manager holds the programme and the standard against the pressures that erode them, and the discipline of the design is maintained through the running. This is the delivery-side partner of the standards maintenance of Lesson 05: a course kept true in the running is a course that keeps delivering what it certifies.

At the same time, the running is watched and captured as continuing feedback, because even after trial and roll-out a course goes on revealing things, and these feed the evaluation and improvement of Lesson 10. Records of how the course ran, where it strained, how the learners did, are kept, not as bureaucracy but as the raw material for keeping the course good over time.

Finally, a course must be capable of being run well by people other than its designer, which is the point of handover. A course that only its designer can run is a fragile thing that dies when the designer moves on; a course properly handed over, with complete materials, clear instructions for running it, the objectives and standard plainly stated, and the instructors prepared, can be run well by the next course manager and the one after. Handover is what turns a course from one person's creation into a durable asset of the College, and a designer's work is not truly finished until the course can run without them. This durability, a course that survives its designer and runs true across many deliveries and many years, is the real product of good implementation.

In Practice: Fielding a New Course

A course designer of the Royal Army College has finished designing a new course, objectives written, course designed, materials developed, and now must put it into service. A weak designer would declare it finished and hand the materials to whoever runs the next serial, expecting it to work because the design was sound. The College's designer treats implementation as the decisive stage it is.

She prepares for service first: she briefs and standardises the instructors who will deliver it, so they teach and assess the designed course to one standard rather than each their own way; she confirms every material, aid, assessment, and resource is actually ready and not merely assumed; she checks the training audience arrives at the starting level the course was designed for, prerequisites confirmed; and she builds a realistic programme with slack for overruns. Then, knowing a design rarely survives first contact, she trials the course on a small, representative running before full roll-out, watching it closely and capturing everything that does not work as predicted: a practical that needed more time, an explanation that confused, a timing that overran. She refines the course to close those gaps, correcting what reality showed wrong without letting it drift from its objectives.

Only then does she roll it out, and even then she has the early runnings watched and captured as continuing feedback for Lesson 10's evaluation. And she hands it over properly, with complete materials, clear running instructions, the objectives and standard plainly stated, and the instructors prepared, so that the course can be run well by managers who are not her, and will survive her moving on. The course works in service, not because the design was sound alone, but because it was implemented: prepared so the design had a fair chance, trialled so its faults were found cheaply, run true to its design, and handed over so it endures. That is the difference between a course on paper and a course in service.

Check Your Understanding

Explain why implementation is a real and distinct stage of the systems approach, and why a design "rarely survives first contact unchanged." Why should a designer treat the first running as feedback rather than as the simple execution of a finished thing?
Set out what is involved in preparing a course for service (instructors, materials and resources, training audience, programme), and explain why preparing and standardising the instructors is the most important and most neglected part.
Explain the purpose of a trial run before roll-out and how it is conducted and acted on, and why it is the cheapest place to find a design's faults. Then explain what "running a course true to the design" means and why handover matters.

Reflection (write a short paragraph): This lesson says a course only truly exists when it is run, and that a course no one but its designer can run is a fragile thing. Think about something you have built or planned that worked in your head but ran into trouble when it met reality, and how a small trial would have helped. Then consider: if you designed a course and were posted away the next week, what would you need to have prepared, materials, instructions, standardised instructors, so that the course kept running well without you? What does that tell you about when a designer's job is really finished?

Summary

Implementation is the stage where a designed course becomes a delivered one, meeting real learners, real instructors, and real conditions it could only assume on paper. A design rarely survives first contact unchanged, so the wise designer treats early running as decisive feedback, not as mere execution.
A course is prepared for service so the design gets a fair chance: instructors trained, briefed, and standardised to teach and assess alike (the most important, most neglected part); materials and resources confirmed ready, not assumed; the training audience matched to the assumed starting level, prerequisites, and numbers; and a realistic programme with slack for overruns.
A new course is trialled on a small, representative scale before roll-out, to prove the design and find its faults cheaply, then refined to close the gaps between design and delivery without losing the design's integrity. Where a full trial is impossible, the first running is explicitly treated as one. Prove the course small before betting the training effort on it large.
A course is run true to its design (instructors delivering the designed course to the designed standard; the course manager holding programme and standard against the pressures that erode them), and the running is watched and captured as feedback for evaluation (Lesson 10).
A course must be capable of being run well by others, which is the point of handover: complete materials, clear running instructions, plain objectives and standard, prepared instructors. Handover turns a course from one person's creation into a durable College asset that survives its designer.
This is the knowledge layer of putting a course into service; the delivery itself, the instruction, assessment, and safety, is the work of TRG 301, TRG 310, and TRG 320, performed in person and signed off. This lesson follows the design and development of Lessons 03 and 04, runs courses to the objectives of Lesson 06, maintains the standard of Lesson 05, and feeds the evaluation of Lesson 10.

Implementing and Running the Course