3.2 Planning & Facilitating Discovery Workshops and JAD Sessions

3.2 Planning & Facilitating Discovery Workshops and JAD Sessions

Exam Focus: Discovery workshops and Joint Application Development (JAD) sessions serve as the primary engine for requirements elicitation and cross-functional alignment in Salesforce projects. The Salesforce Certified Business Analyst must know how to construct structured agendas, deploy design thinking frameworks (silent brainstorming, affinity grouping, Crazy Eights, dot voting), manage challenging group dynamics, enforce the "Parking Lot" technique, and synthesize complex workshop data into actionable backlog artifacts within 24 to 48 hours.

Workshop Design & Joint Application Development (JAD) Foundations

Joint Application Development (JAD) is a structured collaborative methodology that brings together business subject matter experts (SMEs), executive decision-makers, and technical solution teams to accelerate requirements definition and system design. Rather than conducting weeks of isolated one-on-one interviews that result in conflicting departmental wish lists, a well-facilitated JAD workshop achieves real-time consensus, validates assumptions, and co-creates solution models.

The Five Pillars of Discovery Workshop Preparation

Executing an impactful discovery workshop requires exhaustive preparation. The actual workshop session represents only twenty percent of the overall effort; eighty percent occurs in the pre-workshop planning and post-workshop synthesis phases.

1. The Workshop Charter: Before booking meeting rooms or virtual collaboration boards, the BA must draft a clear workshop charter. This document outlines:

   • Business Purpose: Why are we convening? (e.g., "Streamline global lead-to-opportunity handoffs across EMEA and AMER sales teams.")
   • Scope Boundaries: What business domains are in scope, and explicitly what is out of scope? (e.g., "In Scope: Lead qualification, routing, duplicate detection. Out of Scope: CPQ quoting, ERP billing integration.")
   • Success Criteria: Measurable outputs required by session adjournment (e.g., agreed future-state Level 2 process flow, prioritized list of twenty pain points, signed-off functional scope document).

2. Participant Curation and Role Definition: Workshops fail when rooms are either under-populated (missing critical operational knowledge) or bloated (paralyzed by thirty passive observers). The ideal workshop cohort ranges from six to twelve active participants.

   • Facilitator (Salesforce BA): Manages the timebox, enforces ground rules, guides design thinking exercises, remains neutral, and ensures every voice is heard.
   • Scribe / Co-Facilitator: Captures verbatim quotes, logs action items, and records Parking Lot items without breaking the lead facilitator's conversational momentum.
   • Business Process Owner: Holds operational decision authority to approve workflows and arbitrate business rules.
   • Subject Matter Experts (SMEs): Frontline power users who execute the current process and understand unwritten edge cases.
   • Solution / Technical Architect: Assesses technical feasibility against Salesforce platform capabilities, Governor limits, and integration patterns in real time.

3. Pre-Work and Participant Homework: Never convene a discovery session to gather baseline facts that could have been collected asynchronously. Three to five days prior to the session, distribute a pre-work packet containing:

   • The workshop charter and agenda.
   • Current-state process documentation or existing high-level flowcharts.
   • Targeted discovery surveys (e.g., "What are the top three bottlenecks in your daily case resolution workflow?").
   • Explicit instructions on what participants must bring (e.g., sample spreadsheets, policy handbooks, customer escalation logs).

4. Timeboxed Agenda Engineering: Agendas must balance divergent thinking (expanding perspectives, generating ideas, unpacking pain points) with convergent thinking (clustering, prioritizing, making firm decisions). Long, unstructured sessions induce cognitive fatigue. Structure the day in ninety-minute thematic blocks separated by deliberate breaks.

---

Facilitation Methodologies & Design Thinking Toolkit

A Salesforce Business Analyst must possess a rich repertoire of interactive facilitation frameworks to stimulate creativity and drive convergence.

       DIVERGENT PHASE                    EMERGENT PHASE                   CONVERGENT PHASE
 (Generate Many Possibilities)         (Explore & Connect)            (Prioritize & Decide)
┌──────────────────────────────┐     ┌──────────────────────┐     ┌────────────────────────────┐
│ • Silent Brainstorming       │────►│ • Affinity Grouping  │────►│ • Dot Voting               │
│ • "How Might We" Statements  │     │ • Theme Clustering   │     │ • 2x2 Impact/Effort Matrix │
│ • Crazy Eights Sketching     │     │ • Root Cause Tree    │     │ • MoSCoW MVP Scoping       │
└──────────────────────────────┘     └──────────────────────┘     └────────────────────────────┘

1. Silent Brainstorming and Affinity Mapping

