Section 1: The Free Classroom
On the 30th of October, something quietly came to an end. The Trailblazer Community forums, where Salesforce people have asked and answered each other’s questions for the best part of twenty years, went read-only. The community is moving to Slack this month. Salesforce has said the old posts will stay searchable, so nobody’s hard-won knowledge is being thrown away. In the scheme of things, it is a platform change: a new home for an old conversation.
But it made me stop and think about what that conversation actually was, and what it was quietly doing for businesses that never paid a penny for it.
I’m Connie Hazendonk, and for more than ten years I’ve helped organisations get their people using Salesforce properly, training thousands of users on projects in more than a dozen countries. But before I was training anyone, I started where so many people in this ecosystem start: as an accidental admin. I’d come from market research, not technology. In 2012 I was working at a drinks company, and my first day with Salesforce was eight hours with an American developer talking about page layouts. There was no Trailhead, no community to speak of and almost no training. I learned the job by breaking things. I built changes straight into production, gave everyone the same profile, and loaded thirty thousand bought records without cleansing them first. Every one of those mistakes cost the business something, and every one of them happened because nobody had shown me a better way.
The people who came after me had a very different experience. Within a few years there was Trailhead: free, well designed, gamified and genuinely good. There was a global community of people who would answer a validation rule question at midnight for no reason other than generosity. A whole generation of admins, developers and consultants learned their craft that way. I’m a Trailhead Academy instructor myself, and I have enormous respect for what Salesforce built.
And yet, somewhere along the way, businesses noticed that this free classroom existed and quietly stopped thinking about learning altogether.
Listen to how many organisations answer the question “How do your people learn Salesforce?” The answer is very often a link. New starter? Send them to Trailhead. Admin stuck? Post it on the community. Struggling user? There’s a module for that. Salesforce has encouraged this reflex for years, pointing customers towards Trailhead whenever the conversation turns to training. That’s a perfectly reasonable thing for a software company to do. It’s a strange thing for a business to accept as its entire strategy.
Because here is the uncomfortable part. Trailhead teaches Salesforce. It does not teach your Salesforce.
It can’t. It doesn’t know that your sales team uses a custom stage called “Verbal” that means something slightly different in each region. It doesn’t know that your service agents must record a case reason before closing a case, or why. It doesn’t know which fields your finance team relies on for commission, which reports the board sees, or which of your record types a new starter should never touch. It teaches the standard platform, with clean data, in a tidy practice org, in the order the product was designed. Your people live somewhere very different: a platform shaped by years of decisions, customisations and compromises, running a process that exists only in your business.
A rep can collect twenty badges and still not know how to update an opportunity the way your forecast needs it. That isn’t a criticism of Trailhead. It’s a description of what it was built for.
The community has the same limitation, only more so. It is extraordinary for the people inside the ecosystem: the admins, developers and consultants who already speak the language. It is almost invisible to the people who use Salesforce every day. The sales rep doesn’t post on a forum. The service agent doesn’t join a Slack workspace to find out why her screen changed overnight. The field engineer certainly doesn’t. The free classroom was always a classroom for the people who build Salesforce, not for the people who work in it.
So what many businesses have really done is outsource two very different things to one free resource, and neither fits.
They have outsourced their users’ learning to a platform that teaches the generic product rather than their process. And they have outsourced the development of their own Salesforce people, the admins and superusers who end up training everyone else, to the goodwill of strangers.
That second one matters more than it looks. The community could teach an admin how to build a flow. It couldn’t teach her how to stand in front of a room of sceptical sales reps and help them change the way they work. It couldn’t teach her how to design training around real jobs rather than screens, how to tell the difference between someone who doesn’t know how and someone who doesn’t feel confident, or how to support people in the weeks after go-live, when the real questions finally arrive. Those are training skills, not platform skills. They were never in the free curriculum, because teaching them was never anyone’s job.
I see the consequence whenever I work with the people who deliver Salesforce training inside their own organisations. Many of them have been doing it for years and know the platform inside out. Very few have ever been shown how adults actually learn: that people forget what they don’t practise, that a room of thirty people from five different roles learns less than three smaller groups who share a job, and that a session built around a real customer situation sticks in a way a tour of the navigation bar never will. They have done their best with what the ecosystem gave them, and the ecosystem gave them product knowledge. Nobody gave them the craft. That isn’t their failure. It’s what happens when the only classroom available teaches the tool and never the teaching.
The result is a strange contradiction. The ecosystem is full of people who know Salesforce brilliantly, and organisations are full of users who still don’t feel confident using it. Both things are true at once, and the gap between them is where an enormous amount of value quietly disappears.
I hear it all the time: “We told them to do the Trailhead modules.” As if the link were the training. I understand why it happens. It’s free, it’s credible, it’s endorsed by the vendor, and it lets everyone tick a box. A new starter is sent a list of modules in her first week. She completes some of them in between everything else, earns a few badges, and then opens your Salesforce for the first time and finds that almost nothing looks like what she practised. Nobody asks whether she can do her job. The badges suggest she can.
Sending someone a link is not a learning plan. It’s a hope, with a URL attached.
None of this is a reason to mourn the forums. Moving the community somewhere more conversational may well make it better for the people who use it. The point is what the move reveals. For twenty years, a free and generous resource sat in the background of Salesforce learning, and it allowed a great many organisations to avoid a question they should have been asking all along: whose job is it to help our people learn our Salesforce?
When the honest answer is “Trailhead’s” or “the community’s”, the real answer is nobody’s. And when learning is nobody’s job, it doesn’t stop happening. It just happens badly, informally and on top of everyone’s day job.
Which raises the obvious next question. If there’s no budget, no plan and no owner, how do people actually learn Salesforce inside a business? I’ve spent more than ten years watching it happen, and the answer isn’t pretty.
Section 2: Nobody’s Job
Ask a leadership team what their Salesforce training budget is and you’ll often get a pause. Not because the number is embarrassing, but because there isn’t one. There was a training line in the implementation project, and it was usually the first thing to be squeezed when the build overran. After go-live, learning was folded into “business as usual”, which is a polite way of saying that nobody is paying for it and nobody is accountable for it.
And yet people do learn. They have to. Salesforce changes three times a year, new starters arrive every month, processes shift and managers ask for new reports. So the learning happens anyway. It just happens in three places that businesses never designed for it.
The first is on the job, by trial and error. A user doesn’t know how to do something, so she clicks around until something works. Sometimes what works is the right way. More often it’s simply a way. She remembers it, repeats it, and within a few weeks it is how she does things. Nobody checks, because nobody knows there’s anything to check. Multiply that across a team and you get five people doing the same task five different ways, each of them confident they’ve got it right. This is where a lot of what leaders later call “poor data quality” begins: not with carelessness, but with people teaching themselves under pressure, with no one to tell them what good looks like.
The second place is the admin’s desk. Every organisation has one person everybody walks over to. Usually it’s the admin; sometimes it’s the one person in operations who “knows Salesforce”. They answer the same question twenty times a week. They write a quick guide when a release changes a screen. They run an impromptu session for new starters because nobody else will. None of this is in their job description, and all of it sits on top of a build backlog that never gets any shorter. I’ve met admins who are effectively the training department, the helpdesk and the change team for several hundred users, and who are measured almost entirely on how many requests they close.
That arrangement has two problems. The obvious one is capacity. One person cannot carry the learning needs of an entire organisation, and burnout among Salesforce professionals is hardly a secret. The less obvious problem is skill. Admins are brilliant at building Salesforce, but nobody ever taught most of them how to teach it. So the training they give, generously and under pressure, tends to be a tour of screens: this is the field, this is the button, this is where it goes. Calling that training is generous. It’s exposure. People nod, go back to their desks, and fall back on whatever they were doing before.
The third place is the superuser. On paper, superusers are a sensible idea: experienced people embedded in each team who help colleagues, spot problems early and pass on good habits. In practice, most superuser networks are assembled in the weeks before go-live and quietly abandoned a few months later. The people chosen are usually the most technically confident, or simply whoever volunteered, rather than the people their colleagues actually listen to. They receive the same training as everyone else, perhaps a little earlier. They get no protected time, so helping colleagues becomes an unpaid second job squeezed in around their real targets. And once the project team leaves, nobody supports them, updates them or thanks them.
So the superuser does what any sensible person would do under those conditions. They help when they can and pass on what they know, and what they know includes all their own shortcuts and workarounds. The new starter sitting beside them learns those too, with all the confidence that comes from learning from someone experienced. That is how one person’s workaround becomes a team’s process. Not because anyone did anything wrong, but because the learning was never given any structure.
Picture a new service agent in her second week. Her induction included a recording of a session from last year and a list of Trailhead modules. She needs to know how to escalate a complaint, so she asks the team’s superuser, who is in the middle of his own queue and shows her quickly, his way. The next day she asks the admin something else. The admin is polite but clearly busy, so she decides not to ask again. By her fourth week she has a working method stitched together from three people, a recording and her own guesses. She’s productive, she’s fast, and she’s doing at least two things in a way nobody intended. Nobody will notice until her cases start appearing in a report that doesn’t quite add up.
Put those three together and you have the real learning system in most businesses: self-teaching under pressure, an overloaded admin, and a superuser network running on goodwill. It is informal, invisible and entirely unmeasured. And it produces exactly what you would expect: inconsistent ways of working, quiet confusion, a handful of people who become indispensable and a much larger group who never quite feel sure of themselves.
The conventional response, when someone eventually notices, is to blame the users. They don’t follow the process. They don’t enter the data. They don’t use the features we paid for. But think about what we actually gave them. A link to some generic modules, a colleague who was too busy to help, and a system that changed three times a year without anyone explaining what had changed. Then we expected consistency.
There is a cost to this that never appears anywhere. Every hour a rep spends working out how to do something that should have been taught is an hour not spent selling. Every question that lands on the admin’s desk is a piece of build work that slips. Every superuser who quietly burns out takes years of local knowledge with them. I call this productivity leakage, and it’s one of the most expensive things in Salesforce precisely because nobody ever sends you an invoice for it.
I’m not arguing that informal learning is bad. People learn an enormous amount from each other, on the job and in the moment, and they always will. The problem isn’t that informal learning exists. It’s that in most organisations it’s the only learning there is, and nobody has decided what it should teach.
So what would change if it were somebody’s job? Not necessarily a big team or a big budget, but somebody who owns the question of how people learn your Salesforce. Somebody who decides which tasks matter most for each role and makes sure those are taught properly. Who chooses superusers for their influence rather than their enthusiasm, gives them protected time and keeps them up to date. Who lets the admin be a builder rather than a helpdesk. And who checks, every so often, whether people can actually do their jobs with confidence, rather than assuming they can because they once sat through a session.
That isn’t a luxury. It’s the difference between learning that happens by accident and learning that happens on purpose. If learning isn’t someone’s job from day one, it isn’t anyone’s job.
But even the organisations that do invest in training usually fall at the next hurdle. They build the materials, run the sessions, and then put everything somewhere safe. In most businesses, that means a folder on SharePoint that nobody has opened in a very long time.
Section 3: The Folder Nobody Opens
Somewhere in your organisation there is a folder. It’s probably on SharePoint, possibly on a shared drive, and it’s almost certainly called something like “Salesforce Training” or “CRM User Guides”. Inside it there’s a slide deck from go-live, a forty-page user guide full of screenshots, a few recordings of sessions that overran, and a quick reference card someone made for the sales team a couple of years ago.
Most of it is out of date. Some of it is simply wrong. And it is still the official answer to the question “Where do people go to learn Salesforce here?”
I often ask organisations a simple question: when were your training materials last updated, compared with your last major release? The answers are rarely comfortable. Salesforce changes three times a year. Most organisations change their own configuration far more often than that: a new field here, a revised stage there, a validation rule added after a difficult quarter. The training materials, meanwhile, were written once, for go-live, by a project team that has long since moved on.
Every change widens the gap a little more. The screenshots stop matching the screen. The process in the guide no longer matches the process in the business. A new starter opens the guide, finds that the first three steps look nothing like what she sees, and closes it. She won’t open it again. Nobody will tell her it’s out of date, because nobody knows. She’ll ask the person sitting next to her instead, and the informal cycle of learning starts all over again.
Outdated training can be worse than no training at all, and I mean that quite literally. No training tells people they need to ask. Outdated training tells them, with complete confidence, to do the wrong thing. And once people have been caught out by a guide, they stop trusting every guide, including the ones that are right. The folder doesn’t just go stale. It teaches people that official guidance isn’t worth reading.
And it’s rarely just one folder. In most organisations I work with, Salesforce knowledge is scattered across a dozen places: the original project site, a team’s own channel, a manager’s personal notes, a few PDFs attached to old emails, and a recording on someone’s drive that only they know how to find. Each was created with good intentions by someone trying to fill a gap. Together they form a library with no librarian. Nobody knows which version is current, so people either trust none of them or, worse, trust whichever one they happened to find first. Ask where a new starter should go to learn how something is done, and the honest answer is usually a person’s name rather than a place.
There’s a second problem with the folder, and it’s a subtler one. Even when the materials are current, they’re usually disconnected from the work. They live in one place, and the job happens somewhere else. The user guide explains how to create an opportunity. It doesn’t explain what your business expects to happen when a prospect goes quiet, when a deal needs a discount approved, or when a customer complains in the middle of a renewal. It’s organised around Salesforce’s objects, not around the moments people actually face in their day.
People don’t start their morning by creating an account. They start by looking at what needs their attention and working out what to do next. Training that follows the screens instead of the job asks users to translate it themselves, every single time, from system language into working language. One frontline sales team summed it up better than I ever could: “I feel like I need a translator just to log a deal.” That translation is exactly what good training is supposed to do, and it’s exactly what the folder doesn’t.
So why does this keep happening? Partly because nobody owns the materials after go-live. They were a project deliverable, signed off and handed over, and ownership quietly evaporated the moment the project closed. Partly because updating training is never anyone’s priority when it competes with build work and urgent requests. And partly because the materials were written as documentation rather than as learning: comprehensive, accurate on the day they were finished, and designed to be filed rather than used.
There’s also a quieter cultural reason. A full folder looks like diligence. When someone asks whether users have been trained, it’s reassuring to point at forty pages and a library of recordings. Nobody asks whether anyone has opened them, whether they still match the system, or whether a single person learned to do their job from them. The folder becomes evidence that training happened, rather than a tool that helps it happen.
The organisations that get this right don’t necessarily produce more material. They usually produce less, and they treat it very differently. They write around jobs rather than screens: short pieces built around the situations people actually face, in the language the business actually uses. They keep it close to the work, so people can find what they need in the moment rather than in a folder three clicks away from anything they’re doing. They give it an owner, someone accountable for keeping it current, with a simple rhythm in which every release and every significant change triggers a review of what’s affected. And they retire material ruthlessly. A guide that’s out of date gets fixed or deleted. It is never left to mislead the next person who finds it. And they involve the people who use it. They ask users what they went looking for last week and couldn’t find, and they treat every question that lands on the admin’s desk as a sign that something is missing, unclear or out of date. The questions people ask are the most honest review your training will ever get.
Most of all, they stop treating training materials as if they were the training. A guide is a reference and a reinforcement, something to come back to. It’s not how people build confidence. Confidence comes from practising on real work, from someone checking that you can actually do the task, and from being allowed to get it wrong while someone helps you get it right. The folder can support all of that. It can never replace it.
Which brings me back to where this started. The Trailblazer Community forums went read-only last week, and the conversation is moving somewhere new. Salesforce has kept the archive, and that’s the right thing to do. But it made me wonder how many businesses could say the same about their own knowledge. If your admin left tomorrow, if your best superuser moved on, if that folder were the only thing a new starter had, what would they actually learn?
For twenty years, a free classroom made it easy not to ask that question. Businesses could point to Trailhead, lean on the community, rely on the person who knew, and file everything else away. It looked like a learning strategy. It was really the absence of one, held together by other people’s generosity.
So here’s something practical to try this week. Pick one role in your organisation. Ask three people in that role how they actually learned to do their job in Salesforce. Then open your training folder and see how much of what they told you is in there. The gap between those two answers is your real training plan.
Be the first to comment