Find an automation worth operating
Start with a bounded task and its failure modes before selecting tools or a model.
Newton & Carter. Published November 7, 2026; updated November 9, 2026. Version 1.1.
Map the current handoff
Record inputs, decision rights, exceptions and the person who owns the result. A workflow with unclear ownership stays unclear after automation.
Define the permitted action
Separate suggesting, drafting and executing. Identify the approval needed before a message, payment, record update or other external action.
Test the unhappy path
Include missing inputs, duplicates, timeouts, stale sources and conflicting instructions. Agree retry behavior, monitoring and a human escalation route.
References for the work
Use these published resources when defining the requirements for your project.
- NIST AI Risk Management Framework Playbook ↗
Use the voluntary Govern, Map, Measure and Manage functions to frame ownership, risks and evaluation.
Synthetic leadership sample / Version 1.0
Product roadmap and decision record
- Scenario
- Fictional service-request product
- Outcome
- Residents can submit and track an eligible service request.
- Open decision
- Confirm the receiving team and service coverage before release.
Put the plan to work
Inspect the versioned source and discuss the structure of your engagement.
Inspect the related versioned sample ↗These are planning practices, not a universal scope, legal interpretation or delivery guarantee. Agree the criteria that apply to your project.
Bring your project brief ↗