Observed evidence
Incidents, accepted work, release history, operational data, dependency maps or other artefacts that can be inspected.
Technology advisory
Evidence worth asking for
A strong technology recommendation should make its evidence visible. Before accepting a recovery plan, architecture choice or delivery forecast, ask which facts support it, which assumptions remain unresolved and what result would cause the recommendation to change.
Decision ownership
The person accountable for accepting risk, changing scope, approving a release or choosing between options.
Uncertainty
What remains unknown, how material it is and how the team intends to reduce that uncertainty.
Outcome test
What observable measure will show whether the intervention improved delivery, reliability, trading or decision confidence.
See Farhan Islam's advisory approach for how evidence is separated from assumption, or use the illustrative recovery scenarios as a preparation guide before a discussion.