From Symptom to System: Why the Same Discipline Works in Any Room

Wed, 26 Aug 2026 14:30:36 GMT

How the Process transcends the singular application.

A patient walks into the clinic with knee pain. The easy answer is to treat the knee. The right answer starts somewhere else: how does this person walk, what does their job ask of their body, what has their training load looked like, and what compensations built up before the knee finally spoke up. The knee is the symptom. The system is everything upstream of it.

That question, asked patiently and in the right order, is the whole of clinical reasoning. It is also the whole of BlueDragon.

One Method, Built for Any System

BlueDragon Integrated Problem-Solving is a structured, sociotechnical root cause analysis framework. It traces a visible failure back through the policies, incentives, culture, and operating conditions that produced it, then tests whether a proposed fix is strong enough to prevent recurrence. The method does not care whether the failure shows up in a hospital, a nuclear facility, a factory floor, or a federal rulemaking. A symptom is a symptom. A system is a system. The discipline of moving from one to the other does not change with the letterhead.

That is a deliberate design choice, not an accident of my background. Seventeen years of direct-access physical therapy trained me to hold two things at once: move fast enough to help the person in front of me today, and look deep enough to understand why they ended up in front of me at all. A retired Air Force officer's years in high-consequence operations added a second layer: the tolerance for ambiguity, and the discipline for after-action review, that any high-stakes environment demands. BlueDragon formalizes that same posture into a repeatable method, and it travels well because the underlying questions are not medical questions or engineering questions. They are systems questions.

What That Looks Like Across Domains

I recently applied that same discipline to a federal rulemaking on radiation exposure policy, a domain with no obvious connection to a physical therapy clinic. The presenting question was narrow: should an agency retire a fifty-year-old safety requirement and replace it with an administrative threshold. The BlueDragon question was the same one I ask about a knee: what is this control actually doing, what happens structurally if it disappears, and does the record support the claim that the replacement performs the same function. The answer did not require expertise in nuclear physics. It required the same discipline that catches a compensation pattern before it becomes an injury: read the primary sources fully, separate the diagnosis from the remedy, and ask what evidence would prove the analysis wrong.

The same pattern holds in financial analysis, in product claims review, and in organizational fit assessments I run for prospective clients. A nonprofit's revenue mix can look healthy in a headline number and fragile underneath it, the same way a joint can look stable under a manual test and still fail under load. A manufacturer's marketed performance claim can rest on a number that was never actually measured the way the label implies. In every case, the job is the same: find where the presenting symptom and the underlying system disagree, and say so plainly.

Three Places Every Fix Has to Land

An analysis that only names a problem is unfinished. BlueDragon work always resolves into recommendations across three interlocking levers, because a fix that lives in only one of them tends not to hold.

Policy is the written rule: the regulation, the protocol, the standard operating procedure. Programs are the structures that carry the policy into daily practice: the training, the monitoring, the audit trail, the budget line that keeps a control funded. People are the humans who live inside both, and whose judgment, workload, and incentives determine whether a well-written policy actually survives contact with a Tuesday afternoon. A recommendation that changes the policy but ignores the program will not stick. A program built on good incentives but resting on an unclear policy will drift. Durable change touches all three, and naming which lever a given recommendation pulls is part of the discipline, not an afterthought.

Why This Matters to You

I am not a specialist who happens to consult. I am a systems thinker whose specialty is the method itself, applied with the same rigor whether the subject is a rotator cuff, a regulatory docket, or a supply chain. Give me the information you have and the outcome you are working toward, and I will bring the same discipline to your system that I would bring to a patient on my table: ask what the symptom is actually telling us, trace it honestly to its source, and recommend the fix that holds.

That is the offer behind Convergence Operational Group, and it is the reason the tagline is not a slogan. From symptom to system is simply how the work gets done.