An original small rehearsal of published sequencing ideas. It does not reproduce a proprietary training exercise or claim that a protected bubble is a complete Mosaic transformation.
This is original learning material, not a reproduced official course. Mechanical checks have determinate answers within the stated case. Worked comparisons for open judgements show defensible reasoning, not the only possible model. Specialist pedagogical review is not recorded.
The case
Fictional case: a service has two staff-days each week available for change, separate from its essential delivery work. A: remove duplicate reporting, needs two change-days in one week and releases two additional change-days per week from the following week. B: redesign triage, needs three change-days in one week and cannot start before A is complete. C: test a resident-led appointment process, needs four change-days in one week and cannot start before B. B and C release no additional capacity in this toy calculation. The released time is available only if managers stop demanding the old duplicate report. The C experiment needs a bounded group of cases and explicit interfaces with ordinary delivery.
Work through it
Use paper, your own drawing tool or the notes below. Attempt each step before opening its comparison. Describe a diagram in words when that is more accessible.
1. Build the smallest feasible sequence.
Produce: A week-by-week capacity and dependency table.
Compare your work for step 1
Week 1: available two days, spend two on A. Week 2: available four days if A's release is real, spend three on B. Week 3: available four days, spend four on C. No banking of unused days is assumed. Starting B or C in week 1 exceeds capacity, even if their expected benefits are larger.
2. Check the assumption that makes the sequence possible.
Produce: A release condition and an observable test.
Compare your work for step 2
The old duplicate report must actually stop, and the freed time must be usable by the people needed for subsequent work. Check calendars, work records and staff experience after A. A nominal saving in one team's spreadsheet may not create available change capacity in another team.
3. Define the C bubble without cutting it off from reality.
Produce: Boundary, permissions, interfaces and stop/exit conditions.
Compare your work for step 3
Specify eligible cases, resident consent, staff discretion, safety constraints and which usual rules may change. Agree hand-offs to specialists and ordinary delivery. Track whether work is displaced outside the bubble. Set conditions for stopping, adapting or incorporating what is learned. A permanent exception that depends on unpaid heroics is not a sustainable redesign.
4. Compare a benefit-first ranking with a feasible change sequence.
Produce: A short explanation of why the rankings differ.
Compare your work for step 4
C may contribute most visibly to the end purpose, but cannot be done with present capacity or before B. A may be valuable partly because it creates the conditions for later work. Doability, contribution, capacity release and removed constraints all matter. The arithmetic does not settle political acceptability or prove any benefit will occur.
Check the basic distinctions
These checks test the supplied case, not your overall competence. Open answers and model variants still need your judgement.
Repair a defective model or claim
The programme launches A, B and C together because each has a strong business case, using the same two staff-days three times.
Compare your repair
Represent shared capacity once. Sequence prerequisites and verify released time before committing it. Make the next step conditional where the release or feasibility is uncertain.
Try a changed case before looking
A releases only one usable change-day each week. Can the original sequence continue?
Compare the changed case
Week 2 has three days, enough for B. Week 3 also has three, insufficient for C's four-day indivisible task. C must be redesigned, postponed or given real additional capacity. Do not silently assume unused time or benefits can be borrowed from the future.
Review the process, not just the score
Capacity is counted once and release timing is explicit.
Dependencies and contribution are distinguished.
Released capacity is tested in actual work.
The bubble has boundaries, interfaces and exit conditions.
A different model can be defensible when its purpose, assumptions and reasoning are explicit. A contradiction, incorrect unit, invented fact or unacknowledged change of purpose needs repair. Keep both your first attempt and revision.
Keep your attempt
No sign-in or submission is required. Notes are not sent by this practice tool. Use fictional information, not identifiable client or learner data. Saving stores this page's attempt only in this browser; clearing browser data can remove it. Export a copy to keep it elsewhere.
External resources and their limits
The complete original case above is free. Links below distinguish exercises from explanations, recordings, software and paid study. Reading a page or drawing in a tool is not itself a model check.
Further reading for each framework row, including the separate references associated with transposing theory.
What was checked, and what was not
Public sharing confirmed; approach and theory bibliography inspected. The presence of a reference does not establish that it contains self-check exercises.