Table of Contents
Friends don't let friends learn the hard way.
Create how-to guides, in seconds.
Try Tango for free

LinkedIn isn’t short on advice for IT, operations, training, and enablement teams. But when it comes to what makes us stop the scroll, what beats a widely acknowledged best practice every time? 

A hot take 🌶️ or hard lesson learned. 💡

Here’s a quick round-up of training and enablement traps to avoid this year—from people who have been there, done that, and bought the t-shirt (despite the best intentions).

  1. Training when it’s convenient for you, not your end users
  2. Creating how-to guides with walls of text
  3. Including uncropped screenshots without crystal clear annotations 
  4. Recording videos that don’t help people get unstuck ASAP 
  5. Hosting mandatory workshops that pull people away from their jobs
  6. Shipping the long version of anything
  7. Committing random acts of enablement 
  8. Hoping your ambivalent adopters will magically lean into change and new software
  9. Measuring product usage instead of process adoption
  10. Expecting your tech stack to solve business problems your tools weren’t designed for

To avoid subjecting you to a wall of text, let’s dig into #10 and save the others for another time. 😊

The reddest of red flags: Expecting your tech stack to solve business problems your tools weren’t designed for

Say you have an internal software training rollout. 

Maybe you’re switching customer relationship management platforms or standing up a new human resources information system. The stakes are…not low, and neither is the pressure to quickly influence behavioral change and drive widespread process adoption.  

If you’re thinking about leaning on your Learning Management System and/or Knowledge Base for software training success, do not pass go, do not collect $200, and do not set your project (and your co-workers) up for failure. 🫠

The greenest of green flags: Using the right tool, at the right time, for the right project

A chart breaking down the modern training and enablement tech stack according to general knowledge and software knowledge.

If you want to increase general knowledge (about your market, customer, company, product, or service)...

👉🏾 That’s what Learning Management Systems and Knowledge Bases are for. 

If you want to increase software knowledge (so everyone can perform your company’s most critical workflows without pinging you every 10 minutes)...

👉 That’s where Digital Adoption Platforms (DAPs) and Work Instructions Tools come in.

And if you want to knock your internal software training or rollout out of the park…

👉🏼 That’s where Real-Time Enablement (RTE) makes a world of difference.

DAPs excel at using RTE to make teaching and learning new software possible—whether you’re a process expert with an org-wide rollout hanging over your head or an end user who just wants to know what to do and where to click.  

Think about the impact you could drive if you had a way to:

↳ Empathize with your ambivalent adopters (who really hate change)
↳ Nix all your wordy documentation and long videos 
↳ Embed instructions directly inside of the tools where your end users already work
↳ Deliver just enough training to help people evolve at their own pace 
↳ Distribute process knowledge that can be applied in the moment
↳ Help everyone focus on more strategic projects (instead of trying to memorize software SOPs)

All you need is a tool purpose-built for internal software enablement. 💡

This is some text inside of a div block.