Use this when
The situation fits this depth.
- Problems that survived previous fixes
- Conflicting explanations across teams
- A change decision that requires evidence across authority, workflow, information, people, or technology
Level 02
System Diagnostic
Follow the work, decisions, authority, and exceptions until the real pattern becomes visible.
System Diagnostic moves beyond a first read. It examines real evidence, decision paths, handoffs, workarounds, and human load to produce an evidence-backed problem definition.
Not for
This should not become a shortcut.
- A request to blame one person or team
- A client unwilling to provide relevant evidence or access
- A pre-decided solution seeking a diagnostic label
Two scopes, one diagnostic family
Change the depth without multiplying the catalogue.
Focused Diagnostic
One difficult problem or decision path, examined with 2–4 relevant stakeholders.
- Duration
- 5–7 business days
- Price
- USD 2,500–5,000
- Participants
- 2–4 stakeholders
Cross-System Diagnostic
A problem spanning multiple teams, functions, authority layers, or operating systems.
- Duration
- 2–4 weeks
- Price
- USD 5,000–10,000
Inputs and evidence
Depth begins with evidence, not terminology.
SE Ocean separates observation, evidence, hypothesis, interpretation, and recommendation throughout the work.
- Relevant documents and operating records
- Stakeholder interviews
- A real workflow or decision path
- Exceptions, workarounds, and prior interventions
Concrete outputs
What should exist when this scope ends.
Current System Map
Problem and Decision Map
Authority and Responsibility Gaps
Workflow, handoff, and exception analysis
Human-load and workaround patterns
Evidence-backed problem definition
Structural Tension Register
What should change, wait, or remain untouched
Specialist applications
AI, search, and workflow are system contexts, not competing service pillars.
- Delegation and decision rights
- Workflow and handoffs
- Performance and information flow
- AI and human accountability
- Search and discovery decisions
- Governance and escalation
Boundaries
Uncertainty should be written down, not hidden.
- Diagnosis does not guarantee one root cause
- Recommendations distinguish evidence from interpretation
- Architecture begins only when the problem definition is credible