TAP TAP GO
Record the comparison
Summarise the problem, shortlisted options, evaluation criteria and evidence reviewed. State the reason for the selected approach without rewriting the process as though there were no trade-offs. Include material limitations, workarounds and assumptions. Avoid relying on a meeting recording or a long email chain as the only record. Someone new to the project should be able to understand the decision quickly.
Preserve review triggers
Identify the conditions that would justify revisiting the choice, such as a change in scale, scope or dependency. Record the owner responsible for monitoring those triggers. Keep the decision separate from the contract and implementation plan while linking to both where appropriate. A good record does not prevent future change; it makes change more informed by showing which assumptions have held and which no longer apply.
Put the guide to work
Attach the final evaluation criteria to the decision record. Without them, a later reviewer may judge the choice against requirements that did not exist at the time. Clear context makes it easier to distinguish a reasonable earlier decision from a current need that has changed.
Hypothetical example
A company selects a service because it fits a small regional team with limited administration. Six months later, a larger rollout is proposed. The decision record shows that scale was an explicit assumption, prompting a fresh evaluation rather than automatic expansion.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
