Control Charts: Understanding Common Cause and Special Cause Variation

Control Charts: Understanding Common Cause and Special Cause Variation

"Control charts are essential tools that help project managers determine when to take action and when to leave processes alone. By distinguishing between normal variations and significant problems, they prevent unnecessary adjustments while highlighting genuine issues that require attention. This knowledge is a key component of the PMP® examination and practical project management."

What Are Control Charts?

Control charts are visual tools that track how a process performs over time. Think of them as the project manager's dashboard for quality – they help you see when things are running normally and when something unusual needs your attention.

Why Control Charts Matter

Control charts help project managers:

• Make Better Decisions: Know when to take action and when to leave things alone
• Save Time and Resources: Avoid wasting effort fixing problems that aren't really there
• Spot Real Problems Early: Identify genuine issues before they impact project success
• Demonstrate Control: Show stakeholders that quality is being actively monitored
• Improve Processes: Gather data to drive meaningful improvements

Unlike other charts that just show data at a point in time, control charts tell a story about your process over time, helping you understand not just what is happening, but whether it's normal or needs attention.

How Control Charts Work

Control charts may look technical at first glance, but their basic structure is straightforward and practical.

The Basic Parts

Every control chart has these essential elements:

• Central Line: The average or expected value of what you're measuring
• Control Limits: Upper and lower boundaries showing the normal range of variation
• Data Points: Your actual measurements plotted in time order
• Time Scale: Horizontal axis showing when measurements were taken

Think of control limits like the lanes on a highway – staying within them means you're on track, while crossing them signals that something unusual is happening.

Real Project Examples

Control charts can track many aspects of your projects:

• Task Completion Time: Are tasks consistently being completed within expected timeframes?
• Defect Rates: Is the team producing a consistent level of quality?
• Budget Variance: Is spending staying within expected ranges?
• Customer Satisfaction: Are satisfaction ratings stable or showing concerning patterns?
• Resource Utilization: Is team capacity being used as expected?

PMP® Exam Tip: For the PMP exam, remember that control charts are part of the "Control Quality" process in the Quality Management Knowledge Area. You should understand the difference between common cause and special cause variation, and know that the appropriate management response differs for each type. The exam may present scenarios asking you to identify which type of variation is present and what action a project manager should take.

The Two Types of Variation: Common Cause vs. Special Cause

The most important concept behind control charts is understanding the difference between two types of variation that affect all processes.

Visual Examples of Variation Types

Common Cause Variation

Key Characteristics:

• Points randomly distributed around the central line
• All points within control limits
• No obvious patterns or trends
• Natural, expected variation

Special Cause Variation

Key Characteristics:

• Points outside control limits (red circles)
• Clear downward trend (not random)
• Multiple consecutive points on one side of central line
• Indicates something unusual affecting the process

Common Cause Variation: The "Normal" Noise

Common cause variation is like the everyday background noise in your project:

• What It Is: The normal, expected ups and downs that happen in any process
• How to Spot It: Data points stay within control limits and show no patterns
• Project Examples:
  • Small differences in how long team members take to complete similar tasks
  • Minor fluctuations in daily progress
  • Routine variations in meeting durations
  • Normal differences in resource usage from day to day

Special Cause Variation: The "Unusual" Events

Special cause variation is like an unexpected siren in the midst of normal background noise:

• What It Is: Unusual, non-random changes caused by specific factors that aren't part of the normal process
• How to Spot It: Data points outside control limits or showing clear patterns
• Project Examples:
  • Sudden spike in defects after a new team member joins
  • Consistent improvement in completion times after training
  • Unexpected delays due to a vendor issue
  • Dramatic improvement after implementing a new tool

Why The Difference Matters

Characteristic	Common Cause Variation	Special Cause Variation
What it means	The process is stable and predictable	Something unusual is affecting the process
Required Action	Leave the process alone - don't make adjustments	Investigate and address the specific cause
Who should act	Only senior management (system changes)	Process owners and team members
Consequences of wrong response	Tampering makes things worse	Problems continue or worsen

Practical Application Tip: When using control charts in your projects, start simple. Choose one important metric like defect rates or schedule variance, and track it consistently. Create a visual display where the team can see the chart and understand what's happening. Make reviewing the chart a regular part of status meetings. Remember to celebrate when the process stays in control, not just when you find and fix special causes.

Spotting Special Cause Variation

You don't need advanced statistical knowledge to identify when something unusual is happening in your process. These simple patterns are your warning signs:

Common Patterns that Signal Special Causes

Points Beyond Control Limits

What it means: One or more points fall outside the control limits, indicating a significant unusual event.

Project example: A sudden spike in defects after a new team member joins without proper training.

Run of Points on One Side

What it means: Seven or more consecutive points all on the same side of the central line, indicating a systematic shift.

Project example: Sustained improvement after implementing a new development tool or process.

Trend in One Direction

What it means: Seven or more consecutive points all increasing or all decreasing, showing a consistent trend.

Project example: Continuous improvement as team members gain experience or gradual deterioration as they experience burnout.

Sudden Shift in Level

What it means: A sudden change in the process average that persists, often indicating a fundamental change.

Project example: Implementation of new requirements or addition of experienced team members.

Key Signs of Special Cause Variation

Look for these clear indicators:

