Diagnostic walkthrough
One ordinary case, taken through the whole path.
The point of this page is the order of operations. Facts before variables, variables before conclusions, and an explicit list of what could not be established. The case below is composite and anonymized.
The path
The sequence being applied.
- Event
- Appraisal
- Accessible capacity
- Allocation
- Agency
- Decision
- Behavior
- Outcome
- Recovery
- Learning
- New conditions
The path is a search order, not a mechanism. It does not claim that conditions determine behavior or that the outcome could have been predicted from any stage.
Step one
What is established.
- A shared document was due Thursday. It was delivered Friday at 16:20.
- The person had said 'yes, that's fine' when the deadline was set on Monday.
- Two unrelated urgent requests reached the same person on Wednesday morning.
- One of those requests came from someone more senior than the person who set the deadline.
- No message was sent on Thursday to say the deadline would move.
Only observable, checkable statements. No motives, no adjectives about the person.
Step two
Plausible variables.
Allocation
Two priorities landed in the same window, set by different people who could not see each other's requests.
Agency
It is not established whether this person was permitted to decline or reorder work set by a senior colleague.
Clarity
It is not established whether Thursday was understood as a hard date or an intention.
Recovery
The same person covered an absence the previous week. Load had not come down in between.
Appraisal
Silence on Thursday may reflect an expectation that raising it would not be welcome. This is a hypothesis, not a finding.
Step three
What was ruled out, and why.
Skill
Ruled out. The same document type has been produced correctly nine times before.
Tooling
Ruled out. Nothing in the system prevented or delayed submission.
Information
Ruled out. Everything needed to write the document was available on Monday.
Willingness
Not supported by the available facts. Agreement was given and the work was completed, late.
Step four — what remains uncertain
- Whether the missing Thursday message was avoidance, an oversight, or a reasonable read of how the message would land.
- Whether the senior request was intended as an override of existing work or was simply unaware of it.
- Whether this is a one-off collision or a repeating weekly pattern — one case cannot tell you.
The document was still late, and that still needed to be addressed. What changed is which problem the conversation was about: two people setting priorities for the same person without visibility of each other.
Why this framing
Ordinary troubleshooting, applied to people and systems.
The engine light
Common
Cover the light with tape. The dashboard looks fine again.
Diagnostic
Read what the light is reporting. The light was never the problem; it was the only part of the problem that was visible.
The tripped breaker
Common
Keep flipping the breaker back and calling the person who flips it unreliable.
Diagnostic
Ask what load is on that circuit. A breaker that trips at the same hour every day is reporting something about the load, not about itself.
The slow machine
Common
Tell it to try harder. Restart it and hope.
Diagnostic
Find out what else is running. Very little available capacity is a resource problem, and resource problems do not respond to motivation.
The leak in the ceiling
Common
Repaint the stain. It looks solved for a while.
Diagnostic
Trace it upstream. Where a problem appears is often not where a problem is, and repainting guarantees a return visit.
Where a problem appears is often not where the problem is.