Technology assessment · Evidence planning · Product strategy
How do you scope a product or technology assessment around a decision?
Match the assessment’s questions, evidence access and specialist depth to the decision it must support. Agree what an early view can establish, how new questions change the work and what the final report will cover.
Name the decision and the version being assessed
Start with the choice the assessment must inform, who will make it and when. Evaluating a proposed integration, selecting a product and designing a new strategy call for different work. Specify whether the assessor should test an existing plan or develop alternatives.
HM Treasury’s Magenta Book frames evaluation around decision needs, useful timing and proportionate methods. Apply that discipline to the commission: name the relevant products, operating context and planning horizon, then identify which uncertainties could materially change the choice.
Record the plan and product versions in scope. List exclusions alongside included work, especially specialist testing. A broad product review should not imply that security testing, customer research or intellectual-property analysis has also been commissioned. Assign responsibility for conclusions that cross disciplines.
Match each question to an achievable evidence plan
For each important question, agree the evidence needed, the access required and the person responsible for obtaining it. Check existing material before requesting new presentations. A useful operating record may answer more than a newly prepared summary, while requiring less work from the team.
GOV.UK’s user-research planning guidance connects questions, participant groups and research activities. Use the same connection when commissioning discovery: customer interviews can address buying behavior; technical specialists can inspect implementation; a demonstration can expose the steps of a workflow.
When direct access is unavailable, narrow the conclusion accordingly. Public interfaces and documentation can reveal questions worth investigating, while leaving internal operation unresolved. State what the assessment can establish with available access and which decision would still require additional evidence.
Agree checkpoints and a way to change the scope
Give an early readout and a final report separate completion conditions. An interim concern may need immediate attention before the wider inquiry is finished. Reserve time for substantive review and correction before a decision-maker relies on the final conclusions.
The UK government’s analysis standard distinguishes commissioning, analytical work, assurance and approval. Translate those responsibilities into named owners and review dates. Agree who consolidates findings, who challenges them and who accepts each deliverable.
When a new question arrives, identify the additional evidence, expertise and access it needs. Then choose whether to replace lower-priority work, extend the commission or leave the question open. Update the scope and report promise together so the final comparison describes the work actually completed.