Customization vs Configuration in Higher Ed Cloud Technology
2 min read
The word custom gets thrown around a lot in higher education technology—especially during transitions from legacy, on-premise systems to modern cloud platforms like Workday, Slate, or Handshake. But here's the catch: custom doesn't mean the same thing across these systems. In fact, its meaning shifts pretty dramatically depending on your tech stack.
Let’s break it down.
Cloud Technology: “Custom” with Guardrails
In the cloud world, custom typically means configured. You’re not diving into source code or restructuring databases—you’re working within the boundaries of the vendor’s platform. Think of it as customizing within the lines: using delivered fields, configurable reports, and integration tools that play nicely within the ecosystem.
You’ve got flexibility, yes, but you’re coloring inside the lines.
On-Prem Systems: Deep Custom Control (and Debt)
With legacy systems like Banner, Oracle, or Colleague, custom means something else entirely. You own the stack, and that means you can tweak—or break—almost anything: the code, the data structures, even the underlying infrastructure.
Sounds powerful, right? It is—but that power comes at a cost: technical debt, high maintenance, and a risk of breakage every time a vendor releases an update. That kind of custom is more like building your own off-road trail than configuring a cloud dashboard.
“Custom” Is Like a Language Translation
It reminds me of how words change meaning between languages. In English, gift is a good thing. In German, Gift means poison. Same word, totally different vibe.
Custom is the same. In legacy tech, it’s deeply technical. In cloud platforms, it’s mostly configuration within a structured framework.
Reframing How We Think About “Custom Reports”
I often hear folks hesitate to use a "custom" report or dashboard in Workday—like it’s something risky. But if you’re using delivered fields, building within the framework, and respecting release cycles, then guess what? You’re not going rogue. You’re configuring!
Even though the button says “Create Custom Report,” what you’re really doing is building a configured report that helps:
Cut down user clicks
Reduce frustration and shadow tracking
Support smarter decisions with targeted data
Should We Just Rename It?
Honestly, I wish we could rebrand “Create Custom Report” to something like “Create Configured Report.” It would save a ton of confusion. Maybe it’s time for a new brainstorm—anyone else miss that feature in Workday Community?
If you work at an institution and have questions about building custom reports in your Workday Student, complete this form to schedule a complimentary consulting session or email us at info@legatostrategic.com.
To have articles delivered directly to your mailbox, subscribe!
