Last updated: 2026-09-23

U
Undergraduate level

How Much Structure to Impose: A Design Decision Guide for Educators

This page doesn't re-argue the theory — Pedagogy, Andragogy, Heutagogy, Rhizome covers the four positions in full, and Personal Learning Maturity covers the maturity progression a learner moves through. This page is the other side of that same coin: a practical decision guide for someone designing a module, an assessment, or a piece of guidance, who needs to decide how much of the "what, how, and when" to fix in advance versus leave to the learner. The flowchart below is meant to be walked through per decision, not answered once for a whole course — the right answer for a first-year foundational topic and a final-year project brief is routinely different, sometimes within the same module.

graph TD A["A design decision:
a module, an assessment,
a piece of guidance"] --> B{"Does it depend on
foundational content
the learner doesn't
have yet?"} B -->|Yes| C["Pedagogy: fix the content,
sequence, and pace.
Not a failure of trust —
the learner can't yet judge
what they don't know."] B -->|No| D{"Is the target outcome
a checkable competency
(a fact, a technique,
a known procedure)?"} D -->|Yes| E["Andragogy: fix WHAT is
learned, let the learner
choose HOW and WHEN.
State the outcome as a
testable Given/When/Then."] D -->|No, it's judgement
or transfer| F{"Does the learner already
have the foundational
competency this assumes?"} F -->|Not yet| E F -->|Yes| G{"Is the field changing
faster than your own
review cycle?"} G -->|No| H["Heutagogy: fix the outcome,
let the learner set their
own path to it. State the
syllabus's own coursework-
sharing/reuse position."] G -->|Yes| I["Rhizome: point at the
practitioner community/
current literature as a
supplement — the syllabus
can't be the final word."] style C fill:#FFC857 style E fill:#00A896,color:#fff style H fill:#FF7B2A,color:#fff style I fill:#C9A8E0

What Each Outcome Actually Means to Do

  • Pedagogy (fix everything): this is the correct, default choice for genuinely foundational material — it isn't a lesser option to graduate out of as fast as possible. See the theory page's account of why a learner without the background can't yet judge what's worth learning next.
  • Andragogy (fix what, free how/when): state the outcome as a concrete, testable scenario rather than a vague aim — Project Marking as BDD covers writing a rubric line as a Given/When/Then a student can check their own work against before submitting, which is the practical form this design choice takes.
  • Heutagogy (fix outcome, free path): this is where a syllabus statement about coursework sharing and reuse actually matters — Building a Professional Portfolio's "For Module Leaders" section covers what that statement needs to say and why leaving it unstated pushes the question onto individual query emails instead.
  • Rhizome (point outward): name specific, real venues — a practitioner forum, a recent paper, an active open-source project — rather than a generic "keep up with the field" instruction, which asks a learner to do the discovery work a specific pointer would do for them.

A Worked Example: A Final-Year Project Brief

A project brief is rarely purely one of the four. A typical brief mixes them deliberately: the department fixes the assessment criteria and the submission format (pedagogy — non-negotiable, comparability depends on it); it fixes the general expectation that a project demonstrates a real, working system plus critical reflection, stated as testable outcomes (andragogy); it leaves the actual research question, technology choice, and day-to-day working method to the student (heutagogy); and it expects the student to draw on current literature and practitioner discussion the supervisor hasn't necessarily read yet, because the field moved since the module handbook was last revised (rhizome). Naming which parts of a brief are doing which job, out loud, is more useful to a student than leaving them to guess which parts are actually negotiable. How to Read This Section does exactly this classification for real, against this site's own Project Guidance pages, rather than a generic brief.

Note well. Most real design decisions mix more than one of the four positions deliberately. The flowchart is for deciding each individual piece, not for picking one label for a whole module.