Why I’ve Changed How I Design Salesforce Builds

I spent last week at TrailblazerDX in San Francisco, and by the time Salesforce wrapped the Headless 360 keynote it was hard to miss the direction of travel. The platform most of us have designed for (Lightning, page layouts, the browser-based world) is being quietly rearchitected to be one surface among many. Headless 360 is the architectural umbrella: the whole platform accessible via APIs, MCP tools and CLI commands (no browser required), with a new experience layer for rendering agent interactions wherever users actually work (Salesforce Ben, TDX 2026).

None of this came out of nowhere. A fortnight earlier, Parker Harris, the co-founder who built the Lightning UI, had stood on a stage in San Francisco and asked out loud why anyone should still log into Salesforce (SalesforceDevops.net, 31 March 2026). Salesforce had just unveiled more than thirty new AI capabilities for Slackbot and was openly positioning Slack as the place where enterprise work actually happens (SiliconANGLE, 31 March 2026). TDX gave that direction an architectural backbone.

I've been running Salesforce programmes long enough to tell the difference between a real product shift and a new coat of paint. This is a real shift. And it's going to change how I approach every new build.

Where I've landed

I don't think the Lightning desktop UI is going away. Anyone who tells you otherwise is either selling something or hasn't watched real users get real work done in it. But I do think it's quietly moving from the interface to one of several, and for a growing number of users, it's no longer the primary one.

A field sales rep closing out their week isn't opening a laptop. A service user logging an IT request isn't filing a ticket in a portal. Salesforce itself has called time on portal-driven ticketing and is pushing customers toward conversational, agent-led experiences across Slack, Teams, email, web and voice (Salesforce Newsroom, 26 February 2026). An admin setting up OAuth scopes isn't clicking through five screens any more. They're having a conversation with Agentforce for Setup.

The canvas has moved. My approach has to move with it.

The evidence isn't subtle any more

A year ago I could have written this as speculation. I can't now.

The piece of Headless 360 that's caught my attention most is what Salesforce calls the Agentforce Experience Layer, the rendering component of the new architecture. It lets you define an interaction once and have it render across Slack, mobile, Teams, ChatGPT, Claude, Gemini, anything that speaks MCP. The pitch from Salesforce is literally build once, render everywhere (Salesforce Ben, TDX 2026). Slackbot has become an MCP client in its own right, coordinating across thousands of apps in the Slack Marketplace and on AppExchange, and from this summer Slack will be provisioned automatically with every new Salesforce customer (The Next Web, April 2026).

The number that's stuck with me: one enterprise customer whose Agentforce adoption jumped from 22% to 78% in six weeks. The agent itself didn't change. Only the surface it was offered on (SiliconANGLE, 15 April 2026). That's the clearest sign I've seen that the interface question has become properly separable from the capability question.

None of this means Lightning is done. It just means Lightning has company.

What's changed in how I design

The old default on a Salesforce programme went roughly: persona → process → object model → page layouts → automation → reports. Page design sat in the middle and pulled everything into its orbit. You could point at a screen and say "this is what the user does." When half the user base doesn't look at a screen any more, that method falls over.

Here's what I'm doing differently.

I start with intents, not pages. The first artefact on my current programme isn't a screen inventory. It's a list of user jobs. Confirm the competitor on a deal. Work out why an account's slipping. Log an expense from the road. Only once the intent is clear do I ask: on which surface is this best served? Some want a desktop page. Some want a Slack command. Some want a conversation. Some want all three, and I design them to behave consistently.

I make actions surface-agnostic. An "update opportunity stage with rationale" action has to be the same action whether it's invoked from a Lightning button, a Slack message or an Agentforce topic. Reusability across surfaces isn't a nice-to-have any more. It's the starting point.

I take Data 360 seriously, and earlier. Salesforce has rebranded Data Cloud as Data 360 and put it squarely at the centre as the unified data layer that gives every agent context (Salesforce Investor Relations, Dreamforce 2025). Independent analysis is consistent on this: Data 360 is what retrieval-augmented agents actually ground their answers in (360 Degree Cloud, December 2025). A half-populated Account record on a Lightning page is ugly. The same record feeding an agent produces a confidently wrong answer. Data quality has moved from a hygiene concern to an architectural one.

I treat prompt templates, topics and actions as first-class artefacts. Same rigour I apply to flows and page layouts: versioned, reviewed, tested, governed. The temptation to treat them as lightweight config is strong. They're closer to code.

I've changed how I think about testing. You can't regression-test an agent the way you can a page. Salesforce has been honest about this: agents are probabilistic, not deterministic, and can land on unexpected outcomes that are behaviour to observe rather than bugs to fix (Salesforce Ben, TDX 2026). Testing Center, Observability and Session Tracing are the new instruments. Most teams I'm seeing, partners included, are still catching up to what probabilistic QA actually means for their delivery lifecycle.

What hasn't changed, and now matters more

One thing I'm seeing in the market is an assumption that the platform fundamentals matter less now. If anything, they matter more.

The object model still has to be right. An agent will expose a broken data model faster and more publicly than a Lightning page ever did. Sharing and security still have to be right, and it's harder now because architects are reasoning about agent identity as well as user identity. When an agent acts on a user's behalf, whose permissions apply? What can it see that the user can't? These are live questions, and they don't have clean answers yet.

