Claude-skill-registry ba-orchestration
Multi-technique business analysis orchestration using BABOK. Coordinates 14 techniques across strategic analysis, problem solving, planning, and design into comprehensive analysis packages.
git clone https://github.com/majiayu000/claude-skill-registry
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/ba-orchestration" ~/.claude/skills/majiayu000-claude-skill-registry-ba-orchestration && rm -rf "$T"
skills/data/ba-orchestration/SKILL.mdBusiness Analysis Orchestration
Coordinate multiple business analysis techniques into comprehensive analysis packages. Based on BABOK v3 methodology for combining techniques effectively.
Overview
Business analysis rarely uses a single technique in isolation. Complex initiatives require orchestrated combinations of techniques, sequenced appropriately, with findings synthesized into actionable recommendations.
Available Techniques (14 Skills)
Strategic Analysis
| Skill | Purpose |
|---|---|
| SWOT, PESTLE, Porter's Five Forces |
| BMC, Lean Canvas, 9-block analysis |
| Competitive analysis, industry comparison |
Problem Solving
| Skill | Purpose |
|---|---|
| Fishbone/Ishikawa, 5 Whys |
| Decision tables, weighted scoring, decision trees |
| Risk registers, probability/impact matrices |
Planning & Estimation
| Skill | Purpose |
|---|---|
| MoSCoW, Kano model, weighted scoring |
| Analogous, parametric, PERT, story points |
| Business capabilities, maturity models |
| Power/interest, RACI, communication plans |
Process & Data Design
| Skill | Purpose |
|---|---|
| Current/future state, Lean analysis |
| Customer experience, touchpoints |
| BPMN notation, workflows |
| ERDs, data dictionaries |
Technique Selection Guide
| Goal | Primary Technique | Supporting Techniques |
|---|---|---|
| Strategic planning | SWOT/PESTLE | Capability Mapping, Benchmarking |
| Business model design | Business Model Canvas | Stakeholder Analysis, Value Stream |
| Process improvement | Value Stream Mapping | Root Cause Analysis, Process Modeling |
| Customer experience | Journey Mapping | Stakeholder Analysis, Prioritization |
| Problem investigation | Root Cause Analysis | Risk Analysis, Decision Analysis |
| Technology decision | Decision Analysis | Benchmarking, Risk Analysis |
| Project estimation | Estimation | Prioritization, Risk Analysis |
| Backlog prioritization | Prioritization | Stakeholder Analysis, Estimation |
| Database design | Data Modeling | Process Modeling, Capability Mapping |
| Risk management | Risk Analysis | Prioritization, Stakeholder Analysis |
| Transformation planning | Capability + VSM | SWOT, Stakeholder Analysis |
| New initiative | Full analysis | Multi-technique package |
| M&A due diligence | Capability + Benchmarking | Stakeholder Analysis, Risk |
| Competitive positioning | Benchmarking | SWOT, Business Model Canvas |
Standard Workflows
Workflow 1: Strategic Planning
1. Stakeholder Analysis - Identify key stakeholders 2. Capability Mapping - Create capability model 3. Benchmarking - Compare against industry 4. SWOT/PESTLE Analysis - Environmental scan 5. Prioritization - Investment decisions
Workflow 2: Customer Experience Improvement
1. Stakeholder Analysis - Identify user segments 2. Journey Mapping - Map current experience 3. Value Stream Mapping - Identify operational waste 4. Capability Mapping - Link to capabilities 5. Prioritization - Impact vs effort matrix
Workflow 3: Process Optimization
1. Process Modeling - Capture current process (BPMN) 2. Value Stream Mapping - Identify waste and bottlenecks 3. Journey Mapping - User experience perspective 4. Root Cause Analysis - Identify improvement areas 5. Estimation - Plan improvement effort
Workflow 4: Full Analysis Package
1. Stakeholder Analysis - Who is involved? 2. Process Modeling - What happens today? 3. Capability Mapping - What do we do? 4. Value Stream Mapping - How efficiently? 5. Journey Mapping - What's the experience? 6. Synthesis - Integrated findings
Workflow 5: Strategic Assessment
1. SWOT/PESTLE Analysis - Environmental scan 2. Benchmarking - Competitive position 3. Business Model Canvas - Current model 4. Capability Mapping - Internal strengths 5. Gap Analysis - Strategic gaps 6. Prioritization - Strategic initiatives
Workflow 6: Problem Investigation
1. Stakeholder Analysis - Who's affected? 2. Root Cause Analysis - What's causing it? 3. Risk Analysis - What's at risk? 4. Decision Analysis - What are options? 5. Prioritization - Which solution? 6. Estimation - Implementation effort
Workflow 7: New Project Planning
1. Stakeholder Analysis - Who's involved? 2. Risk Analysis - Project risks 3. Estimation - Effort and duration 4. Prioritization - Backlog ordering 5. Process Modeling - Key workflows 6. Data Modeling - Data structures
Workflow 8: Database/System Design
1. Process Modeling - Business workflows 2. Data Modeling - Entity relationships 3. Stakeholder Analysis - Data owners 4. Risk Analysis - Data risks 5. Capability Mapping - System capabilities
Orchestration Process
Step 1: Understand the Goal
Ask clarifying questions:
- What decision needs to be made?
- Who are the key stakeholders?
- What's the time frame?
- What data/access is available?
Step 2: Select Workflow
Based on the goal, select the appropriate workflow from above or design a custom sequence.
Step 3: Execute Techniques
For each technique in the workflow:
- Load the appropriate skill
- Gather required inputs
- Execute the technique
- Capture outputs
Step 4: Synthesize Findings
Combine outputs into integrated analysis:
- Cross-reference stakeholders to capability owners
- Link pain points to capabilities and processes
- Align improvements across all techniques
- Prioritize recommendations by impact and feasibility
- Create unified roadmap
Parallel vs Sequential Execution
When to Parallelize
Execute techniques in parallel when:
- No data dependencies between them
- Different stakeholders/SMEs provide input
- Time constraints require faster completion
When to Sequence
Execute techniques sequentially when:
- Output of one feeds into another
- Same stakeholders for both (avoids fatigue)
- Earlier technique shapes scope of later one
Example Parallel Plan
Phase 1 (Parallel):
- Stakeholder Analysis
- Capability Mapping (discovery)
Phase 2 (Parallel, after Phase 1):
- Value Stream Mapping (uses stakeholder context)
- Journey Mapping (uses persona from stakeholder analysis)
Phase 3 (Sequential):
- Synthesis and Integration
Output Package Structure
Integrated Analysis Package
## Integrated Business Analysis: [Initiative] ### Executive Summary [Key findings and recommendations] ### Stakeholder Landscape [From stakeholder-analysis skill] ### Capability Model [From capability-mapping skill] ### Value Stream Analysis [From value-stream-mapping skill] ### Customer Experience [From journey-mapping skill] ### Integrated Findings [Cross-cutting insights] ### Prioritized Roadmap [Unified recommendations] ### Appendix: Detailed Outputs [Full outputs from each technique]
Quality Checklist
Orchestrated packages must include:
- Clear problem/goal statement
- Technique selection rationale
- Outputs from each technique
- Cross-referenced findings
- Integrated recommendations
- Prioritized roadmap
- Traceability between deliverables
Related Skills
- Stakeholder identification and engagementstakeholder-analysis
- Business capability modelingcapability-mapping
- Lean value stream analysisvalue-stream-mapping
- Customer/user experience mappingjourney-mapping
- BPMN process documentationprocess-modeling
- Entity-relationship designdata-modeling
- Problem investigationroot-cause-analysis
- Strategic environmental scanswot-pestle-analysis
- Business model designbusiness-model-canvas
- MoSCoW, Kano, weighted scoringprioritization
- Risk identification and mitigationrisk-analysis
- Decision support techniquesdecision-analysis
- Effort and duration estimationestimation
- Competitive analysisbenchmarking
Version History
- v1.0.0 (2026-01-10): Initial release - extracted from ba-orchestrator agent