Stakeholder brief
The payments API is ready in week 8, warehouse integration in week 6, and 4,000 open spreadsheet cases have duplicate IDs and missing status timestamps. Launch is week 10.
Decision brief
Build a dependency map and critical decision dates. Define data profiling, mapping, deduplication, trial migration, reconciliation, cutover, rollback and ownership. State go/no-go criteria.
Deliverable template
Problem / evidence / assumptions: Options and tradeoffs: Recommendation and rationale: Decision owner / governance: Dependencies / risks / mitigations: Success measure / review date:
Worked example & tradeoffs
Use a stub for early integration tests but reserve end-to-end payment tests after week 8. Preserve source IDs in an audit field; send ambiguous duplicate cases to business owners rather than deleting them. Reconcile record counts, monetary totals and open-case states by cohort. Pilot before full cutover; freeze or delta-sync writes. Roll back only with a plan for payments already sent, since database rollback cannot reverse external money movement.
One defensible approach. Your decision can differ if your evidence and tradeoffs support it.
Write the artifacts in your own words. Use identifiers to connect the objective, requirements and tests.