01
EVIDENCE
Observation is not policy.
What people do can suggest a rule. It cannot approve one.
METHOD & SOURCES
The method answers one question: what is the smallest change that can improve this work? Observation shows the problem. A test shows whether the change helped. The client decides what happens next.
01
THE METHOD
Each step supplies the facts for the next. Completing a step does not approve another one.
01
State what a person or team must accomplish without assuming the current tool is the answer.
02
Follow authorized examples from trigger to outcome. Record decisions, exceptions, handoffs, and delays.
03
Separate observed facts from interpretation. Ask operators to correct the model and expose counterexamples.
04
Compare policy, training, configuration, purchased software, integration, custom work, and no change.
05
Test one change against a baseline, known risks, stop conditions, and a client decision.
02
FOUR RULES
01
EVIDENCE
What people do can suggest a rule. It cannot approve one.
02
AUTHORITY
The client approves policy, exceptions, access, and production use.
03
CHOICE
A clearer rule or better configuration should beat custom software when it solves the problem.
04
RESULT
Measure use, failures, exceptions, cost, and the result the client wanted.
03
SELECTED SOURCES
These works shaped the method. Inclusion does not imply endorsement of Tinework’s synthesis.
01
02
03
04
05
ARTICLE
Fabrizio Dell’Acqua et al.. Harvard Business School Working Paper 24-013, 2023.
06
07
08
FRAMEWORK
National Institute of Standards and Technology. NIST AI 100-1, 2023.
FULL REFERENCE
The compendium contains the full definitions, controls, and bibliography.
Download the compendium