Technology Selection

Technology selection is the choice of an approach, and the tools that support it, so that a defined need is met under real constraints. It covers more than picking a product name. Extending an existing system, configuring a purchased service, building a narrow component, or keeping the current process while fixing its data are all candidate approaches, and the need does not predetermine which one wins.

The requirements come before the shortlist

For an invoice-evidence lookup, the need is that an authorized clerk finds the right order and receipt records and verifies them. Requirements such as permitted-record retrieval, a displayed result within two seconds under an agreed workload, branch isolation on every access path, and an export that keeps identifiers intact are written before any vendor demonstration. Each product is then judged against those conditions rather than the conditions being adjusted to fit a product.

Mandatory conditions act as gates: an option that fails one is not acceptable in the current scope, whatever its price. Preferences rank the options that pass. Calling every convenience mandatory makes the shortlist arbitrary, so each gate should carry the need or obligation behind it and the person who owns it.

Evidence has three states

For each requirement and option, record demonstrated support, demonstrated failure, or unknown. A supplier’s roadmap promise stays unknown until the version and deployment you would actually use has been tested. A fast demonstration on small cached samples is evidence about that demonstration, not about the clerk’s workload.

Operation, total cost over a stated period, and exit belong in the decision, because the team that must run, pay for, and eventually replace the technology inherits those conditions. GOV.UK’s guidance on defining user needs includes the skills, commercial, and operational needs around a technology change, and its Technology Code of Practice adds points such as open standards and purchasing strategy.

References: GOV.UK: Define user needs, GOV.UK: Technology Code of Practice. Examples here are illustrative and name no actual product.