The Business Analysis Core Concept Model (BACCM)
In short The BACCM is a set of six linked concepts: change, need, solution, stakeholder, value and context. Ask a question about each one and you get a fast check that your analysis has not skipped something important.
Based on: IIBA, BABOK® Guide v3, section 2.1; IIBA, Global Business Analysis Core Standard, ch. 1.
On this page
Key ideas#
Six concepts, equally important#
The BABOK® Guide introduced the BACCM in version 3 as a shared vocabulary for business analysis. It works regardless of industry, methodology, organization level or perspective. The six concepts, in plain words:
| Concept | What it means | Question to ask |
|---|---|---|
| Change | Moving from the current way of working to a new one, with the aim of performing better | What is changing? |
| Need | Something that is not working, or a chance to do better | What problem or opportunity are we responding to? |
| Solution | What you put in place to address the need: a system, a process, a policy, or a mix | What are we building, buying or changing? |
| Stakeholder | Anyone, person or group, who is affected by, involved in or able to influence the change | Who is affected, involved or has a say? |
| Value | What something is worth to a particular stakeholder: money, time, lower risk, or harder-to-measure benefits | What will each stakeholder gain or lose? |
| Context | The surroundings that shape the change or are shaped by it: culture, rules, systems, timing | What surrounds this? |
Each concept is defined by the others#
None of the six stands alone. A need only makes sense in relation to stakeholders who have it. Value only exists for a stakeholder. A solution meets a need within a context. A change is what moves you from the current situation to the solution. In the BABOK Guide each concept is described in terms of the other five, and no concept ranks above another.
The practical consequence: when one concept changes, re-check the other five. If a new stakeholder appears, value and needs may shift. If the context changes (a new regulation, a budget cut), the solution may no longer fit.
What the model is for#
The BABOK Guide lists several uses. It gives analysts a common language to describe their work. It helps them assess how the concepts relate. And it supports better analysis, because you look at the whole picture at any point in the work, not just at the requirements in front of you. Each of the six knowledge areas has its own short description of how the BACCM applies there.
How to apply it#
- Kick-off check. At the start of any task (a workshop, a requirements review, a business case), write the six questions on one page and answer each in a sentence or two.
- Mark the gaps. An empty or vague answer shows where to elicit next. A vague “value” usually means nobody has said who benefits and how.
- Test proposed solutions. When someone proposes a solution, trace it back: which need does it address, for which stakeholders, and what value does it create? A solution with no clear need behind it is a warning sign (see Why? What? How?).
- Re-run it when something shifts. A new stakeholder, a change in scope or a new constraint is a trigger to walk the six concepts again.
- Use it in reviews. In Strategy Analysis, it frames current and future state. In Solution Evaluation, it reminds you to measure value for stakeholders, not just whether features shipped.
Example#
The analyst at The Workshop, a fictional chain of 12 bike-repair workshops, fills in the BACCM before the first stakeholder meeting:
| Concept | The Workshop |
|---|---|
| Change | Move from phone-only booking to online booking with repair-status notifications; improve spare-parts ordering. |
| Need | Front-desk staff are overloaded with status calls; booking slots go unused; repairs wait for late parts. |
| Solution | A booking page, automatic status messages, a parts-reorder process (options still open). |
| Stakeholders | Owner (sponsor), workshop managers, mechanics, front-desk staff, customers, parts supplier, outside development team. |
| Value | Customers: no need to call. Front desk: time back. Owner: more booked hours. Mechanics: fewer jobs stalled by missing parts. |
| Context | Spring rush, mechanics rarely at a computer, paper job cards today, customer contact details are personal data. |
Two gaps stand out. Nobody has asked mechanics what value they would get, and “mechanics rarely at a computer” may make status updates the weak point of the whole solution. Both go on the elicitation plan.
Pitfalls#
- Starting from the solution. Filling in “solution” first and back-filling the rest produces a justification, not an analysis.
- Value for the sponsor only. Check value for every stakeholder group, including the ones who will do extra work.
- Ignoring context. Constraints like seasonality, regulations or existing systems often decide whether a solution works.
- Treating it as a process. The BACCM is not a sequence of steps. It is a lens you can apply at any point.
Sources and further reading#
- IIBA. A Guide to the Business Analysis Body of Knowledge (BABOK® Guide), version 3. International Institute of Business Analysis, 2015. Section 2.1 (the BACCM) and the “BACCM in context” notes in sections 3-8.
- IIBA. Global Business Analysis Core Standard. International Institute of Business Analysis. Ch. 1 (the same model in condensed form).