Begin the Era of Structured System Management

1. Introduction: Quality Principles for the Other Half of the Workflow

Quality management has developed extraordinarily powerful tools for managing processes — manufacturing processes, service delivery processes, clinical procedures, software development workflows. These process-management tools assume a relatively clear input-to-output chain: defined inputs, defined transformation steps, defined outputs, and measurable quality characteristics at each stage.

But organizations do more than execute processes. They manage complex systems — healthcare safety programs, infrastructure development programs, government service delivery, cross-departmental initiatives — where the 'workflow' is not a linear process chain but a multi-year, multi-stakeholder, multi-milestone system with interdependencies that no single process map can capture. These complex organizational systems — what ASQ's Government Division calls the 'other half' of organizational workflow — have historically operated outside the systematic quality management tools developed for processes.

Structured System Management (SSM), most fully developed in the ASQ/ANSI G1 standard, provides a quality framework specifically designed for this domain. SSM allows quality principles — defined milestone events, specific requirements and measures, documented workflows — to apply to any organizational span of control, not just to defined operational processes. This session provides an overview of SSM, its conceptual foundations, and its application through two case studies.

"Every complex organization manages systems, not just processes. SSM gives quality practitioners the tools to apply systematic quality thinking to the full scope of organizational work — including the parts that have previously operated without quality discipline."

2. Understanding Structured System Management

2.1 The Gap SSM Addresses

Traditional quality management tools — process mapping, control plans, SPC, FMEA — are optimized for repetitive, defined processes where the same inputs and transformation steps produce the same output type each cycle. Most ISO 9001 and sector-specific quality frameworks share this process focus.

The organizational domain that SSM addresses is fundamentally different:

2.2 The Core SSM Concept: Milestone-Based Quality Management

The foundational concept of SSM is milestone-based quality management: defining the specific deliverables, requirements, and measures associated with each milestone in a complex organizational system, and systematically managing quality at each milestone rather than only at final delivery.

This concept addresses a critical gap in complex program management: in multi-year programs with many interdependent workstreams, quality problems that are not detected at intermediate milestones compound exponentially before final delivery. A requirements misalignment discovered at milestone 2 costs 10 times less to correct than the same misalignment discovered at milestone 8.

• Milestone definition: Each major program decision point or deliverable is defined as a formal milestone with documented requirements — what must be true for this milestone to be considered complete and acceptable.
• Milestone requirements: For each milestone, specific quality requirements are established: what deliverables must be produced, what quality standards they must meet, what review and approval process they must complete.
• Milestone measures: Quantitative performance measures for each milestone provide objective evidence of milestone quality — and enable trend analysis across milestones that reveals improving or deteriorating program health.
• Workflow documentation: The workflows that connect milestones — the sequence of activities, responsibilities, and handoffs that must occur for each milestone to be reached — are documented with the same rigor that process maps document operational processes.

3. The ANSI G1 Guidelines: Quality for Government Operations

3.1 Background and Scope

The American National Standards Institute G1 Guidelines for Evaluating Government Operations were published in 2021 by ASQ's Government Division. They represent the most developed codification of SSM principles and provide a practical framework for applying quality management to complex government programs and systems.

The G1 Guidelines address a genuine need: government agencies manage some of the most complex, multi-stakeholder, long-horizon programs in any sector — infrastructure construction, public health programs, social service delivery, regulatory program management. These programs have historically operated without the systematic quality management frameworks that comparable private-sector programs employ. G1 provides that framework.

3.2 The BEST Framework

A key element of the G1 Guidelines is the BEST assessment framework — a structured approach for evaluating organizational systems against best practice standards and identifying improvement opportunities. BEST stands for:

• B — Best Practice identification: What does best practice look like for this type of system or operation? What do the highest-performing comparable organizations do that this organization does not?
• E — Evidence-based assessment: How does the current system's actual performance compare to the best practice standard? What evidence supports the comparison?
• S — Systemic gap analysis: Which gaps between current practice and best practice represent systemic opportunities — gaps that, if closed, would improve performance across multiple program areas?
• T — Transformation roadmap: What specific changes, in what sequence, would most effectively close the priority gaps? What does the pathway from current to best practice look like?

3.3 The BEST Quick Scan

The BEST Quick Scan is an efficient assessment tool — typically completed in one to two days — that provides organizations with a rapid baseline assessment of their system quality maturity. It evaluates performance across the key dimensions of SSM: milestone definition completeness, requirements clarity, workflow documentation, measurement and monitoring practices, and leadership engagement with system quality.

Quick Scan outputs include:

• A maturity score for each SSM dimension, enabling prioritization of improvement investment.
• A gap analysis comparing current practice to the G1 best practice standards.
• A prioritized improvement roadmap identifying the highest-value transformation actions.

4. SSM in Practice: Two Case Studies

4.1 Case Study 1: State Department of Transportation Bridge Program

A State Department of Transportation manages a complex, multi-year program for the creation, contracting, and construction of bridges and other highway structures — a program spanning multiple departments, contractors, regulatory agencies, and funding sources over a 3–10 year lifecycle per project.

