There’s a version of Salesforce that your team loves. Where a sales rep can find everything they need about a client in thirty seconds. Where a service manager can see the full customer history before picking up the phone. Where data flows between teams without anyone having to chase it down, copy it across, or build a workaround spreadsheet that only one person understands.
Most organisations know that version exists. A lot of them are still waiting for it.
The common explanation is that implementation is hard, change management is hard, Salesforce is complex. All of that is true. But it misses the more uncomfortable reason that most Salesforce projects underdeliver: the people were an afterthought.
Not intentionally. Nobody sits down to design a system that their team will avoid. But when you scope a project around features, timelines, and licences rather than around how your people actually work, you get a technically complete implementation that nobody wants to use. The platform works. The adoption doesn’t.
Technology doesn’t fail in the server room. It fails at the desk.
The moment of failure is never a missing integration or an unconfigured field. It’s the sales rep who opens Salesforce, can’t find what they need in under a minute, and opens Excel instead. It’s the service agent who’s been told to log everything but hasn’t been shown why, so they log the minimum and move on. It’s the manager who pulls a report that doesn’t match reality and stops trusting the data.
These are not technology problems. They are human problems that technology was supposed to solve but didn’t, because the humans weren’t at the centre of the design.
This is why we named our founding philosophy what we did. Human-centred Salesforce solutions isn’t a tagline. It’s the observation that sits underneath every project we’ve delivered, and a few we’ve inherited that we had to fix.
When you design for people first, you ask different questions from the start. Not “what does Salesforce support?” but “what does this role actually need to do its job?” Not “what data should we capture?” but “what data will someone actually enter, and what would make entering it feel worth their time?” Not “how do we configure this feature?” but “how does this team work, and what would change that for the better?”
The answers to those questions produce a different outcome. Simpler, often. Faster to use. More likely to stick.
The organisations that get the most from Salesforce are not the ones with the most features turned on.
They’re the ones where the platform reflects how their people think and work. Where adoption wasn’t something that had to be managed after go-live because it was designed in from the beginning. Where the system earns trust because it actually makes someone’s day easier instead of adding to it.
That gap between a system that works and a system that people actually use is where a lot of Salesforce investment quietly disappears. It doesn’t show up as a failed project. It shows up as low adoption, workarounds that become permanent, reports nobody trusts, and a sense that you got less than you paid for.
After more than 1,000 Salesforce projects across Australia, we’ve seen what separates the ones that deliver from the ones that don’t. The differentiator is rarely technical. It’s whether the people who have to live with the system had a meaningful say in how it was built.
This applies to every wave of technology, not just the last one.
Right now, a lot of organisations are wrestling with AI. The same pattern is already playing out. Tools are being evaluated on capability rather than fit. Pilots are being run to prove the technology works, not to understand whether it actually helps a real person do a real job better. And the people who’ll eventually have to use the outputs are not yet in the room.
Some of those pilots will succeed on their own terms and fail in practice. Not because AI doesn’t work, but because the humans were an afterthought.
The answer isn’t to slow down. It’s to keep asking the question that changes the outcome: who is this for, and have we actually talked to them?
If your Salesforce platform isn’t delivering what you expected, or you’re about to take on a new implementation, a migration, or an AI initiative and want to get it right the first time, that question is where we’d start.
That’s always where we start.
