Chapter 20 / 20
20. Your Next Ninety Days
Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.
Imagine returning to the meeting where somebody first proposed the tool. This time the question on the table is not "How many people will use it?" It is "Which important result is waiting, what holds it back, and what is the smallest safe way to learn whether this will help?" That question does not settle the answer. It gives the people responsible a fairer way to find it.
In the first thirty days, choose one named customer or operational outcome. Trace the path backward through discovery, build, review, approval, release, and use. Ask the person at each boundary where work waits and who can see a failure. Record the baseline and the limits of what you know. Put an AI option beside a non-AI improvement, a defer option, and a reasoned decline.
In days thirty-one through sixty, run one bounded comparison if the permissions and measurements are ready. Name the primary outcome and guardrails before adoption, include the whole cost, and give a person authority to pause the experiment. If there is no credible comparison, start by improving the instrumentation or shortening the question; do not pretend a license rollout is a pilot.
In days sixty-one through ninety, sit with customer, finance, engineering, security, reviewers, and affected workers. Ask what became better, which change was observed rather than merely reported, and who absorbed work elsewhere. Record a keep/change/scale/stop decision, what would reverse it, and the next unanswered question. If the test found no benefit, you have still avoided a larger unexamined commitment.
There are trail markers at the important junctions: the destination, the context and permissions, the verification gate, the release, and the return to learn from what actually happened. They are not commands to take every step in the same way. The purpose is to help people and teams explore without losing their responsibilities to customers—or each other.
The next marker: Make the first decision small enough to revisit. Do not ask the team to prove its enthusiasm. Ask it to show, with the people affected, whether the route led anywhere worth going.
No external sources cited in this chapter. Browse all references →