Strategy, Risk, and Investigation Techniques
Key Takeaways
- Root cause analysis distinguishes a problem's underlying cause from its visible symptoms, often using the 5 Whys or a fishbone diagram.
- Risk analysis and management assesses probability and impact of uncertainty and defines responses such as avoid, mitigate, transfer, or accept.
- SWOT analysis organizes internal strengths and weaknesses and external opportunities and threats to support strategic decision-making.
- Lessons learned compiles what worked and what did not from an initiative to inform future work.
- Root cause analysis looks backward at a known problem, while risk analysis and management looks forward at potential future uncertainty.
Investigating Problems and Managing Uncertainty
This section covers four BABOK techniques used to investigate problems, assess uncertainty, evaluate strategic position, and capture organizational knowledge over time. They are used throughout an initiative -- before a solution is chosen, while options are being evaluated, and after work concludes -- rather than being tied to one lifecycle stage.
The Four Techniques at a Glance
| Technique | Purpose | When to Use |
|---|---|---|
| Root Cause Analysis | Determine the underlying cause of a problem rather than treating its symptoms | Investigating a problem before selecting a solution, to make sure the true cause is addressed |
| Risk Analysis and Management | Identify, assess, and plan responses to areas of uncertainty that could affect outcomes | Throughout BA work, especially when evaluating options or solutions, whenever uncertainty could affect value |
| SWOT Analysis | Evaluate internal Strengths and Weaknesses and external Opportunities and Threats to support strategic decisions | Strategy analysis or a high-level evaluation of a current state, proposed change, or investment |
| Lessons Learned | Capture what worked and what did not from an initiative to improve future performance | At project milestones or closure, to feed continuous improvement and organizational process assets |
Root Cause Analysis
Root cause analysis distinguishes between the symptoms of a problem and its true underlying cause, using techniques such as the "5 Whys" or a fishbone (Ishikawa) diagram to trace effects back to their origin. Its purpose is to prevent the BA and stakeholders from designing a solution that only addresses a visible symptom while the actual cause continues to generate the problem. A BA applies root cause analysis early in problem investigation, before a solution is proposed, whenever a described issue looks like it could have several possible underlying drivers. Common supporting tools include the fishbone diagram, which organizes potential causes into categories such as people, process, technology, and environment, and Pareto analysis, which highlights the small number of causes responsible for the majority of a problem's impact.
Risk Analysis and Management
Risk analysis and management identifies areas of uncertainty that could positively or negatively affect a solution, a business analysis effort, or an organization's ability to realize value, and assesses each in terms of probability and impact. Once assessed, risks are addressed through defined responses -- avoid, mitigate, transfer, or accept. Unlike root cause analysis, which looks backward at a known problem, risk analysis looks forward at what could go wrong. It is used continuously throughout business analysis work, and especially when evaluating solution options, since different options usually carry different risk profiles. Risk analysis typically produces a risk register that records each identified risk, its likelihood and impact rating, and the assigned response owner, giving the team a living reference throughout the initiative.
SWOT Analysis
SWOT analysis organizes information into four categories -- Strengths and Weaknesses, which are internal to the organization, and Opportunities and Threats, which are external to it -- to build a structured, high-level picture of an organization's or initiative's strategic position. It is a lightweight technique, often used in a workshop setting, that helps stakeholders align on context before deeper analysis begins. A BA reaches for SWOT analysis during strategy analysis, or when a sponsor needs a quick, broad understanding of the current state or of a proposed change or investment before committing resources to detailed work. Because SWOT analysis produces only a high-level snapshot, it is often paired with more detailed techniques, such as risk analysis or business capability analysis, once the broad strategic picture has identified where deeper investigation is warranted.
Lessons Learned
The lessons learned technique compiles knowledge gained during an initiative -- what went well, what did not, and what should be done differently -- into a record that can inform future work. It is typically conducted through a facilitated retrospective session and captured as documented organizational process assets. Unlike the other three techniques in this section, lessons learned looks backward at completed or concluding work rather than forward at a live problem or decision. A BA applies it at project milestones or at closure, ensuring the organization's collective experience compounds across initiatives instead of being lost when the current team disbands. Effective lessons learned sessions capture not only what happened but why, so recommendations can be generalized to future initiatives rather than treated as one-off observations.
Connecting the Four on the Exam
These four techniques map cleanly onto a simple timeline test the exam likes to use in situational stems:
- A scenario where a problem keeps recurring despite an earlier fix points to root cause analysis, since the earlier fix likely addressed a symptom.
- A scenario asking what could threaten this solution's success, or whether to proceed given uncertainty, points to risk analysis and management.
- A scenario asking for a quick picture of the organization's position before committing to an investment points to SWOT analysis.
- A scenario about capturing what the team learned as a project closes points to lessons learned.
Recognizing whether a scenario is diagnosing a problem, weighing an uncertain future, framing a strategic decision, or closing out a completed effort is usually sufficient to identify the right technique, independent of memorizing a BABOK section number.
A customer complaint-handling process has been 'fixed' three times, yet the same complaints keep recurring. Which technique should the BA use to identify why the problem keeps returning?
Before selecting between two solution options, the BA wants to formally assess the probability and impact of factors that could derail each option and plan appropriate responses. Which technique should the BA apply?