2.3 Discovery Elicitation: Contextual Inquiry, Shadowing & Journey Mapping

2.3 Discovery Elicitation: Contextual Inquiry, Shadowing & Journey Mapping

The quality of a Salesforce implementation is bounded by the quality of the discovery that precedes it. If a Business Analyst relies exclusively on conference-room interviews and self-reported stakeholder questionnaires, they will capture what users think they do—or what they wish they did.

To uncover the ground truth of enterprise operations, the Salesforce BA must master immersive discovery elicitation techniques: Contextual Inquiry, Job Shadowing, User Persona Development, and Customer Journey Mapping.

---

Discovery Elicitation Methodologies

In user research, there is a profound difference between attitudinal data (what people say) and behavioral data (what people actually do). Users often omit critical steps during interviews because repetitive actions become subconscious habit, or because they are reluctant to admit using unauthorized shortcuts.

Contextual Inquiry: Principles of Field Observation

Contextual Inquiry is an immersive discovery technique where the Business Analyst observes and interacts with users while they execute their daily work in their actual work environment (whether in a contact center, an office cubicle, or on a mobile device in the field).

Contextual Inquiry rests on four fundamental principles:

1. Context: Observation must occur where the work happens. Sitting next to a customer service agent wearing a headset reveals ambient noise, dual-monitor ergonomics, network latency, and physical desktop tools (e.g., sticky notes plastered on monitors) that never appear in a meeting room.
2. Partnership: The BA and user establish a collaborative master-apprentice relationship. The user is the master of their daily craft; the BA is the apprentice seeking to understand the workflow without judgment or evaluation.
3. Interpretation: The BA and user collaboratively interpret the meaning behind observed actions. Rather than guessing why a user switched to an external calculator, the BA checks their hypothesis with the user in real time.
4. Focus: The BA maintains a clear discovery boundary tied to the project scope, preventing the session from devolving into an unstructured venting session.

Job Shadowing: Passive vs. Active Modalities

Job shadowing is a core observation tool within contextual inquiry, categorized into two primary styles:

• Passive Shadowing ("Fly on the Wall"):
  • Mechanism: The BA sits alongside the user in complete silence, taking detailed, timestamped notes on every keystroke, mouse click, screen transition, telephone interaction, and interruption. The BA does not interrupt the workflow.
  • Primary Strength: Preserves authentic operational tempo and captures accurate baseline metrics (e.g., measuring exact task cycle duration, frequency of incoming call interruptions, and unprompted usage of cheat sheets).
  • Limitation: The BA cannot ask for clarification during complex mental calculations, requiring a debrief session afterward where user memory may have faded.
• Active Shadowing ("Interactive Inquiry"):
  • Mechanism: The BA observes the user but pauses them at logical break-points or immediately following an unexpected behavior to ask probing questions: "I noticed you just copied that account number into a separate Notepad file. Why did you do that?"
  • Primary Strength: Uncovers the real-time cognitive rationale behind idiosyncratic decisions and clarifies confusing business rules immediately.
  • Limitation: Artificially slows down task execution, invalidating cycle-time measurements and potentially frustrating the user during high-volume periods.

Elicitation Method Comparison

---

Developing Practical Salesforce User Personas

User personas in enterprise business analysis differ sharply from marketing personas. While marketing personas emphasize buyer demographics, income levels, and lifestyle aspirations, Salesforce User Personas represent operational archetypes that define how specific employee groups interact with technology to fulfill their job duties.

Essential Dimensions of a Salesforce Persona

An actionable Salesforce user persona must document:

1. Role Demographics & Environment: Job title, reporting line, physical work location (deskbound, remote, mobile in the field), hardware devices (laptop, tablet, iPhone), and monitor configuration.
2. Daily Responsibilities & Core Tasks: The primary recurring workflows the persona must complete to be considered successful.
3. Primary Frustrations & Pain Points: Operational bottlenecks, system latencies, repetitive data entry, and manual processes that hinder performance.
4. Technical Proficiency & Platform Sentiment: Level of software comfort, openness to automation, and historical sentiment toward Salesforce (champion vs. skeptic).
5. Salesforce Interaction Patterns: Frequency of logins (all day vs. weekly batch), key objects accessed (Leads, Cases, Custom Objects), licensing type, and required visibility/security clearance.

Worked Persona Examples

Persona Archetype 1: The Fast-Moving Field Sales Rep