Integration patterns, governance and change management are all more load-bearing, not less. The inversion is that the work we used to spend most of our time on (screens) is getting distributed across surfaces, while the work that was often underinvested in (data model integrity, data quality, security, governance) has quietly become the foundation everything else rests on.

Where I'd push back on the hype

Let me be honest about where I think the current narrative overshoots.

Not every interaction belongs in an agent. Agents are bad at some things: deep multi-step workflows with strong audit requirements, mass data operations, pixel-precise reporting, anything where a user needs to see and manipulate a lot of structured information at once. Lightning exists for good reasons and a lot of them are still valid.

It's worth listening to the skeptical voices too. The Register has pointed out that the vision of Slackbot as a single interface across every enterprise application rather glosses over how complex those systems actually are, and how hard it is to keep the underlying data current and well-governed (The Register, 2 April 2026). Salesforce reported combined Agentforce and Data 360 ARR of around $1.4 billion in Q3 FY26. Meaningful, but still a fraction of the overall business, and the bar for what counts as a successful deployment varies wildly (Futurum Group, December 2025).

The failure mode I'm watching for isn't "we didn't do enough with agents." It's "we turned every interaction into a conversation and alienated the users who just wanted a grid."

How we should be changing our approach

For anyone scoping or delivering a Salesforce programme right now, the practical implication of all this is that the surface question belongs in scope from the first release, not deferred to a later phase once "the core is live." That shift has a few concrete knock-ons I think we should be planning for from the first workshop:

Document user journeys across surfaces, not as single-screen flows. The same intent will often surface in Lightning, in Slack, and in an Agentforce conversation, and our designs need to anticipate that.

Design core capabilities to be invocable from any surface (Lightning, Salesforce Mobile, Slack, Agentforce) with the same action, data model and security underneath. Reusability across surfaces becomes the starting point, not a later optimisation.

Treat Data 360 scope and data quality as go-live blockers rather than enhancements. If agents are anywhere on the roadmap, the data foundation has to come first.

Extend governance to cover topics, agents and prompt templates alongside profiles, permission sets and sharing rules. The governance model most programmes run today simply doesn't cover these new artefacts.

Build evaluation and behavioural testing into test plans for anything an agent will touch, not just the deterministic flows. Probabilistic QA is a new discipline for most of us.

None of this is radical in isolation. What's different from even a year ago is that all of it needs to be day-one design, not something we sort out after go-live.

Where this leaves us

The line that's stayed with me through all of it is still Harris's. The person publicly questioning the Lightning UI was the person who built it. That kind of candour is unusual in this industry, and at TDX it became clear there's an architecture being built behind the rhetoric.

We're not heading into a world without the Salesforce UI. We're heading into a world where the UI is one of several interfaces to the same platform, and where the central design question is no longer "what goes on the page" but "what intent are we serving, and on which surface?" The platform disciplines get more important. The screen disciplines get more distributed.

For those of us designing and delivering these programmes, the work isn't getting easier. It's getting more architectural, and a lot more interesting. The teams that'll do well over the next two or three years are the ones who stop treating the desktop UI as the default and start designing for a multi-surface world from the first workshop.

The Lightning page isn't dead. It's just no longer where my design conversation starts.

References

Parker Harris Just Told You to Stop Logging into Salesforce. SalesforceDevops.net, 31 March 2026. https://salesforcedevops.net/index.php/2026/03/31/parker-harris-stop-logging-into-salesforce-slackbot-march-2026/

Salesforce transforms Slackbot into the ultimate work assistant with 30 new AI features. SiliconANGLE, 31 March 2026. https://siliconangle.com/2026/03/31/salesforce-transforms-slackbot-ultimate-work-assistant-30-new-ai-features/

Salesforce Headless 360 and Agentforce Vibes 2.0 Revealed at TDX 2026. Salesforce Ben, April 2026. https://www.salesforceben.com/salesforce-headless-360-and-agentforce-vibes-2-0-revealed-at-tdx-2026/

Salesforce Targets ITSM: 180 Organizations Adopt Agentforce IT Service. Salesforce Newsroom, 26 February 2026. https://www.salesforce.com/news/press-releases/2026/02/26/agentforce-it-service-selected-for-itsm/

Slack's biggest AI update turns Slackbot into a desktop agent. The Next Web, April 2026. https://thenextweb.com/news/slack-slackbot-30-ai-features-agentic

Salesforce bets on conversation as the new interface for developers. SiliconANGLE, 15 April 2026. https://siliconangle.com/2026/04/15/salesforce-bets-conversation-new-interface-developers/

Welcome to the Agentic Enterprise: With Agentforce 360. Salesforce Investor Relations, Dreamforce 2025. https://investor.salesforce.com/news/news-details/2025/Welcome-to-the-Agentic-Enterprise-With-Agentforce-360-Salesforce-Elevates-Human-Potential-in-the-Age-of-AI/default.aspx

How Salesforce Data 360 Fuels Context-Aware AI Agents. 360 Degree Cloud, December 2025. https://360degreecloud.com/blog/how-salesforce-data-360-fuels-context-aware-ai-agents/

Salesforce looks to Slackbot to help solve SaaSpocalypse. The Register, 2 April 2026. https://www.theregister.com/2026/04/02/salesforce_slack_update/

Salesforce Q3 FY 2026: AI Agents, Data 360 Lift Bookings. Futurum Group, December 2025. https://futurumgroup.com/insights/salesforce-q3-fy-2026-ai-agents-data-360-lift-bookings-and-fy26-outlook/