ARGO · 2026
CONNECTS for Salesforce
Designing a contextual view of CONNECTS customer information inside an existing Salesforce workflow.
- Role
- UX Direction & Research
- Scale
- Two weeks · six information domains · two layouts
- Focus
- Information Architecture · Interaction Design · Design Direction
The problem
ARGO wanted Salesforce users to see relevant CONNECTS customer information, and receive referrals from CONNECTS, without leaving Salesforce. Most of those users had never used CONNECTS, and the component had to fit Salesforce's own layouts.
What I did
I led UX direction for a two-week sprint with a designer, a product director and a business analyst. I compared one contained component against several separate cards, built one information hierarchy for narrow and wide layouts, and reused existing CONNECTS and QUADS patterns wherever they fit.
Try a decision. Six kinds of CONNECTS information need to appear inside a Salesforce page. Separate cards, or one component?
Outcome
Final designs were handed off on September 11, 2026, with feasibility discussions with Salesforce underway. The direction: one ARGO component that adds what Salesforce doesn't already show, with drill-in from overview to record detail.