Shared System, Local Decisions: The Hard Work of Higher Education Collaboration

State systems are asked to do something organizationally unusual: Create the benefits of scale across institutions that retain their own histories, governance structures, priorities, and relationships with the communities they serve.

The potential advantages of state-wide higher education collaboration are substantial.

• Shared applications and ease of transfer can reduce friction for students.
• Common data standards can make information more useful across institutions.
• Coordinated approaches to transfer, direct admissions, adult learners, and workforce pathways can make a collection of colleges and universities function more coherently for the people moving among them.

The architecture, however, is often easier to imagine than the organization required to support it. Every shared initiative eventually encounters questions about who has authority to make which decisions, where institutional autonomy needs to remain intact, what must be standardized for the education system to work, what efficiencies can be gained, and what can remain different. Formal authority matters, but so does the practical influence of stakeholders who can accelerate, reshape, or slow implementation. Institutions also enter these initiatives with widely varying technologies, staffing models, policies, resources, and readiness for change. Yet systems with the right technology integrated across their institutions are those that are best positioned to consistently serve their students well.

Those conditions suggest a useful distinction between shared infrastructure and standardized decision-making. Systems can build stronger connective tissue among their institutions without requiring them to become more alike. But doing so requires deliberate capacity around governance, stakeholder mapping, data standards, institutional autonomy, implementation sequencing, and communication.

Large-scale initiatives have a natural tendency to begin with design. Teams ask what the platform should do, what data it should collect, what the student experience should look like, and which processes might benefit from centralization.

Those choices quickly encounter questions of governance.  For instance, a centralized application requires someone to determine which information is collected and which requirements remain institution-specific. Shared data requires agreement about definitions, access, stewardship, and responsibility for accuracy. A statewide student pathway can touch admissions authority, academic policy, transfer, advising, and institutional identity.

The earlier those questions become visible, the more deliberately an education system can decide where authority should live. Some decisions may belong at the state or system level, while others with individual institutions, and still others may require collective agreement. There will also be areas where variation among institutions creates little friction for the larger initiative and can remain intact. The aim is to establish enough clarity about decision rights that the architecture reflects the way the system intends to operate.

Org charts capture formal authority reasonably well, but they are less useful for understanding all the relationships through which system-level change actually travels.

Large initiatives move through networks of presidents, provosts, enrollment leaders, registrars, CIOs, institutional researchers, faculty governance bodies, state agencies, legislators, accreditors, system offices, and campus staff. Some participants hold decision rights. Others possess operational knowledge without which implementation will struggle. Some represent constituencies whose support matters even when they do not have formal approval authority.

Stakeholder mapping therefore belongs early in the design of a system initiative. Leaders need to understand:

• Who can authorize the work.
• Who will implement it.
• Who understands consequences that may be difficult to see from a system office.
• Who will ultimately explain the change to students, faculty, staff, policymakers, or the public.

And remember that a useful map reveals more than reporting lines: It shows the path through which decisions, information, influence, and implementation will have to travel.

Any meaningful collaboration will require some degree of standardization. The more consequential question addresses where consistency produces enough value to justify it.

• Common data definitions can make information portable.
• Shared technical standards can allow systems to communicate.
• Common identity infrastructure can reduce friction as students move among institutions.
• Agreed-upon transfer conventions can make academic progress easier to carry from one institution to another.

None of those choices requires every institution to make identical admissions decisions, organize programs the same way, communicate with students in the same voice, or pursue the same enrollment strategy. In many systems, those differences reflect institutional missions, local labor markets, student populations, histories, and community needs.

This is where the distinction between infrastructure and decision-making becomes especially useful. The strongest candidates for standardization are often the connective structures that allow institutions and students to move information, credentials, applications, or academic progress across organizational boundaries. Local discretion can remain where institutional differences carry meaningful value.

Large transformations are often represented as a clean progression from concept to launch. System-level implementation is usually less orderly because institutions begin from different places.

One campus may already have the technology and staffing necessary to participate in a new initiative. Another may need to replace a system, revise policy, negotiate data-sharing agreements, or secure faculty approval. Political conditions and leadership priorities may differ as well, even among institutions governed by the same system.

That variability makes sequencing consequential. Leaders need to know which dependencies must be resolved before later work can begin, which institutions are positioned to move early, where initial implementation can generate useful learning, and which changes can proceed independently while others require coordinated adoption.

System-wide progress doesn’t always require synchronized movement. A carefully designed sequence can allow early institutions to surface problems, establish practices, and demonstrate value while others prepare to participate. Over time, those individual movements can produce change at system scale.

Governance, stakeholder mapping, data standards, autonomy, sequencing, and communication recur across large-scale collaborations. Yet organizations often rebuild the capacity to manage them each time a new initiative emerges. There is an opportunity for systems to treat these capabilities as institutional infrastructure of their own. Teams can develop reusable governance models, stakeholder frameworks, decision-rights structures, data practices, implementation methods, and communication approaches that become more sophisticated with each initiative.

That matters because many of the most consequential challenges facing higher ed increasingly cross institutional boundaries. Transfer, workforce alignment, adult learner pathways, direct admissions, credit mobility, data interoperability, and affordability all require some degree of coordination among organizations that retain distinct missions and responsibilities.

The challenge for state systems is finding forms of coordination strong enough to make those boundaries easier for students to cross while preserving the institutional differences that allow colleges and universities to respond to their communities.

Technology will be part of that work, as will policy, funding, and political leadership. Much of the lasting work, though, will happen through organizational design: deciding what should be shared, where decisions should remain local, and building the capacity to manage the space between the two.

For more insights into current state of system-level enrollment management, download Onboarding Innovation in State Systems: A Blueprint for Transforming Higher Education Enrollment Management today.

And to hear a discussion about what a system can accomplish that its institutions can't do alone, watch The Power and Limits of the System: Rethinking Collaboration Across Public Higher Education.