Curriculum vs Programme

We use these two words like everyone knows what they mean. Then someone puts a module spec or session plan in front of you and suddenly they blur into one. They are not the same thing. Getting them straight is worth doing, because the confusion is where bad programme design hides.

The short version

The curriculum is what we are committed to teaching. The body of knowledge, the professional values, the skills a Youth Worker needs to practise. It is the National Occupational Standards, the ethical framework, the theories of informal education, the understanding of how power works in young people’s lives and how all of that is contested and negotiated. It answers: what should someone leaving this programme know, be able to do, and embody?

The curriculum is the territory. It belongs to the profession, not to any one institution.

The programme is how we organise that. The module sequence, the teaching methods, the assessment schedule, the credit structure, the placement model, the progression rules. It answers: how do we move someone from where they are at intake to ready to practise across three years?

The programme is the map. That one is ours to draw.

	Curriculum	Programme
What is it?	The what: knowledge, skills, values	The how: structure, sequence, delivery
Who defines it?	The profession, over time	Practitioners, within validation parameters
Does it change?	Slowly, by professional consensus	Every cycle, based on feedback and data
What goes wrong?	Gaps: something we promised is not covered	Flow: students drowning because the structure fights itself

Where it gets complicated

That neat separation works fine for most professions. Nursing has a curriculum about aseptic technique and anatomy, and the programme decides whether you learn that in a simulation lab or on placement. The how does not change the what. You can teach anatomy through problem based learning or lectures and the student still ends up knowing where the femur is. Same outcome, different route.

Youth Work does not work like that.

Because our method is relational, voluntary, negotiated. If the programme is delivered through a model where the expert tells, the student receives, and the assessment measures compliance, then the programme is actively teaching against the curriculum. The student learns that hierarchy and standardisation are the real values, regardless of what the module handbook says about participation and empowerment.

In Youth Work, the programme is a second curriculum. It is the one students actually learn from. They might forget the theory of informal education by graduation^[1]. They will not forget that their personal tutor never returned emails, that module choices were made for them without consultation, that the complaints process treated them like customers.

The same fight, one level up

This confusion is not just an institutional problem. The same blurring plays out at sector level with the National Youth Work Curriculum, which is, as you might expect, contested.

The NYWC tries to codify what Youth Work is into a framework of outcomes, progression and entitlement. A written statement of promises every young person can expect. The intention is honourable: protect the quality and consistency of provision, give young people something to hold providers to.

But it imports the same assumption. That someone, or somebody, can decide in advance what the curriculum of Youth Work should contain, regardless of who walks through the door. That the territory can be mapped before anyone has crossed it.

The profession has always said otherwise. The curriculum of Youth Work emerges from the young person. It is negotiated, not prescribed. It starts from their concerns, not from a pre-approved list. A national curriculum document, however well-intentioned, sits awkwardly against that starting point because it is an act of programme logic applied to the curriculum itself. It tries to fix the what in advance, when the what is supposed to be co-authored every time someone walks into a youth club.

So you get two symmetrical problems, at different scales:

• At institutional level: a programme built on training logic that cannot deliver a relational, negotiated curriculum
• At sector level: a curriculum document built on the same logic, trying to standardise something that resists standardisation by its nature

Both come from the same mistake: treating Youth Work as something you can plan, package and deliver, rather than a practice you enter into alongside young people.

The bit that is broken

There is an assumption that a Youth Work qualification can be delivered like any other training product. Standardised inputs. Fixed outcomes. Cohort progression. Assessor led. Tick the boxes, pass the course, qualify.

That assumption works if the curriculum is a neutral list of things to cover. It is not. The curriculum of Youth Work is value-laden. It says young people are partners in their own learning. It says power should be shared. It says knowledge is co-constructed, not transmitted. A programme built on training logic says the opposite in practice, and it says it every day for three years.

The student does not need a lecture on anti-oppressive practice. They need a programme that does not oppress them. They need to experience what it feels like to be taken seriously, to have a say, to be trusted with their own learning. If they do not get that on the programme, no amount of theory will undo what the structure has taught them.

The curriculum says what we stand for. The programme says whether we mean it.

---

^[1] Some of them forget it before the certificate is dry.