The one-page investment proposal
Customer task. Which need will be met better? Baseline. How often does it occur, how is it handled today and where do cost or errors arise? Change. What will the system do and what remains with people? Dependencies. Which data, rights, providers and agreements are required?
Evidence. Which complete process will actually be verified? Economics. What additional effect is expected and what migration might occur? Expansion. Under which observed conditions will the company expand, repair or stop? Do not manufacture precision. One decisive unknown is more useful than three unsupported decimal places.
The mandate card
Write the permitted action in one sentence. Identify principal, executing actor, object group, amount limit, currency, period and exceptions. State which changes require renewed approval. Identify where policy is enforced and how revocation operates.
An explicitly illustrative example: an agent may reorder approved consumables for one cost centre if total and delivery remain within an authorised range. New products and addresses require separate approval. Actual design depends on the organisation.
The outcome record
Record input, relevant configuration, data used and observed effect. Separate proposal, approved action and persisted result. Note a counterexample and the observed response. Evidence should be understandable without exposing every internal conversation.
When problems arise, this helps distinguish a missing capability, broken integration and a disproved assumption. That distinction saves more time than the general label “unreliable agent.”
The incident discussion
What did the customer want? What was permitted? What did the system do? Where did the first divergence occur? What consequences followed? How was state corrected? Which specific change prevents recurrence? Each answer needs an authoritative source.
Start with the first wrong information or action. Improving only the final wording is insufficient if the stored order is wrong. A more polite apology is good service, but not yet a technical repair.
The monthly leadership sheet
Show task volume, correctly completed processes, unauthorised executions, correction work and incremental economic contribution. Add the most important unresolved assumptions and the next concrete repair. Explain declining aggregate measures through individual causes.
Do not demand ever-longer reports. The sheet should enable a decision: continue, remove a constraint or change scope. If it merely records activity, it has missed its purpose.