Your staff know the job. Why must they also memorise the software?

Recognise the hidden work.

A simple request can turn into a series of small tasks: find the right screen, remember the filter, export a list, ask someone to check it, and explain the result to another person.

Schools often develop a dependency on the colleague who knows the system best. That person becomes a guide for other people’s routine work as well as their own.

Begin with the intention.

An agentic ERP experience offers a different starting point. A person expresses what they need, such as a summary of pending requests or help preparing an update. The system helps surface relevant information and guide the work forward.

This does not mean every request should happen automatically. The person’s role, the context, and the consequences of an action still matter. A useful experience makes the next step clearer and gives people the right opportunity to review it.

Evaluate a workflow, not a buzzword.

Ask to see a familiar task from beginning to end. What information is needed? Who can access it? What happens if something is missing? Where does someone review a decision or message?

These questions turn a broad technology promise into an experience your staff can judge. They also make the rollout conversation much more practical.

Confidence is part of adoption.

The aim is not to make people care more about software. It is to let them concentrate on the institution they already care about. A clearer way to work can help a team start with its own expertise and build confidence from there.