What this covers
Most of what makes Salesforce feel slow or hostile to your team is fixable. Layouts that show every field instead of the ones the user needs. Screens that ask for the same information twice. Buttons that take three clicks when they could take one. The work here is the unglamorous, high-leverage UX cleanup that drives adoption.
- Page layout and Lightning record page redesign for sales, service, and ops users.
- Screen flows that walk users through complex tasks (lead intake, case escalation, quoting) with the right validation and the right defaults.
- Quick actions and global actions — keep users out of edit mode for fast, bounded changes.
- Console layouts for service and inside-sales users.
- Mobile experience for field-facing teams.
- In-app guidance and walkthroughs for new features and new hires.
How we typically engage
UX work is usually scoped against a specific persona — "make the SDR experience tolerable" or "rebuild the case console for tier-1 support." A two-week shadow + redesign + build cycle is typical.
What "done" usually looks like
- The user can complete their primary tasks in fewer clicks, with the right information visible without scrolling.
- Adoption metrics measurable — we agree on what they are at the start so we can read them at the end.
- The layouts are documented and the rationale captured so future admins don't accidentally undo the work.