Traditional open brainstorming often falls prey to groupthink and the HIPPO effect (Highest Paid Person's Opinion), where junior staff mirror the viewpoints of senior executives.

• Procedure: The BA presents a prompt (e.g., "What are the primary obstacles preventing you from converting leads within 24 hours?"). Participants spend five to seven minutes writing one idea per digital or physical sticky note in total silence.
• Affinity Mapping: Once all notes are posted, participants and the facilitator collaborate silently to group related notes into natural operational clusters (e.g., "Data Quality Issues," "Duplicate Records," "Approval Latency," "Lack of Mobile Access"). The group then names each thematic cluster.

2. "How Might We" (HMW) Problem Framing

Before jumping into software features, the BA reframes raw complaints into design opportunities using the "How Might We" format.

• Raw Complaint: "Sales reps waste two hours copying data from Salesforce into pricing spreadsheets to get manager discounts."
• Reframed HMW Statement: "How might we empower sales reps to calculate and submit discounted pricing directly within Salesforce in under three minutes?" This framing prevents premature technical solutioning (e.g., "build an Apex trigger") and focuses the team on user outcome and efficiency.

3. Crazy Eights Rapid Sketching

When defining user experiences (such as a Salesforce Lightning Service Console or an Experience Cloud portal), verbal descriptions create misunderstandings.

• Procedure: Each participant folds a blank sheet of paper into eight rectangles (or uses an eight-frame digital canvas). The BA sets a timer for eight minutes—giving participants exactly sixty seconds per frame to sketch eight distinct visual ideas, wireframes, or workflow steps.
• Outcome: Rapid sketching bypasses self-censorship, levels the playing field between designers and business users, and produces innovative layout ideas that would never emerge through conversation alone.

4. Dot Voting (Cumulative Prioritization)

Once dozens of features or pain points are clustered, the facilitator must lead the group to consensus without lengthy political debates.

• Procedure: Each participant receives a constrained allocation of voting tokens (e.g., three to five digital or physical colored dots). Participants place their dots on the clusters or feature ideas they consider most critical to the project's core objectives. They can distribute dots across multiple items or place all dots on a single high-priority item ("poker-style").
• Analysis: The facilitator tallies the votes to instantly reveal the group's collective priorities, which then feed directly into the MVP backlog.

---

Orchestrating Group Dynamics & In-Flight Conflict Management

Managing the human dynamic in a discovery workshop requires emotional intelligence, vigilance, and structured interventions.

Setting Ground Rules Upfront

At the start of every session, establish and gain verbal consensus on foundational operating norms:

• "Be Present and Focused:" Laptops and phones remain closed unless directly utilized for session exercises.
• "One Conversation at a Time:" No sidebar whispering or simultaneous cross-talk.
• "Focus on the Process, Not the Person:" Critique operational bottlenecks, not individual capabilities.
• "Disagree and Commit:" Robust, respectful debate is expected during divergent ideation; once a decision is finalized, all participants align behind execution.
• "All Voices Carry Equal Weight:" Frontline daily users possess domain insights as critical as executive strategy.

Mitigating Dominant Personalities

Senior leaders or aggressive participants often dominate discussions, drowning out crucial frontline feedback.

• Facilitator Tactic: Intervene politely but firmly. Validate the dominant speaker's contribution, then immediately pivot the microphone to another participant: "Thank you for highlighting that corporate governance objective, David. I want to pause there and hear directly from Maria in tier-1 support—how would that proposed mandatory approval gate impact your team's live call resolution time?"
• Utilize structured round-robin elicitation and silent writing exercises to completely neutralize vocal dominance.

Drawing Out Quiet Subject Matter Experts (SMEs)

Quiet, introverted frontline participants often understand the day-to-day workflow better than anyone else in the company—including the manual cheats, workarounds, and unwritten system bypasses.

• Facilitator Tactic: Never put quiet SMEs on the spot with aggressive or open-ended questions like "Tell us what you think about the entire architecture." Instead, ask narrow, experience-based questions that acknowledge their expertise: "Elena, when a complex warranty claim comes in with an expired service contract, what specific screen do you open first to look up the customer history?"

The "Parking Lot" Technique

Workshops frequently derail when passionate participants enter deep technical debates over out-of-scope or edge-case topics.

• Definition: The Parking Lot is a prominent, designated space on the whiteboard or digital canvas reserved for capturing off-topic, unresolved, or tangential discussions.
• Operational Protocol: When an off-topic debate begins consuming time, the facilitator intervenes: "This is a vital topic regarding enterprise billing reconciliation, but it falls outside our Sales Cloud lead qualification charter. Let's record it verbatim on the Parking Lot."
• The Golden Rule of Parking Lots: A parking lot must never become a "black hole" where ideas go to die. Every parked item must have an assigned owner, a documented follow-up action, and a target resolution date established before session adjournment.

---

Synthesis, Readouts, and 24-48 Hour Post-Workshop Execution

The true test of a discovery workshop is what happens after the physical or virtual room empties. Workshop momentum experiences exponential decay; if participants do not see structured deliverables within 24 to 48 hours, alignment dissolves, memories blur, and political backtracking begins.

Post-Workshop Deliverables Checklist

1. Executive Workshop Readout (The 1-Page Summary):

   • High-level business objectives reviewed.
   • Core consensus decisions reached (e.g., "All parties agreed to eliminate manual tier-2 approval steps for quotes under $50,000").
   • Identified business risks and technical dependencies.
   • Designed for C-suite and executive sponsors who cannot read granular workshop stickies.

2. Refined Backlog & Process Artifacts:

   • Conversion of whiteboard flows into standardized Level 2 / Level 3 process diagrams (using BPMN standards).
   • Translation of prioritized sticky clusters into initial Epic and User Story shells with preliminary Acceptance Criteria.

3. Formal Action Item & Decision Register:

   • Exhaustive review of all Parking Lot items.
   • Tabulation of every action item with: (1) Detailed task description, (2) Single assigned owner, (3) Expected completion deadline.

4. The 48-Hour Feedback Window:

   • Circulate the synthesis packet to all attendees with a clear call to action: "Please review these documented decisions and action items. If any representation does not align with your understanding from yesterday's session, submit edits by Thursday at 5:00 PM. Silence constitutes concurrence."