Using the practice pack

Dry runs for learning a craft

This pack grew from repeated requests by apprentices during Benjamin P Taylor's teaching with SCiO on the level 7 Systems Thinking Practitioner apprenticeship. They wanted simple exercises, worked examples and answers so they could try out methods and check their understanding.

Systems practice is learned through application in the real world. Teaching, workshop exercises, worked examples and support with live situations all contribute to apprenticing in a craft. A dry run can help develop technical skills and reveal a misunderstanding before using a method with people. It cannot reproduce the purposes, relationships, uncertainty and consequences of that work.

Use the exercises as preparation for practice and as a way to revisit a technical point. Getting a model or answer right is useful, but it is not the purpose of systems practice or the practice itself.

For a learner

Choose one approach with your tutor. Read only the case and task first. Use paper, text or your preferred drawing tool. State the purpose, boundary, assumptions and notation. Keep the first attempt. Open a comparison only after attempting the step, and record a revision. Then do the changed case without copying the first answer.

The suggested times are practice timeboxes, not measured completion guarantees. Pause where needed. You can use the task-only collection offline, and a practice partner can hold the answer key.

What the feedback means

A calculation, unit, named function or specified relation can have a determinate answer within a fictional case. The check can identify a mismatch. It cannot determine whether your chosen purpose is legitimate, whether people agree, or whether the method works in your organisation.

For an open answer, ask whether the reasoning follows its purpose, whether the model uses the method coherently, whether observations and interpretations are separated, and whether alternatives and exclusions are visible. A different answer is not automatically wrong. An unsupported assertion is not rescued by calling it another perspective.

For a tutor or peer

Use a short teach-back: ask the learner to explain a link, a boundary, an omitted activity or a changed assumption. Give them a fresh variation and see what they revise. Mark a specific technical defect where there is one. For a defensible alternative, record the assumptions that make it work.

Use three outcomes: ready for another basic case; revise a named technical point; or needs guided practice. These are local learning judgements, not professional accreditation. Ask for real-world evidence separately and use the actual programme assessment requirements.

Accessibility and privacy

Every case, question, comparison and answer is ordinary HTML and can be read without JavaScript. A text description is accepted as an alternative to drawing or physical positioning. Interactive checks, browser saving and export need JavaScript. No account is required by this pack.

Use fictional information in the notes. The practice script does not transmit answers. Saving is limited to this browser and can fail when storage is blocked. Export a copy rather than relying on browser storage as a permanent record. External sites have their own access and privacy terms.

Research and review status

External links were researched on 7 September 2026. Each record states whether the exercise, page, listing or access route was inspected. A paid course description is not evidence that its exercises or tutor feedback were tested. A source access problem is recorded rather than silently presented as a working exercise.

The cases and comparisons are original material prepared with AI assistance for this publication. The build includes deterministic checks of the numerical examples, coverage and page behaviour. No independent specialist pedagogical review or provider endorsement is claimed. Send a specific correction through the site's feedback route; preserve the case, disputed step and proposed repair.

Moving beyond rehearsal

Before using a method with people, establish your remit, competence, consent, data handling and sector-specific duties. Agree what the model is for and how participants can challenge it. Transfer is a new inquiry, not permission to impose a worked example on a real situation.

Do not use completion of these pages as proof of sustained collaboration, resilience, ethical conduct, change implementation or level-7 competence. The pack supplies a place to practise the basics and expose mistakes before that work.