FROM FIRST CONVERSATION TO A CONNECTED DAY
A thoughtful start. A practical path forward.
Plan the change around your institution’s calendar, people, and priorities. Give each stage clear responsibilities and a decision before moving on.
Produce a first-phase brief naming the population, workflows, accountable sponsor and constraints. Record what remains outside the phase and the dependencies on identity, billing or academic structures. A list of desired modules is not yet an agreed operating scope.
- 01
Discover
Map your institution, current systems, priorities, and the people who own each process.
- 02
Configure
Agree academic structures, roles, permissions, workflows, and the first launch scope.
- 03
Migrate
Map, clean, import, and reconcile the records needed for the agreed phase.
- 04
Prepare
Train administrators and role-based teams using realistic tasks and a practice environment.
- 05
Launch
Pilot with an agreed group, review readiness, and move into a staged rollout.
- 06
Improve
Review adoption, resolve follow-ups, and plan the next institutional priorities.
A plan your teams can work with.
Your discovery conversation should produce a scope, responsibilities, dependencies, milestones, and acceptance criteria. Timelines depend on institution size, data readiness, integrations, and the chosen launch scope.
A CLOSER LOOK
What each launch decision should leave behind.
A rollout becomes manageable when its outputs are explicit. The next team needs something it can use: an approved scope, a reconciled record set, a tested workflow or a clear support responsibility.
Before configuration
Produce a first-phase brief naming the population, workflows, accountable sponsor and constraints. Record what remains outside the phase and the dependencies on identity, billing or academic structures. A list of desired modules is not yet an agreed operating scope.
Before go-live
Review a normal workflow and a common exception with the people who will use them. Record data acceptance, role permissions, unresolved issues and the person authorized to accept each remaining risk. Choose the launch date around readiness and the institutional calendar.
After the first operating cycle
Review the work people actually completed, the questions reaching support and the handovers that still stall. Use that evidence to prioritize changes before expanding to another team or campus. Carry unresolved actions into the next phase with their owners.
ImplementationBefore configuration → After the first operating cycleSEE HOW THE WORK CONNECTS
A rollout with explicit acceptance points
Agree what readiness means before moving into the next phase.
- 01
Before configuration
Produce a first-phase brief naming the population, workflows, accountable sponsor and constraints. Record what remains outside the phase and the dependencies on identity, billing or academic structures. A list of desired modules is not yet an agreed operating scope.
- 02
Before go-live
Review a normal workflow and a common exception with the people who will use them. Record data acceptance, role permissions, unresolved issues and the person authorized to accept each remaining risk. Choose the launch date around readiness and the institutional calendar.
- 03
After the first operating cycle
Review the work people actually completed, the questions reaching support and the handovers that still stall. Use that evidence to prioritize changes before expanding to another team or campus. Carry unresolved actions into the next phase with their owners.
Illustrative workflow · Shape the details around your institution.
MAKE THE PLAN YOURS
Ready for a manageable first phase?
Use this session checklist to identify what is ready and what needs an owner.
0 of 5 ready
Plan around the real dependencies.
Can we begin with one team or campus?
A pilot is useful when it represents the important workflow and its dependencies. Define what it must prove and how findings will change the wider rollout.
Who decides whether to launch?
Named institutional and delivery owners should review the agreed acceptance criteria, unresolved issues, data checks, and user readiness before the go-live decision.
How long will implementation take?
Confirm scope, source-data quality, integrations, decision availability, and institutional dates before agreeing a schedule. The plan should make dependencies and acceptance gates visible.
YOUR CONTEXT COMES FIRST
Let’s make it specific to your institution.
Bring your people, processes, and priorities into the conversation.