What Happens When More Campus Processes Live in Slate?
I have four daughters, and between them, we have soccer, travel soccer (somehow different), lacrosse, select lacrosse, club lacrosse, ballet, competitive ballet, field hockey, and yes, club field hockey. And of course, nearly every activity has its own app. Sometimes we have multiple apps for the same sport, depending on the team, league, or tournament.
I understand why these apps exist. They’re designed to support specific activities and do things that a more general platform might not handle particularly well. But keeping track of everything across all of them is exhausting. And despite having an app for seemingly everything, we still end up with Google Sheets to manage tournament teams and schedules.
The more I think about it, the more it reminds me of the CRM environment across higher education.
A Proliferation of Specialized Applications, Managed in Spreadsheets
For years, colleges and universities have turned to specialized applications to address needs that their larger enterprise systems weren’t designed to support. A giving portal, a smaller CRM to manage workforce partnerships, an appointment scheduling tool for tutoring, or a separate application for continuing education programs.
These solutions filled important gaps and allowed departments to manage processes that didn’t fit neatly into their existing technology. And just like my daughters’ sports teams, plenty of campus processes are still being managed through spreadsheets.
Over time, many of these applications have become permanent parts of the campus technology environment, each with its own licensing costs, integrations, data, and administrative requirements. While they may still work well, it’s worth asking whether they’re all still necessary.
It’s Time to Think More Broadly About Slate
As institutions increasingly use Slate across admissions, student success, and advancement, there’s an opportunity to think more broadly about the role of an enterprise CRM. Rather than viewing Slate as supporting three distinct areas, what if we considered all the other campus processes and relationships that could benefit from operating within that environment?
If an institution already uses Slate for admissions, could that investment also support continuing education and workforce development? If Slate supports advising and early alerts, is tutoring or coaching still being managed in separate applications? And if advancement is managing constituent relationships in Slate, could event registration become part of that same environment?
Beyond Admissions, Advancement, and Student Success
Think about student success for a moment. We talk a lot about providing students with coordinated support, but how coordinated is it when advising, tutoring, and coaching all operate in different systems? We’ve seen institutions use Slate for everything from tutoring appointments and attendance to early alerts and student referrals. What could we accomplish if more of those services were connected, with the right information available to the right people?
And it’s hardly limited to student success. Scholarship applications, academic petitions, research opportunities, and alumni volunteer signups are all examples of processes that institutions are managing in Slate today. Many of these activities have similar needs: collecting information, managing approvals, communicating, and tracking participation. Do they really need their own applications?
Continuing education offers a particularly good example. One university brought noncredit registration, reporting, and communications into Slate and was able to eliminate several separate email marketing subscriptions. They also integrated with their learning management system to automate work that had previously required manual coordination. They didn’t eliminate every system, but they found ways to simplify the work and get more out of the technology they already had.
The Cost of Keeping Everything Separate
The obvious benefit is potentially reducing software expenses. But I think there’s a bigger opportunity here. Every separate application comes with work that someone has to manage. Integrations need maintenance, data needs to be reconciled, users need support, and reports often require pulling information from several places. And when those systems don’t quite do what we need, someone inevitably creates another spreadsheet.
Over time, those workarounds and dependencies can become technical debt. We’re spending time and resources maintaining the connections between systems rather than improving the processes themselves. Of course, moving a complicated workflow into Slate doesn’t automatically make it simpler, and we need to consider what it will take to build and support it.
Then there’s the information we’re collecting along the way. Think about everything an institution learns about a student, from their initial interests during recruitment to their academic experiences, campus involvement, and eventual relationship as an alumnus. How much of that information lives in separate systems, collected for one purpose and never really used again?
I’m not suggesting every department needs access to everything. But when we bring the right processes and information together, we have an opportunity to better understand those relationships, coordinate our work, and make better use of what we already know. That takes thoughtful planning, particularly when institutions operate multiple Slate instances, but it’s an opportunity worth exploring.
Maybe It’s Time for a Broader Review
I can’t convince every soccer, lacrosse, and field hockey organization my daughters participate in to use the same application. Fortunately, colleges and universities have a little more control over the technology they choose to support their own operations.
For institutions already using Slate, I think there’s a real opportunity to take a broader look at the smaller applications and processes operating across campus. Not just whether we’re getting the most out of our admissions or student success instance, but what else we’re maintaining that might fit within our larger CRM strategy.
A campus-wide business process and application review could be a good place to start. What systems are departments using? What are we paying for them? When do those contracts renew? What processes are still managed through spreadsheets, and where are staff spending time connecting information between systems?
From there, we can evaluate what makes sense to bring into Slate, what should remain separate, and where better integrations might be the answer. The goal isn’t to move everything into one platform. It’s to identify opportunities to reduce unnecessary spending, simplify our work, and get more value from our existing investment.
Maybe before the next software renewal or request for a new application, we should take a closer look at what we’re already using and ask whether there’s a better way to manage that work.
We might be surprised by how much more we could be doing with Slate. If you’re interested in bringing more of your campus processes into Slate, SIG can help.