Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Use When
- Use this skill when the assignment needs business-analysis tools, diagnostics, or decision-support methods.
- Load it when a proposal section needs structured analysis rather than generic commentary.
Do Not Use When
- The task only needs formatting or proposer-profile selection.
- Another supporting skill is a closer fit for the assignment.
Required Inputs
| Artefact | Source | Required? | If absent |
|---|---|---|---|
| Assignment brief and analytical question | Client or proposal lead | required | Stop tool selection and state the unresolved question. |
| Decision criteria, evidence, and constraints | ToR, client records, verified research | conditional | Use a labelled hypothesis; do not present a diagnosis as fact. |
Workflow
Stop or block the workflow when a required input, permission, or acceptance basis is missing. Recover by revising the scope, obtaining evidence, or returning the narrowest qualified draft before proceeding.
- Identify which analytical question the proposal actually needs to answer.
- Decide whether the assignment needs business value assessment, business analysis planning, solution refinement, or solution evaluation support.
- Use discovery questions where the brief is unclear on outcomes, users, data, workflows, support, or decision criteria.
- Read the local references only where they materially improve the output.
- Select the tools that fit the assignment and convert them into proposal-ready logic, not academic summary.
- Integrate the output into the relevant proposal section and check for consistency.
Quality Standards
- Translate analysis into practical proposal language, decisions, and outputs.
- Keep the selected tools specific to the assignment rather than listing frameworks for their own sake.
- Show how findings move from situation -> gap -> solution -> transition -> evaluation.
- Preserve compatibility with existing repository workflows and file paths.
Anti-Patterns
- Dumping framework names without application. Fix: state the question, evidence, analysis, and decision for each tool.
- Using SWOT where causal diagnosis is needed. Fix: use root-cause analysis or an issue tree.
- Treating assumptions as findings. Fix: label hypotheses and name the validation source.
- Selecting tools before reading evaluation criteria. Fix: map each tool to a scored deliverable.
- Producing analysis with no consequence. Fix: state what the client can choose or change from the result.
Outputs
| Artefact | Consumer | Acceptance condition |
|---|---|---|
| Analysis method block or standalone analysis plan | Evaluator and delivery team | Names the question, tool, evidence, steps, output, and decision use. |
Evidence Produced
| Evidence | Consumer | Acceptance condition |
|---|---|---|
| Tool-selection rationale and assumption register | Traceable table | Every method maps to a ToR requirement and unsupported claims are labelled. |
Capability and Permission Boundaries
Read and search are required; any edit or external action remains within the explicit authority and permission boundary stated below. Read and search are required. Default to read-only analysis. Edit proposal files only when drafting is authorised; do not alter client source data or certify findings.
Degraded Mode
If client data or verification capability is unavailable or missing, return the narrowest qualified analysis plan, hypotheses, and evidence gaps. Mark the diagnosis not assessed.
Decision Rules
| Analytical need | Action | Risk avoided |
|---|---|---|
| Cause of a defined problem | Root-cause analysis or issue tree | Symptom-level recommendations |
| Compare feasible choices | Options appraisal or MCDA | Predetermined selection |
| Describe operating gaps | Process map plus gap analysis | Abstract framework dumping |
Worked Example
A revenue-leakage assignment uses a process map to locate control breaks, then an options appraisal to rank fixes by value, cost, and implementation risk; it does not substitute a generic SWOT.
References
- Proposal skills router for repository-wide routing and mandatory quality gates.
- Local
references/files when detailed frameworks or examples are needed. - ../references/discovery-question-bank-for-proposals.md when elicitation must clarify proposal assumptions.
- ../references/service-design-methodology-module.md when business analysis must cover journeys, touchpoints, service blueprints, or support experience.
- ../references/technical-strategy-credibility-checklist.md when analysis affects software, SaaS, AI, cloud, integrations, or operations decisions.
Top-tier proposals reference named analytical frameworks and tools — they show the evaluator how the firm thinks, not just what it will do. This skill provides a library of business analysis tools that proposal sections draw from, particularly methodology (06), understanding of assignment (03), and executive summary (02).
When to Read This Skill
- Drafting methodology sections that describe how the firm will analyse problems
- Proposing a diagnostic or assessment approach
- Structuring the conceptual framework section of a methodology
- The ToR asks for specific analytical deliverables (gap analysis, benchmarking, options appraisal)
- Strengthening a proposal with named, credible frameworks that demonstrate structured thinking
Business Analysis Lifecycle
Use this four-part structure when the proposal must show disciplined analysis rather than isolated tools:
- Business value assessment — understand the situation, identify gaps, and define the high-level solution direction.
- Business analysis planning — define governance, stakeholder engagement, decision rights, and the analysis roadmap.
- Solution refinement — elicit, analyse, and package requirements or other solution information.
- Transition and evaluation — define adoption, rollout, acceptance, benefits realisation, and post-implementation review.
Proposal language should make the chain explicit: "We will first establish the current-state problem and desired outcomes, then govern the analysis process, refine the requirements with stakeholders, and finally support transition and solution evaluation."
Business Analysis Planning and Governance
Business Analysis Governance
Use for: assignments where the client needs clarity on decision rights, approval routes, standards, or change authority.
Cover:
- decision-making forums and approval thresholds
- documentation and sign-off rules
- traceability expectations
- escalation and change control links to project governance
- level of rigour needed for predictive versus adaptive delivery
Stakeholder Engagement Approach
Use for: politically complex assignments, cross-functional reforms, digital projects, or any work with many affected groups.
Define:
- stakeholder groups and why they matter
- engagement objective by group
- preferred techniques by group
- cadence and decision points
- known sensitivities, resistance points, and availability constraints
Business Analysis Work Plan
Use for: methodology sections that need a visible roadmap for analysis activities.
Include:
- analysis activities by phase
- expected artefacts and who approves them
- dependency on client inputs
- analysis checkpoints before design or implementation begins
- links to testing, transition, and benefits tracking
Situation, Scope, and Problem Framing
Use these patterns before jumping to requirements:
- Situation statement — what is happening now and why it matters
- Goal statement — what improved future state the client wants
- Context diagram — the boundary of the work and key external actors, systems, and information flows
- Customer segments/personas — distinct user or beneficiary groups whose needs differ materially
- Business events — triggers that cause work to happen and reveal real functional needs
These patterns are especially useful where the ToR is solution-biased and the proposal needs to reframe the assignment around the actual business problem.
Strategic Analysis Tools
SWOT Analysis
Use for: organisational assessments, sector diagnostics, baseline studies.
| Positive | Negative | |
|---|---|---|
| Internal | Strengths | Weaknesses |
| External | Opportunities | Threats |
Best practice: never present a SWOT alone — always follow with "So what?" — which strengths to leverage, which weaknesses to address, which opportunities to prioritise, and which threats to mitigate.
PESTLE Analysis
Use for: environment scanning, policy analysis, sector assessments, feasibility studies.
| Factor | Description | Proposal Application |
|---|---|---|
| Political | Government policy, political stability, regulatory direction | Public sector reform, governance assignments |
| Economic | Growth rates, inflation, exchange rates, fiscal environment | Financial sector, economic development assignments |
| Social | Demographics, cultural factors, health, education levels | Health, education, social protection assignments |
| Technological | Digital infrastructure, technology adoption, innovation | ICT, digital transformation assignments |
| Legal | Legislation, regulatory frameworks, compliance requirements | Regulatory reform, legal framework assignments |
| Environmental | Climate, natural resources, environmental regulations | Agriculture, energy, infrastructure assignments |
STEEPLE Analysis
Use for: comprehensive environment scanning that adds ethical considerations to PESTLE. Add one row to the existing PESTLE table: | Ethical | Community consent, safeguarding standards, environmental justice, indigenous rights, anti-corruption norms | Development projects, extractive industries, community-based interventions | Reference STEEPLE instead of PESTLE when the ToR involves community-level interventions, safeguarding, or ethics-sensitive sectors.
Porter's Five Forces
Use for: market analysis, competition assessments, sector studies, private sector advisory.
- Threat of new entrants
- Bargaining power of suppliers
- Bargaining power of buyers
- Threat of substitute products or services
- Competitive rivalry within the industry
Value Chain Analysis
Use for: sector competitiveness studies, agricultural value chain assessments, industrial diagnostics.
- Map the full chain from inputs to end consumer
- Identify where value is created and where it is lost
- Pinpoint bottlenecks, inefficiencies, and opportunities for intervention
- Common in agriculture, manufacturing, and trade assignments
TOWS Matrix
Use for: extending SWOT into actionable strategy options. Build on a completed SWOT by generating four strategy types:
| Strategy | Combination | Question |
|---|---|---|
| SO (Maxi-Maxi) | Strengths × Opportunities | How can we use strengths to maximise opportunities? |
| ST (Maxi-Mini) | Strengths × Threats | How can we use strengths to minimise threats? |
| WO (Mini-Maxi) | Weaknesses × Opportunities | How can we minimise weaknesses by exploiting opportunities? |
| WT (Mini-Mini) | Weaknesses × Threats | How can we minimise weaknesses and avoid threats? |
| Always present TOWS as the "So what?" after SWOT — it converts analysis into strategy. |
SOAR Analysis
Use for: positive/appreciative organisational assessments, strategic planning, rebranding.
| Dimension | Focus |
|---|---|
| Strengths | What are we doing well? What are our greatest assets? |
| Opportunities | What are the best possible market/sector opportunities? |
| Aspirations | What do we care deeply about? What is our preferred future? |
| Results | How will we know we are succeeding? What measurable outcomes? |
| Use when the ToR calls for a forward-looking, strengths-based assessment rather than a deficit-focused diagnostic. |
McKinsey 7-S Framework
Use for: organisational effectiveness assessments, institutional capacity reviews, change readiness. Seven interdependent factors that must be aligned:
| Hard Elements | Soft Elements |
|---|---|
| Strategy — the plan | Shared Values — core beliefs and culture |
| Structure — how the org is organised | Style — leadership and management approach |
| Systems — processes and procedures | Staff — people and their capabilities |
| Skills — competencies and capabilities | |
| Misalignment between any elements explains organisational underperformance. Commonly used in institutional capacity assessments for government agencies and development organisations. |
Value Proposition Canvas
Use for: product/service design, market positioning, customer-centric strategy. Two components:
- Customer Profile: customer jobs (what they need to do), pains (frustrations, risks), gains (desired outcomes)
- Value Map: products/services offered, pain relievers (how you address pains), gain creators (how you deliver gains) Useful in private sector advisory, market development, and enterprise development assignments.
Diagnostic and Assessment Tools
Gap Analysis
Use for: any assignment that compares a current state to a desired state.
| Area | Current State | Desired State | Gap | Priority | Recommended Action |
|---|
Gap analysis is the backbone of most consulting methodology — phase 1 assesses current state, phase 2 defines desired state, the gap drives the recommendations.
Benchmarking
Use for: efficiency reviews, performance assessments, institutional comparisons.
Types of benchmarking to reference in proposals:
| Type | Compares Against | Example |
|---|---|---|
| Internal | Other units within the same organisation | Branch-to-branch performance comparison |
| Competitive | Direct peers or competitors | University-to-university administrative cost comparison |
| Functional | Best practice in a specific function, regardless of sector | Comparing procurement processes against ISO 20400 |
| International | Peer institutions in other countries | Comparing Uganda's revenue authority against Kenya's and Rwanda's |
Deloitte pattern: reference proprietary benchmark databases as a tool the firm brings — not just experience but comparative data.
Maturity Model Assessment
Use for: institutional capacity assessments, digital readiness, process maturity evaluations.
Standard five-level maturity scale:
| Level | Name | Description |
|---|---|---|
| 1 | Initial | Processes are ad hoc and reactive |
| 2 | Managed | Basic processes established, but not standardised |
| 3 | Defined | Processes documented and standardised across the organisation |
| 4 | Measured | Processes monitored with metrics and performance data |
| 5 | Optimised | Continuous improvement embedded, processes regularly refined |
Adapt the levels and naming to the specific domain (e.g., IT maturity, data governance maturity, gender mainstreaming maturity).
Root Cause Analysis
Use for: problem diagnostics, system failure assessments, process improvement.
Tools:
- 5 Whys: iterative questioning to reach the root cause
- Fishbone (Ishikawa) diagram: categorises causes under People, Process, Technology, Policy, Environment
- Pareto analysis: 80/20 rule — identify the 20% of causes producing 80% of the problems
Hypothesis-Driven Issue Tree
Use for: structured problem decomposition in diagnostic and advisory assignments.
- State the overriding question at the top
- Break into mutually exclusive, collectively exhaustive (MECE) sub-questions
- For each sub-question, identify the data needed and method to answer it
- Structure the methodology phases around the tree branches
- As evidence is gathered, eliminate branches and converge on root cause
This is the standard consulting problem decomposition approach used by McKinsey, BCG, and Bain. It signals intellectual rigour and structured thinking in methodology sections.
Business Event Analysis
Use for: requirements-heavy assignments, service redesign, process reviews, and system implementation planning.
Business events are the triggers that cause work to be performed. They are often a better starting point than interface screens or forms because they reveal:
- what starts the work
- who responds
- what outcome must be produced
- what information is needed
- what rules and exceptions must be handled
Use business events to organise discovery workshops and then convert the prioritised events into use cases, stories, process maps, or functional requirements.
For service design and support-heavy assignments, pair business events with journey stages and service blueprint layers so requirements show both the user's visible experience and the backstage work needed to fulfil it.
Context Diagram
Use for: clarifying scope before detailed analysis.
Show:
- the work or solution in the middle
- external actors, organisations, and systems around it
- major information or material flows across the boundary
Use the context diagram early to expose hidden interfaces, external dependencies, and stakeholders who can approve, block, or supply information.
Process and Operations Tools
Business Process Mapping
Use for: process improvement, system requirements gathering, efficiency reviews.
- Map current state (as-is) processes using flowcharts or swimlane diagrams
- Identify bottlenecks, redundancies, handoff failures, and manual workarounds
- Design future state (to-be) processes
- Quantify the improvement: time saved, steps eliminated, error rate reduced
RACI Matrix
Use for: governance design, organisational clarity, role definition.
| Activity | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| [Activity name] | [Who does it] | [Who owns it] | [Who is asked] | [Who is told] |
Essential in methodology sections for project governance and in team composition sections for role clarity.
Balanced Scorecard
Use for: performance management frameworks, strategic planning, M&E design.
| Perspective | Objective | Measure | Target |
|---|---|---|---|
| Financial | [e.g., reduce cost per transaction] | [Cost per transaction] | [20% reduction] |
| Customer/Stakeholder | [e.g., improve service satisfaction] | [Satisfaction score] | [80%+] |
| Internal Process | [e.g., reduce processing time] | [Average days to process] | [3 days] |
| Learning and Growth | [e.g., increase staff competence] | [% staff certified] | [90%] |
Financial and Economic Analysis Tools
Cost-Benefit Analysis (CBA)
Use for: options appraisal, investment justification, policy analysis, feasibility studies.
| Item | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | Total |
|---|---|---|---|---|---|---|
| Benefits | ||||||
| [Benefit 1] | ||||||
| Costs | ||||||
| [Cost 1] | ||||||
| Net benefit | ||||||
| NPV | ||||||
| BCR |
Include discount rate, Net Present Value (NPV), and Benefit-Cost Ratio (BCR). State the discount rate used and why.
Total Cost of Ownership (TCO)
Use for: ICT system evaluations, technology options appraisal, procurement advisory.
- Capital expenditure (hardware, software, implementation)
- Recurring costs (licences, hosting, maintenance, support staff)
- Hidden costs (training, change management, downtime, opportunity cost)
- Comparison across options over a five-year horizon
Return on Investment (ROI)
Use for: business case development, investment proposals, impact assessment.
ROI = (Net Benefits / Total Costs) × 100
Always present ROI alongside payback period — how many months until the investment pays for itself.
Decision-Making and Prioritisation Tools
Multi-Criteria Decision Analysis (MCDA)
Use for: options appraisal, site selection, technology selection, policy prioritisation.
| Criterion | Weight | Option A | Score | Option B | Score | Option C | Score |
|---|---|---|---|---|---|---|---|
| [Criterion 1] | [%] | [Rating] | [Weighted] | [Rating] | [Weighted] | [Rating] | [Weighted] |
Rules: criteria and weights agreed with the client before scoring. Transparent and auditable.
Prioritisation Matrix (Impact-Effort)
Use for: recommendation prioritisation, action planning, quick-win identification.
| Low Effort | High Effort | |
|---|---|---|
| High Impact | Quick wins — do first | Major projects — plan carefully |
| Low Impact | Fill-ins — do if time permits | Avoid — low return on investment |
Deloitte pattern: compile a "catalogue of opportunities", then prioritise using a criteria matrix before developing business cases for the top-priority items.
Options Appraisal
Use for: any assignment requiring a recommended course of action from multiple alternatives.
Standard structure:
- Define the options (including "do nothing" as a baseline)
- Define evaluation criteria (agreed with the client)
- Assess each option against the criteria
- Present the comparison with a recommended option and rationale
Reference Library
Detailed tool descriptions, templates, and synthesis from PMI Guide to Business Analysis (2017), Business Analysis for Practitioners (PMI, 2015), Business Analysis Methodology Book (Yayici, 2015), and Seven Steps to Mastering Business Analysis (Champagne, 2019).
| Reference File | Contents |
|---|---|
references/elicitation-techniques.md |
13 elicitation techniques with planning, question types, and selection guidance |
references/business-analysis-planning-and-governance.md |
Situation framing, governance, stakeholder engagement, BA work planning, transition planning, and solution evaluation |
references/requirements-analysis-models.md |
Scope, process, rule, data, and interface models with templates |
references/strategic-analysis-frameworks.md |
SWOT, PESTLE, gap analysis, benchmarking, maturity models, root cause analysis, feasibility, Power Curve, ETM Model, Bold Moves, Inside/Outside View, Competitive Systems Matrix, VRIST, Three Horizons, Theory of Constraints, Causal Loop Diagrams, Morphological Box, ICE Scoring, Ansoff's Growth Matrix, BCG Growth-Share, GE/McKinsey Matrix, Hedgehog Concept, Organisational Readiness Assessment |
references/prioritisation-and-decision-tools.md |
MoSCoW, weighted ranking, MCDA, Kano, impact-effort, options appraisal, CBA, financial methods |
references/requirements-documentation.md |
Requirement types, use case and user story formats, quality criteria, documentation principles |
references/traceability-and-change-control.md |
RTM, requirements lifecycle, change control process, impact analysis, governance |
references/solution-evaluation.md |
Acceptance criteria, UAT, go/no-go decisions, benefits realisation, lean KPIs |
Read the relevant reference file when a proposal requires detailed tool descriptions, templates, or structured frameworks beyond the summaries in this SKILL.md.
Data and Research Tools
Stakeholder Mapping (Power-Interest Grid)
Cross-references stakeholder-engagement/SKILL.md — included here as an analytical tool.
Survey Design and Sampling
Cross-references data-management/SKILL.md and monitoring-and-evaluation/SKILL.md.
Statistical Analysis
For quantitative assignments, reference:
- Descriptive statistics (mean, median, distribution)
- Regression analysis (for impact evaluation)
- Confidence intervals and margin of error (for survey-based findings)
- The analytics ladder: descriptive for what happened, diagnostic for why it happened,
predictive for what may happen, and prescriptive for what action is recommended under
constraints. Pair with
data-management/references/data-analytics-methodology-for-proposals.mdwhenever the methodology includes datasets, dashboards, AI analytics, forecasting, or decision-support tools.
Using Tools in Proposals
In the Conceptual Approach
Name the frameworks that will structure the analysis: "Our approach applies a PESTLE analysis to map the external environment, followed by a gap analysis to compare current state against regional best practice."
In the Phase Descriptions
Reference tools as activities: "During Phase 1, we will conduct a maturity model assessment of the client's data governance practices across the five dimensions of the Data Management Maturity Model."
In the Deliverables Table
Tools produce deliverables: "Current State Assessment Report (including SWOT analysis, process maps, and benchmarking results)."
In Requirements-Heavy Methodologies
Name the requirements process explicitly: "Our business analysis work will follow a structured path from situation assessment and context mapping, through stakeholder-led elicitation and business event analysis, to prioritised and testable requirements with full traceability to business objectives."
In Transition-Oriented Assignments
Show that analysis does not stop at documentation: "We will package requirements for design and implementation, define transition needs such as training and migration, and establish the acceptance criteria and benefits measures used for solution evaluation."
McKinsey Pattern
Name the tools as proprietary where possible: "Using our [Firm Name] Diagnostic Framework, we will assess..." — even a standard gap analysis becomes more credible when it has a name and a structured process.
Follow east-african-english standards throughout.