Technology accountable to the organisation
A business system should improve a defined outcome without creating hidden cost, fragile dependencies or an exit the organisation cannot control. This guide connects the whole decision from the first operational need to renewal or replacement.
Define the users, process, outcome and constraints before comparing products. Model the complete cost, require comparable supplier evidence, test migration and everyday work, control access, preserve a workable fallback and review realised value before every renewal.
Follow the complete business technology route
Procurement is only one point in a longer operating cycle. A credible decision also explains how people will adopt the change, how data and access will move, how work continues during disruption and how the organisation can leave without losing records or control.
Define requirements
Turn the current process, user evidence, outcomes, constraints and acceptance tests into a short decision brief.
Build the business case
Compare the baseline with realistic benefits, whole-life cost, uncertainty, capacity and consequences.
Select a supplier
Give every provider the same questions and distinguish evidence, contract terms, assumptions and promises.
Implement and support
Pilot important workflows, prepare people, define support and use acceptance evidence before wider rollout.
Migrate data
Inventory, map, minimise, test, reconcile and protect data before a controlled cutover.
Manage access
Give named users the least access their roles need and remove or change it when work changes.
Preserve continuity
Set recovery priorities, manual fallbacks, dependencies and tested restoration responsibilities.
Review, renew or exit
Measure realised value, service evidence and exit readiness before a renewal deadline removes choice.
Keep five records throughout the lifecycle
- Decision record: what was chosen, for whom, which alternatives were considered and which assumptions could change the answer.
- Service owner: the accountable person for outcomes, supplier contact, access, continuity, review and exit.
- Cost record: recurring, usage, internal, change, support, migration and exit costs against the original case.
- Dependency map: integrations, identities, devices, data flows, specialist people, subcontractors and manual workarounds.
- Evidence log: tests, incidents, service performance, user feedback, unresolved risks and renewal actions.
Primary sources used to frame the route
- GOV.UK Service Standard: choose the right tools and technology for user impact, total cost, sustainability and future choice.
- NIST SP 1305 for communicating technology supplier requirements and managing supply-chain risk.
- UK NCSC identity and access management guidance for access lifecycle and least privilege.
- UK ICO data protection by design guidance for organisations subject to UK data-protection law.
Procurement, contracting, employment, accessibility, privacy, records and sector obligations vary by country and activity. Verify current requirements for the markets in which the system will operate.
Business technology FAQs
What counts as business technology?
It includes software, cloud services, communications, devices, infrastructure, integrations and data services used to operate or improve an organisation. The decision method should follow the business process and risk, not a narrow product label.
Should a small business use the same process as a large organisation?
Use the same disciplines at a proportionate depth. A small, reversible tool needs a short brief and light evidence; a critical system holding sensitive data needs stronger technical, contractual, migration, continuity and specialist review.
Who should own a business technology system?
Name one accountable service owner, while involving users and the people responsible for operations, finance, data, security, legal duties and procurement where relevant. Supplier responsibility does not remove the organisation’s ownership of the outcome.
Continue your business technology decision
Use the next guide that matches the requirement, investment, supplier, implementation, migration, access, continuity or renewal question you still need to resolve.
