Blog Post
.png)
It’s a tale as old as time: the legacy learning management system (LMS) that took your company from point A to point B no longer meets your needs.
Your company has grown.
You now educate multiple audiences.
You plan to scale your eLearning academy.
But your legacy solution just isn’t scalable; adding new users requires lots of human effort.
Meanwhile, your company’s burning cash on apps that barely get used, and employees across the organization are doing duplicate work inside similar systems (e.g., building product onboarding courses inside an LMS and an LXP).
You’re sure it’s time for a tech stack consolidation.
But how do you get started? How do you convince resistant colleagues? And how do you avoid “rookie” mistakes?
Read on to learn:
- Why companies have bloated edtech stacks
- Benefits of consolidating your edtech stack
- What most articles don’t tell you about tech stack consolidation
- Best practices to ensure a smooth consolidation process
Why companies have bloated edtech stacks
The average organization uses 130 apps, according to a 2023 study from BetterCloud.
.gif)
And while we couldn’t find any reputable studies citing the number of edtech apps used, McKinsey says the adult edtech sector is growing quickly to keep up with increased market demand; more companies realize the value in doing organizational education.
Do you know how many tools are in your edtech stack?
Often, education professionals can’t answer this question with certainty for one simple reason: teams responsible for educating different audiences buy education tools to meet their needs.
For example:
- HR purchases an LMS for employee education.
- Marketing purchases a course authoring tool for customer education.
- Partner success purchases a digital badge/certification platform for partner education.
The bloat builds each time a team adds an additional tool—i.e., when someone identifies a need to use gamification to boost learner engagement and buys a bolt-on gamification tool.
In other words, your edtech stack is bigger than your team’s edtech stack; it encompasses all tools used across the business to educate your company’s audiences. And chances are, your organization uses more tools than you realize.
Benefits of consolidating your edtech stack
A common problem companies with bloated tech stacks face is resource waste. For example, different teams upload similar course content to two separate eLearning platforms—when they could have adopted a single eLearning platform that lets them share content across audiences. (They’re paying for two tools and the humanpower required to maintain two tools.)
Consolidating your ed tech stack can help you to eliminate costly redundancies.
Other key benefits of consolidating your tech stack include:
- Reduced employee stress: As we found by surveying 445 workplace education professionals, education teams are being pressed to “do more with less,” and they’re stressed out. When you eliminate redundant work, these employees gain back hours in the day—and feel less overwhelmed.
- Improved scalability: Scalability is the ability to support additional learners with minimal administrative effort. As part of the consolidation process, you will eliminate unscalable legacy tools that are incompatible with company growth.
- Centralized reporting: If you currently struggle to measure the business impact of your education initiatives because you do similar work in multiple systems that don’t “talk” to each other, consolidation can help.
- Fewer silos: PwC found that 55% of companies work in silos. Going through the process of tech stack consolidation forces you to identify—and break down—silos. For example, if two teams are building product training from scratch in two different apps, you can flag that and find a way to repurpose some or all of the content inside one app.
The benefits of consolidation are clear.
But while most articles on tech stack consolidation jump straight from the benefits into the how, there are two important points to understand before you take action.
What most articles don’t tell you about tech stack consolidation
If you open an article that attempts to make tech stack consolidation sound easy, run.
.gif)
As much as we’d love to share “five easy steps to consolidate your tech stack,” we’d be doing you a disservice.
We interviewed Yevgeniy Tsvetov, Principal Consultant at Cleartelligence, a Boston-based data and analytics consultancy serving brands like Boston Scientific, TJX, and Citizens Bank. Tsvetov’s an expert in tech stack consolidation who helps companies plan and organize their deployment—from deciding which apps to choose to planning implementation.
He mentioned two important points worth sharing:
“There is no specific playbook.”
Unlike cooking an omelet where you follow a set of clearly defined, predetermined steps, tech stack consolidation isn’t a “first do this, then always do this, then always do that” type of activity.
“It’s nuanced,” Tsvetov said. “There’s no specific playbook I use with every client.”
For example, consolidation steps can vary based on factors like:
- Whether the company is local or global
- Whether the tech is in-house or cloud-based
- What level of data security the company requires
- Who will be using the app: One team? Several teams?
“[For multiple teams using an app] you’ll need some sort of chargeback structure: this department has x number of users; this department has x number of users,” Tsvetov said. “If they can’t charge it back, we’re out of luck.”
"Tech stack consolidation is nuanced. There's no specific playbook." - Yevgeniy Tsvetov, Principal Consultant at Cleartelligence
“No one wants to spend time and effort figuring it out.”
“Learning management systems are usually purchased out of compliance requirements,” Tsvetov said. “At the time of purchase, no one is truly excited about it. But as time goes on, three different systems get bought by departments because they have to facilitate training. Eventually, someone new is in charge of merging systems, and they’re excited to replace several legacy systems with a better solution.”
For example, one manufacturing company brought on an experienced education leader to take its digital education to the next level. That leader got a lay of the land and started working to see if it was possible to consolidate various platforms into one system.
But while some people see a need to consolidate in order to scale, not everyone agrees.
“Some stakeholders feel the amount of effort that would go into replatforming—and figuring out who’s paying for or partitioning licensing—is too high,” Tsvetov explained. “So they say ‘let’s stick with what we have.’ No one wants to spend time and effort figuring it out.”
The takeaway?
Prepare to be met with resistance. And have a plan for overcoming resistance.
That said, if you don’t have deep experience overseeing a tech stack consolidation—and if you don’t have a Chief Information Officer or Chief Data Officer to guide you—you can hire outsourced expertise. This activity is too important to go it alone and hope for the best!
Best practices to ensure a smooth process
Since there’s no one playbook to run in every situation, we’re sharing some “best practices” rather than rigid steps to follow.
Get buy-in from other stakeholders.
As mentioned above, teams often create education content in silos. Customer support creates knowledge base articles. Customer success creates customer webinars. Product creates product onboarding videos. Marketing creates a certification. Learning & Development creates on-demand courses.
Because there are many cooks in the kitchen, you’re not just making decisions that impact your team; you’re making decisions that impact several teams. This means you’ll need buy-in from other team leads and senior leadership in charge of IT and security.
Develop a business case for consolidation including:
- Anticipated benefits of consolidation (i.e., cost savings, improved efficiency)
- Impact of maintaining status quo (i.e., unnecessary spend, duplicative work)
- Effects of consolidation on organizational goals (i.e., faster revenue growth)
If you have an executive sponsor, that person will likely be critical in terms of helping you gather the support and resources you need to complete the consolidation project. Remember what Tsvetov said: “No one wants to spend time and effort figuring it out.” Your executive sponsor can help you polish your argument and present information in a way that overcomes objections.
Interview stakeholders across the company to understand which tools they’re using.
Most advice will tell you to “go audit your tech stack.” But that advice can be interpreted as “go audit your team’s tech stack” rather than “go audit your company-wide tech stack.”
When it comes to edtech tools, you might not be aware of which tools are being used, why, how, and by whom. Put on your detective hat and interview stakeholders across the business.
Questions you can ask include:
- Who on your team, if anyone, is creating educational content?
- What kind of content are you creating?
- Who is this content for?
- Why are you creating this content?
- How are you measuring performance?
- What technology are you using?
- How often do you use the technology?
- How many seats are you paying for?
- How many seats are you using?
- What is the annual cost of each tool?
Identify redundancies.
Interviews are often eye-opening. Perhaps you find that your organization pays for a standalone gamification tool and an LMS that offers built-in gamification functionality.
.gif)
Perhaps you find that employees on three different teams do customer product training. In addition to time spent creating the content, they also upload and maintain content in different systems: an event platform, an LMS, and a LXP. Is this necessary or efficient? Probably not.
But before you rush to cancel subscriptions, make sure you understand exactly what features, support, and professional services each company offers. For example, that standalone gamification tool might offer learners the ability to trade in points for physical goods via an e-store. If your LMS doesn’t offer the same functionality—and it’s critical in keeping learners engaged and returning to your academy—you might decide to keep both tools.
Pinpoint gaps.
Do a gap analysis. The learnings from your interviews also help to identify gaps.
Perhaps you discover that measurement and reporting is a pain point for several stakeholders because you’re unable to track the full learner journey—or visualize education content performance. You can’t make smart data-driven decisions without high-quality data.
You might look for a tool with built-in analytics and robust dashboards—or one that integrates with your preferred data visualization tool (i.e., Domo or Tableau).
Or perhaps you discover that it takes lots of extra effort to support new learners inside your LMS. In other words, your ed tech platform isn’t scalable. This is a gap you’ll want to address quickly as it’s something your senior team cares about. (Last year, we surveyed 502 decision makers involved in workplace education and found that scalability is the most valued learning platform capability among C-level respondents.)
Watch the on-demand webinar: Build for scale and reach more learners faster.
Define your goals and required functionality (before contacting vendors).
Not long ago, Jaclyn Anku, Director of Community and Education at Gusto, set out to replace her legacy LMS with a more robust LMS in order to build Gusto Academy.
“We’d outgrown our previous LMS, and we needed to rip off the Band-Aid—but the prospect of migrating our content, data, and systems made my head spin,” Anku said. “As daunting as it was however, we had one thing going for us: we knew exactly what we needed to do.” (Jaclyn and her colleague had prepared by doing internal interviews and competitive research.)
Lots of competitive research.
“After all the competitive research James and I had done, we had a 10-page wish list (read: highly detailed specs doc) outlining all of the baseline features and services we were looking for, along with all those extra bells and whistles that made my heart skip a beat when I saw them in action.”
This legwork allowed Gusto to enter vendor conversations with a robust RFI (request for information), which made the buying process more efficient and effective.
Collaborate internally to select the best tools for your needs.
Like Gusto, impact.com needed to upgrade their legacy LMS to support their growing eLearning academy.
After vendor conversations, an internal committee of 10 employees reviewed RFP (request for proposal) responses and attended demos to narrow down the selection. The group used scorecards to make a final decision.
If employees across the organization will be asked to adopt a new tool, they should have some say as to which tool is best.
Implement your new tool within your existing tech stack
If you’re moving from one tool to another, you’ll need to safely and efficiently migrate your existing data and content so that your learner experience isn’t interrupted.
Find out in advance whether your new tech partner offers migration support—as well as the level of support provided.
And if needed, hire an expert to oversee your implementation and ensure a smooth transition.
Continue your learning
If you liked this article, you might enjoy these related content pieces:
About the Author
