AboutMethodology

    Consulting Methodology

    Every engagement follows internationally recognised frameworks — BABOK® v3, BPMN 2.0, and structured AI assessment protocols. No proprietary black boxes. No methodology theatre. Proven frameworks applied with practitioner judgment.

    Requirements Engineering Framework

    All requirements work follows the IIBA BABOK® v3 knowledge areas — providing a consistent, internationally recognised structure for elicitation, analysis, and documentation.

    Process Steps

    1. 1Discovery workshop: structured stakeholder interviews and business context mapping
    2. 2Requirements elicitation: interviews, observation, facilitated workshops, and document analysis
    3. 3Requirements analysis: decomposition, gap analysis, process modelling (BPMN)
    4. 4Requirements documentation: BRD, FRS, or user story map depending on delivery methodology
    5. 5Requirements validation: stakeholder review, sign-off, and traceability matrix

    Frameworks Used

    • BABOK® v3
    • BPMN 2.0
    • IEEE 830 (SRS)
    • Gherkin/BDD

    Deliverables

    • Business Requirements Document (BRD)
    • Functional Requirements Specification (FRS)
    • Process maps (swimlane, BPMN, value stream)
    • User story map with acceptance criteria
    • Requirements traceability matrix

    AI Strategy Framework

    AI strategy engagements follow a structured 4-phase protocol that separates problem diagnosis from solution selection — preventing organisations from buying AI tools before they understand the problem.

    Process Steps

    1. 1Phase 1 — Readiness assessment: data quality audit, process maturity review, team capability evaluation, leadership alignment
    2. 2Phase 2 — Opportunity mapping: stakeholder interviews, workflow analysis, AI use case generation across 3 time horizons
    3. 3Phase 3 — Prioritisation: RICE scoring (Reach, Impact, Confidence, Effort) against data availability and implementation risk
    4. 4Phase 4 — Roadmap: phased implementation plan (0–3 months, 3–9 months, 9–18 months) with governance framework

    Frameworks Used

    • RICE Scoring
    • MoSCoW Prioritisation
    • AI Readiness Scorecard (5 dimensions)
    • KANO Model

    Deliverables

    • AI Readiness Scorecard (0–5 scale, 5 dimensions)
    • AI Opportunity Map (5–8 prioritised use cases)
    • Vendor evaluation and build-vs-buy analysis
    • Phased implementation roadmap
    • AI Governance Framework

    Process Analysis and Improvement

    Current-state process mapping is the foundation of all improvement work. You cannot fix what you have not documented — and most organisations underestimate how much ambiguity exists in their current processes.

    Process Steps

    1. 1Current-state mapping: BPMN 2.0 swimlane diagrams capturing every actor, system, and decision point
    2. 2Pain point analysis: waste identification using Lean principles (waiting, rework, handoff delays)
    3. 3Root cause analysis: 5 Whys, fishbone diagram, and data analysis
    4. 4Future-state design: optimised process with automation opportunities identified
    5. 5Implementation requirements: detailed specifications for system changes required

    Frameworks Used

    • BPMN 2.0
    • Lean / Value Stream Mapping
    • Six Sigma DMAIC
    • 5 Whys Root Cause Analysis

    Deliverables

    • Current-state BPMN process map
    • Future-state BPMN process map
    • Gap analysis with improvement recommendations
    • Automation opportunity assessment
    • Implementation requirements for process changes

    Stakeholder Management Protocol

    Requirements quality is directly proportional to stakeholder engagement quality. The protocol ensures all voices are heard — and conflicting priorities are resolved with evidence, not politics.

    Process Steps

    1. 1Stakeholder identification: RACI matrix mapping all decision-makers, subject matter experts, and end users
    2. 2Interview protocol: structured discovery questions tailored to role and context
    3. 3Workshop facilitation: consensus-building techniques for conflicting requirements
    4. 4Communication plan: cadence, format, and escalation path agreed upfront
    5. 5Change management: impact assessment and adoption plan for system/process changes

    Frameworks Used

    • RACI Matrix
    • Stakeholder Power/Interest Grid
    • MoSCoW Consensus
    • Change Impact Assessment

    Deliverables

    • Stakeholder register with roles and interests
    • Discovery interview synthesis
    • Requirements workshop outputs
    • Communication and escalation plan

    Methodology Questions

    What is BABOK® and why does it matter?

    BABOK® (Business Analysis Body of Knowledge) is the international standard for business analysis practice, published by IIBA. It defines the knowledge areas, tasks, and techniques that constitute professional-grade business analysis. The CBAP® certification validates mastery of BABOK® — meaning every engagement follows internationally recognised standards, not ad-hoc approaches.

    How is the RICE prioritisation framework applied to AI use cases?

    RICE scores AI use cases across four dimensions: Reach (how many users or processes are affected), Impact (business value when the use case succeeds), Confidence (quality of evidence for the estimate), and Effort (implementation cost in person-months). Dividing Reach × Impact × Confidence by Effort gives a comparable priority score across all candidates — removing politics from the decision.

    Do you work in Agile or Waterfall projects?

    Both. The BABOK® framework explicitly covers adaptive (Agile) and plan-driven (Waterfall) delivery. In Agile teams, requirements are expressed as user stories with BDD acceptance criteria. In Waterfall contexts, formal BRDs and FRS documents with stakeholder sign-off are produced. Hybrid approaches — formal discovery with iterative delivery — are common in healthcare and fintech.

    What does BPMN stand for and why do you use it?

    BPMN stands for Business Process Model and Notation — the international standard for process modelling. BPMN diagrams are unambiguous, tool-agnostic, and readable by both business and technical stakeholders. Unlike informal flowcharts, BPMN distinguishes between tasks, events, gateways, and data objects — preventing the kind of interpretation gaps that cause rework.

    Apply these frameworks

    See the methodology in action

    Book a free discovery call to discuss how these frameworks apply to your specific project.

    Also on this site