Name the task first
Before comparing features, write down the work you need to do. Identify the people involved, the input data and the output they need. A teaching exercise, a research comparison and a clinical task call for different evidence and approvals.
Ask what has actually been tested
Separate the product roadmap from verified behaviour. Ask which inputs were used, how failures were counted and what the comparison was against. A promising example is a starting point for an evaluation, not a reliability estimate.
Follow a file through the workflow
Check how the software carries units, orientation and processing details from import through export. Reopen an exported file in the intended receiving tool and compare it with the source project. Record settings so another person can repeat the check.
Understand the operating environment
Ask about the supported operating system, storage location, account requirements and network connections. Work out what stays on the workstation and what is sent to a service. Use authorised data and your organisation’s approved environment.
Agree on the next decision
An evaluation is most useful when it answers a specific question. Set success criteria and stopping conditions before starting. For Wellbeing, the current conversation is about research and product development; the software is not ready for clinical use.