Problem definition
The outcome, constraints, assumptions, business impact, and agreed measures of success.
Our problem-solving method
The ROZY Logic finds the variable that changes the outcome.
Complex technology problems arrive as symptoms, requested solutions, and competing explanations. The ROZY Logic makes the reasoning visible—from the problem worth solving to the result the evidence supports.
The method
Four stages. One visible chain of reasoning.
Each stage produces something the next stage can test. The process can move backwards when new evidence changes what is known.
-
Stage 1
Reframe
What outcome matters, and what problem are we actually solving?
Separate the reported symptom from assumptions, requested solutions, constraints, business impact, and the conditions that would count as success.
- Output
- A shared problem statement and definition of success.
-
Stage 2
Observe
What is actually happening?
Map the system as it behaves, gather evidence, reproduce the behaviour where possible, establish a baseline, and record what remains unknown.
- Output
- An evidence record and current-state map.
-
Stage 3
Zero In
Which explanation or intervention is best supported?
Compare hypotheses, test uncertainty, remove explanations that do not survive the evidence, and isolate the condition or decision that changes the outcome.
- Output
- A justified finding or decision, with uncertainty recorded.
-
Stage 4
Yield
Did the intervention produce the intended outcome?
Implement or pilot safely, measure against the baseline, check consequences, transfer the operating knowledge, and revise when the result is incomplete.
- Output
- A verified result—or a documented reason to continue investigating.
ROZY in practice
The queue accepted every update. Nothing deployed.
The visible symptom pointed at the management controller. The decisive variable sat across the system boundary.
A physical server's management controller accepted valid firmware packages into its update queue, but deployment never began. Installing and removing the expected operating-system service did not change the behaviour.
The investigation did not stop at the component displaying the symptom. It followed the execution path until one missing condition explained why a valid queue could remain idle.
- Reframe
- Which component actually executes the update, and where must that execution run?
- Observe
- The packages were valid, the queue persisted, and the obvious host-service change did not alter the result.
- Zero In
- x was the execution context—the controller held the queue, but the workflow still needed the correct host-side execution path.
- Yield
- Running the vendor update manager from the host against the controller queue started deployment and produced a repeatable procedure.
Evidence boundaries
“We do not know yet” is a valid result.
Unsupported certainty is not.
A hypothesis is not a finding. A finding is not automatically a solution. A solution is not finished until the intended outcome has been measured.
ROZY keeps those boundaries explicit. It can prove an intervention, disprove an explanation, or show that the evidence is still incomplete. Yield may send the investigation back to Observe; the method is a reasoning loop, not theatre built around a predetermined answer.
The variable may be a cause, boundary, dependency, ownership gap, constraint, missing condition, or chosen intervention. Some problems have several contributing factors rather than one hidden root cause.
What remains after the work
Evidence your team can operate with.
Deliverables vary by engagement, but the reasoning never disappears into a black box.
System and evidence map
Dependencies, boundaries, flows, observations, baselines, and gaps in what is known.
Decision record
Hypotheses, rejected explanations, options, trade-offs, and the evidence behind the chosen intervention.
Verified result
Measured outcome, remaining uncertainty, operational guidance, and what should happen next.
Bring us the problem, not a predetermined solution.
Tell us what is happening, what it affects, and what has already been tried. We will start by reframing it.
Bring us the problem