Colour theme
Book a consultation

Owning the technology your business depends on

Identify the technology behind customers, staff, records and suppliers, then assign ownership, support and recovery decisions.

A person typing on a laptop with a larger monitor in the background.

A business doesn’t need to call itself a technology company to depend on technology. Orders, staff access, customer communications and supplier records can all stop when a system becomes unavailable.

Write those dependencies down and give someone the authority to manage them.

Start with the work that matters

Ask which tasks create revenue, deliver services or meet obligations. Map the systems, records and people each task requires.

Include less visible dependencies such as identity, domain registration, internet service and a specialist supplier’s account.

Walk through a normal day, then ask what stops if the internet, email or a key app goes down.

Include customer-facing systems

Review the website, payments, appointments and call handling. Identify who maintains information and who receives failures or customer questions.

A service may be running while the customer journey is broken. Test that requests reach a person and records arrive where staff need them.

The customer-side technology checks can help make that review concrete.

Assign staff and device responsibilities

Confirm who provides devices, applies updates and changes access when staff join or leave. Identify a support route that works for remote staff as well as the office.

Don’t let the business depend on one employee’s personal account or on steps only they know. Make sure a second person has access and can follow written instructions.

Give records an owner

Specify where important records belong, who may access them and how the business keeps or disposes of them. Include information held in external tools.

Check that the staff who should have access can retrieve the records needed for a real task. Being able to find a file doesn’t mean it’s the right version, that only the right people can open it or that you could restore it.

Review supplier dependencies

Keep current contracts, renewal dates, support contacts and a way to export your data. Ask what the supplier does and what remains your responsibility.

The Cyber Centre’s cloud contract guidance explains this division for cloud services.

Plan how essential work would continue if the supplier went down or you had to replace the service.

Treat automation as an owned process

Use automation or AI for a specific task, and decide up front how you’ll check that it works. Name someone to handle the cases it gets wrong and to maintain it.

A new tool is another dependency. Count the work of running it before deciding whether it helps.

Budget for operation and recovery

Include licences, support, maintenance, replacement and tested recovery. Confirm priorities for an interruption using the business interruption guide.

Cloud storage doesn’t help when the internet connection or the sign-in system is down. Test what staff can still do during an outage.

Review ownership regularly

Keep a short list of systems, business owners, technical owners and unresolved decisions. Revisit it after significant changes and before renewals.

The IT consulting service can help turn that list into a plan with priorities and next steps.


Featured Image Credit