• Points Beyond the Limits: Any data point that falls outside the upper or lower control limits
• Consistent Direction: Seven or more consecutive points all increasing or all decreasing
• One-Sided Trend: Seven or more consecutive points all on the same side of the central line
• Zigzag Pattern: Points that alternate up and down in a consistent pattern
• Sudden Shift: A group of points that suddenly starts running at a different level

These patterns rarely happen by chance. When you see them, it's time to investigate what changed in your process.

Project Management Context

In your projects, these patterns might indicate:

• Point Beyond Limits: A team member facing a significant blocker or a breakthrough improvement
• Consistent Direction: Gradual team improvement from learning or progressive fatigue
• One-Sided Trend: A systematic change like a new tool or process
• Zigzag Pattern: Different team members with varying skill levels assigned to similar tasks
• Sudden Shift: A major change like new requirements or different team composition

Taking the Right Action

The main value of control charts is helping you know when to act and what kind of action to take.

For Common Cause Variation (Normal Process)

When your process shows only common cause variation:

• DO:
  • Accept that this variation is normal - don't chase every up and down
  • Use the data to set realistic expectations with stakeholders
  • Focus on improving the process as a whole if current performance isn't satisfactory
  • Consider if specifications or requirements need adjustment to match process capability
• DON'T:
  • React to individual data points as if they represent problems
  • Blame team members for normal variations
  • Make frequent small adjustments to the process (this makes things worse)
  • Expect to eliminate all variation

For Special Cause Variation (Unusual Events)

When your process shows special cause variation:

• DO:
  • Investigate what changed - talk to the team and look for recent modifications
  • Take specific action to address the identified cause
  • Document what happened for future learning
  • Monitor to confirm your action resolved the issue
• DON'T:
  • Ignore the signals - they won't fix themselves
  • Apply system-wide changes when only a specific issue exists
  • Assume you know the cause without investigation
  • Delay your response - special causes often worsen over time

PMP® Exam Tip: A key testing point on the PMP exam is understanding that "tampering" with a stable process (one showing only common cause variation) actually increases variation rather than reducing it. Conversely, failing to address special cause variation represents a missed opportunity to improve process performance. The exam may present scenarios asking what a project manager should do when faced with different patterns on a control chart.

Getting Started with Control Charts

Simple Implementation Steps

You can start using control charts in your projects with these basic steps:

1. Choose One Important Metric: Select something critical to project success (defect rates, task durations, cost variance)
2. Collect Data Consistently: Gather at least 20 data points with the same measurement method
3. Calculate the Average: Find the mean of your measurements (this becomes your central line)
4. Set Control Limits: Many project management tools can do this automatically, or use ±3 standard deviations
5. Plot Your Data: Add new measurements as they occur
6. Look for Patterns: Watch for the signals of special cause variation
7. Take Appropriate Action: Respond differently to common cause versus special cause signals

Modern project management and quality tools can help you create control charts without complex calculations.

Practical Applications in Projects

Start with these straightforward applications:

• Sprint Velocity Chart: Track team output stability in agile projects
• Defect Rate Chart: Monitor quality consistency in deliverables
• Task Duration Chart: See if estimation is consistent and accurate
• Budget Variance Chart: Track if spending is within expected ranges
• Resource Utilization Chart: Monitor if team capacity is being used as expected

These practical applications give you visibility into process stability without requiring advanced statistical knowledge.

Practical Application Tip: Many project managers find it helpful to create a "decision rule card" for their teams that explains in simple terms: 1) What the control chart is measuring, 2) What patterns indicate special cause variation, and 3) What actions to take when special causes appear. Post this near your visual control chart to help everyone respond appropriately to what the data is showing.

Common Mistakes to Avoid

Watch Out For These Pitfalls

Even experienced project managers sometimes make these mistakes:

• Overreacting to Normal Variation: Making changes when the process is actually stable
• Ignoring Clear Signals: Failing to investigate when special causes appear
• Inconsistent Measurement: Changing how or when you collect data
• Setting Arbitrary Targets: Confusing specification limits with control limits
• Too Many Charts: Tracking too many metrics and diluting attention
• Not Involving the Team: Keeping the charts to yourself rather than making them visible

Setting Your Team Up for Success

Make control charts work for your project with these approaches:

• Keep It Visual: Display charts where the team can see them daily
• Make It Relevant: Choose metrics that matter to project success
• Explain the Purpose: Help the team understand this is for process improvement, not blame
• Celebrate Stability: Recognize when processes remain in control
• Learn Together: Involve the team in investigating special causes

Conclusion: Control Charts as Project Management Tools

Control charts offer project managers a practical way to separate normal process variation from genuine issues that require attention. By understanding the difference between common cause and special cause variation, you can avoid wasting time on non-issues while addressing real problems promptly.

For PMP® certification candidates, these concepts appear regularly in exam questions about quality management. The key insight is knowing when to take action and when to leave a process alone – a distinction that can save your project significant time and resources.

In your day-to-day project management, control charts provide objective data for conversations with stakeholders about performance expectations and variation. Rather than making promises of perfect consistency, you can use control charts to demonstrate what normal variation looks like and set realistic expectations.

By implementing these fundamental concepts, you'll improve your decision-making, reduce unnecessary interventions, and focus your valuable time and resources on addressing the issues that truly matter to project success.

Become a Certified Project Management Professional (PMP)®

Find Out More

Share this post: