Death By 1,000 Clicks: The Hidden Cost of Tiny Salesforce Inefficiencies

There is a question I find myself asking more often these days when I look at Salesforce environments. Not whether the system works. Not whether the implementation was delivered on time. Not even whether users are logging in. The question is much simpler than that. How much effort does it actually take for somebody to do their job? It sounds like an obvious question, yet surprisingly few organisations ever stop to ask it. Instead, they focus on the bigger, more visible measures of success. They look at project delivery dates, licence utilisation, automation statistics and system uptime. Those things are certainly important, but they often distract attention away from something far more influential: the day-to-day experience of the people using the platform. Because the truth is that most Salesforce environments do not struggle because of one catastrophic decision. They struggle through accumulation. They struggle because small inefficiencies are introduced over time, and those inefficiencies slowly become accepted as normal. A field gets added here. An approval step gets introduced there. A screen becomes a little busier. A process takes a few seconds longer than it did six months ago. Nobody notices because each individual change feels insignificant. The problem is that insignificant things rarely stay insignificant when they are repeated hundreds or thousands of times every day. Imagine a sales representative logging customer interactions. Perhaps the process takes thirty seconds longer than it should because information is spread across multiple tabs, or because there are fields that need to be completed that provide little real value. Thirty seconds sounds trivial. In fact, if you raised that issue in many project meetings, it would probably be dismissed immediately. Thirty seconds is hardly a business problem. But organisations do not operate at the level of a single transaction. They operate at scale. A sales team of one hundred people logging ten activities per day creates a thousand transactions every single day. Suddenly, those thirty seconds become more than eight hours of lost productivity. Every day. Every week. Every month. Over the course of a year, that tiny inefficiency has consumed hundreds of hours of working time. Not because anybody made a terrible decision, but because nobody paid attention to a small one. Now let's explore another scenario. Imagine a growing organisation that has invested heavily in Salesforce over the last five years. The implementation was successful. Users adopted the platform. Reporting improved. Leadership gained visibility they never had before. On paper, everything looks positive. During those five years, however, the business continued to evolve. New products were introduced. New departments joined the platform. Different managers requested different information. Compliance requirements changed. Reporting needs expanded. Each time a request appeared, a sensible decision was made. "We'll just add another field." "We'll just add another status." "We'll just add another approval." "We'll just add another section to the page." None of those decisions were wrong. In fact, many of them were probably entirely justified. The challenge only becomes visible when somebody compares today's experience with the experience users had five years earlier. What once required five pieces of information now requires fifteen. What once took two screens now takes six. What once felt intuitive now requires explanation. The organisation hasn't experienced one large problem. Instead, it has accumulated hundreds of small ones. And because the accumulation happened gradually, nobody noticed. I think this is one of the biggest hidden risks in mature Salesforce environments. Organisations become so focused on adding value that they rarely stop to ask whether they are also adding friction. Growth introduces complexity. Complexity introduces effort. Effort introduces resistance. Resistance eventually impacts behaviour. That behaviour is where things become particularly interesting. Let's explore another scenario. Imagine two sales representatives who both leave a customer meeting at exactly the same time. They both need to update Salesforce before moving on to their next appointment. The first representative opens Salesforce, enters a few updates, completes the required fields and moves on. The process takes two minutes. It feels simple. It feels reasonable. The second representative faces a slightly different experience. They need to navigate multiple screens. Several fields seem unclear. Some information feels duplicated. A few mandatory fields appear to exist purely for reporting purposes. The process takes six minutes instead of two. Neither user complains. Neither user raises a support ticket. Neither user tells management there is a problem. But their behaviour starts to diverge. The first representative continues updating Salesforce immediately after every meeting because the effort feels manageable. The second representative starts postponing updates until later in the day. Then later in the week. Then perhaps they begin keeping notes elsewhere with the intention of updating Salesforce later. Eventually, some information never makes it into the system at all. When leadership reviews reports several months later, they see data quality issues. The temptation is to conclude that the user is the problem. Perhaps they need more discipline. Perhaps they need more accountability. Perhaps they need another reminder from management . But what if the real issue started months earlier with a process that simply demanded too much effort? What if the data quality problem is actually a usability problem wearing a different disguise? I think organisations often underestimate how closely behaviour is linked to effort. Human beings naturally gravitate towards the path of least resistance. We all do it. If something feels easy, we repeat it. If something feels difficult, we avoid it. That principle applies whether we're exercising, managing our finances or updating Salesforce. The challenge is that effort is rarely measured. Businesses measure logins, opportunities, activities, revenue. Very few businesses measure how difficult it feels to perform those activities in the first place. And yet that difficulty influences almost everything that follows. This is where the conversation starts moving beyond efficiency and into psychology. Every time somebody opens a Salesforce record, their brain is making decisions. They are processing information, filtering distractions, prioritising actions and determining what matters most. The more information presented to them, the greater the mental workload becomes. Let's explore one final scenario. Imagine two account pages. The first contains only the information required for the user's role. Key details are immediately visible. The next action is obvious. The page feels clean. Users can quickly understand what they are looking at and what they need to do next. The second page has evolved over several years. Different teams have requested additional fields. Managers wanted extra reporting information. Historical requirements were never removed. The page now contains dozens and dozens of fields, multiple sections and information relevant to people who may never even look at the record. Technically, both pages function. Technically, both pages provide information. Technically, neither page is broken. Yet the experience is entirely different. On the first page, users focus on customers. On the second page, users focus on navigating the system. That distinction matters more than many organisations realise. Because the purpose of Salesforce is not to help people use Salesforce. The purpose of Salesforce should be to help people do their jobs and make it easier to do their job. Whenever users spend more energy interacting with the system than serving customers, managing cases, or progressing opportunities, something has shifted out of balance. This is one of the reasons I have become increasingly interested in the concept of cognitive debt. We often hear discussions about technical debt, but cognitive debt can be just as damaging. Every unnecessary field, every confusing process and every additional click creates a small mental burden. Individually, those burdens feel insignificant. Collectively, they can create an environment that feels exhausting to navigate. And when users become mentally exhausted, performance suffers. Not dramatically. But gradually. Quietly. Almost invisibly. Which brings us to training. Most organisations view training as an activity designed to teach users how the system works. While that is certainly part of its purpose, I think the most valuable trainers provide something else entirely. They provide visibility. A good trainer spends hours observing users interact with the platform. We see where people hesitate. We hear the questions users repeatedly ask. We notice which processes require explanation and which ones make sense immediately. Those observations are incredibly valuable because they often reveal future inefficiencies before they become embedded into daily behaviour. If twenty people struggle with the same screen during training, that is not random. If multiple users ask the same question, that is not random. If people consistently take longer to complete a particular process than expected, that is not random. Those are signals. Signals that waste may be developing. Signals that the organisation has an opportunity to improve the user experience before the inefficiency becomes normalised. Unfortunately, many organisations position training at the very end of a project and treat it as a tick-box exercise. The system is built. Training is delivered. The project closes. But what if training is actually one of the most powerful diagnostic tools available? What if the training room is where hidden inefficiencies reveal themselves for the first time? What if trainers are not just educators but observers, translators and early warning systems? I think there is a strong argument that we are. What fascinates me is how often businesses become obsessed with large transformation initiatives while overlooking these smaller opportunities. There is enormous excitement around artificial intelligence, automation and digital transformation. Every organisation wants to become more productive, more efficient and more intelligent. Yet many businesses are simultaneously carrying thousands of tiny inefficiencies that quietly drain productivity every single day. Those inefficiencies rarely appear in strategy presentations. They rarely appear in board reports. They rarely appear in implementation reviews. But they are there. Waiting. Accumulating. Compounding. The irony is that removing five minutes of daily friction from a hundred users can often create more immediate value than launching an entirely new initiative. It simply lacks the excitement and visibility that organisations naturally gravitate towards. Perhaps that is why these problems persist for so long. They're too small to attract attention individually. Yet together they become remarkably expensive. When you think about it that way, this podcast is not really about clicks at all. The clicks are simply a symbol. What we're really discussing is accumulated waste. We are talking about the hidden cost of tiny inefficiencies that slowly become embedded within an organisation. We are talking about the gap between how processes are designed and how people actually work. Most importantly, we are talking about the fact that productivity is rarely lost in dramatic moments. More often, it disappears quietly, a few seconds at a time, until those seconds become hours, those hours become weeks and those weeks become a significant business cost. The next time somebody tells you that an extra click does not matter, I would encourage you to challenge that assumption. One click probably doesn't matter. One additional screen probably doesn't matter. One extra thirty-second task probably doesn't matter. But one thousand clicks matter. One thousand moments of hesitation matter. One thousand tiny inefficiencies matter. And some of the most expensive problems in Salesforce are not the ones we notice immediately. They are the ones we have stopped noticing altogether.