agentleFS
peterbamuhigirepeterbamuhigire/proposal-skills/skills/domain-delivery/business-analysis-tools/SKILL.md

business-analysis-tools

Skill11 starsChanged 16 days agoMITView on GitHub

Use when a proposal needs diagnostic, requirements, options-appraisal, process, or decision-support tools. Unlike consulting-frameworks, this skill selects and applies business-analysis techniques to a defined analytical question and deliverable.

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 17 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈17

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the assignment needs business-analysis tools, diagnostics, or decision-support methods.

    line 17
  2. Distinctive:

    Stop or block the workflow when a required input, permission, or acceptance basis is missing.

    line 32
  3. Distinctive:

    Use discovery questions where the brief is unclear on outcomes, users, data, workflows, support, or decision criteria.

    line 35
  4. Distinctive:

    Read the local references only where they materially improve the output.

    line 36
  5. Distinctive:

    Keep the selected tools specific to the assignment rather than listing frameworks for their own sake.

    line 42
  6. Distinctive:

    Read and search are required.

    line 65
  7. Distinctive:

    Read and search are required.

    line 66
  8. Distinctive:

    If client data or verification capability is unavailable or missing, return the narrowest qualified analysis plan, hypotheses, and evidence …

    line 69
  9. Distinctive:

    Use this four-part structure when the proposal must show disciplined analysis rather than isolated tools:

    line 103
  10. Distinctive:

    Use these patterns before jumping to requirements:

    line 147
  11. Distinctive:

    Add one row to the existing PESTLE table:

    line 184
  12. Distinctive:

    Always present TOWS as the "So what?" after SWOT — it converts analysis into strategy.

    line 214
  13. Distinctive:

    Use when the ToR calls for a forward-looking, strengths-based assessment rather than a deficit-focused diagnostic.

    line 224
  14. Distinctive:

    Use business events to organise discovery workshops and then convert the prioritised events into use cases, stories, process maps, or …

    line 313
  15. Distinctive:

    Use the context diagram early to expose hidden interfaces, external dependencies, and stakeholders who can approve, block, or supply …

    line 325
  16. Distinctive:

    Always present ROI alongside payback period — how many months until the investment pays for itself.

    line 390
  17. Very specific:

    Read the relevant reference file when a proposal requires detailed tool descriptions, templates, or structured frameworks beyond the …

    line 441
  18. Distinctive:

    Follow east-african-english standards throughout.

    line 486

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Business Analysis Tools

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

<!-- dual-compat-start -->

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

ArtefactSourceRequired?If absent
Assignment brief and analytical questionClient or proposal leadrequiredStop tool selection and state the unresolved question.
Decision criteria, evidence, and constraintsToR, client records, verified researchconditionalUse 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.

  1. Identify which analytical question the proposal actually needs to answer.
  2. Decide whether the assignment needs business value assessment, business analysis planning, solution refinement, or solution evaluation support.
  3. Use discovery questions where the brief is unclear on outcomes, users, data, workflows, support, or decision criteria.
  4. Read the local references only where they materially improve the output.
  5. Select the tools that fit the assignment and convert them into proposal-ready logic, not academic summary.
  6. 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

ArtefactConsumerAcceptance condition
Analysis method block or standalone analysis planEvaluator and delivery teamNames the question, tool, evidence, steps, output, and decision use.

Evidence Produced

EvidenceConsumerAcceptance condition
Tool-selection rationale and assumption registerTraceable tableEvery 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 needActionRisk avoided
Cause of a defined problemRoot-cause analysis or issue treeSymptom-level recommendations
Compare feasible choicesOptions appraisal or MCDAPredetermined selection
Describe operating gapsProcess map plus gap analysisAbstract 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.

<!-- dual-compat-end -->

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:

  1. Business value assessment — understand the situation, identify gaps, and define the high-level solution direction.
  2. Business analysis planning — define governance, stakeholder engagement, decision rights, and the analysis roadmap.
  3. Solution refinement — elicit, analyse, and package requirements or other solution information.
  4. 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.

PositiveNegative
InternalStrengthsWeaknesses
ExternalOpportunitiesThreats

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.

