Appendix / working tools
Field Guide
Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.
These are working templates, not universal standards. Adapt them with the people who will use and be affected by them.
A. Competency map
When an outcome stalls, look across the nine competencies: delivery and execution; quality and reliability; flow and developer experience; architecture and technical strategy; product and customer focus; innovation and learning; people and culture; collaboration and communication; security and compliance. Identify a concrete constraint and owner. Do not assign a maturity score to an individual or assume the highest score requires the most AI.
B. The four-way decision card
Problem and recipient: Who is waiting for what? Current path: Where does work wait or fail? Options: What could AI change? What non-AI improvement would compete with it? What would justify deferring or declining? Consequences: What can each option read, propose, or change? Who verifies and recovers? Decision: Which smallest test, by whom, and when will it be revisited?
C. Value ledger and pilot card
| Perspective | Primary or check? | Baseline and comparison | Cost, harm, or uncertainty |
|---|---|---|---|
| Customer | Task success, time to use, or safe resolution | Same population and observation window | Exclusion, trust, reliability, privacy |
| Company | Margin, booked saving, avoided cost, or funded capacity | Finance-owned assumptions and actual spend | Tool, compute, review, training, operation |
| Team | End-to-end flow and safe delivery | Comparable risk, change size, and staffing | Review queue, rework, on-call load |
| Individual | Agency, growth, sustainable work | Voluntary feedback and practice opportunities | Surveillance, workload transfer, lost mentoring |
Record one primary decision metric, observation window, target or meaningful change, pause condition, comparison design, and a named decision owner. Put self-reports, measured events, and modeled values in separate columns; do not double-count freed hours as savings and new output.
D. Usage-policy prompts
Specify approved tools and data; maximum permissions; prohibited disclosure or irreversible actions; review and audit needs; escalation and rollback authority; representative evaluation cases; and a justified way to decline AI without penalty. Ask whether a human reviewer can actually inspect the work entrusted to them. A signed policy does not replace a tested workflow.
E. Evidence label
Next to each consequential number, write its source, publication date, population, denominator, method, comparison, and limitation. Mark it measured, self-reported, modeled, inferred, or unknown. A randomized task study is not a customer-revenue study; an incident report is not a model-evaluation study; a vendor's ROI model is not independently booked cash.
F. Terms
Outcome: A change in the condition or ability of a person or organization, not the artifact that might produce it. Capacity: Time or ability made available, whose value depends on what it enables. Counter-metric: A measure chosen to detect a cost or harm hidden by an apparent gain. Verification: A check able to falsify a proposed result, not a confident explanation of it. Trail marker: An explicit decision or safety checkpoint that helps people steer without controlling every action. Provisional draft: A text awaiting original reporting, source review, revision, and author approval; this book remains one.