The Situation
A higher education institution had invested in CRM and engagement technology that gave teams greater visibility of student behavioural and engagement signals.
The technology was working.
Information was available. Signals were being surfaced.
But the institution wasn’t consistently seeing the operational value it expected from that increased visibility.
Similar signals could lead to different responses. Some remained under observation without a clear point at which action should begin. Responsibility could move between teams. Staff were using additional tracking, follow-up and cross-team communication to keep work moving.
The question was no longer simply whether the CRM worked. It was what happened after meaningful information became visible.
The Question
The institution needed to understand:
What needs to be true operationally for the information available through the CRM to result in timely, consistent and proportionate action?
That meant looking beyond the technical capability itself.
The issue was whether the wider organisation had the conditions needed to turn greater visibility into consistent action, and ultimately realise more of the value of the capability it had already purchased.
What Was Already Known
The institution already knew that the CRM could surface useful information.
It also had evidence of inconsistency around what happened next.
Signals were visible, but responses could vary. Monitoring did not always have an explicit point at which it became intervention. Responsibility could move between teams, and additional manual activity had developed around the platform.
NDPP did not need to establish whether the technology functioned. The uncertainty sat in the work around it.
What NDPP Did
NDPP conducted a focused diagnostic of the journey between signal and response.
The work combined stakeholder conversations, operational pathway reconstruction, workflow and process review, documentary analysis and examination of the signal environment surrounding the CRM.
Rather than examining the technology in isolation, NDPP traced activity across the wider journey:
enquiry → application → offer-holder → enrolment → early engagement → retention risk → intervention → closure
The work examined:
- what happened after a signal appeared;
- when monitoring became intervention;
- how decisions about action were made;
- where responsibility sat as work moved between teams;
- what happened as the seriousness of a situation increased;
- where manual tracking, follow-up and additional coordination had developed;
- and how the institution determined that an issue had genuinely been resolved.
The purpose was to understand the conditions between visibility and action.
What the Evidence Showed
The primary constraint was not the CRM’s ability to surface information.
The more significant difficulty appeared after the information became available.
Similar signals could result in different responses depending on where they appeared and who received them.
Intervention thresholds were not always explicit.
Responsibility could move between functions without sufficient continuity.
The distinction between continuing to monitor something and taking action was not always clear.
Completing an action did not necessarily establish whether the underlying issue had been resolved, required further escalation or had moved elsewhere.
Staff were compensating for these gaps through additional monitoring, parallel records, manual follow-up and cross-team clarification.
The technology had increased the institution’s ability to see what was happening faster than its ways of working had developed to determine what should happen next.
What Changed
Before the work, the difficulty had been understood largely through CRM adoption, staff consistency and use of the platform’s existing capability.
That made one question appear particularly important:
“How do we get people to use the CRM more consistently?”
The evidence showed that this explanation was incomplete.
Some of the behaviour that could appear to be an adoption issue was serving a purpose: people were compensating for unresolved questions about decision-making, ownership, escalation and workflow.
The question therefore changed to:
“What needs to be true operationally for the signals within the CRM to produce consistent institutional action?”
That changed what became worth addressing.
What Became Worth Doing
The evidence pointed towards targeted organisational requirements rather than wholesale system redesign.
These included:
- clearer responsibility for priority signal categories;
- explicit distinctions between monitoring and intervention;
- clearer thresholds for when action should begin;
- defined conditions for escalation;
- stronger continuity when responsibility moved between functions;
- ways for increasing severity to trigger a different response;
- reduced duplicated monitoring and parallel tracking;
- stronger connections across recruitment, enrolment, student-success and retention activity;
- and clearer definitions of when an issue could genuinely be considered closed.
An important distinction also emerged between organisational requirements and technical requirements.
Some improvements depended first on organisational decisions about responsibility, thresholds, escalation and workflow.
Others could subsequently be supported through CRM configuration.
That distinction prevented the technology from being expected to resolve organisational questions that had not yet been answered.
The Outcome
The immediate outcome was a different and more actionable explanation of the problem, together with a prioritised basis for what needed to change.
The institution had clearer requirements around decision thresholds, responsibility, escalation, workflow continuity and closure.
It also had clearer boundaries between:
what the technology could provide;
what the organisation itself needed to determine;
and
where subsequent technical configuration could support those decisions.
Rather than recommending wholesale system replacement or simply asking staff to use the CRM more consistently, the work established what needed to change around the technology for its existing capability to be used more effectively.
Scope Note
NDPP’s commission ended at the diagnostic and recommendation stage.
NDPP therefore does not claim subsequent effects on retention, conversion, workload or other organisational outcomes that would require post-implementation evaluation.
What This Demonstrates
A functioning technology investment does not automatically create organisational value.
Sometimes the important question sits between the capability the technology provides and what the organisation is able to do with it.
NDPP helped distinguish the two and turn that understanding into clearer organisational and technical requirements.