FactorDescriptionProposal Application
PoliticalGovernment policy, political stability, regulatory directionPublic sector reform, governance assignments
EconomicGrowth rates, inflation, exchange rates, fiscal environmentFinancial sector, economic development assignments
SocialDemographics, cultural factors, health, education levelsHealth, education, social protection assignments
TechnologicalDigital infrastructure, technology adoption, innovationICT, digital transformation assignments
LegalLegislation, regulatory frameworks, compliance requirementsRegulatory reform, legal framework assignments
EnvironmentalClimate, natural resources, environmental regulationsAgriculture, 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.

  1. Threat of new entrants
  2. Bargaining power of suppliers
  3. Bargaining power of buyers
  4. Threat of substitute products or services
  5. 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:

StrategyCombinationQuestion
SO (Maxi-Maxi)Strengths × OpportunitiesHow can we use strengths to maximise opportunities?
ST (Maxi-Mini)Strengths × ThreatsHow can we use strengths to minimise threats?
WO (Mini-Maxi)Weaknesses × OpportunitiesHow can we minimise weaknesses by exploiting opportunities?
WT (Mini-Mini)Weaknesses × ThreatsHow 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.

DimensionFocus
StrengthsWhat are we doing well? What are our greatest assets?
OpportunitiesWhat are the best possible market/sector opportunities?
AspirationsWhat do we care deeply about? What is our preferred future?
ResultsHow 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 ElementsSoft Elements
Strategy — the planShared Values — core beliefs and culture
Structure — how the org is organisedStyle — leadership and management approach
Systems — processes and proceduresStaff — 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.

AreaCurrent StateDesired StateGapPriorityRecommended 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:

TypeCompares AgainstExample
InternalOther units within the same organisationBranch-to-branch performance comparison
CompetitiveDirect peers or competitorsUniversity-to-university administrative cost comparison
FunctionalBest practice in a specific function, regardless of sectorComparing procurement processes against ISO 20400
InternationalPeer institutions in other countriesComparing 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:

LevelNameDescription
1InitialProcesses are ad hoc and reactive
2ManagedBasic processes established, but not standardised
3DefinedProcesses documented and standardised across the organisation
4MeasuredProcesses monitored with metrics and performance data
5OptimisedContinuous 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.

  1. State the overriding question at the top
  2. Break into mutually exclusive, collectively exhaustive (MECE) sub-questions
  3. For each sub-question, identify the data needed and method to answer it
  4. Structure the methodology phases around the tree branches
  5. 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.

ActivityResponsibleAccountableConsultedInformed
[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.

PerspectiveObjectiveMeasureTarget
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.

ItemYear 1Year 2Year 3Year 4Year 5Total
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.

CriterionWeightOption AScoreOption BScoreOption CScore
[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 EffortHigh Effort
High ImpactQuick wins — do firstMajor projects — plan carefully
Low ImpactFill-ins — do if time permitsAvoid — 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:

  1. Define the options (including "do nothing" as a baseline)
  2. Define evaluation criteria (agreed with the client)
  3. Assess each option against the criteria
  4. 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 FileContents
references/elicitation-techniques.md13 elicitation techniques with planning, question types, and selection guidance
references/business-analysis-planning-and-governance.mdSituation framing, governance, stakeholder engagement, BA work planning, transition planning, and solution evaluation
references/requirements-analysis-models.mdScope, process, rule, data, and interface models with templates
references/strategic-analysis-frameworks.mdSWOT, 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.mdMoSCoW, weighted ranking, MCDA, Kano, impact-effort, options appraisal, CBA, financial methods
references/requirements-documentation.mdRequirement types, use case and user story formats, quality criteria, documentation principles
references/traceability-and-change-control.mdRTM, requirements lifecycle, change control process, impact analysis, governance
references/solution-evaluation.mdAcceptance 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.md whenever 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.

Weighted Strategic-Factor Analysis

Read weighted strategic-factor analysis when a diagnostic must reduce the scan to fewer than ten weighted, rated, time-bound and justified strategic factors (external, internal and combined summaries), compare against competitors with an industry matrix, run the strategic audit as a four-workstream diagnostic, or write objectives, missions and control lines that pass explicit tests.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.