Is the business problem this technology will solve clearly defined?
The decision should begin with a genuine business need rather than a product feature or current technology trend.
Review business value, security, privacy, integration, cost, vendor risk, resilience and implementation before introducing a new platform.
The decision should begin with a genuine business need rather than a product feature or current technology trend.
Examples may include reducing administration, improving customer response times, reducing risk or improving reporting.
The business should know how it will measure adoption, time saved, cost, quality, risk reduction or customer outcomes.
A nominated owner should remain accountable for business value, user adoption, approvals and ongoing decisions.
The business should know who will manage users, access, integrations, configuration, updates and vendor support.
People who use or depend on the process should be involved before the technology is selected.
The review should consider account security, authentication, access controls, encryption, logging and known risks.
Important business platforms should support MFA for standard users and administrators.
Users should receive only the access required for their responsibilities.
The business should be able to review sign-ins, administrative changes, data access and suspicious activity.
The business should understand every type of information stored, processed or transferred by the platform.
The business should understand where data is hosted, backed up and processed, including any overseas locations.
The business should assess whether the technology's collection, use, retention and sharing of information is appropriate.
The organisation should retain appropriate rights to access, export and control its information.
The business should know how long information is retained and whether deleted data is removed from backups and related systems.
The business should understand which applications, databases, email platforms and workflows must connect to the technology.
Credentials should not be stored in spreadsheets, source code or personal accounts.
The business should understand what happens when connected systems are unavailable, delayed or return incorrect information.
The business may already own tools that provide similar capabilities or can be configured to meet the requirement.
Compatibility should be confirmed before licences are purchased or implementation begins.
The platform should remain usable and affordable as the organisation expands.
Include licences, implementation, integrations, training, support, data migration, consulting and ongoing administration.
Low initial pricing may increase significantly when the business grows or requires advanced capabilities.
The business should understand its commitments before signing or accepting online terms.
Consider the vendor's history, customer support, security record, financial stability and service availability.
The business should understand support hours, response channels, escalation, service levels and any additional support cost.
Useful evidence may include security policies, independent reports, certifications, incident processes and data-handling information.
The business should understand which operations would stop and how staff would continue working during an outage.
The business should not depend entirely on one vendor without a practical method to recover or export important information.
The business should understand how users, data, documents, integrations and records can be moved to another platform.
A pilot helps confirm suitability, identify issues and collect user feedback before wider implementation.
Users should understand how to use the system, protect information and report problems.
Technology often fails when employees are not prepared for changes to their daily work.
The business should confirm whether expected outcomes were achieved and identify security, cost, adoption or support issues.
Please answer all questions to calculate your technology-review score.