Case Study

Agentforce Coworker

In beta · screens not yet public
Role Design Lead
Partners Agentforce · GO · Search · Data Cloud
Focus Setup, config & the default agent
Timeline 2024 – 2025
In beta
Want to see the screens?
This product isn't fully public yet, so I've kept the detailed flows and final screens off the page. I'd happily walk you through the whole setup experience and the decisions behind it in a portfolio review. Just reach out.

A new product is only as good as the day you turn it on.

Agentforce Coworker is Salesforce's AI teammate, embedded in the search bar and available across Slack, Teams, and mobile, so people can find and act on information scattered across CRM, Slack, Data Cloud, and outside systems through one interface. None of that power matters if an admin can't stand it up. As Design Lead for setup and configuration, I owned the end-to-end experience for getting the product running, from the guided enablement flow, built against a ten-minute north star, to how admins return to adjust it over time, plus the default agent that ships with it.

The hard part was never a single screen. It was holding one coherent setup together across four partner platform groups, Agentforce, Salesforce GO, Search, and Data Cloud, each moving fast and owning a different piece. Left to run alone, each would have shipped its own setup, and an admin would have felt every seam. Making sure that didn't happen was the job.

Ship the agent on, not off.

The default agent that powers search could have been left for admins to wire up themselves after enabling the product. That looks like the safer call: more control, fewer assumptions made on the user's behalf. I argued the opposite. An admin who just enabled agentic search has already said what they want. Making them hand-assemble the agent afterward turns one setup into two, right at the moment they are most likely to stall or walk away.

I designed the default agent as a managed dependency instead: it turns on automatically when the product does, configured and ready, with the controls to adjust it still there for admins who want them. The tradeoff I accepted was less up-front configuration in exchange for a working search far sooner. For a setup measured against a ten-minute north star, getting an admin to value before options was the whole game.

Creating alignment across complexity.

Agentforce Coworker lived across five teams, my own Setup team plus four platform groups: Agentforce, Data Cloud, Search, and Salesforce GO, each with its own roadmap, priorities, and timeline. The hard part was never a single screen. It was making one coherent experience emerge from teams all moving at once, in different directions. As the Setup lead, that coherence became the real work: I held the whole-system view, shared designs early and often, got teams reviewing the same work in the same room, and represented the admin whenever priorities pulled apart. Left to run alone, five capable teams would have shipped five disconnected pieces. The influence that mattered came from understanding and trust, not authority.

Creating alignmentacross complexity
Setup
Agentforce
Search
Data Cloud
Salesforce Go

Different teams. Different priorities. Different timelines. One experience.

A new agentic product, made set-up-able.

0→1
New agentic search product
4
Source types unified: CRM, Slack, Data Cloud & third-party
10 min
Enablement north-star, from weeks of integration
5
Teams aligned behind one setup experience: Setup plus four platform groups

What working in chaos taught me.

The work that mattered most wasn't any single screen. It was holding the whole-system view while a dozen teams moved at once, and being the person who could pull them toward one coherent setup for a genuinely vast product. I went deep on Data Cloud, Search, and Agentforce fast to keep up, and learned to lead designers and teams I didn't manage, alongside some of the best designers I've worked with. It's the hardest thing I've done, and the work I want more of.

Next Project
Welcome.Salesforce.com →
Where platform complexity meets a first-time admin.