The successful pattern: identify the recurring workflow, build a view that scopes records and surfaces the right columns, share with the team if applicable, pin to default for users who use it daily. The cost is minutes; the workflow gain compounds across thousands of list visits per quarter.
- Identify the workflow the view serves
My open opportunities for this week, cases I own with SLA breach, accounts in my territory needing renewal review. The workflow drives filter and column choices.
- Open the object's list page and click New List View
The gear icon, New List View. Name the view per the workflow.
- Set the filter criteria
Scope tightly to the workflow. Owner = me, Stage IN (open stages), Close Date = THIS QUARTER. Tight scope keeps the list useful; broad scope produces noise.
- Pick the columns
6 to 10 columns. The fields the user needs to make decisions from the list, not every available field. Order matters; left-to-right by importance.
- Set the sharing scope
Private for personal, public for org-wide, group for team. Default to private if unsure; sharing later is easy.
- Test the view performance
Load the view, time the response. Slow loads usually mean filters are too broad or hit non-indexed fields.
- Train the team if the view is shared
Users do not discover shared views on their own. A five-minute training brief gets adoption; without it the view sits unused.
Which records the view shows. Supports AND/OR logic and boolean filter expressions.
Which fields display per row. 6 to 10 is the workable range.
Private, Public, or Group-shared. Drives who sees the view.
Table, Kanban, or Chart-on-top. Per-user toggle.
Per-user default view for the object. The view that loads when the user navigates to the object.
- Broad filters can time out on large objects. Filter on indexed fields (Owner, Status, Created Date) and bound result counts.
- Private views accumulate. Quarterly review and retire stale ones; the view picker becomes unusable past a few dozen entries.
- Shared views need user training. Discovery is poor; users find views they were briefed on, not views that exist quietly.
- Mass actions respect user permissions. A view that exposes a mass action a user cannot run produces a confusing error.
- Kanban mode requires a picklist for grouping. Custom objects without a picklist field cannot use Kanban mode.