Define the problem and non-software alternatives
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
Start with the operating problem, affected users and current evidence. A tool category is not a requirement. Explain which outcome should improve and how it will be measured. Consider process changes, better configuration or retiring redundant tools before adding another system. Separate essential requirements from preferences and assign a decision owner. Include candidate and operator experience, not only executive reporting. A procurement brief should state what is out of scope so a polished demonstration does not expand the project without a business reason.
Worked example
A team wants an AI scheduler, but the baseline shows most delay comes from managers not reserving interview time. The procurement exercise first tests a working agreement and calendar policy.
Put it into practice
Write a problem brief with three alternatives, including one without new software.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
Each option should address the observed cause. Define a measurable outcome and the evidence needed to justify purchase. Avoid writing requirements as a list of a favourite supplier’s features.
Sources and further reading
Original Academy teaching and fictional examples. These references provide context, not endorsement. Edition 2026.09; updated 2026-09-24.
- GOV.UK: Responsible AI in recruitment
UK guidance on procuring and deploying recruitment AI.
- NIST: AI Risk Management Framework
Voluntary framework for organising AI risks and controls.