Radial Cycle: Continuous Improvement

A radial cycle diagram showing the DMAIC (Define, Measure, Analyze, Improve, Control) continuous improvement cycle with "Quality" as the central hub.

This diagram demonstrates the radial cycle pattern where a central concept drives all outer stages, which also connect sequentially to each other.

View Radial Cycle Fullscreen

How It Works

The central hub (Quality) connects to all five outer nodes via dashed spokes
The outer nodes connect sequentially with curved arrows, forming the cycle
Hover over any node to see its description in the infobox below
The color-matched label pattern links the infobox to the hovered node

Features

Width-responsive p5.js canvas
Dashed spokes distinguish hub connections from sequential cycle arrows
Hover highlighting with thicker borders
Color-matched bold label in the description area

Lesson Plan: Understanding Quality as a Continuous Cycle

Overview

This lesson uses the DMAIC Radial Cycle diagram to teach two interconnected ideas: (1) what each stage of the quality improvement process does, and (2) why the circular structure of the diagram matters — quality is an ongoing cycle, not a one-time event. The interactive diagram makes both ideas tangible through hover exploration and visual structure.

Duration: 30–40 minutes Audience: Instructional designers, educators, business professionals, or students in a quality management or process improvement course Prerequisites: None — the lesson introduces all concepts from scratch

Learning Objectives

By the end of this lesson, learners will be able to:

Describe each of the five DMAIC stages and explain what happens at each stage
Explain why Quality sits at the center hub rather than as one of the outer stages
Distinguish between a basic cycle (equal stages in a ring) and a radial cycle (a central driver powering outer stages)
Argue why quality improvement must be continuous rather than a one-time fix

Part 1: The Quality Improvement Process (15–20 minutes)

Introduce the Problem

Begin by asking learners: "Has your organization ever fixed a problem, only to see it return six months later?" This common experience motivates the need for a structured, repeating approach to quality.

Walk Through the Five Stages

Have learners hover over each outer node in sequence, reading the description that appears in the infobox. Discuss each stage:

1. Define Every improvement effort starts by clearly identifying what needs to improve. Without a precise problem statement, teams waste effort on symptoms rather than causes. Ask learners: "What happens when a team skips this stage and jumps straight to solutions?"

2. Measure Before changing anything, you need a baseline. Measurement answers the question: "How bad is the problem right now?" Without data, you cannot tell whether your improvements actually worked. This stage connects directly to the central hub — Quality defines what to measure.

3. Analyze Raw data does not explain itself. Analysis identifies root causes — the underlying reasons the problem exists. A common technique is the "5 Whys," asking why repeatedly until you reach a cause you can act on. Point out that analysis transforms measurement data into actionable insight.

4. Improve This is where changes happen. Solutions are designed, tested, and implemented based on the root causes identified in the previous stage. Emphasize that improvement is targeted — it addresses specific causes, not general dissatisfaction.

5. Control The most frequently skipped stage — and the most important for sustainability. Control means putting monitoring systems in place so you know immediately if the problem returns. Ask learners: "What is the difference between a team that improves and a team that improves and controls?" The answer: the second team does not have to solve the same problem twice.

Discuss the Central Hub

Now have learners hover over the red Quality node at the center. Ask:

"Why is Quality in the center instead of being a sixth stage in the outer ring?"
"What do the dashed spokes represent that the solid arrows do not?"

Guide learners to see that Quality is not a step — it is the driving force behind every step. The dashed spokes show that Quality goals shape what you Define, what you Measure, what you Analyze for, what you Improve toward, and what you Control against. Quality is omnipresent, not sequential.

Part 2: Why a Cycle, Not a Checklist (10–15 minutes)

The Checklist Trap

Many organizations treat quality improvement as a project with a start and end date: define the problem, fix it, move on. This "checklist" mindset leads to a predictable pattern:

A problem is identified
A team is assembled to fix it
The fix is implemented
The team disbands
Six months later, the problem returns

Ask learners: "What is missing from this sequence?" The answer: the return arrow. There is no mechanism to loop back, monitor, and re-engage.

The Power of the Circle

Direct learners' attention to the curved arrow from Control back to Define. This single arrow is the most important visual element in the diagram. It communicates that:

Completion is an illusion. When you finish controlling one improvement, the data you are now collecting reveals the next problem to define.
Each revolution makes the system better. The first cycle addresses the most critical issue. The second cycle addresses the next most critical issue. Over time, the system improves continuously.
The cycle is self-sustaining. Control generates data, data reveals new problems, new problems trigger new cycles. The process does not need an external push to restart.

Compare to the Basic Cycle

If learners have already seen the AI Flywheel (a basic cycle in the same chapter), ask them to compare the two:

Feature	Basic Cycle (AI Flywheel)	Radial Cycle (DMAIC)
Central hub	None — all stages are equal	Quality drives all stages
Spokes	None	Dashed lines from hub to every stage
Key message	Stages follow each other	One concept powers all stages
Visual metaphor	A wheel rolling forward	A wheel with an axle

The radial cycle adds the insight that not all elements are equal — some concepts are architecturally central to the process.

Real-World Application

Close with a brief discussion connecting the diagram to learners' own contexts:

Educators: How does your curriculum review process work? Is it a one-time event or a repeating cycle? What would a DMAIC approach to course improvement look like?
Instructional designers: When you build a MicroSim, do you measure its effectiveness after deployment? What would "Control" look like for educational content?
Business professionals: Which stage does your organization most often skip? What is the cost of skipping it?

Assessment

Ask learners to answer these reflection questions:

A colleague says, "We already fixed that problem last year." Based on the DMAIC cycle, what question should you ask them?
- Expected answer: "Did you put controls in place to sustain the fix?"
Why does the diagram use dashed lines for the spokes and solid lines for the outer arrows? What does this visual distinction communicate?
- Expected answer: The dashed spokes show an ongoing influence relationship (Quality shapes every stage), while the solid arrows show sequential flow (each stage feeds the next).
What would happen to the diagram if you removed the arrow from Control back to Define? How would the meaning change?
- Expected answer: It would become a process diagram (linear sequence) instead of a cycle diagram. The message would change from "continuous improvement" to "one-time improvement project."

Key Takeaway

The circular structure of this diagram is not decorative — it is the argument. By placing stages in a circle with a return arrow, the diagram asserts that quality improvement never ends. By placing Quality at the center with spokes to every stage, the diagram asserts that quality is not one concern among many — it is the central concern that shapes all the others. The interactive hover behavior reinforces both messages: exploring any node always brings you back to the relationship between that stage and the central hub.