Persona And Journey Mapping (Salesforce-Anchored)
This skill activates when an admin, BA, or architect needs to define who actually
uses the org and how, in a way that drives concrete Salesforce configuration
decisions rather than abstract UX deliverables. Every persona must anchor to org
artifacts the platform exposes — Permission Set Groups, record types, list views,
dashboards, automation — and every journey must walk a real task with measured
friction so the output feeds downstream auditing and design agents.
Before Starting
Gather this context before producing any persona artifact:
- The list of in-scope roles and their headcount. Roles without users are noise.
- The target Permission Set Group(s) for each role — if the PSG does not yet
exist, flag it; do not invent one. Personas without a PSG anchor become opinion
pieces.
- The primary record types each role touches and the list views they live
in. These are observable, not invented.
- Mobile vs desktop usage, ideally measured (Lightning Usage app, login
history, EventLogFile UriEvent / LightningPerformance) — never assumed.
- Dashboards the role consumes daily/weekly. If a dashboard is named in a
persona but does not exist in the org, it is a hallucination — flag it.
- The automation that fires for the role (record-triggered Flow, validation
rules, assignment rules, approval processes, Agentforce topics) — captured by
metadata, not memory.
Core Concepts
Persona = User × Org Artifacts
A Salesforce-anchored persona is the join between a user population and the
concrete artifacts the platform uses to constrain and serve them. The five
anchors are non-negotiable: PSG (what they can do), record types (what they
work on), list views (what they see), dashboards (how they measure success),
automation (what fires for them). A persona missing any anchor cannot drive a
configuration decision.
Mobile vs Desktop Posture
Salesforce mobile (the Salesforce app) and Lightning Experience desktop are
different products with different UX rules: mobile favors Compact Layouts,
mobile-only Quick Actions, and brief related-list summaries; desktop favors
Dynamic Forms, multi-tab record pages, and dense related lists. The
mobile_pct / desktop_pct split — measured, not guessed — is what tells you
which surface to optimize. A 70% mobile field rep persona and a 95% desktop
SDR persona need very different record pages even on the same object.
Journey Map vs Process Flow
A journey map is persona-first: one persona, one task, every step
they take, with friction tagged. A process flow is system-first: the
sequence of system events regardless of who triggers them. Journey maps drive
UX decisions (Dynamic Forms, Quick Actions, page redesign, path); process
flows drive automation decisions (Flow vs Apex, callouts, approvals). Do not
conflate them. If you find yourself describing a callout, you are writing a
process flow — stop and switch artifacts (admin/process-flow-as-is-to-be).
Friction Taxonomy (Fixed Enum)
Every friction point must be tagged from this enum so downstream agents can
route work:
| Friction Tag |
Meaning |
Typical Fix |
cognitive_load |
Too many fields, sections, or related lists in view at once |
Dynamic Forms, conditional visibility, page redesign |
click_count |
Task takes more navigation clicks than necessary |
Quick Action, Path step, list view inline edit, related list tuning |
mode_switch |
Forces user from mobile→desktop or app→browser mid-task |
Mobile-friendly Quick Action, mobile-aware Lightning page, offline-capable LWC |
data_input |
Repeated typing, no defaults, no picklist where appropriate |
Default field values, validation rule with a useful message, picklist conversion |
search |
User cannot find a record, list view, or related item |
List view tuning, search layout, pinned list views, Einstein Search config |
Common Patterns
Pattern: PSG-First Persona Sketch
When to use: brand-new persona work, or when an existing persona doc has
drifted from org reality.
How it works: start from the PSG (or planned PSG) — extract assigned
object permissions, record types, layouts, and tabs. Bind that to a named
persona. Every claim in the persona profile must trace back to a PSG, a
record type, a list view, a dashboard, or an automation in the org.
Why not the alternative: title-based personas ("Sales Rep") describe a
stereotype, not a user. They drift, they collide, and they cannot be audited.
Pattern: One Task Per Journey Map
When to use: every primary persona task — captured one task per journey
artifact, not bundled.
How it works: the journey artifact has a single task (e.g. "Log a
visit", "Triage an inbound case", "Update opportunity stage to Negotiation"),
the frequency (daily / weekly / monthly / quarterly), the steps in order,
the friction tag on each problematic step, and the next task the persona
moves to (so the journey doesn't end at "saves record").
Why not the alternative: combining tasks into a single map produces a
deliverable nobody reads and a friction list nobody can route.
Decision Guidance
| Situation |
Recommended Approach |
Reason |
| Asked for personas with no PSG roadmap yet |
Flag the gap. Do not write personas; write a PSG sketch first. |
Personas without PSG anchors cannot be audited or kept current. |
| Asked to map mobile vs desktop and no measurement exists |
Flag the gap. Pull from Lightning Usage app or EventLogFile, then resume. |
Inventing mobile_pct corrupts every downstream UX decision. |
| Persona task ends at "record saved" |
Extend it — what task does the persona do next, on what surface? |
A journey that ends at save misses the most common friction (mode switch to next task). |
| 9+ personas in a single phase |
Reduce to ≤7 by merging adjacent personas. |
More than 7 personas is noise; signal-to-decision ratio collapses. |
| Persona references a dashboard nobody can find in the org |
Remove or replace with a real dashboard |
Hallucinated artifacts make the persona untrustworthy. |
| Friction tag does not fit the taxonomy |
Either re-frame to fit the enum or capture as notes |
Free-text tags break the routing handoff. |
Recommended Workflow
- Identify personas from PSG roadmap. Pull the planned (or current) Permission
Set Groups; one persona per distinct user population the PSGs serve. If a
PSG covers two distinct populations with different journeys, split it.
- Anchor each persona to org artifacts. Fill the canonical schema:
psg_assigned, primary_record_types[], primary_list_views[],
dashboards[], automation_touched[], and the measured mobile_pct /
desktop_pct. No anchor → not a persona.
- Build a journey map per primary task. One task per artifact. Record
frequency, every step in order, friction points tagged from the fixed
taxonomy, and the next task the persona transitions to.
- Flag friction that needs UI work.
cognitive_load, click_count, and
mode_switch typically route to record-page redesign, Quick Actions, Path,
or Dynamic Forms — handed off to lightning-record-page-auditor.
- Flag friction that needs automation.
data_input and some click_count
friction routes to Flow, defaults, validation rules, or assignment rules —
handed off to the automation agents.
- Hand off to downstream agents. Emit the handoff JSON: persona id, anchor
artifacts, friction backlog, and target agents
(
lightning-record-page-auditor, list-view-and-search-layout-auditor,
path-designer, plus UAT test design which runs each case as a persona).
- Revisit per release. Personas drift as PSGs and record types change;
re-run the anchor check every release train.
Canonical Persona Schema
{
"persona_id": "outside_sales_rep",
"name": "Outside Sales Rep",
"headcount": 42,
"psg_assigned": "PSG_Sales_Field",
"primary_record_types": ["Account.Customer", "Opportunity.Field_Deal", "Visit__c.Standard"],
"primary_list_views": ["My_Open_Opps_This_Week", "Visits_Due_Today"],
"dashboards": ["Field_Sales_Daily"],
"mobile_pct": 70,
"desktop_pct": 30,
"automation_touched": [
"Flow:Visit_After_Save",
"ValidationRule:Opp.Field_Stage_Required_Fields",
"AssignmentRule:Lead_Field_Territory"
]
}
Canonical Journey Schema
{
"persona_id": "outside_sales_rep",
"task": "Log a customer visit between meetings",
"frequency": "daily",
"steps": [
{"step": "Open Salesforce mobile app", "surface": "mobile"},
{"step": "Tap Visits Due Today list view", "surface": "mobile"},
{"step": "Open visit, tap Log Visit Quick Action", "surface": "mobile"},
{"step": "Enter notes, attendees, next step", "surface": "mobile", "friction": "data_input"},
{"step": "Save", "surface": "mobile"},
{"step": "Move to next visit on list", "surface": "mobile"}
],
"friction_points": [
{"step_index": 3, "tag": "data_input", "note": "No default for Visit Type; user retypes territory each time"}
],
"desired_outcome": "Visit logged in <60s without leaving the mobile app",
"next_task": "Drive to next account and repeat"
}
Handoff JSON Shape
{
"personas": [ /* persona records */ ],
"journeys": [ /* journey records */ ],
"friction_backlog": [
{
"persona_id": "outside_sales_rep",
"task": "Log a customer visit between meetings",
"friction_tag": "data_input",
"recommended_target": "lightning-record-page-auditor",
"recommended_intervention": "Default Visit Type from territory; review mobile compact layout"
}
]
}
Review Checklist
Salesforce-Specific Gotchas
- PSG drift after release. PSGs change between releases as new objects ship; re-run anchor checks every release train or personas go stale silently.
- Mobile usage measurement gaps. Lightning Usage app shows desktop-only by default; you must enable Mobile App usage and EventLogFile UriEvent to get the real split.
- List view personalization invisible to admins. Users create personal list views the admin never sees; persona list-view anchors should bias to shared list views or you misread the journey.
Output Artifacts
| Artifact |
Description |
personas.json |
Array of persona records following the canonical schema. |
journeys.json |
Array of journey records, one per persona-task pair. |
friction_backlog.json |
Routed friction items with target agent and recommended intervention. |
handoff.json |
Combined handoff envelope consumed by downstream auditing agents. |
Related Skills
admin/stakeholder-raci-for-sf-projects — Use for stakeholder authority and decision rights, not user-facing persona work.
admin/process-flow-as-is-to-be — Use for system-side process flows; this skill stays user-facing.
admin/lightning-app-builder-advanced — Use for the actual record page build once friction is identified.
agents/lightning-record-page-auditor — Downstream audit agent that consumes per-persona record page friction.
agents/list-view-and-search-layout-auditor — Downstream agent for search and list-view friction.
agents/path-designer — Downstream agent for per-record-type path design driven by journey stages.
1---2name: persona-and-journey-mapping-sf3description: "Build Salesforce-anchored personas and journey maps where every persona ties to a Permission Set Group, primary record types, list views, dashboards, automation, and a measured mobile/desktop posture, and journeys walk each task end-to-end with friction tags that drive UX decisions. NOT for stakeholder authority / RACI (use admin/stakeholder-raci-for-sf-projects), NOT for system-side process flows (use admin/process-flow-as-is-to-be), NOT for Lightning page design itself (use admin/lightning-app-builder-advanced or the lightning-record-page-auditor agent), NOT for pure design / UX research disconnected from org artifacts."4category: admin5salesforce-version: "Spring '25+"6well-architected-pillars:7 - User Experience8 - Operational Excellence9 - Performance10triggers:11 - "persona journey map salesforce"12 - "user persona salesforce features"13 - "salesforce mobile vs desktop persona"14 - "map sales rep journey to record page friction"15 - "service agent persona dashboard list view PSG"16 - "tie persona to permission set group and record type"17 - "find friction points in user journey for dynamic forms quick actions"18tags:19 - persona-and-journey-mapping-sf20 - persona-design21 - journey-map22 - user-experience23 - permission-set-group24 - mobile-vs-desktop25 - friction-analysis26inputs:27 - "list of user roles and counts in scope (target Permission Set Groups, profiles, record types)"28 - "primary tasks each role performs and rough frequency (daily / weekly / monthly)"29 - "available org artifacts to anchor against: PSGs, record types, list views, dashboards, automation"30 - "measured (not assumed) mobile vs desktop usage split per role"31outputs:32 - "persona records (canonical schema) anchored to PSG + record types + list views + dashboards + automation + mobile/desktop posture"33 - "per-task journey maps with steps, frequency, friction points tagged from a fixed taxonomy, and desired outcome"34 - "a friction-to-fix backlog: which friction points need UI work (Dynamic Forms, Quick Actions, page redesign, list view tuning) vs automation (Flow, validation rule, assignment rule)"35 - "handoff JSON consumed by lightning-record-page-auditor, list-view-and-search-layout-auditor, path-designer, and UAT test design"36dependencies: []37version: 1.0.038author: Pranav Nagrecha39updated: 2026-04-2840metadata:41 source: https://skillmd.com/skills/pranavnagrecha/persona-and-journey-mapping-sf42---4344# Persona And Journey Mapping (Salesforce-Anchored)4546This skill activates when an admin, BA, or architect needs to define **who actually47uses the org and how**, in a way that drives concrete Salesforce configuration48decisions rather than abstract UX deliverables. Every persona must anchor to org49artifacts the platform exposes — Permission Set Groups, record types, list views,50dashboards, automation — and every journey must walk a real task with measured51friction so the output feeds downstream auditing and design agents.5253---5455## Before Starting5657Gather this context before producing any persona artifact:5859- The **list of in-scope roles** and their headcount. Roles without users are noise.60- The **target Permission Set Group(s)** for each role — if the PSG does not yet61 exist, flag it; do not invent one. Personas without a PSG anchor become opinion62 pieces.63- The **primary record types** each role touches and the **list views** they live64 in. These are observable, not invented.65- **Mobile vs desktop usage**, ideally measured (Lightning Usage app, login66 history, EventLogFile UriEvent / LightningPerformance) — never assumed.67- **Dashboards** the role consumes daily/weekly. If a dashboard is named in a68 persona but does not exist in the org, it is a hallucination — flag it.69- The **automation** that fires for the role (record-triggered Flow, validation70 rules, assignment rules, approval processes, Agentforce topics) — captured by71 metadata, not memory.7273---7475## Core Concepts7677### Persona = User × Org Artifacts7879A Salesforce-anchored persona is the join between a *user population* and the80*concrete artifacts* the platform uses to constrain and serve them. The five81anchors are non-negotiable: PSG (what they can do), record types (what they82work on), list views (what they see), dashboards (how they measure success),83automation (what fires for them). A persona missing any anchor cannot drive a84configuration decision.8586### Mobile vs Desktop Posture8788Salesforce mobile (the Salesforce app) and Lightning Experience desktop are89different products with different UX rules: mobile favors Compact Layouts,90mobile-only Quick Actions, and brief related-list summaries; desktop favors91Dynamic Forms, multi-tab record pages, and dense related lists. The92mobile_pct / desktop_pct split — **measured, not guessed** — is what tells you93which surface to optimize. A 70% mobile field rep persona and a 95% desktop94SDR persona need very different record pages even on the same object.9596### Journey Map vs Process Flow9798A journey map is **persona-first**: one persona, one task, every step99they take, with friction tagged. A process flow is **system-first**: the100sequence of system events regardless of who triggers them. Journey maps drive101UX decisions (Dynamic Forms, Quick Actions, page redesign, path); process102flows drive automation decisions (Flow vs Apex, callouts, approvals). Do not103conflate them. If you find yourself describing a callout, you are writing a104process flow — stop and switch artifacts (`admin/process-flow-as-is-to-be`).105106### Friction Taxonomy (Fixed Enum)107108Every friction point must be tagged from this enum so downstream agents can109route work:110111| Friction Tag | Meaning | Typical Fix |112|---|---|---|113| `cognitive_load` | Too many fields, sections, or related lists in view at once | Dynamic Forms, conditional visibility, page redesign |114| `click_count` | Task takes more navigation clicks than necessary | Quick Action, Path step, list view inline edit, related list tuning |115| `mode_switch` | Forces user from mobile→desktop or app→browser mid-task | Mobile-friendly Quick Action, mobile-aware Lightning page, offline-capable LWC |116| `data_input` | Repeated typing, no defaults, no picklist where appropriate | Default field values, validation rule with a useful message, picklist conversion |117| `search` | User cannot find a record, list view, or related item | List view tuning, search layout, pinned list views, Einstein Search config |118119---120121## Common Patterns122123### Pattern: PSG-First Persona Sketch124125**When to use:** brand-new persona work, or when an existing persona doc has126drifted from org reality.127128**How it works:** start from the PSG (or planned PSG) — extract assigned129object permissions, record types, layouts, and tabs. Bind that to a named130persona. Every claim in the persona profile must trace back to a PSG, a131record type, a list view, a dashboard, or an automation in the org.132133**Why not the alternative:** title-based personas ("Sales Rep") describe a134stereotype, not a user. They drift, they collide, and they cannot be audited.135136### Pattern: One Task Per Journey Map137138**When to use:** every primary persona task — captured one task per journey139artifact, not bundled.140141**How it works:** the journey artifact has a single `task` (e.g. "Log a142visit", "Triage an inbound case", "Update opportunity stage to Negotiation"),143the frequency (daily / weekly / monthly / quarterly), the steps in order,144the friction tag on each problematic step, and the **next task** the persona145moves to (so the journey doesn't end at "saves record").146147**Why not the alternative:** combining tasks into a single map produces a148deliverable nobody reads and a friction list nobody can route.149150---151152## Decision Guidance153154| Situation | Recommended Approach | Reason |155|---|---|---|156| Asked for personas with no PSG roadmap yet | Flag the gap. Do not write personas; write a PSG sketch first. | Personas without PSG anchors cannot be audited or kept current. |157| Asked to map mobile vs desktop and no measurement exists | Flag the gap. Pull from Lightning Usage app or EventLogFile, then resume. | Inventing mobile_pct corrupts every downstream UX decision. |158| Persona task ends at "record saved" | Extend it — what task does the persona do next, on what surface? | A journey that ends at save misses the most common friction (mode switch to next task). |159| 9+ personas in a single phase | Reduce to ≤7 by merging adjacent personas. | More than 7 personas is noise; signal-to-decision ratio collapses. |160| Persona references a dashboard nobody can find in the org | Remove or replace with a real dashboard | Hallucinated artifacts make the persona untrustworthy. |161| Friction tag does not fit the taxonomy | Either re-frame to fit the enum or capture as `notes` | Free-text tags break the routing handoff. |162163---164165## Recommended Workflow1661671. **Identify personas from PSG roadmap.** Pull the planned (or current) Permission168 Set Groups; one persona per distinct user population the PSGs serve. If a169 PSG covers two distinct populations with different journeys, split it.1702. **Anchor each persona to org artifacts.** Fill the canonical schema:171 `psg_assigned`, `primary_record_types[]`, `primary_list_views[]`,172 `dashboards[]`, `automation_touched[]`, and the measured `mobile_pct` /173 `desktop_pct`. No anchor → not a persona.1743. **Build a journey map per primary task.** One task per artifact. Record175 frequency, every step in order, friction points tagged from the fixed176 taxonomy, and the next task the persona transitions to.1774. **Flag friction that needs UI work.** `cognitive_load`, `click_count`, and178 `mode_switch` typically route to record-page redesign, Quick Actions, Path,179 or Dynamic Forms — handed off to `lightning-record-page-auditor`.1805. **Flag friction that needs automation.** `data_input` and some `click_count`181 friction routes to Flow, defaults, validation rules, or assignment rules —182 handed off to the automation agents.1836. **Hand off to downstream agents.** Emit the handoff JSON: persona id, anchor184 artifacts, friction backlog, and target agents185 (`lightning-record-page-auditor`, `list-view-and-search-layout-auditor`,186 `path-designer`, plus UAT test design which runs each case as a persona).1877. **Revisit per release.** Personas drift as PSGs and record types change;188 re-run the anchor check every release train.189190---191192## Canonical Persona Schema193194```json195{196 "persona_id": "outside_sales_rep",197 "name": "Outside Sales Rep",198 "headcount": 42,199 "psg_assigned": "PSG_Sales_Field",200 "primary_record_types": ["Account.Customer", "Opportunity.Field_Deal", "Visit__c.Standard"],201 "primary_list_views": ["My_Open_Opps_This_Week", "Visits_Due_Today"],202 "dashboards": ["Field_Sales_Daily"],203 "mobile_pct": 70,204 "desktop_pct": 30,205 "automation_touched": [206 "Flow:Visit_After_Save",207 "ValidationRule:Opp.Field_Stage_Required_Fields",208 "AssignmentRule:Lead_Field_Territory"209 ]210}211```212213## Canonical Journey Schema214215```json216{217 "persona_id": "outside_sales_rep",218 "task": "Log a customer visit between meetings",219 "frequency": "daily",220 "steps": [221 {"step": "Open Salesforce mobile app", "surface": "mobile"},222 {"step": "Tap Visits Due Today list view", "surface": "mobile"},223 {"step": "Open visit, tap Log Visit Quick Action", "surface": "mobile"},224 {"step": "Enter notes, attendees, next step", "surface": "mobile", "friction": "data_input"},225 {"step": "Save", "surface": "mobile"},226 {"step": "Move to next visit on list", "surface": "mobile"}227 ],228 "friction_points": [229 {"step_index": 3, "tag": "data_input", "note": "No default for Visit Type; user retypes territory each time"}230 ],231 "desired_outcome": "Visit logged in <60s without leaving the mobile app",232 "next_task": "Drive to next account and repeat"233}234```235236## Handoff JSON Shape237238```json239{240 "personas": [ /* persona records */ ],241 "journeys": [ /* journey records */ ],242 "friction_backlog": [243 {244 "persona_id": "outside_sales_rep",245 "task": "Log a customer visit between meetings",246 "friction_tag": "data_input",247 "recommended_target": "lightning-record-page-auditor",248 "recommended_intervention": "Default Visit Type from territory; review mobile compact layout"249 }250 ]251}252```253254---255256## Review Checklist257258- [ ] Every persona is anchored to a real PSG (planned or existing).259- [ ] Every persona lists ≥1 record type, ≥1 list view, and ≥1 dashboard from the org.260- [ ] `mobile_pct + desktop_pct ≈ 100` (within ±2 for rounding) and the source of the measurement is named.261- [ ] Every primary task has its own journey artifact with ≥3 steps.262- [ ] Every friction point uses a tag from the fixed enum.263- [ ] Every journey names the `next_task`; none end at "save".264- [ ] Persona count for the phase is ≤ 7.265- [ ] Friction backlog routes each item to a downstream agent.266267---268269## Salesforce-Specific Gotchas2702711. **PSG drift after release.** PSGs change between releases as new objects ship; re-run anchor checks every release train or personas go stale silently.2722. **Mobile usage measurement gaps.** Lightning Usage app shows desktop-only by default; you must enable Mobile App usage and EventLogFile UriEvent to get the real split.2733. **List view personalization invisible to admins.** Users create personal list views the admin never sees; persona list-view anchors should bias to shared list views or you misread the journey.274275---276277## Output Artifacts278279| Artifact | Description |280|---|---|281| `personas.json` | Array of persona records following the canonical schema. |282| `journeys.json` | Array of journey records, one per persona-task pair. |283| `friction_backlog.json` | Routed friction items with target agent and recommended intervention. |284| `handoff.json` | Combined handoff envelope consumed by downstream auditing agents. |285286---287288## Related Skills289290- `admin/stakeholder-raci-for-sf-projects` — Use for stakeholder authority and decision rights, not user-facing persona work.291- `admin/process-flow-as-is-to-be` — Use for system-side process flows; this skill stays user-facing.292- `admin/lightning-app-builder-advanced` — Use for the actual record page build once friction is identified.293- `agents/lightning-record-page-auditor` — Downstream audit agent that consumes per-persona record page friction.294- `agents/list-view-and-search-layout-auditor` — Downstream agent for `search` and list-view friction.295- `agents/path-designer` — Downstream agent for per-record-type path design driven by journey stages.