Designing for Humans vs Designing for Processes

Words matter more than we often realise. They shape expectations, influence decisions and determine where organisations invest their time, money and attention. A single word can change how a project is perceived, how a budget is allocated and how seriously an initiative is taken. This is particularly true when it comes to Salesforce transformation. For years, organisations have used the words training and enablement almost interchangeably. On the surface, this may seem harmless. After all, both involve helping people learn new skills and use new systems. Yet I have increasingly come to believe that the distinction between these two terms is far more significant than most organisations appreciate. In fact, if you are still framing your Salesforce learning strategy purely as training, you may already be limiting the success of your transformation. Not because training is unimportant. But because the word itself often creates expectations that are too small for the challenge organisations are trying to solve. When executives hear the word training, they tend to picture a familiar set of activities. A workshop. A webinar. A slide deck. Perhaps a session delivered shortly before go-live. Training is often viewed as a project task, something that must be completed before a system can be handed over to users. It is seen as a necessary activity. Rarely is it seen as a strategic investment. This perception creates consequences. Training budgets become vulnerable when project timelines tighten. Training is often one of the first areas to be reduced when costs need to be controlled. Sessions become shorter. Content becomes more generic. Role-specific support is removed. Learning becomes compressed into increasingly unrealistic timeframes. The assumption is that training is simply about transferring information. As long as users have been shown the system, the requirement has been fulfilled. Unfortunately, this mindset overlooks a much bigger challenge. The goal of a Salesforce transformation is not simply to help people understand a system. The goal is to help people perform differently. And that requires something far more substantial than information transfer. This is where enablement enters the conversation. Enablement is often misunderstood as a more fashionable word for training. In reality, it represents a fundamentally different way of thinking about learning and organisational change. Training focuses on knowledge. Enablement focuses on capability. Training asks whether users know what to do. Enablement asks whether users can consistently apply that knowledge in real situations. The distinction may appear subtle, but the implications are significant. Consider a sales team adopting Salesforce. Traditional training may teach users how to create opportunities, update records and run reports. The learning objective is centred on system usage. Enablement takes a broader view. It asks whether salespeople can use the platform to manage their pipeline effectively, identify risks, prioritise opportunities and make better decisions. It focuses not only on understanding the system, but on improving performance through the system. The same principle applies across every role. A service advisor does not simply need to know how to update a case. They need confidence handling customer interactions while navigating the platform. A manager does not simply need to know where a dashboard is located. They need the ability to interpret information and coach their teams effectively. These outcomes extend far beyond system knowledge. They represent organisational capability. And capability is where transformation truly begins. This distinction becomes particularly important when engaging senior leadership. Executives rarely invest enthusiastically in activities. They invest in outcomes. Training sounds like an event. Enablement sounds like a result. One is something you do. The other is something you achieve. This difference influences how learning initiatives are positioned within organisations. A request for training budget often triggers questions about duration, cost and logistics. A proposal focused on capability-building prompts discussions about performance, productivity and business outcomes. The conversation changes because the language changes. Suddenly the focus shifts from delivering sessions to improving organisational effectiveness. The same dynamic exists at the user level. People respond differently depending on how learning is presented. If users are told they must attend Salesforce training, many approach it as an obligation. It becomes another item on an already crowded calendar. Something to complete before returning to real work. The underlying message is that the system is the priority. Enablement creates a different perception. When users understand that the objective is to help them work more effectively, make better decisions and feel more confident in their role, engagement increases. The learning experience becomes relevant because it is connected directly to performance rather than compliance. This shift also changes the design of learning itself. Traditional training often focuses on functionality. Users are shown screens, buttons and processes. The emphasis is on understanding how the platform works. Enablement starts with real work. Scenarios replace demonstrations. Practical challenges replace feature tours. Learning becomes role-specific, contextual and outcome-driven. Users are not simply learning Salesforce. They are learning how to succeed within Salesforce. This distinction is particularly important because adoption is not measured by logins. It is measured by behaviour. An organisation can achieve excellent login statistics while still struggling with poor data quality, inconsistent processes and low confidence. Users may technically be using the system while failing to extract meaningful value from it. Enablement addresses this gap because it focuses on behavioural change rather than system exposure. It recognises that true adoption occurs when people stop thinking about how to use Salesforce and start using Salesforce to achieve better outcomes. This becomes even more critical as organisations embrace automation, analytics and artificial intelligence. Much of the current conversation focuses on technology. New tools promise greater efficiency, faster decision-making and improved productivity. Yet every one of these initiatives depends on a common foundation. Capability. Artificial intelligence is only valuable if users understand how to interpret and challenge its outputs. Automation is only effective when processes are clear and consistently followed. Reporting only creates value when managers know how to use the information available to them. Technology can accelerate performance. It cannot replace capability. This is why I often describe enablement as the foundation upon which every future initiative is built. Before automation comes alignment. Before AI comes clarity. Before scale comes capability. Organisations that invest in capability-building create an environment where future innovation can thrive. Those that focus solely on training often find themselves repeatedly addressing the same adoption challenges because the underlying capability gap remains unresolved. Ultimately, this is why the language matters. Not because organisations need new terminology. But because words influence how we think. When learning is framed as training, it is often treated as a cost. Something necessary but secondary. A support activity attached to the real work of transformation. When learning is framed as enablement, it becomes something different. It becomes a strategic investment. A mechanism for improving performance. A driver of adoption. A source of competitive advantage. Most importantly, it becomes aligned with the actual objective of transformation. Because Salesforce success is not determined by whether users attended a session. It is determined by whether they developed the confidence, consistency and capability required to work differently. That is the real goal. Not training. Capability. And the organisations that understand this distinction are the ones most likely to achieve lasting transformation. Because in the end, systems create potential. People create outcomes. And enablement is what bridges the gap between the two.