Today's AI Specialist: The Course Strategist. The Agent Who Turns "Topic, Level, Pathway" Into a Programme You Can Actually Learn From.

Most language courses are built by sequencing what is convenient to teach. Present simple first because it is easy. Past simple next because it is the obvious follow-on. Modals later because the rules are messy. Pronouns somewhere in the middle because they have to go somewhere. Vocabulary attached to whichever lesson it fits least awkwardly.

The result is a course that looks coherent from the inside and produces learners who, three months in, can conjugate verbs they will never use under pressure and cannot ask the question that matters to the meeting they are walking into on Wednesday.

The Course Strategist refuses to build courses that way. She sequences from what the learner has to be able to say at the end of the programme, back through the scenarios that get them there, and only then asks what each lesson should contain. The convenience of what is easy to teach does not enter the design until the end.

She is the agent I want to walk through today.

What the Course Strategist is, precisely

The Course Strategist is the curriculum architect on the Editorial Director's Curriculum & Content Production team. She is a strategic Slovak woman in her early forties, Bratislava-born and Zurich-based for the last decade, with the sharp asymmetric bob — chin-length on the right, angling noticeably longer toward the left jaw — that her team has come to recognise as the deliberate architectural haircut signalling her design sensibility. Warm hazel eyes, neatly defined eyebrows. The day she designs in: a deep raspberry fine-knit jumper over a cream collared shirt.

Her remit is the strategic structure of any professional fluency programme. Given a topic, a CEFR level, and a pathway, she returns the structure that gets the learner from where they are to the named outcome — pathways, milestones, the order lessons should run in, and which scenarios the Dialogue Creator builds for.

She does not write scripts. The Lesson Script Writer does that. She does not write assessment items. The Assessment Builder does that. She does not price the course or position it in the market — that is a Council-and-above decision. The seat exists to do one thing well: design the architecture of a learning programme that survives contact with real professional life.

Why does this need to be a separate agent?

The honest answer is that it did not have to be. For the first year of EFO, the course content production happened end-to-end inside a smaller pipeline, and structure was implicit in whatever the script writer was producing.

The pipeline scaled to about a dozen courses before the structural problem surfaced. Different courses started to share the same five lessons but in different orders, and the order mattered. A course that introduced the negotiation scenario in week three produced different learner outcomes from a course that introduced it in week seven, even when the lesson scripts were identical. The structure was doing real work nobody had named.

The Course Strategist was the moment I separated the architectural job from the writing job. The same model writes very different programmes depending on whether the architectural decisions have been made deliberately upstream or are being made implicitly inside the script. Separating the two meant the architecture became reviewable on its own terms, and the writing became cleaner because the writer was no longer simultaneously designing.

What does she actually do per programme?

Four things in order.

First, she defines the named outcome. Not learner improves their English. Specifically: learner can run a fifteen-minute weekly progress call with an English-speaking project sponsor at C1 register, including hedge-and-commit moves, on a project they own. The named outcome is what the rest of the architecture sequences toward. If the outcome cannot be named that precisely, the seat refuses to design the course. A named outcome is the load-bearing input.

Second, she works backwards from the outcome to the scenarios. What scenarios does the learner have to be able to handle to produce the outcome cleanly? For the progress-call example, the scenarios include: opening a status report, acknowledging slippage without over-apologising, naming a risk before being asked, accepting feedback in real time, closing with what the speaker is asking for. Each of those is a named scenario she lists explicitly. They become the briefs the Dialogue Creator works from.

Third, she sequences the scenarios. The sequencing follows the cognitive-load curve the learner will actually experience. Not the easiest-first curve. The structural-foundations-first curve. Acknowledging slippage without over-apologising depends on the learner already being able to hedge without weakening their authority, which depends on the learner already being able to name the situation cleanly, which depends on the learner already being able to open the status report without defensive throat-clearing. The Course Strategist's blueprint is a directed graph of dependencies, not a list.

Fourth, she hands the blueprint to the MVP Course Builder as a grid. The grid names every lesson, the scenario it serves, the place it sits in the dependency graph, and the structural moves the lesson has to leave in the learner's hands by the end. The MVP Course Builder takes the grid and builds the smallest credible course that delivers the named outcome. The Course Strategist returns the structure for review at the brief stage; once approved, the writing happens without her further involvement.

What does she refuse to do?

Three things, deliberately.

She does not write lesson script content. That is the Lesson Script Writer's domain. If she pretended to write at the script level, she would lose the clarity of architectural decisions by smuggling content choices into them.

She does not design assessment items. That is the Assessment Builder's domain. The Course Strategist names the assessment moments inside the structure — at the end of week three, the learner has to demonstrate the hedge-and-commit move under timed conditions — but does not write the actual prompt or scoring rubric.

She does not decide the course is worth running. That is a Council-and-above call. Pricing, market positioning, whether this programme deserves a quarter of production capacity — those decisions sit upstream of her remit. She designs the programme that the Council has decided is worth designing.

Who consults the Course Strategist?

Heavily, across the production pipeline and into the journeys the learner sees.

She is consulted by the MVP Course Builder on whether a particular structural decision in the blueprint is actually buildable inside the production constraints, by the Lesson Script Writer when a script idea raises a question the architecture has to answer, by the Dialogue Creator on whether the scenarios as named are dramatically renderable, by the Assessment Builder on whether the named moments allow for valid assessment under realistic time, and by the Editorial Director at the brief stage as the gate that decides whether the architecture is signed off before the writing begins.

Outside the production pipeline, her work shapes the MASTERY journey directly — the 90-day arc the MASTERY programme is built around is a Course Strategist output. The learner does not see her work directly. The learner lives inside it.

What does this cost?

Two things.

It costs the comforting fiction that the writer alone can design the programme. The Lesson Script Writer is excellent. So is the Dialogue Creator. Neither of them is the architect, and pretending that the architecture emerges from good writing is how the first year of courses produced the implicit-structure problem.

It costs me a brief stage that did not exist before. Every programme now passes through an architectural review before the writing begins. That review takes time. The trade is that the writing, when it begins, knows what it is for.

The trade is one I would make again. A learner who reaches the end of a Course Strategist-designed programme can produce the named outcome in a real conversation. A learner who reaches the end of a course where the structure was implicit can pass an exam on the lesson material. Those are very different products.

TL;DR

The Course Strategist is the curriculum architect on the Editorial Director's team. She sequences from the named learner outcome backwards through the scenarios that produce it, designs the dependency graph of the lessons, and hands the blueprint to the MVP Course Builder as a grid. She does not write scripts (Lesson Script Writer's domain), does not design assessment items (Assessment Builder's domain), and does not decide whether the course is worth running (Council-and-above). The seat exists because at scale, the architecture that was implicit in good writing started doing the work nobody had named, in ways that diverged across courses. Separating the architectural job from the writing job costs a brief stage that did not exist before. It buys courses whose graduates can produce the outcome the programme was designed for, not just pass an exam on the material.

---

If you are running an SME and any of this looks like the conversation you should be having about your own programme architecture, that is the side of things I help with. → /build