Operations, Process Mapping, and Continuous Improvement
As the cooperative grows, informal memory stops being a reliable operating system. Process mapping makes handoffs, delays, rework, decision points, and safeguards visible so the organization can improve without losing professional judgment.
What you’ll be able to do
Week objectives
- Define a process by trigger, outcome, customer or beneficiary, owner, and boundary.
- Build a current-state swimlane map.
- Identify bottlenecks, handoff failures, rework, delay, and control gaps.
- Design a future state and simple standard operating procedure.
- Use measures and small tests to support continuous improvement.
Core concepts
Build the mental model
Process
A process is a repeatable sequence that turns an input or trigger into an outcome. 'Evaluation intake' begins with a defined request and ends with an accepted assignment, timeline, records, and communication—not merely an email.
Process owner
The owner is accountable for end-to-end performance across roles and handoffs. Individual participants still own their steps.
Swimlane map
Swimlanes show which role performs each step. They expose handoffs, duplicate entry, unclear decisions, and work that waits between organizations.
Cycle time, touch time, and wait time
Cycle time is total elapsed time; touch time is active work; wait time is inactivity between steps. Reducing wait may improve timelines without asking professionals to work faster.
Bottleneck and capacity
A bottleneck is the constrained step that limits flow. Improving a non-bottleneck may create local efficiency without improving the overall result.
Standard work and professional judgment
Standard work captures the best known routine, controls, roles, and exceptions. It should protect necessary professional judgment rather than script clinical decisions.
Continuous improvement
Use a small cycle: define the problem, understand the current state, test a change, measure, learn, and standardize or revise.
Control and privacy
Process design must include access controls, required approvals, secure transfer, retention, incident escalation, and minimum necessary use of student or personnel information.
In practice
What it looks like
- An intake request waits three days because no one owns completeness review. A standard request form and daily triage reduce wait without changing evaluation quality.
- District billing requires three spreadsheets and repeated correction because service definitions differ. A shared data dictionary and one source of truth reduce rework.
- A staffing assignment map shows that the director approves routine schedule swaps. Delegated criteria remove a bottleneck while preserving escalation for compliance risk.
Required viewing
Learn from trusted instructors
3 verified videos · 2 hr 27 min. Watch in order, then mark each complete.
Ses. 1-2: The Start of Your Lean Journey
MIT OpenCourseWare
Introduces Lean as a way to see value, flow, waste, and improvement. The course reframes these ideas around reliable public service rather than manufacturing output.
System Dynamics: Systems Thinking and Modeling for a Complex World
MIT OpenCourseWare
Shows why local fixes can have delayed or unintended system effects. It helps the learner improve processes shared across roles and districts without optimizing one step at everyone else’s expense.
Process Mapping
Galton College
Demonstrates core process-mapping techniques in a focused format. The learner can immediately apply the notation to intake, staffing, billing, hiring, renewal, or reporting.
Apply the ideas
Current-State and Future-State Process Map
Choose new-district onboarding, evaluation intake, staff assignment, billing, hiring, renewal, or monthly reporting. Do not include student-identifying details.
Process charter
Current-state steps
Improvement analysis
Future state
Weekly deliverable
Turn the week into working practice.
A current-state process map, improvement analysis, future-state map, and draft standard operating procedure for one cooperative process.
- Define the trigger, end outcome, owner, beneficiaries, scope, and exclusions.
- Observe or reconstruct the current process with people who perform it.
- Map steps, decisions, roles, handoffs, wait, rework, systems, and controls.
- Select one root problem and design a small, reversible test.
- Draw the future state and write an SOP covering purpose, roles, steps, exceptions, controls, and measures.
- Set a review date and identify who can authorize adoption.
Both maps show roles and decision points, the improvement is linked to evidence, the future state preserves required safeguards, the SOP can be followed by a trained backup, and two measures plus a review date are defined.
Executive questions
Questions worth carrying
- What event starts this process, and what observable result ends it?
- Where does work wait, return, or lose information?
- Which step limits the whole process?
- What exception requires professional judgment or escalation?
- Which two measures would show whether the change helped?
Optional AI practice
Use AI as a thinking partner—not a records system.
Protect sensitive information. Do not upload personally identifiable student information, protected student records, confidential personnel information, unredacted contracts, credentials, or sensitive financial information to an AI system without explicit authorization. Follow FERPA, IDEA, district policy, employment-confidentiality duties, contractual restrictions, records rules, and approved data-security procedures.
Week 8 in one sentenceOperational improvement begins by seeing the real work end to end. Clear ownership, handoffs, controls, and measures make service more reliable without reducing professional judgment.