When a Tool Rollout Takes Choices Away

For years, the creditors clerk had a way of working. Supplier invoices came in, were sorted by due date in a folder, checked against delivery notes in an order she had refined over time, and captured in batches on Tuesday and Thursday. It was not written down anywhere, but it worked, and she could explain every step of it.

Then the business introduced a new finance system. Invoices now arrived in a shared queue, had to be processed in the order the system presented them, required fields she had never needed before, and could not be saved until every one was filled. Her batches were gone. So was the order she had chosen. The new process was, on paper, more efficient. In practice, she spent the first months working the way the software wanted rather than the way she knew.

Tool rollouts are usually discussed in terms of features, cost and adoption. Less often discussed is what they remove: the small, accumulated choices people had about how to do their own work.

What a standard process takes, and why

Standardising a process through software has real benefits. It reduces errors from inconsistent methods, makes work easier to hand over, and creates a record that others can follow. Many businesses introduce new finance and admin tools precisely because personal methods had become a risk: work that only one person understood, or that fell apart when they were away.

But standardisation is not neutral. Every mandatory field, fixed sequence and locked template is a decision made on behalf of the people who will use it. When those decisions are made by a vendor's default configuration or a project team that never did the work, they can strip out choices that were doing useful work, such as the clerk's habit of checking delivery notes first.

Mellorca has written about how software purchases can go wrong in buying business software without letting the demo decide, and about the business cost of buying software for every process problem. The human side deserves its own attention.

What the guidance says about change and control

The UK Health and Safety Executive's Management Standards on work-related stress include a standard on change. It sets as a goal that organisations engage employees frequently during change, and lists states to achieve, including timely information about the reasons for change, adequate consultation with opportunities to influence proposals, information about the probable impact on people's jobs, and access to support and training.

Prosci's ADKAR model, widely used in change management, makes a related point from a different direction. It frames change as happening one person at a time, through awareness of why the change is needed, desire to take part, knowledge of how to change, ability to do it in practice, and reinforcement to sustain it. A rollout that delivers training but skips awareness and desire may produce people who know how to use the tool and still resent it.

The UK Government's Service Manual, written for public digital services, is blunt about the design side: if you do not understand who your users are or what they need, you cannot build the right thing, and opinions not grounded in user research should be treated as assumptions to be tested. Internal staff are users too.

The human tax

The tax here is autonomy and, often, confidence. People who were competent and self-directed under the old method can find themselves slower, unsure and dependent on others for help. Their expertise in the old way of working loses value overnight. Some will adapt quickly and welcome the structure; others will grieve the method they built. It would be wrong to assume one response is right. What can be said is that a rollout that does not ask what people were doing, and why, risks removing good choices along with bad ones.

An illustrative example

Consider an illustrative case: a Rustenburg mining-services company with about seventy staff. It moves from a desktop accounting package and email-based purchase approvals to a cloud finance system with built-in workflows. The project is led by the financial manager and an implementation partner. Configuration follows the partner's standard template.

In this scenario, the purchasing officer discovers that she can no longer split an order across two suppliers, something she did regularly to secure stock during shortages. The creditors clerk loses her batching. A site administrator finds that the new mandatory cost-centre field has options that do not match how sites actually work, so he picks the closest one, and the reports become less accurate. Each problem is small. Together they make the system feel like something done to the team rather than for it. Mellorca has explored a similar dynamic in why CRM adoption problems are often workflow problems.

What could realistically change

Learn the current method before replacing it. Sit with the people who do the work and ask what they do, in what order and why. Some of their choices will be habit. Others will be protecting against real problems.
Decide deliberately which choices to keep. Not every personal method should survive, but the ones that matter should be built into the new configuration rather than lost by default.
Leave room for safe flexibility. Where risk allows, let people choose their own order of work, save drafts, or undo mistakes easily. Nielsen Norman Group's guidance on user control and freedom stresses clearly marked ways to exit, cancel and undo, because people who feel trapped by an interface become frustrated.
Explain the reasons. When a choice must be removed, say why. A mandatory field that exists for VAT compliance is easier to accept than one that seems arbitrary.
Plan a review after go-live. Ask users after a few weeks what is not working, and change the configuration where it makes sense.

What changes first, and the human dividend

The first change is in how the rollout feels. People who were consulted recognise their own work in the new tool. Fewer workarounds appear, and the data entered is more accurate because the options fit reality. The business outcome is better adoption and fewer post-launch fixes.

The human dividend is autonomy preserved where it matters. People keep some say over how their work is done, and their expertise carries into the new system rather than being discarded. That is a different experience from having a tool arrive fully formed. Mellorca has looked at a related loss of control in when the system decides what you can do today.

The trade-offs

Consultation slows projects. Learning current methods and reviewing configurations takes time and costs money, especially with an external partner.
Keeping choices can keep risk. Some personal methods exist because they hide errors or avoid controls. Preserving them uncritically can undermine the purpose of the new system.
Flexibility reduces consistency. The more variation a system allows, the harder it is to report on and to hand over.
Not every loss can be avoided. Some choices will go, and people may still feel the loss even when the reason is sound.

Why it matters

A new finance or admin tool can genuinely improve how a business runs. But the improvement is often measured only in speed and control, while the loss of individual choice goes unrecorded. Mellorca's interpretation is that the people who did the work before the tool arrived usually know which of their choices mattered. Asking them, and building what matters into the configuration, turns a rollout from something that takes choices away into something that keeps the right ones.

Sources and further reading

Management Standards - Change - HSE (last verified 10 October 2026)
The Prosci ADKAR® Model - Prosci (last verified 10 October 2026)
Learning about users and their needs (last verified 10 October 2026)
User Control and Freedom (Usability Heuristic #3) (last verified 10 October 2026)