The Quality Challenge

Without a systematic milestone-based quality framework, the program experienced recurring patterns:

• Requirements that were clearly understood at program initiation became unclear through the design and contracting process, generating scope disputes and change orders.
• Quality problems discovered during construction that would have been preventable if identified during design review — each caught at the wrong milestone.
• Inconsistent quality across projects managed by different regional teams, with no mechanism for sharing lessons learned across the program portfolio.

SSM Application

The program applied SSM to define:

• Eight formal milestones across the full program lifecycle, from initial project concept through final construction acceptance, each with documented requirements and review criteria.
• Milestone-specific quality requirements: what deliverables must be produced and approved before advancing to the next milestone, what stakeholder approvals are required, and what quality measures must be met.
• Cross-project lessons learned capture: a standardized protocol for capturing quality insights at each milestone review and sharing them across the regional project teams.

Results

• Change order rates attributable to scope ambiguity reduced by 38% across the three-year implementation period.
• Cross-regional quality consistency improved measurably on five key construction quality indicators.
• Project teams reported significantly better understanding of what was required at each milestone, reducing the project management ambiguity that had previously consumed leadership attention.

4.2 Case Study 2: Healthcare Safety Management Program

A regional healthcare system wanted to apply SSM to its Patient Safety Management Program — a cross-departmental initiative spanning clinical, administrative, and quality functions.

The Quality Challenge

The safety management program had clear goals and committed leadership, but operated without a systematic milestone framework:

• Safety improvement projects were initiated with good intentions but without clear milestone definitions, making progress assessment subjective and inconsistent.
• Handoffs between clinical, administrative, and quality teams at each stage of safety improvement work were poorly defined, creating coordination gaps.
• No consistent mechanism existed for sharing safety improvement learning across clinical departments, preventing insights from one unit from benefiting others.

SSM Application

SSM provided a milestone framework for the full safety improvement lifecycle:

• Defined milestones: problem identification and scope definition, root cause analysis completion, intervention design and approval, pilot implementation and evaluation, full rollout, and sustained performance monitoring.
• Milestone requirements: for each milestone, specific deliverables (root cause analysis report, intervention protocol, pilot evaluation data), approval stakeholders, and quality criteria.
• Workflow documentation: explicit documentation of which team (clinical, quality, administrative) is responsible for each activity within each milestone, with defined handoff criteria.

Results

• Time from safety event identification to implemented corrective action reduced by 42% in the first year.
• Significant improvement in cross-departmental coordination — teams understood their role in the safety improvement workflow rather than operating in functional silos.
• Safety improvement learning was systematically captured and shared across 14 clinical departments, with three innovations from one unit successfully transferred to others.

5. Workshop Flow for a 4-Hour Session

6. Discussion Questions for Q&A

Conceptual Understanding

• Identify one complex program in your organization — a multi-year initiative, a cross-departmental system, or a multi-stakeholder program — that currently operates without a systematic milestone quality framework. What quality problems recur in that program that a milestone-based approach might prevent?
• The G1 Guidelines were developed for government operations. Where in non-government organizational contexts do you see the same need — complex systems that generate recurring quality problems precisely because they lack a systematic framework?
• The BEST framework identifies gaps between current practice and best practice. For the complex program you identified: what would best practice look like? What organizations or programs represent the standard you would benchmark against?

Application and Design

• Apply the milestone-based quality management concept to your identified program. What are the 3–5 most critical milestones? For each milestone, what deliverable must be produced and what quality requirements must it meet before the program advances?
• The DoT case study showed that SSM reduced change orders attributable to scope ambiguity by 38%. In your organizational context, what is the equivalent cost of milestone quality failures — scope disputes, rework in later phases, coordination failures? How would you estimate it?
• Design the workflow documentation for one transition between milestones in your identified program. Which team is responsible for each activity? What are the handoff criteria? What quality measure confirms the milestone is complete and acceptable?

7. Conclusion: Quality Belongs Everywhere

Quality management's most powerful contribution to organizational performance may not be improving individual processes — although it does that extraordinarily well. Its most powerful contribution may be systematically extending quality thinking to organizational domains that have historically operated without it: complex multi-stakeholder programs, government service systems, long-horizon initiatives, and the full range of organizational work that does not fit neatly into a process map.

Structured System Management is the framework that makes this extension possible. By adapting the core quality concepts — defined requirements, measured performance, systematic review, continuous improvement — to the milestone-based structure of complex organizational systems, SSM provides quality practitioners with tools that reach the 'other half' of organizational workflow that traditional process-focused quality management cannot address.

The organizations that apply SSM — that bring systematic quality discipline to their programs and systems as well as their processes — will build the organizational capability to consistently achieve complex program objectives, reduce rework and scope disputes across program lifecycles, and share quality learning across program boundaries that traditionally prevent it.

Quality principles apply everywhere. SSM provides the tools to apply them where they have been missing. That is the beginning of a new era.