The map proves the cause
Everybody recognised the feedback loop, so it must explain the problem.
The case
A fictional library team draws a loop: less assistance leads to incomplete applications, which lead to repeat visits, which consume assistance time. Staff recognise the story. No repeat-visit data have been collected. A software failure and a change in eligibility rules occurred during the same period.
Try it before reading on
Turn the loop into a bounded hypothesis. Specify one observation that would challenge it and one competing explanation worth investigating.
Use paper or your own notes. Keep the first answer as well as any revision.
Compare your reasoning
Recognition makes the hypothesis worth examining; it does not establish the mechanism. State which visitors, period, and assistance changes the claim covers. Examine whether incomplete applications actually precede repeat visits and whether repeats consume the relevant capacity. A decline in repeats despite reduced assistance would challenge the proposed loop, although changed access could complicate interpretation. Investigate the software and eligibility changes rather than crediting one familiar story with every effect.
When could the claim be defensible?
Shared practitioner recognition can be useful evidence of experience. It becomes stronger when specific observations and contradictory cases can be inspected. Dismissing it merely because it is qualitative would lose relevant information.
Change the conditions
Your new reporting makes staff record repeat visits more carefully. Recorded repeats rise. What belongs in the observer note?
Compare the changed case
The measurement intervention changed recording behaviour, so a rise may partly reflect ascertainment. Explain your role, retain the definition change, and seek comparable evidence before interpreting it as a worsening service.
Follow the specific connection
Systems concepts: make your boundary inspectable
A first rehearsal of boundaries, relationships, perspectives, feedback and emergence. It is not a complete treatment of systems philosophy or complexity science.
Evaluation and reflexivity: test the claim you are tempted to make
A basic mixed-evidence evaluation rehearsal. It is not a complete impact evaluation, statistical inference course or assessment of real practitioner behaviour.
Source routes and reading limits
The methodological route below uses the existing practice pack's checked resource descriptions. This release does not claim fresh reading of the external works.
OU: drawing systems maps, SAQ 3 and Activities 19-22
Attempt SAQ 3 before opening its answer. Draw your own map for Activities 19-22, then compare the author's choices. Different justified boundaries need not match the example.
Existing check: Tasks, defective maps, answer text and worked revisions inspected. Historic Child Support Agency case, not current policy guidance.
OU: systems maps, updated tutorial
Check containment and boundaries. An OU systems map is not a causal-loop diagram; do not add untyped causal arrows to it.
Existing check: Updated 2021 tutorial page and diagram conventions inspected; playback not independently tested.
OU: systems diagramming
Use the text conventions and printable activities. Use the newer systems-map tutorial below instead of the Flash element.
Existing check: Course content inspected. An old Flash activity is unavailable; do not depend on it.
UK Government: introductory systems thinking toolkit
Select the named tool, try the associated template and compare with the example. Use the pack's explicit checks where the toolkit provides no answer key.
Existing check: HTML toolkit inspected, including mapping, stock-flow, theory of change and evaluation sections. Its examples are not automatic validation of a learner's model.
Deming Institute: PDSA cycle
Write a prediction before a change and compare observation with it. The service and evaluation cases here give a small exercise and answers.
Existing check: The Institute's account of prediction, study and theory revision inspected. It distinguishes PDSA from a simple implementation check.
Wenger-Trayner: systems convening, free book and resources
Use the cases to examine legitimacy, boundaries, agency and learning partnerships. The original case here provides the checkable rehearsal.
Existing check: Authors' page, free PDF route and paperback links inspected. It is a related social-learning resource, not identical to every method grouped in the bridge exercise.
Take one revision away
Write the claim you can now support, the assumption you changed, and the observation or decision still needed. Do not turn the worked comparison into a compulsory answer where the question admits alternatives.
Choose another claim · Print all task sheets · Download the cases and route record