Playbook: Human + Agent Team Design
The Human & Agent Design encourages you to Design the Work Before the Role Panic. The question is not only what AI does but who supervises to catch exceptions.
Vieews
Signal: More AI Usage does not equal more AI Value
More AI Usage does not always equal more AI Value, it can bring value but the speed is moving faster than most organisations can absorb. Value discipline is needed to ensure realistic value and ROI estimations.
Playbook: AI Value Ledger: Hours Saved Is Not EBIT
Playbook helps separate soft benefits, useful productivity, exit-rate value, and bankable impact. AI programs often count activity, usage, or claimed time savings long before the business can bank value. The missing discipline is a value ledger that links AI activity to an actual business mechanism.
Signal: Job Fear starts with Fuzzy Decision Rights
Job loss anxiety is here; connecting the decision rights of your tech stacks like AI/Agent will help add clarity to this discussion. The higher the Agent autonomy, the more clearly the human role must be designed.
Playbook: Autonomy Ladder; what AI is allowed to do
Do you know what your AI/Agent is allowed to do? Use this playbook to get familiar with understanding how much action the system is actually allowed to do.
Signal: Who Catches the Agent when it is wrong?
Who catches it when it is wrong? A readiness gate does not slow humans down. It makes sure humans know how to supervise, correct, and rely on the system once it touches real work.
Playbook: The AI/Agent Readiness Gate
Use this playbook to help review conditions to be met before an AI workflow, copilot, automation, or agent is allowed to move from pilot into live use.
Playbooks
Playbook: Platform Agents do not equal Operating Model
Does connecting AI/Agent to your workflow mean you have an AI operating model or a new tool sprawl new mode aka Agent sprawl? Understand the difference today…
Signals
Signal: A human operator is not a blocker
A human operator in the AI/Agent discussion is getting harder to ignore. Every AI-Enabled workflow needs someone who can be the control layer between platform capability and real impact work.
Field Note: Platforms arriving with Own Agent
Field Note When every platform arrives with its own agent A field note on what happens when the business gets multiple agents before it gets one operating model. NotesField proofAgent sprawl A function starts with one useful assistant. Then another team adds a workflow agent. Then a vendor adds a
Operator Note: Agent sprawl is tool sprawl with permissions
Operator Note Agent sprawl is tool sprawl with permissions The risk is not only too many tools. It is too many tools that can advise, draft, trigger, or act without one operating spine. NotesAgent sprawlControl point Tool sprawl used to look like too many apps. Agent sprawl looks like too
Companion Sheet
Companion Sheet: Platform Agent Operating Spine
Companion Sheet Platform Agent Operating Spine A simple companion sheet for comparing agent-enabled workflows across platforms without getting trapped in vendor language. Meeting toolFree-member workbook available Use this in a meeting when multiple AI platforms are being deployed and nobody has one neutral operating view. The one-page