8.4 List Views, Kanban, Path, and User Adoption Tools

Work surfaces, not decoration

List views are one of the most important adoption tools in Salesforce because they tell users what to work next. A queue of new leads, overdue tasks, high-priority cases, stalled opportunities, expiring contracts, or accounts missing next steps can change behavior more effectively than a training slide. The admin should design list views around action: who owns the record, what status it is in, what date makes it urgent, and what field tells the user the next move.

List view governance matters because unmanaged list views become clutter. Users may create personal views with unclear filters, duplicate names, or outdated assumptions. Public list views can help teams standardize work, but the admin should decide who can create, edit, and share them. Sensitive data should not be exposed by adding fields to a public list view if the audience lacks a business need, even though field-level security still controls actual field visibility.

Kanban is useful when the object has a status-like field and users benefit from seeing work grouped visually. Opportunities by stage, cases by status, leads by status, and tasks by owner or status can all be useful. The admin should verify whether users can drag records between columns, whether validation rules or required fields block stage changes, and whether automation runs when a value changes. Kanban is not just visual; it can update data.

Path is a guided process feature. It can show key fields and guidance for success at each stage or status. A good Path reflects the organization's real process language. For an opportunity, early stages may emphasize qualification fields and discovery notes, while later stages may require legal review, primary contact, next step, close plan, and competitor information. For cases, Path may guide triage, investigation, customer response, resolution, and closure quality.

Adoption workflow for administrators

Adoption is an admin support workflow, not a one-time launch event. If a team is not updating opportunities, the admin should ask whether the page makes the right fields easy, whether list views show stale records, whether Path guidance matches the actual sales process, whether managers review the same fields, and whether automation creates friction. Users follow systems that help them do real work and that managers reinforce consistently.

Adoption design checklist:

1. Choose one target behavior, such as closing cases with complete resolution details.
2. Identify the objects, fields, stages, and user groups involved.
3. Build or revise list views that expose records needing action.
4. Configure Path guidance and key fields for each meaningful stage or status.
5. Add quick actions, dynamic visibility, or validation only where they support the behavior.
6. Create reports or dashboards that managers will actually use in coaching.
7. Train with realistic records, then collect support tickets and user feedback after launch.
8. Retire outdated prompts, list views, and guidance when the process changes.

Inline editing and mass changes can improve productivity, but they introduce control questions. Some fields cannot be inline edited because of field type, page configuration, record type differences, dependent picklists, or other constraints. Even when inline edit is available, validation rules and automation still apply. A user moving several opportunities in Kanban may trigger flows, approval requirements, forecast changes, notifications, or required-field errors. The admin should test the bulk workflow before telling users to rely on it.

Path guidance should be specific enough to shape behavior. Text such as Update the opportunity is not useful. Better guidance says what evidence belongs in the stage, which field must be current, what handoff is expected, and when the user should advance or move backward. However, the guidance should not try to replace the full training manual. Keep it short, action-oriented, and reviewed by the business owner.

Support teams should watch for adoption friction signals. If users repeatedly export list views to spreadsheets, maybe the list view lacks the right filters, fields, or inline actions. If managers ask for manual status updates, maybe dashboards are not trusted or records are not current. If users avoid Path stages, maybe stage names do not reflect reality or required fields are asked too early. The admin's job is to diagnose the operating model, not just add another required field.

Agentforce and AI features may appear in productivity conversations, but admin judgment still applies. AI-generated summaries, recommendations, or agents can support work only when the data is reliable, permissions are respected, use cases are approved, and outputs are tested. Do not use AI to paper over an unclear process. A poor stage model, stale activities, or unmanaged list views will still produce poor guidance.

Study trap: do not confuse adoption with login count. A user can log in every day and still manage deals in a spreadsheet. Better adoption measures include overdue tasks, opportunities with next steps, cases updated within service targets, records missing required process fields, and manager use of standard reports.