AI Implementation Brief
Turn architecture work into an implementation-ready brief without losing the decision, context, governance, and operating assumptions.
Fill this onlineTemplate preview
The exact sections inside the download.
Frame the operating decision
Who uses the system, and what role do they play? Which sources, records, or memory inputs are required? Use the combined view to name the business outcome, source of truth, and owner who will decide whether to proceed.
Set the control boundary
Which systems must the workflow read from or write to? Which approval, permission, or audit controls are required? State the risk to avoid, review or escalation route, and record needed to keep the workflow controlled.
Commit to the first move
What will show that the first release works? What is included in the first release? Record the smallest safe scope, baseline, owner, evidence, decision date, and next action.
Decision summary
What is included in the first release? What should explicitly wait? Summarize the proposed move, operating benefit, and the evidence that supports it.
Evidence and control
What must be true before the system is live? State the source, review boundary, accountable owner, and condition that would require revision or pause. Keep the decision receipt with the workflow record.
Next review
Record the decision owner, evidence source, review date, and the explicit condition to scale, revise, defer, or stop. Confirm how the resulting decision will be communicated, implemented, and retained in the operating record.
01 / 03
Frame the decision
Name the real operating need before designing a solution.
Give the implementation a working name that reflects the workflow.
Name what the system helps users do.
Internal operators, leadership, customers, advisors, or a specific team.
How to use it
Start with one real decision.
Complete the canvas with the workflow owner, then use the blank areas to expose missing context and controls.
Before you begin