A new ERP can create the opportunity to improve how a university works. But that opportunity can be lost when a project begins with screens, settings, and software choices before leaders agree on the work the system needs to support.
Higher education depends on processes that cross departments: hiring a research assistant, approving a purchase, managing a grant expense, onboarding an employee, or tracking a budget. If these processes are unclear or unnecessarily complicated, configuring a new system around them may carry the confusion forward. The technology changes, but the work does not get better.
A business process-first approach reverses that order. It starts with institutional responsibilities and outcomes, then uses those priorities to guide technology decisions. The goal is not to configure less for its own sake. It is to make sure each technology decision supports a clear, useful purpose, and that the resulting system is something people can use in their daily work, not shelfware.
Start with the work, not the software
An ERP project affects more than IT. It changes how finance, human resources, procurement, academic departments, research administration, and other teams carry out their responsibilities. Each group may have different needs, but their processes often intersect.
Consider a purchasing request. The request might begin in a department, pass through budget review, move to procurement, and end with receiving and payment. If those stages are designed separately, staff may encounter duplicate entry, unclear ownership, or delays at handoffs. A system can make each step digital without fixing the underlying experience.
Starting with business processes gives leaders a way to ask useful questions before configuration begins:
What outcome should this process produce?
Who is responsible at each point?
Where do decisions, approvals, and handoffs occur?
Which steps support a necessary institutional purpose, and which create avoidable effort?
What should employees be able to see and act on?
These questions help an institution distinguish between practices that should continue, processes that need improvement, and requirements that may reflect old system limitations rather than current needs.
The University of California, Davis, for example, describes process design as part of ERP implementation planning. Its process design overview illustrates why institutions benefit from considering future work practices alongside technology.
Make role-based dashboards useful from the first login
The start of the day begins with reviewing Role Based Dashboards, with tasks associated with each employee’s responsibilities. That first view should help a person understand what needs attention, what is waiting, and what action they are expected to take.
For a department administrator, that may mean requests awaiting review or items requiring follow-up. A finance employee may need visibility into approvals or exceptions within their area. A manager may need a view of pending decisions and key indicators relevant to their team.
The specific information will differ by role. The principle is the same: dashboards should reflect the work people are accountable for, not simply display whatever information is easiest to place on a screen.
When role responsibilities and process steps are understood early, the institution can make more informed decisions about which tasks, alerts, and information belong in each user’s view. That can reduce unnecessary searching and help employees focus on actions relevant to their work. It also gives leaders a stronger basis for evaluating whether the system is supporting day-to-day operations.
A dashboard that looks polished but does not help a person do their job is not a successful outcome. The measure is whether employees can recognize their responsibilities and take the right next step with confidence.
A five-phase path from process understanding to adoption
CD&A Consulting Services Inc.’s business process-first approach follows five phases: Discover, Design, Build, Test, and Deploy. The phases connect institutional priorities to practical use of the system.
Discover: Establish a shared understanding of the current environment, work priorities, and desired outcomes.
Design: Define how key processes should work and what employees need from them.
Build: Align technology decisions with the intended processes and responsibilities.
Test: Confirm that representative users can complete important work as expected.
Deploy: Prepare people and operations to use the updated processes with confidence.
The phases are not a reason to postpone learning about the platform. Teams can consider standard capabilities as they discuss how work should be done. The important distinction is that software menus do not dictate the university’s operating model. Process goals inform technology decisions, and the technology is evaluated in that context.
This approach is platform-agnostic. It can be applied in projects involving Infor CloudSuite environments (including FSM, CloudSuite Industrial (SyteLine), or CloudSuite Public Sector (Luma)) as well as Banner/Ellucian environments or custom system configurations. The systems differ, but the leadership questions remain: What outcomes matter? How should work flow? What do employees need to do their jobs?
Reduce the risk of carrying old problems forward
When configuration leads the conversation, there is a risk that teams will recreate the old environment in a new one. Existing approvals, duplicate steps, departmental workarounds, and inconsistent definitions can be carried forward simply because they are familiar.
That can create a system that is technically live but difficult to use. Employees may keep separate spreadsheets, route work through email, or avoid functions they do not trust. The institution then pays for technology that does not deliver its intended operational benefit.
A process-first approach helps leaders make deliberate choices. Some existing practices may still be necessary. Others may be simplified or standardized. Certain exceptions may need to remain, but they should be understood rather than inherited by default.
The aim is not to force every department into the same process. It is to identify where consistency improves clarity and where real institutional needs call for different treatment. Clear decisions can help reduce rework, support adoption, and give project teams a more stable basis for planning.
CD&A has also explored how business process transformation can reduce administrative friction in higher education and why legacy data deserves early attention in an ERP project. Both topics reinforce a broader point: technology change is more valuable when it is connected to the work and information the institution relies on.
Test the experience people will actually have
Testing is more meaningful when it reflects real responsibilities and scenarios. Can an employee complete the task they are expected to perform? Can a reviewer understand what is waiting for them? Does a handoff make sense to both the person sending work and the person receiving it?
These questions are more useful than checking a screen in isolation. A complete process may involve several roles, decisions, and departments. Testing with representative users can surface unclear responsibilities, missed steps, or gaps between the intended process and the actual experience.
That perspective also helps make deployment more practical. Employees need to understand not just where to click, but how the updated process relates to their responsibilities. When the process is clear, training can focus on the work people need to complete and the decisions they need to make.
A stronger starting point for ERP leadership
For higher education leaders, a CloudSuite ERP project is an institutional change effort as well as a technology investment. Starting with business processes helps keep the focus on outcomes: clearer responsibilities, more useful role-based dashboards, less unnecessary effort, and a system that supports rather than obstructs daily work.
The first question should not be, “How should we configure this screen?” It should be, “What does the institution need people to accomplish, and what process will help them do it?”
When those answers guide the project from Discover through Deploy, configuration has a purpose. Employees can see how the system relates to their work, and leaders have a clearer basis for assessing whether the investment is delivering value.
CD&A Consulting Services Inc. supports ERP consulting, business process transformation, and IT program and project management. To discuss a process-first perspective for your institution, visit CD&A Consulting Services Inc..
© 2026 CD&A Consulting Services Inc. All rights reserved. No part of this article may be reproduced or transmitted in any form without written permission from the author.
