The Juran Trilogy: Quality Planning, Control, and Improvement
Turn this article into takeaways for your work.
Each assistant summarizes the article only for you and suggests best practices for your work.
The Juran Trilogy is Joseph Juran's model for managing quality through three connected processes: quality planning, quality control, and quality improvement. Planning designs a product or process to meet customer needs. Control keeps it performing at the planned level. Improvement breaks through to a better level.
What is the Juran Trilogy?
Think of how a finance team works: it budgets (planning), monitors spending against the budget (control), and works to cut costs (improvement). Quality needs the same three disciplines, yet many organizations practice only one of them, usually control: inspect, catch defects, fix them, repeat.
According to Juran's own institute, the trilogy is presented on a chart with time on the horizontal axis and the cost of poor quality on the vertical axis. That chart tells the story in one picture:
- After a process goes live, there's a level of chronic waste. The institute's example has more than 20 percent of work being redone.
- A sudden spike, say a power failure or a human error, pushes failures well above that level (the example shows more than 40 percent).
- Control brings the process back to the chronic level through corrective action. It doesn't push it lower.
- Improvement drives the chronic level far below where it started.
That's the key distinction. Control restores. Improvement changes the baseline.
Juran himself was born in 1904 and died in 2008 at age 103, according to the Juran Institute's history of Dr. Juran. The same page dates his Quality Control Handbook to 1951 and his visit to Japan to 1954, and credits him with the phrase "the vital few and the trivial many." You'll see that idea again under improvement, because it's how you pick which chronic problem to attack first. It's the logic behind Pareto analysis.
Key Facts
- The Juran Trilogy has three processes: quality planning, quality control, and quality improvement.
- Control holds performance at the planned level. Only improvement lowers the chronic level of waste.
- The institute describes planning as "quality by design," control as process control, and improvement as the pursuit of breakthrough change (Juran Institute).
- The first edition of Juran's Quality Control Handbook appeared in 1951 (Juran Institute).
- The "vital few and trivial many" idea is how improvement projects get prioritized.
- The trilogy sits underneath most modern total quality management programs.
The three processes in detail
1. Quality planning
Planning is where quality gets built in, before the first unit ships or the first customer calls. The Juran Institute describes it as creating something new, whether a product, service, or process, along with the controls needed to produce it, and notes it's also referred to as Design for Six Sigma.
In practice, planning means:
- Identify who the customers are, including internal ones.
- Find out what they need, in their words.
- Translate those needs into product or service features.
- Design the process that delivers those features.
- Hand the process to operations with its controls in place.
Tools that fit here include voice of the customer, quality function deployment, and DMADV.
A weak plan is expensive because every flaw designed in becomes chronic waste later. If a customer-onboarding process asks for the same document three times, no amount of downstream inspection fixes that. The process was planned badly.
2. Quality control
Control is the day-to-day job of keeping a process on target. You set a standard, measure actual performance, compare the two, and act on the gap. The institute connects the term to a shift from after-the-fact inspection toward prevention.
Typical control work includes:
- Setting measurable targets for each process output
- Monitoring with control charts and statistical process control
- Defining who acts, and how, when a measure drifts out of range
- Fixing the cause of a sudden spike, then confirming it stays fixed
Control is firefighting in the good sense: a spike appears, someone responds, the process returns to normal. The danger is mistaking that for progress. A team that is excellent at control can run for years at the same chronic 20 percent rework and feel busy and successful the whole time.
3. Quality improvement
Improvement is a deliberate project to reach a performance level the process has never had. The Juran Institute defines it as "the organized creation of beneficial change and the attainment of unprecedented levels of performance," and links it to Lean Six Sigma. It cites a Six Sigma level of 3.4 ppm, or a tenfold improvement over current performance, as possible targets for unprecedented change.
Improvement works project by project:
- Pick a chronic problem worth solving, using Pareto thinking to find the vital few.
- Build a case: what does the problem cost?
- Diagnose the cause with data, not opinion.
- Test a remedy and prove it works.
- Hand the new level to control so it stays put.
DMAIC is the best-known structure for this, and the cost of quality is the usual way to make the business case.
How the three processes connect
The trilogy is a loop, not a ladder.
- Planning produces a process and its controls.
- Control keeps that process stable and exposes chronic waste.
- Improvement attacks the chronic waste and produces a better process.
- The better process goes back through control, and sometimes a redesign goes back to planning.
One skipped step breaks the loop. Skip planning and you spend your life on improvement projects that patch design flaws. Skip control and improvement gains erode. Skip improvement and you'll stay stable at a level your competitors may soon beat.
Juran Trilogy vs. other quality frameworks
| Framework | Core idea | Main focus | How it relates to Juran |
|---|---|---|---|
| Juran Trilogy | Manage quality as planning, control, and improvement | Whole quality lifecycle, project-by-project improvement | The reference model |
| Deming / PDCA | Plan, do, check, act in a continuous cycle | Learning and iteration, systems thinking | PDCA is a cycle you run inside each of Juran's three processes |
| Crosby zero defects | Quality means conformance to requirements; the target is no defects | Standards and mindset | Crosby sets the attitude; Juran sets the management structure |
| Total quality management | Quality is everyone's job, organization-wide | Culture and customer focus | TQM is the umbrella; the trilogy is one of its working models |
| Six Sigma | Reduce variation using data, with DMAIC and DMADV | Statistical project delivery | Six Sigma supplies the methods for improvement and, via DMADV, for planning |
The easiest way to hold these together: Deming gives you the learning cycle, Crosby gives you the standard, Six Sigma gives you the project method, TQM gives you the culture, and Juran gives you the management architecture that tells you which activity you're doing and why.
Step-by-step: applying the trilogy in your organization
- Pick one process. Choose something customers feel, such as order fulfillment, claims handling, or invoicing.
- Map the current state. Draw the process and list the customers of each output.
- Check the plan. Do the process outputs match what customers actually need? If not, you have a planning gap.
- Set the controls. Define a few measures, a target for each, an owner, and a response when it goes off target.
- Measure the chronic level. Track a few weeks of data and find the normal level of rework, delay, or error. That's your baseline.
- Separate spikes from chronic waste. Spikes go to control. Persistent waste goes to improvement.
- Rank the chronic problems. Use a Pareto chart to find the vital few.
- Charter an improvement project. One problem, one owner, one clear goal, a team with real authority.
- Lock in the gain. Update the controls to the new level and document the new standard.
- Repeat. Return to step 5 with the new baseline.
Template: trilogy review sheet
Copy this into a spreadsheet or doc and fill one row per process.
| Process | Customer need (planning) | Control measure and target | Current chronic level | Biggest vital-few cause | Improvement project and owner | Review date |
|---|---|---|---|---|---|---|
| Example: Invoice processing | Accurate invoice paid on time | Error rate per 100 invoices | (your baseline) | Missing purchase order numbers | Standardize PO capture, Finance Ops lead | (date) |
Examples by business function
| Function | Planning | Control | Improvement |
|---|---|---|---|
| Manufacturing | Design the part and its inspection plan together | Control charts on critical dimensions | Project to cut the largest scrap cause |
| Customer support | Define response standards from customer expectations | Daily dashboard of backlog and response time | Redesign the most common repeat-contact issue |
| Finance | Design the month-end close with clear handoffs | Checklist and reconciliation tolerances | Remove the manual step behind most late closes |
| HR | Design onboarding around what new hires need in week one | Track completion of onboarding steps | Fix the top reason for delayed access to tools |
| Sales operations | Define what a complete deal record looks like | Weekly data-quality checks on the pipeline | Eliminate the most frequent source of missing fields |
| Healthcare | Design the discharge process around patient needs | Monitor discharge-error reports | Project on the leading cause of delayed discharge |
Do's and don'ts
Do:
- Treat planning, control, and improvement as a single loop.
- Separate sudden spikes from chronic waste before deciding what to do.
- Put a number on the cost of the chronic problem before you launch a project.
- Hand every improvement back to control so the gain holds.
- Give improvement projects a named owner and real authority.
Don't:
- Count a return to normal as an improvement.
- Launch improvement projects without data on where the waste is.
- Let planning be done by a team that will never run the process.
- Chase every problem at once. Go after the vital few.
- Treat the trilogy as a one-time rollout. It's a management habit.
Common mistakes
Living in control. Many teams are great at reacting. The sign is that the same problems come back every quarter, each solved and each unsolved.
Improving without controls. A project closes, performance improves, then slips within months because nobody changed the monitoring or the standard work.
Under-investing in planning. It's invisible when done well, so it rarely gets budget. But it's where the cheapest quality gains live.
Confusing the models. Teams sometimes argue Juran versus Deming versus Six Sigma. They solve different parts of the problem and combine well.

Customer Success Operations Manager
On this page
- What is the Juran Trilogy?
- The three processes in detail
- 1. Quality planning
- 2. Quality control
- 3. Quality improvement
- How the three processes connect
- Juran Trilogy vs. other quality frameworks
- Step-by-step: applying the trilogy in your organization
- Template: trilogy review sheet
- Examples by business function
- Do's and don'ts
- Common mistakes