Business Analysis SOPs¶
Why This Exists¶
This document defines SOP areas for repeatable Business Analysis work.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
SOPs make organization understanding, capability analysis, gap detection, and Practice handoffs repeatable and auditable.
SOP Catalogue¶
| SOP ID | SOP | Purpose | Primary Digital Professional |
|---|---|---|---|
| BA-SOP-001 | Organization Context Review SOP | Review and interpret organization context for procurement use. | Orion |
| BA-SOP-002 | Capability Analysis SOP | Assess capabilities, services, products, resources, and evidence. | Orion |
| BA-SOP-003 | Experience Profile Analysis SOP | Interpret past projects and references for procurement use. | Orion |
| BA-SOP-004 | Operating Region Analysis SOP | Interpret geographic coverage and suitability. | Orion |
| BA-SOP-005 | Procurement Preference Analysis SOP | Interpret opportunity preferences and constraints. | Orion |
| BA-SOP-006 | Capability Gap Detection SOP | Identify and classify gaps with evidence basis. | Orion |
| BA-SOP-007 | Organization Intelligence Graph Support SOP | Prepare organization knowledge for graph reasoning. | Orion |
| BA-SOP-008 | Organizational Memory Support SOP | Support durable organization knowledge and context updates. | Orion |
| BA-SOP-009 | Practice Context Handoff SOP | Provide procurement-ready context to dependent Practices. | Orion |
SOP Execution Flow¶
flowchart TD
Trigger[Trigger]
Source[Organization source references]
SOP[SOP]
Analysis[Analysis output]
Gap[Gap signal]
Handoff[Practice handoff]
Trigger --> SOP
Source --> SOP
SOP --> Analysis
SOP --> Gap
Analysis --> Handoff
Gap --> Handoff
SOP Rules¶
- SOPs must preserve source references.
- SOP outputs must distinguish fact, interpretation, gap, confidence, and recommendation.
- Organization fact updates must route through Organization Domain.
- Practice handoffs must identify the receiving Practice and intended use.