• Name / Archetype: "Marcus, Senior Enterprise Account Executive"
• Environment: 70% mobile on road visiting commercial clients; accesses Salesforce via iPhone and iPad; frequently works in low-connectivity environments (airports, industrial client sites).
• Core Tasks: Preparing meeting briefs, updating deal stages post-client meeting, logging verbal customer agreements, requesting non-standard pricing approvals.
• Key Frustrations: Desktop-oriented Salesforce pages that take 12 seconds to load over 4G; forms requiring 35 mandatory fields to advance an opportunity stage; inability to quickly record voice notes.
• Salesforce Interaction: Needs quick-action buttons, optimized Salesforce Mobile App compact layouts, voice-to-text activity logging, and streamlined mobile approval notifications.

Persona Archetype 2: The High-Volume Service Agent

• Name / Archetype: "Elena, Tier-1 Customer Care Specialist"
• Environment: Deskbound contact center; dual-monitor workstation; wears a headset handling 45 to 60 customer phone calls and chat interactions daily.
• Core Tasks: Verifying customer identity, looking up asset warranty entitlements, logging support cases, searching the knowledge base, dispatching replacement parts.
• Key Frustrations: Having to navigate through 6 different browser tabs to locate an account's serial numbers; typing repetitive status update emails to customers manually; lack of telephony integration causing manual dialing.
• Salesforce Interaction: Requires Service Cloud Lightning Console with split-view navigation, Computer Telephony Integration (CTI), pre-built Quick Text templates, and Macro automations to close repetitive cases in one click.

---

End-to-End Customer Journey Mapping

A Customer Journey Map is a visual representation of the end-to-end experience a customer undergoes while interacting with an organization across time and touchpoints. While business process maps focus internally on system steps and handoffs, customer journey maps focus externally on the customer’s perspective, emotional state, and friction points.

The Six Lifecycle Phases

An enterprise customer journey typically spans six major phases:

1. Awareness: The customer discovers a need and engages with marketing content.
2. Lead Qualification & Evaluation: The customer interacts with sales representatives, attends demos, and evaluates capability.
3. Purchase & Contracting: The customer negotiates terms, receives quotes, and executes legal contracts.
4. Onboarding & Implementation: The customer transitions from sales to professional services or customer success to deploy the product.
5. Ongoing Service & Support: The customer utilizes the product, encounters issues, and logs support inquiries.
6. Retention, Upsell & Renewal: The customer evaluates value delivered, renews annual subscriptions, or expands service tiers.

Customer Journey Map Matrix

The following matrix illustrates a complete customer journey map for an enterprise B2B customer, identifying moments of friction and corresponding Salesforce enhancement opportunities:

---

Synthesizing Discovery into Executive Artifacts

Raw discovery observation notes, call recordings, and whiteboard sketches cannot be handed directly to executive sponsors or development teams. The Business Analyst must synthesize qualitative data into structured, authoritative deliverables.

[Raw Discovery Observations] 
       │
       ▼
[Thematic Affinity Mapping] ──► Groups pain points into categories (People, Process, Tech)
       │
       ▼
[Empathy & Journey Maps]   ──► Bridges user emotion to operational friction
       │
       ▼
[Root-Cause Problem Framing] ─► Quantifies cost of inaction and business impact
       │
       ▼
[Executive Discovery Readout] ─► C-suite presentation securing consensus and project funding

The Empathy Map

An Empathy Map captures the user's emotional and behavioral reality, divided into four quadrants:

• Says: Direct quotes captured during shadowing (e.g., "I have to keep 4 tabs open just to answer one phone call").
• Thinks: Unspoken beliefs and worries (e.g., "If I make a mistake on this discount, finance will reject my commission").
• Does: Physical actions observed (e.g., Rep copies tracking number from Salesforce into an external Excel spreadsheet).
• Feels: Emotional sentiment throughout the workday (e.g., Overwhelmed by administrative overhead, frustrated by slow load times).

The Executive Discovery Readout

The culmination of the customer discovery domain is the Executive Discovery Readout. This presentation communicates findings to steering committee leaders and executive sponsors. To maximize impact, the BA structures the readout around business value rather than technical configuration:

1. Executive Summary: Re-anchors the audience to the original strategic objectives and OKRs.
2. Current-State Reality: Presents synthesized journey maps and empathy data, highlighting the hidden costs of shadow IT and manual workarounds.
3. Quantified Business Cost of Inaction: Expresses operational bottlenecks in dollars, hours, and lost customer retention (e.g., "The current quoting process costs $420,000 annually in redundant sales operations labor and creates a 32% opportunity drop-off").
4. Recommended To-Be Vision on Salesforce: Illustrates how standard platform capabilities (Sales Cloud, Service Cloud, Flow) eliminate the identified bottlenecks.
5. Phased Roadmap & Governance Plan: Proposes an MVP Phase 1 scope with explicit boundaries, mitigating delivery risk while establishing immediate value realization.