A workshop introducing Structured System Management and ANSI G1 thinking for applying quality discipline to complex programs, government operations, and milestone-based systems.
Overview
A workshop introducing Structured System Management and ANSI G1 thinking for applying quality discipline to complex programs, government operations, and milestone-based systems.
Every complex organization manages systems, not just processes.
Learning Objectives
- Distinguish process management from structured system management.
- Apply milestone-based quality management to complex work.
- Explain how ANSI G1 extends quality principles to government operations.
- Use the BEST Quick Scan as a rapid system assessment method.
- Translate case-study learning into a system improvement roadmap.
The Other Half of Workflow
Traditional quality tools manage repeatable processes well. Structured System Management addresses complex systems with milestones, stakeholders, dependencies, and long time horizons.
Milestone Quality
SSM defines deliverables, requirements, measures, and decision criteria at each milestone so problems are found while they are still inexpensive to correct.
ANSI G1 and BEST
The ANSI G1 framework and BEST Quick Scan provide a disciplined way to compare current system performance with best practice and translate gaps into improvement plans.
Case Study Application
Transportation, infrastructure, healthcare, and government examples show how SSM reduces coordination failures and creates systematic learning across program portfolios.
Workshop Framework
| SSM concept | Purpose | Workshop application |
|---|---|---|
| Milestones | Define decision points in complex systems. | Identify deliverables, measures, and evidence at each point. |
| Requirements | Clarify what good looks like before work advances. | Prevent late discovery of scope or quality gaps. |
| BEST Quick Scan | Assess best practice, evidence, systemic gaps, and transformation steps. | Prioritize the most important system improvements. |
| Learning portfolio | Reuse lessons across similar systems. | Prevent every program from relearning the same lesson. |
Workshop Flow
| Time block | Activity | Facilitation focus |
|---|---|---|
| 0:00-0:30 | Opening and framing | Introduce the source problem, workshop purpose, and participant context. |
| 0:30-1:15 | Framework teaching | Walk through the core model and connect it to quality leadership practice. |
| 1:15-2:00 | Application exercise | Groups apply the framework to a real or realistic organizational scenario. |
| 2:00-2:15 | Break | Display the core framework and reflection prompt. |
| 2:15-3:00 | Case or tool practice | Use the source examples to practice decision-making, diagnosis, or design. |
| 3:00-3:40 | Implementation planning | Translate the concept into a 30- to 90-day action plan. |
| 3:40-4:00 | Commitments and Q&A | Participants identify one action, one stakeholder, and one evidence measure. |
Discussion Questions
- Where does this topic show up in your current quality system?
- What behavior, decision, or process would change if this framework were adopted?
- Which stakeholder needs to be involved first for the idea to move from training concept to operating practice?
- What evidence would show that the workshop concept created measurable value?
Key Takeaways
- SSM extends quality principles to complex programs and systems.
- Milestone-based quality management detects problems early.
- ANSI G1 provides a developed government-operations framework.
- BEST Quick Scan creates a rapid maturity assessment.
- Case studies show improved coordination, fewer disputes, and better system learning.
Related Resources
Complete Workshop Source Guide
This section preserves the full workshop guide content from the source DOCX so the web page can serve as a complete online version of the material.
WORKSHOP POCKET GUIDE
Begin the Era of
Structured System Management
Focus Area
Transforming Processes
Format
Teaching + Case Studies
Duration
~4 Hours
Audience
Quality Leaders & Government Managers
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:
Characteristic
Process Domain (Traditional QM)
System Domain (SSM)
Work Unit
Repeating operational cycle — the same process produces the same output type each cycle.
Unique program or project — each major deliverable is distinct, with milestones and requirements specific to that program.
Time Horizon
Operational cycles measured in hours, days, or weeks.
Programs spanning months to years, with quality requirements that must be maintained across the full duration.
Quality Focus
Output quality: does the product or service meet specifications at delivery?
Milestone quality: does each defined milestone in the program meet its requirements? Are dependencies between milestones managed effectively?
Stakeholder Complexity
Typically within a single function or team.
Cross-departmental, cross-agency, or cross-organizational — with multiple stakeholders whose requirements must be balanced and whose contributions must be coordinated.
Improvement Mechanism
SPC, PDCA applied to the repeating process cycle.
Milestone review, lessons learned capture, and system redesign between program phases or across program cycles.
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
Time Block
Duration
Content & Activities
0:00 – 0:30
30 min
Opening: The Other Half of the Workflow. Present the process vs. system domain distinction. Poll: What percentage of your organization's critical work occurs in defined operational processes vs. complex multi-milestone programs? Where does traditional QM struggle to apply?
0:30 – 1:15
45 min
SSM Fundamentals. Walk through the core concept of milestone-based quality management. Groups: identify one complex program in their organization that currently lacks a milestone quality framework. What are the recurring quality problems in that program?
1:15 – 2:00
45 min
G1 and BEST Framework. Walk through the G1 Guidelines background and BEST methodology. Groups: apply the BEST Quick Scan framework at a high level to their identified program. What are the most significant systemic gaps?
2:00 – 2:15
15 min
Break. Display both case study summaries. Participants identify which case study is more analogous to their organizational context.
2:15 – 3:00
45 min
Case Study Analysis. Walk through both cases in detail. Groups: which SSM application principles from the case studies are most transferable to their identified program? What would adoption look like?
3:00 – 3:40
40 min
SSM Design Workshop. Groups design a high-level SSM framework for their identified program: milestone definition (3–5 key milestones), requirements per milestone, workflow documentation approach, and quality measures.
3:40 – 4:00
20 min
Share-Out and Q&A. Groups present their SSM framework draft. Open Q&A on G1 standard, BEST methodology, and implementation approach.
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.