Technology investment deserves a business owner

The technology proposal has a delivery plan, a supplier and a budget. The chief information officer can explain how the system will be implemented. The board is ready to approve it.

One question still deserves time: who in the business will be responsible for making it useful?

A new system often requires departments to change their processes, agree common data and give up familiar ways of working. Those decisions can sit beyond the authority of the team asked to deliver the technology.

Name the person who can make the changes

An executive sponsor should have more than a name on the first slide. They need authority to resolve competing demands, commit staff time and decide which operating practices will change.

For an illustrative customer-management system, sales may want speed, finance may need reliable billing information and operations may want fewer exceptions. The technology team can explain the options. It cannot settle every disagreement about how the business should work.

The board should understand who can make those decisions and how unresolved issues reach them. Shared responsibility becomes fragile when each department expects another to compromise first.

Approve the operating choices as well as the spend

Before committing substantial funds, identify the important choices still open. These might concern how products are priced, which customer records are authoritative or how much local variation the business will retain.

Some detail can be resolved during delivery. Decisions that fundamentally change the cost, purpose or scope of the programme need earlier attention.

Ask what happens if agreement is delayed. More customisation may look like a convenient compromise, yet add cost and maintenance demands for years. The board needs to see that trade-off when it is made, rather than discover it in a later request for funding.

Give adoption enough time and authority

Training attendance is a limited measure of whether a new system is being used well. Look at actual work: whether people enter reliable information, use the agreed process and stop maintaining unofficial alternatives.

Managers need time to help teams through the change. They also need a route to report genuine problems without every objection being dismissed as resistance.

Ask how customer service, control and continuity will be protected during the transition. Agree who can delay the switch if readiness is inadequate and what evidence would support that decision.

Keep the owner after launch

Once the system is live, project staff and suppliers may move on. The business still has unresolved issues, new responsibilities and assumptions to test.

The named owner should remain accountable for the operating change, with reporting that shows where the new arrangements work and where they do not. Establish who owns ongoing costs, data quality and further changes.

Directors do not need to choose software features. They do need confidence that someone with the right authority will make the investment work inside the business. Approving a system without that person leaves a significant part of the decision unfinished.