Techniques BABOK Guide v3, chapter 10

The 50 BABOK Techniques: Which One to Use When

In short The BABOK® Guide describes 50 techniques that analysts use across all six knowledge areas. This page groups them by the job they help you do, gives a one-line “use it when” for each, and links to a practical page for every technique.

Based on: IIBA, BABOK® Guide v3, chapter 10 “Techniques” and Appendix B (mapping of techniques to tasks); Watermark Learning, BABOK v3 Study Tables; B. Andersen, Business Process Improvement Toolbox (for Root Cause Analysis and Benchmarking).

On this page

How the catalog works#

Chapter 10 of the BABOK Guide lists the techniques alphabetically and numbers them 10.1 to 10.50. Each one is described in the same structure: purpose, description, elements, and usage considerations (strengths and limitations). An appendix maps which techniques support which of the 30 tasks in the knowledge areas. Most techniques serve several tasks; none belongs to only one knowledge area.

The alphabetical order is convenient for lookup but not for choosing. The groups below are by purpose. A few techniques could sit in more than one group; each appears once, where it is most often used.

How to pick a technique#

Ask these questions in order:

  1. What do you need right now? Information you do not have, a shared picture of something complex, a decision, an order of work, or evidence of results. That points you to a group below.
  2. Who and what is available? Busy executives suit short interviews; many dispersed users suit surveys; hands-on staff suit observation; good documentation suits document analysis.
  3. How formal must the result be? A predictive, contract-driven initiative needs specifications and signed-off models; an adaptive one often needs only stories, sketches and conversation.
  4. Who will read the output? Choose the notation your audience already understands. A model that only analysts can read does not create shared understanding.
  5. What would confirm it? Plan a second technique to cross-check important findings, for example interviews plus observation, or a process model plus a review.

Two habits help. Combine techniques rather than relying on one favorite. And start light: a quick sketch, list or conversation often shows whether a heavier technique is worth the effort.

Elicit and explore information#

Technique No. Use it when…
Interviews 10.25 you need depth from a few individuals, or the topic is sensitive.
Workshops 10.50 several stakeholders must build or agree on something together, fast.
Focus Groups 10.21 you want attitudes and reactions of a user or customer group to a product or idea.
Observation 10.31 what people say they do may differ from what they actually do.
Survey or Questionnaire 10.45 you need answers from many people, quickly, in comparable form.
Document Analysis 10.18 existing material (procedures, contracts, old specs) holds answers, or experts are unavailable.
Brainstorming 10.5 you need many ideas in a short time without early judgment.
Collaborative Games 10.10 a group needs to surface hidden assumptions or engage quieter participants.
Mind Mapping 10.29 you need to lay out a topic, its subtopics and links before structuring it.
Prototyping 10.36 stakeholders must see or try something before they can say what they need.

Understand stakeholders and the organization#

Technique No. Use it when…
Stakeholder List, Map, or Personas 10.43 you need to know who is affected, their influence, and their attitude to the change.
Organizational Modelling 10.32 you need to see units, reporting lines, roles and how teams interact.
Roles and Permissions Matrix 10.39 you must define who may do what in a solution.

Analyze strategy and problems#

Technique No. Use it when…
SWOT Analysis 10.46 you want a quick, shared summary of internal strengths and weaknesses and external opportunities and threats.
Benchmarking and Market Analysis 10.4 you want to learn from better performers, or understand customers and competitors.
Business Model Canvas 10.8 you need a one-page view of how the business creates, delivers and captures value.
Business Capability Analysis 10.6 you need to find which abilities of the business must improve to meet the strategy.
Root Cause Analysis 10.40 a problem keeps coming back and you need its underlying cause, not its symptom.

Model scope and processes#

Technique No. Use it when…
Scope Modelling 10.41 you need to show clearly what is in and out of the analysis or solution.
Functional Decomposition 10.22 something is too big to analyze or estimate as a whole.
Process Modelling 10.35 you need to show who does what, in what order, today or in the future.
Process Analysis 10.34 you need to find where a process wastes time, money or quality, and how to improve it.
Interface Analysis 10.24 the solution exchanges information with other systems, people or organizations.

Describe solution behavior and rules#

Technique No. Use it when…
Use Cases and Scenarios 10.47 you need step-by-step interaction between users and a system, including alternative paths.
User Stories 10.48 you work iteratively and want small, valuable slices of functionality to discuss and plan.
Sequence Diagrams 10.42 you need the exact order of messages between objects or systems in one scenario.
State Modelling 10.44 an entity (order, repair, account) moves through statuses with rules for each change.
Business Rules Analysis 10.9 policies and constraints drive behavior and must be stated, separated and kept consistent.
Decision Modelling 10.17 a repeatable business decision depends on several conditions and data inputs.

Model data and terminology#

Technique No. Use it when…
Glossary 10.23 people use the same words differently, or new terms appear.
Concept Modelling 10.11 you need to agree on business concepts and how they relate, independent of any system.
Data Dictionary 10.12 every data element needs one agreed definition, format and set of allowed values.
Data Modelling 10.15 you must describe entities, their attributes and relationships for a solution.
Data Flow Diagrams 10.13 you need to show where data comes from, how it is transformed and where it goes.
Data Mining 10.14 large data sets may reveal patterns, causes or predictions that people cannot see.

Define quality and check requirements#

Technique No. Use it when…
Acceptance and Evaluation Criteria 10.1 you must define when a solution is acceptable, or how to compare several options.
Non-Functional Requirements Analysis 10.30 performance, security, usability or other qualities matter as much as functions.
Reviews 10.37 a work product needs checking for errors, gaps or agreement before it moves on.

Analyze options and decide#

Technique No. Use it when…
Business Cases 10.7 a decision-maker needs a justified recommendation to start, continue or stop a change.
Financial Analysis 10.20 you must compare the costs and financial returns of options over time.
Decision Analysis 10.16 a complex choice among a few alternatives involves trade-offs and uncertainty.
Estimation 10.19 you need a forecast of cost, effort or duration, even a rough one.
Risk Analysis and Management 10.38 uncertainty could hurt the value of the change and needs a plan.
Vendor Assessment 10.49 part of the solution will come from an outside supplier.

Prioritize and manage the work#

Technique No. Use it when…
Prioritization 10.33 there is more to do than time or money allows.
Backlog Management 10.2 you need an ordered, changing list of work items that is refined just in time.
Item Tracking 10.26 issues, questions, risks and actions must not get lost.
Lessons Learned 10.27 a phase, iteration or project has ended and you want to keep what worked.

Measure performance#

Technique No. Use it when…
Metrics and KPIs 10.28 you need agreed measures of whether a solution or process is achieving its goals.
Balanced Scorecard 10.3 you want strategy turned into measures that go beyond finance.

Techniques by knowledge area#

Each knowledge-area page lists the techniques most used in its tasks:

Sources and further reading#

  • IIBA. A Guide to the Business Analysis Body of Knowledge (BABOK® Guide), version 3. International Institute of Business Analysis, 2015. Chapter 10 “Techniques” (10.1–10.50); Appendix B (mapping of techniques to tasks).
  • Watermark Learning. BABOK v3 Study Tables. 2016. (study aid for the BABOK Guide): summaries of all 50 techniques with strengths, limitations and usage.
  • B. Andersen. Business Process Improvement Toolbox. ASQ Quality Press, 1999: chapter 8 (root cause analysis) and section 10.7 (benchmarking), used for those two technique pages.