# Leading Continuous Improvement (Workshop) > A ready-to-run PD workshop on continuous improvement cycles instead of sweeping reform. Run-of-show, handout, follow-up. *A ready-to-run professional learning workshop from K12 Academics. Source page: https://pd.k12academics.com/leading-continuous-improvement-workshop.html* Big, sweeping reforms often fail, while small, tested changes that build on each other can transform a school over time. Continuous improvement, using cycles to test changes, learn from the results, and refine, offers a disciplined, humble way to actually get better. Sweeping reforms often fail; continuous improvement, testing small changes in cycles, learning from results, and refining, is a disciplined, humble way for a school to actually get better over time. ## Why it works Research on improvement science and continuous improvement in education shows that testing changes in small, rapid cycles (such as Plan-Do-Study-Act), learning from what happens, and refining, often works better than large-scale, all-at-once reform, which frequently fails in implementation. Continuous improvement is disciplined and humble: it treats changes as hypotheses to test, uses evidence to learn, and builds improvement iteratively. It also builds a learning culture rather than a reform-of-the-year churn. **The research:** Improvement science; research on continuous improvement (Bryk). ## The run-of-show ### Staff meeting (15 minutes) A fast introduction to plant one routine. **Goal:** everyone leaves with one thing to try. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 3 min | Hook | How many sweeping reforms have you seen fail in implementation? Name it. | You are surfacing failed reform. | | 0:03 | 5 min | Mini-teach | Test small, learn, refine. One slide. | | | 0:08 | 5 min | Plan one | Name a small change to test on a problem. Turn and talk. | | | 0:13 | 2 min | Commit | Each leader names a cycle to run. | | ### PLC / team meeting (45 minutes) The standard version. **Goal:** every teacher leaves with something designed for a real upcoming lesson. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 5 min | Hook | Big rollout vs small tested change. Which actually sticks? | Let them see the difference. | | 0:05 | 8 min | Mini-teach | Improvement cycles and treating changes as hypotheses. | | | 0:13 | 12 min | See it in action | Design a Plan-Do-Study-Act cycle. | Study with evidence. | | 0:25 | 12 min | Design | Run a continuous improvement cycle. | Protect the full time. | | 0:37 | 5 min | Share | Swap plans in pairs; sharpen the measure. | Keep it in pairs. | | 0:42 | 3 min | Commit + follow-up | Lock it in and set the study point. | | ### Half-day institute (~3 hours) A deep session for a PD day. **Goal:** built, practiced, and a rollout planned. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | Block 1 | 45 min | Experience + why | Failed reform, then improvement science. | | | | 15 min | Break | | | | Block 2 | 60 min | Design cycles | Leaders design test-study-refine cycles. | Small and evidence-based. | | Block 3 | 45 min | Practice | Plan the evidence and refinement. | Iterative improvement is the aim. | | Close | 15 min | Plan the rollout | Launch a cycle; set the study point. | | ## The core activity: run a continuous improvement cycle Leaders leave with a small change to test, study, and refine on a specific problem. - Pick a specific problem to improve. - Design a small change to test (a hypothesis, not a sweeping rollout). - Plan how you study what happens (evidence). - Plan to act on what you learn and refine, iterating. ## Facilitator notes - Test small changes in cycles, as hypotheses. - Study results with evidence, and refine and iterate. - Build a learning culture. ## Adapt it - **All leaders and teams:** the same. - **All settings:** test small, study, refine, iterate. ## Participant handout One page for every teacher. Print it, or save it as a PDF. ### Continuous Improvement: test, learn, refine **Disciplined and humble:** a small change tested as a hypothesis, studied with evidence, and refined iteratively. - The specific problem to improve: __________ - The small change to test (the hypothesis): __________ - How I study what happens (evidence): __________ - How I act on what I learn and refine: __________ - Where sweeping reform has failed before: __________ ## Make it stick - Test small and refine. - Treat changes as hypotheses. - Bring a continuous-improvement cycle to the leadership team. ## Common questions **Isn't big, bold reform how you make change?** Big reforms often fail in implementation. Testing smaller changes in cycles, learning, and refining is frequently more effective and builds lasting improvement, without the churn and fatigue of sweeping reform. **What is a continuous improvement cycle?** Plan a change, do it on a small scale, study what happens, and act on what you learned, then repeat. Changes are treated as hypotheses to test and refine, not mandates to roll out. **How is this different from just trying things?** It is disciplined: clear about what you are testing and why, measuring what happens, learning from it systematically, and refining. Not random trying, but structured learning. ## Go deeper - [Learning Forward](https://learningforward.org) ## Build it into a bigger day - [Leading Change](https://pd.k12academics.com/leading-change-initiative-fatigue-workshop.html) - [Vision & Improvement Goals](https://pd.k12academics.com/vision-school-improvement-goals-workshop.html) - [Data-Driven Instruction](https://pd.k12academics.com/data-driven-instruction-workshop.html) --- Full workshop page: https://pd.k12academics.com/leading-continuous-improvement-workshop.html All workshops: https://pd.k12academics.com/