Most higher education transformation projects start with a technology decision: which ERP, which CRM, which student information system to buy. That's backwards. A rigorous current state future state analysis, done before any system gets selected, is what actually determines whether a business transformation delivers value or becomes another line item that never lived up to its business case. 

The pressure to get this right has only grown. The enrollment cliff that institutions have anticipated for years is no longer a future risk. It is already reshaping budgets and staffing decisions on campuses today, according to the Association of Governing Boards. Institutions weighing a major system change or process overhaul cannot afford a transformation that stalls in the ambiguity between what exists today and what leadership wants tomorrow. 

Why Higher Ed Institutions Underinvest in Current State Analysis 

Current state mapping asks a deceptively simple question: what do we actually do today, and why?  For many institutions, rarely does one person know the answer. The registrar's office, financial aid, academic advising, and the provost's office each understand their own piece of the student journey, but few people can trace how a decision in one office affects the others downstream.  

Current state workshops are where that gap usually surfaces first, and it is uncomfortable. Skipping this step feels efficient in the moment. It rarely is. 

A few patterns show up in almost every current state workshop we run on a campus: 

• Duplicate data entry across the student information system and department-level spreadsheets that nobody outside that department knows exist. 

• Approval workflows that persist because “that's how it's always been done,” not because any policy or accreditation requirement demands it. 

• Staff who don't realize how their process handoffs affect enrollment, financial aid disbursement, or advising outcomes downstream. 

• Legacy systems kept alive because the people who built them, and the reasons behind the original decisions, left the institution years ago. 

None of these business process transformation challenges are unique to higher education, but they are harder to untangle on a campus, where academic units, shared governance, and central administration often operate with different priorities and different definitions of urgency.  

Envisioning Future State: Strategy First, Technology Second 

Once an institution understands its current state, the harder work begins: defining a future state. This current state future state analysis should connect to actual strategy rather than a wish list of features. A future state built around growing online enrollment looks different from one built around improving time to degree or protecting margin during an enrollment downturn. The technology that supports either goal might be the same platform, but the configuration, sequencing, and success metrics should not be. 

Albert Einstein put it well: “We can't solve problems by using the same kind of thinking we used when we created them.” A future state that simply automates a broken current process gives an institution a faster version of the same problem. The more valuable business transformation exercise asks which processes should exist at all, given where the institution is trying to go. 

The Transition Zone: Why the Middle Is the Hardest Part 

The transition zone between current and future state is where most higher education transformations lose momentum. Two systems run in parallel while staff are still expected to carry a full workload. Faculty governance timelines rarely match a vendor's implementation schedule. A registrar's office mid-semester has little bandwidth to test a new workflow, no matter how much better it will be once it's live. 

This is also where ownership gets murky. IT often owns the technical rollout, a project sponsor owns the budget, and the departments living with the new process day to day own none of the decisions that shape it. That gap between who decides and who lives with the decision is where resistance to change takes root, and it shows up as missed deadlines, workarounds, and quiet noncompliance long before anyone calls it resistance out loud. 

Shared governance adds a layer of complexity to organizational change management that most corporate transformations do not have to plan around. A curriculum change or an advising workflow redesign often needs faculty senate input, not just an IT sign-off, and that approval cycle can run on an entirely different calendar than a vendor's go-live date. An institution that treats shared governance as a scheduling obstacle rather than a legitimate part of the transition zone usually ends up relitigating decisions it thought were already made. 

Building the Organizational Change Roadmap: Communication, Sponsorship, and Readiness 

An organizational change roadmap supports organizational change management by naming who does what, and when, well before go-live. A few enablers make the difference between a roadmap that holds and one that gets rewritten mid-project: 

• Segment communication by audience. Faculty, staff, and students hear a system change differently, and one all-campus email rarely lands for any of them. 

• Name a sponsor with real authority. Prosci's research on project sponsorship shows initiatives with highly engaged sponsors are far more likely to meet their goals than those where sponsorship is nominal. 

• Run a change readiness assessment before kickoff, not after resistance shows up. Knowing which units are eager and which are anxious changes how you sequence the rollout. 

• Build in a feedback loop. Staff and faculty need a channel to flag when the future state doesn't match how their work actually happens, before the gap becomes a workaround. 

None of this replaces a strong technical plan. It gives that plan a much better chance of surviving contact with an actual semester. 

Kenway's Business, Product, and Digital Transformation practitioners have run this kind of current state future state analysis across colleges and universities working through ERP replacements, shared services consolidations, and business process transformation engagements. The pattern holds across institution types: the transformations that succeed are the ones where leadership understood their current state honestly, tied the future state to real strategic priorities, and built a roadmap that accounted for how a campus actually operates during the transition.  

An institution that skips this groundwork tends to find out the cost later. Budget gets spent on a system that automates the wrong process. Staff build workarounds that quietly undo the intended efficiency. The technology looks modern in a vendor demo and works exactly like the old process in practice, because nobody redesigned the process itself. 

Institutions that invest in this groundwork see a different outcome. Departments understand why a process changed, not just that it did. Leadership can point to a roadmap that connects the new system back to the strategic plan the board already approved. And the transformation keeps delivering value well after the implementation team has moved on to the next project. 

If your institution is weighing a transformation and wants clarity before committing budget, schedule a transformation readiness consultation with Kenway's Business, Product, and Digital Transformation practice.  

Frequently Asked Questions

What is a current state future state analysis?

A current state future state analysis helps an organization understand how its processes, systems, and teams operate today and define how they should operate in the future. For higher education institutions, this analysis can help identify process gaps, clarify strategic priorities, and guide technology and transformation decisions.

Why is current state analysis important for higher education transformation?

Current state analysis helps institutions uncover inefficient processes, duplicate data entry, disconnected systems, unclear handoffs, and legacy workflows before making major technology investments. Understanding these challenges early can help ensure higher education transformation efforts address the right problems rather than simply automating existing processes.

What should an organizational change roadmap include?

An organizational change roadmap should define responsibilities, communication plans, executive sponsorship, change readiness, and opportunities for stakeholder feedback. In higher education, the roadmap should also account for factors such as shared governance, academic calendars, faculty involvement, and departmental priorities.

How can higher education institutions prepare for business transformation?

Institutions can prepare for business transformation by assessing their current state, defining a future state tied to strategic priorities, evaluating change readiness, and developing a realistic transition roadmap. This groundwork can help leadership align technology decisions with business needs while reducing disruption during implementation.