8.1 Elicitation Planning, Types & Stakeholder Preparation

8.1 Elicitation Planning, Types & Stakeholder Preparation

[!NOTE] PMI-PBA Examination Blueprint Alignment: Domain 3 (Analysis) represents the single largest content area on the PMI-PBA examination, accounting for 35% of all scored items (~61–62 questions). Within Domain 3, Task 1 serves as the operational engine for requirements discovery: "Elicit or identify requirements, using various techniques, in order to draw out requirements from stakeholders." Exam items frequently test your ability to select the optimal elicitation technique based on organizational dynamics, balance project constraints, uncover tacit knowledge, and structure rigorous pre-session stakeholder preparation.

---

The Strategic Imperative of Elicitation Planning

In requirements engineering, the term elicitation is chosen with deliberate semantic precision. Elicitation is derived from the Latin elicere, meaning "to draw forth" or "to bring out what is latent or hidden." It stands in stark opposition to the outdated concept of requirements gathering.

+-----------------------------------------------------------------------------------+
|              Requirements Gathering vs. Requirements Elicitation                  |
+-----------------------------------------------------------------------------------+
| PASSIVE GATHERING (Anti-Pattern)        | PROACTIVE ELICITATION (PMI-PBA Standard)|
| - Assumes requirements exist in read-   | - Recognizes requirements are latent,   |
|   made form in stakeholders' minds.     |   fragmented, unstated, or conflicting. |
| - Treats the BA as a passive scribe or  | - Positions the BA as an analytical     |
|   order taker taking dictation.         |   investigator, facilitator, and guide. |
| - Captures stated "wants" and surface-  | - Discovers underlying "needs", root    |
|   level solution preferences.           |   causes, constraints, and business rules.|
| - High risk of missing tacit knowledge  | - Employs multi-method triangulation to |
|   and unstated assumptions.             |   surface unspoken and unconscious rules.|
+-----------------------------------------------------------------------------------+

When business analysts merely "gather," they transcribe executive wish lists and symptoms. When business analysts "elicit," they apply structured analytical frameworks to unpack underlying problems, question operational assumptions, reconcile contradictory perspectives, and translate business realities into verifiable requirements. Systematic planning is essential: launching elicitation without a tailored plan results in stakeholder fatigue, incomplete scope discovery, uncontrolled rework, and budget overrun.

---

The Tripartite Classification of Elicitation Archetypes

According to The PMI Guide to Business Analysis and Business Analysis for Practitioners: A Practice Guide, elicitation techniques are categorized into three operational archetypes based on their discovery mechanism:

                          ┌─────────────────────────────────────┐
                          │     PMI Elicitation Archetypes      │
                          └──────────────────┬──────────────────┘
                                             │
         ┌───────────────────────────────────┼───────────────────────────────────┐
         ▼                                   ▼                                   ▼
┌──────────────────┐               ┌──────────────────┐                ┌──────────────────┐
│  COLLABORATIVE   │               │     RESEARCH     │                │   EXPERIENTIAL   │
│  Direct Human    │               │  Mining Records, │                │   & EXPERIMENTAL │
│   Interaction    │               │ Data, & Systems  │                │ Observing & Doing│
├──────────────────┤               ├──────────────────┤                ├──────────────────┤
│ • Interviews     │               │ • Document Anal. │                │ • Job Shadowing  │
│ • Focus Groups   │               │ • Interface Anal.│                │ • Contextual Inq.│
│ • JAD Workshops  │               │ • Reverse Eng.   │                │ • Prototyping    │
│ • Brainstorming  │               │ • Benchmarking   │                │ • User Journeys  │
└──────────────────┘               └──────────────────┘                └──────────────────┘

1. Collaborative Elicitation (Direct Human Interaction)

Collaborative techniques rely on direct, interactive engagement with stakeholders to explore ideas, negotiate priorities, and build consensus.

• Core Techniques: One-on-one interviews, focus groups, facilitated Joint Application Design (JAD) workshops, brainstorming, and Delphi panels.
• Primary Strengths: Rapid exploration of nuanced perspectives, real-time feedback, direct resolution of political friction, and immediate consensus generation.
• Primary Risks: Vulnerable to interpersonal cognitive biases, power dynamics, groupthink, dominant personalities, and scheduling bottlenecks.

2. Research Elicitation (Mining Records, Data, and Systems)

