Project discipline
PMI-trained reviewers should see a clear path from scope condition to owner, constraint, risk, decision, and closeout record.
Operating Method
Methodology
In plain English, SG looks at why the same work problem keeps returning. The method then separates the starting condition, current pattern, owner, proof, and next decision.
ProblemOwnerRecordResult
The operating premise
Exit strategy before motion.
SG starts by understanding the operating state, the drift already in motion, and the specific condition the client needs to reach.
Diagnostic model
The 3-State Gap Model
Engagements begin by separating fact from motion from intent. The gap between those states defines the work.
State 01
Beginning State
The starting condition brought into the conversation: what the client believes should be happening, what triggered the review, and what the work is expected to do.
State 02
Current State
What the work is actually showing now: repeated problems, unclear ownership, delayed records, workarounds, rework, waiting points, and decisions that are not holding.
State 03
Desired State
The operating condition leadership needs next: who owns the work, where the record lives, what proof closes the loop, and what review cadence keeps the process from drifting.
Method-Literate Review
Plain language at the front door. Systematic control underneath.
The plain-language story explains the problem before the framework language appears. The method remains rigorous enough for reviewers trained in project management, process improvement, Lean operating controls, or iterative delivery.
Process improvement
Six Sigma and Lean-trained reviewers should see how SG separates observed work from assumed work, then identifies where variation, delay, or rework enters the route.
Iterative delivery
Sprint-trained reviewers should see a review cadence, a defined backlog of operating issues, and a way to test whether each corrective action changed the work.
Executive control
Leadership should see the operating exposure, the decision needed, the evidence behind the recommendation, and the record that remains after SG leaves.
Plain-English Method Guide
You do not need these words to start.
Method words are useful after the real problem is visible. This guide translates the terms into everyday work examples so novice readers can recognize the pattern, while process-trained readers can still see the structure underneath.
Systematic approach
Do the work in a repeatable order instead of reacting differently every time.
A recurring billing delay is reviewed the same way each time: what happened, who touched it, where it waited, what proof was missing, and what changed.
Why it matters: It keeps improvement from becoming guesswork.
PMI / project management
Define the scope, owner, risk, decision, and closeout before the work drifts.
A field change is logged with the impact, responsible owner, due date, approval need, and closeout record.
Why it matters: It protects schedule, cost, responsibility, and decision history.
Six Sigma / Lean
Find variation, waiting, rework, and waste in the path of work.
Three people answer the same customer question because the current answer is not stored in one trusted place.
Why it matters: It shows where effort is being spent without moving the work forward.
Kanban
Make work visible so people can see what is waiting, active, blocked, or done.
Instead of asking who has the file, the team sees the request, owner, status, blocker, and next move on one board.
Why it matters: It reduces chasing and shows where work is piling up.
Sprint / Scrum
Work in short review cycles so the team can test, learn, and adjust.
A two-week improvement cycle tests one new closeout rule, then checks whether repeat calls dropped.
Why it matters: It prevents big fixes from drifting without feedback.
SOP
The agreed way work should move from request to done.
When a provider is out, the office knows who reviews messages, who calls back, and what record proves the loop closed.
Why it matters: It turns tribal memory into a usable standard.
KPI
A number that should help someone make a better decision.
Queue age matters only if it shows where work is waiting too long and who can release it.
Why it matters: It keeps dashboards from becoming decoration.
Root cause / corrective action
Find why the problem keeps returning, then change the control point that lets it return.
The issue is not that staff forgot. The issue is that no owner, due time, or proof standard existed.
Why it matters: It fixes the condition instead of blaming the symptom.
After-action discipline
The review does not end when the meeting ends.
SG's method comes from field environments where a lesson had to become a usable route. The work is observed, tested, corrected, and handed back as something the client can keep operating.
Observe before prescribing
Start with what people actually do, not the title of the form, software, meeting, or department.
Match the work to the role
A shared process can have one backbone, but each role needs language, examples, and standards tied to the duty they perform.
Test the route in motion
Walk the scenario, let the handoffs reveal themselves, and adjust the route before the new standard becomes policy.
Capture the lesson
Record what changed, what held, what broke, and what needs the next review so the team keeps improving after SG steps back.
Corrective Action Logic
The method follows the work from symptom to controlled review.
SG does not begin with a tool preference. The review starts with the route of work, then decides what ownership, record structure, control point, or review cadence is missing.
01
Define the condition
One repeated workflow, symptom, field change, patient follow-up, billing delay, or ownership question is selected.
02
Measure the present route
SG records how work moves today: source, owner, handoff, queue, record, decision, proof, closeout.
03
Analyze the break
The review separates people working hard from the control point that is failing to hold the route together.
04
Design the corrective path
The recommendation names the new owner point, record location, review cadence, and decision trigger.
05
Review the result
The action is checked against expected outcome, adoption, evidence quality, and whether the problem returns.
Engagement phases
From diagnostic to operating rhythm.
The model only matters if it becomes action. These phases turn the baseline into a decision record, then into reviewable execution.
The record is the differentiator.
Most advisory work can describe what happened. SG builds the record that explains why a decision moved, who owned it, what outcome was expected, and whether the result held up under review.