Research techniques examine historical records, organizational collateral, technical architectures, and competitive benchmarks without requiring live stakeholder collaboration.

• Core Techniques: Document analysis (SOPs, contracts, defect logs, regulatory statutes), interface analysis (APIs, schemas, batch pipelines), reverse engineering legacy source code, and market research/benchmarking.
• Primary Strengths: Establishes objective, factual baselines; identifies regulatory and contractual constraints; minimizes SME operational disruption.
• Primary Risks: Documents may be outdated, misleading, or poorly maintained; written policies often diverge significantly from actual operational practices.

3. Experiential and Experimental Elicitation (Observing and Doing)

Experiential techniques immerse the business analyst in the operational environment or provide interactive models to simulate future-state behaviors.

• Core Techniques: Passive job shadowing, active job shadowing, contextual inquiry, exploratory prototyping, mockups, and proof-of-concept demonstrations.
• Primary Strengths: Uncovers tacit knowledge that stakeholders cannot verbalize; reveals workarounds and ambient operational friction; validates user mental models early.
• Primary Risks: Time-consuming, resource-intensive, and susceptible to the Hawthorne Effect (operators modifying behavior when aware of being observed).

[!TIP] Triangulation on the PMI-PBA Exam: High-performing business analysts never rely on a single elicitation technique. The PMI-PBA standard advocates technique triangulation—validating requirements across multiple archetypes. For example, a BA reviews existing policy documents (Research), observes an underwriter processing live claims (Experiential), and then conducts a semi-structured interview (Collaborative) to resolve discrepancies between policy and practice.

---

Developing the Formal Elicitation Plan

An Elicitation Plan is a foundational subsidiary component of the Business Analysis Plan. It defines how requirements discovery will be structured, executed, controlled, and closed out across the initiative. Developing this plan requires the BA to synthesize five core operational dimensions:

+-----------------------------------------------------------------------------------+
|                     Core Dimensions of the Elicitation Plan                       |
+-----------------------------------------------------------------------------------+
| 1. Scope & Objective Definition                                                   |
|    - What business capabilities, user stories, or processes are being targeted?   |
|    - What specific analytical artifacts must this elicitation effort produce?     |
|                                                                                   |
| 2. Technique Selection & Sequencing                                               |
|    - Which combination of Collaborative, Research, and Experiential techniques?   |
|    - How are techniques sequenced to maximize efficiency and minimize SME fatigue?|
|                                                                                   |
| 3. Stakeholder Identification & Engagement Logistics                               |
|    - Which personas, organizational tiers, and SMEs must participate?             |
|    - What roles will they play (RACI: Responsible, Accountable, Consulted, Inform)?|
|                                                                                   |
| 4. Logistics, Tooling & Environment Configuration                                 |
|    - Physical venues, collaboration software (whiteboards, video conferencing).   |
|    - Recording permissions, translation services, non-disclosure agreements.      |
|                                                                                   |
| 5. Risk Assessment & Contingency Management                                      |
|    - SME unavailability, conflicting stakeholder agendas, scope volatility.      |
|    - Unavailability of legacy systems or outdated documentation dependencies.     |
+-----------------------------------------------------------------------------------+

Sequencing Logic in Elicitation

Sequencing elicitation activities correctly saves substantial organizational capital. A standard best-practice sequence follows a progressive funnel:

1. Foundational Research First: Conduct document and interface analysis to master business domain terminology, organizational policies, and legal frameworks before speaking with SMEs.
2. Observational Immersion Second: Execute job shadowing or contextual inquiry to observe operational workflows in their native setting, noting undocumented workarounds.
3. Broad Exploratory Collaboration Third: Administer surveys or run exploratory workshops to capture high-level requirements, identify variance across operating units, and chart process dependencies.
4. Targeted Deep Dives Fourth: Conduct semi-structured one-on-one interviews with key SMEs to resolve specific discrepancies and deep-dive into complex business logic.
5. Experiential Validation Fifth: Deploy wireframes, clickable prototypes, or user story maps in facilitated consensus sessions to confirm requirements accuracy.

---

Elicitation Technique Selection Framework

Selecting the appropriate elicitation technique is not arbitrary; it depends on stakeholder availability, political alignment, cultural dynamics, project complexity, and delivery methodology.

---

Stakeholder Readiness, Psychological Priming & Ground Rules

One of the most frequent causes of failed elicitation sessions is stakeholder unreadiness. Inviting participants into a workshop or interview without adequate psychological priming results in defensive posturing, anxiety, lack of preparation, and superficial engagement.

Psychological Priming Protocols

Business analysts must actively prepare stakeholders before engaging in elicitation:

• Demystify the Purpose: Stakeholders often perceive elicitation as an operational audit designed to downsize staff or expose inefficiencies. The BA must explicitly frame the initiative around eliminating operational friction, empowering workers, and aligning systems with strategic goals.
• Distribute Pre-Session Briefing Dossiers: Send briefing materials 3 to 5 business days prior to the session. The dossier must contain the meeting objective, a focused agenda with time allocations, the specific business questions to be explored, relevant background metrics, and explicit expectations for what the participant should bring.
• Secure Executive Sponsorship Aircover: Ensure operational managers have formally authorized the SME's time away from daily duties. If an SME is worried about accumulating unprocessed operational backlog during a four-hour workshop, their mental engagement will be severely impaired.

Establishing Operating Ground Rules

At the onset of any collaborative elicitation event, the BA must establish and gain explicit consensus on non-negotiable ground rules:

1. Focus on Business Problems, Not Solutions: Forbid premature discussions of specific vendors, software platforms, or coding preferences until functional needs are fully bounded.
2. Equal Voice and Psychological Safety: Hierarchical job titles are neutralized inside the elicitation room. Every participant's operational reality carries valid analytical weight.
3. Active Listening and Disagreement Without Disrespect: Disagreements must focus on process flows, data requirements, and operational rules, never on personalities.
4. The Primacy of the "Parking Lot": Tangential, out-of-scope, or intractable debates are logged in an overt Parking Lot for subsequent triage, preventing agenda derailment.

---

Surfacing Tacit Knowledge and Unconscious Competence

One of the greatest analytical challenges tested on the PMI-PBA examination is uncovering tacit knowledge—the intuitive, uncodified knowledge that stakeholders possess but cannot easily express.

                                [ EXPLICIT KNOWLEDGE ]
                      Codified, written in SOPs, easily verbalized.
                     "The manual says to approve claims under $500."
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (Waterline)
                                 [ TACIT KNOWLEDGE ]
                    Intuitive, lived experience, unwritten heuristics,
                             unconscious cognitive shortcuts.
             "Unless the customer's phone area code doesn't match their billing
               address, in which case I always run a manual fraud check first."

The Four Stages of Competence Framework

Psychologist Noel Burch's hierarchy illuminates why veteran SMEs struggle during standard interviews:

1. Unconscious Incompetence: The individual does not understand or know how to do something and does not recognize the deficit.
2. Conscious Incompetence: The individual recognizes the deficit and the value of acquiring the skill.
3. Conscious Competence: The individual can perform the skill, but execution requires heavy conscious thought and concentration.
4. Unconscious Competence: The individual has performed the skill so often that it becomes "second nature." They execute complex heuristics, risk evaluations, and decision trees automatically without conscious cognitive awareness.

Veteran subject matter experts operate predominantly in Unconscious Competence. When asked in an interview, "How do you adjudicate a high-risk mortgage application?" they frequently reply, "I just look at it and know if it feels right."

BA Tactics for Uncovering Tacit Knowledge

A business analyst cannot accept intuitive dismissal. To extract the underlying business rules governing unconscious competence, practitioners employ four structured tactics:

• Critical Incident Walkthroughs: Ask the SME to reconstruct the most bizarre, extreme, or catastrophic transactions they encountered in the past calendar year. Edge cases force the brain out of automated autopilot into conscious cognitive recall.
• Contradiction Analysis: Compare observed behavior during job shadowing against written SOPs. When a discrepancy occurs, ask: "I noticed you checked three external registry screens before clicking approve, but the SOP doesn't mention that step. What risk were you evaluating?"
• Role Reversal Simulation: Have the SME instruct the business analyst step-by-step as the BA operates the software. When the BA makes a deliberate mistake, the SME will immediately intervene, vocalizing the latent rule: "Stop! You can't process that transaction before confirming the customer's tax exemption status."
• Artifact Archaeology: Examine physical artifacts in the SME's workspace—sticky notes on monitors, customized desktop spreadsheets, desktop cheat sheets, and printed manuals with handwritten annotations. These artifacts almost always represent uncodified operational requirements and system workarounds.