Serving the Customer Who Never Looks

John Rector / The web edition A business cookbook From attention to absorption Serving the Customer Who Never Looks A practical guide to maintaining outcomes in the age of delegation. By John Rector 12 recipes to turn a promise into a responsibility your business can carry. The complete book is here. Read, explore the examples, and work through the questions as you go. The customer has gone to do something else. The service still has to happen. Begin with one ordinary morning The same towels. A different obligation. The gym opens at six. The owner wants clean towels in the cabinet so she can welcome a new member. Tap between the two arrangements. Compare search and delegation Google it Delegate it The owner carries the coordination Remember the towels. Find a suitable service. Arrange the ordinary order. Check whether it happened. Chase what remains unresolved. Search can meet attention at the moment of approach. The person still carries the matter through the surrounding work. The arrangement carries the coordination 5:45 a.m. Clean, usable towels. In the agreed cabinet. Verified. The provider and authorized delegate carry ordinary ordering, access, evidence, and recovery. The owner is welcoming a new member. The need remains. The obligation to keep watching can disappear. How to use this edition Open a chapter. Make one service better. Start with the foundation, or bring a real service to the one hour exercise. Each recipe contains the full method, a worked example, and questions you can answer here. Keep chapters open as you work, or fold them away by tapping their titles. All twelve recipes and the complete practice and reference material are included below. The examples are illustrative. The source notes connect the work to fifteen earlier articles. Working notes and checkmarks are temporary on this page. Copy answers you want to keep. The print and editable editions are available at the end if you prefer them. 01 / Understand the shift Start with the responsibility A The foundation Attention, the Reality Equation, and the roles a delegated service must carry. This book is for the owner, manager, service designer, or student who needs to change a real service. Choose one outcome a customer should be able to entrust to your business. Work on that same outcome throughout. The practical result is a service that maintains a defined condition, verifies what happened, recovers from ordinary problems, and returns to the person for decisions that belong to them. FOUNDATION / 01 The customer has gone to do something else At six in the morning, the gym owner opens the towel cabinet. The clean towels are there. She walks over to greet a new member. Somewhere else, a service has collected used towels, washed them, checked the quantity, delivered the next supply, and recorded what happened. Her delegated system has carried the requirement across those events. The owner has not searched for a supplier, approved the ordinary order, or watched a delivery screen. Her business still needs the towels. The laundry still has a customer. Money still changes hands. An economic relationship continues without the owner attending to its ordinary operation. This is the customer who never looks. The phrase describes the absorbed matter. It does not describe a person who has lost curiosity, judgment, or concern. She is looking at the new member. Her attention is fully alive elsewhere. What search solved Search receives a person who has already approached a subject. The question and the search session are evidence that attention is participating. Search accidentally helped solve the timing problem: the business could meet the person at that approach. Delegation changes the requirement. An authorized system may carry the need, compare suitable offers, coordinate performance, and verify the result. A human search session need not appear at all. Improving your chance of winning that session cannot be the whole response when the session disappears. What the business must carry The physical product remains necessary. So does the work surrounding it: remembering, choosing, coordinating, checking, and recovering. If those responsibilities keep returning to the customer, the service still lives in the customer's attention. A good first question is therefore practical: what does the customer have to keep in mind so that our product works for them? This book follows those obligations until each has a reliable home. Old services have sometimes earned this kind of absence. The change is that synthetic prediction, joined to authorized action and dependable operations, can extend it across much more changing coordination. This is a new basis for designing the relationship, not a claim that trust or delegation was invented yesterday. Source trail: S1 to S5 . FOUNDATION / 02 Locate absorption in the Reality Equation My framework begins with Reality as a quotient. People experience Reality, rather than Actual in isolation. Expectation has a real component, Predicted, and an imaginary component, Ideal. R = A / E E = P + iI S = ln(R) A is Actual, the numerator. E is Expectation. P is Predicted. I is Ideal. AI supplies a synthetic prediction machine in the real component of the denominator. It does not manufacture the Ideal component. A prediction machine predicts; an agent acts. Human attention is normalized accumulated surprise. In the exact absorption case, the completed artifact and the predicted artifact coincide, and the Ideal component is zero. The effective numerator and denominator match. Then: R = 1 ln(1) = 0 No human attention is stolen. When the Ideal component is negligible rather than exactly zero, the framework describes the approach toward that limiting case. Do not drop the condition merely because the shorter equation is convenient. A complete artifact For the gym, the relevant service includes the expected towels being available in the agreed condition at opening. A delivery notification is a different artifact. A predicted delivery is different again. The prediction does not wash or deliver anything; an agent and the service operation must act. If the owner has to correct the order or chase the van, the event has returned to attention. Completing the delivery later does not erase that intervention. You can learn from the episode and improve the next one without relabeling the past episode as absorbed. A design principle rather than a dashboard formula The worksheet named expected condition is an operational description of a promise. It is not the entire complex denominator. Counting messages or defects does not measure S. We will use those counts as practical evidence of burdens and failures, without pretending to have measured consciousness. Keep the unit clear. Absorption concerns a particular matter. A person can choose to examine a record, change a standing preference, or attend a meaningful service encounter. The goal is to remove the ordinary obligation to monitor, not to prohibit looking. Source trail: S4 , S6 , S7 . FOUNDATION / 03 Keep the roles distinct A customer can delegate without becoming irrelevant. The customer remains the person whose outcome and interests the service exists to serve. A system may represent that person within a defined scope. It is not a new owner of the relationship. The customer The customer establishes what matters, which tradeoffs are acceptable, and which decisions remain personal. They can change or withdraw the delegation. Some of that requires deliberate attention at the beginning. A useful standing relationship avoids reconstructing it for every ordinary event. The customer delegate The delegate maintains the customer's context and acts within the authority granted to it. A prediction machine may predict a useful next artifact. An agent may make a reservation, send an instruction, or accept an offer. Keep the prediction and the action separate, even if one product contains both capabilities. The provider The provider must make a truthful offer, accept a specific commitment, perform it, and produce evidence. Its own systems may help, but its responsibility does not vanish into them. The provider must know which customer representative can authorize a change. The accountable operator Inside the provider's business, a named person owns the service and its unresolved cases. The customer's absence does not require every worker to disappear. Moving coordination into a capable service can be valuable before all of that coordination becomes automated. Do not hide a burden transferred to staff. Record their work, equip them to resolve it, and include it in the economics. A quiet customer experience supported by an exhausted employee is not a durable operating model. Begin with ordinary tools You can pilot the relationship with a shared commitment record, a monitored inbox, a service operator, and clear standing instructions. Introduce more automation where it removes a demonstrated gap. Buying an AI interface before assigning responsibility often gives the customer one more thing to operate. The practical loop is: understand the obligation, keep the relevant context, act within authority, observe the result, recover where possible, and surface the unresolved decision. Every recipe strengthens a part of that loop. Source trail: S8 , S9 , S11 . B Your first hour Find one recurring obligation and expose the work the customer still carries. Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Choose a service you already deliver. Invite the person who operates it and, when possible, the customer who carries its loose ends. Bring one recent completed job and one job that required chasing. First ten minutes Write what the customer wanted to be true. Then list every moment they remembered, searched, selected, confirmed, checked, corrected, or chased. Include work outside your product. Their reminder to themselves counts even if your software never saw it. Next fifteen minutes Choose one recurring obligation from that list. Remove it if it serves no useful purpose. Keep it if human presence is part of its value. Consider it for absorption if the outcome must continue but ordinary supervision should disappear. Next fifteen minutes Write five sentences: the condition we maintain; the actions already authorized; the evidence that closes the job; the recovery we can perform; and the condition that requires the customer's judgment. If any sentence depends on an unknown fact, name the owner who will resolve it. Final twenty minutes Walk the two old jobs through those sentences. Could the ordinary one finish without a new customer decision? Could the problem job recover without hiding its consequence? If not, identify the first missing piece. Your pilot begins there. The obligation we will work on throughout this book The customer work it currently creates The first missing capability and its owner Do not promise the customer that the service is absorbed at the end of this hour. You have selected the unit of work and exposed its dependencies. The recipes turn that first sketch into a service you can test. 02 / The twelve recipes Method → Example → Your turn 01 Choose one recurring obligation Find the customer work hiding around your product. 1 / Learn the method 2 / See the example 3 / Work on your service Choose one recurring obligation Result A small, consequential responsibility whose ordinary operation the customer should be able to stop supervising. Bring a recent job, a complaint or chase message, and someone who understands delivery. 1 Follow the customer through a complete occurrence. Start before your order form and end after your receipt. Ask what they must remember or arrange for your work to be useful. A repair completed without access restored is not the end of the customer's problem. 2 Separate three categories. Remove work that no longer serves an outcome. Preserve encounters whose purpose includes human participation. Select necessary recurring coordination as a candidate for absorption. Automating an unwanted weekly report preserves the wrong obligation. 3 Choose a boundary you can explain in one sentence. Prefer an outcome with observable completion, repeatable variations, a reachable owner, and manageable recovery. Start small enough that one missed assumption does not scatter across the whole business. 4 Record the present burden. Count customer reminders, repeat explanations, routine approvals, status checks, and corrections over a defined set of jobs. Ask about checking outside your system. These are operational observations, not a measurement of the Reality Equation. 5 Name what this pilot does not include. A towel service can maintain clean stock without taking responsibility for every purchasing decision in a gym. A clear boundary makes a later expansion intelligible. Test before proceeding Ask whether the obligation still matters if the customer never opens your interface. If the answer is no because the activity is unnecessary, remove it. If the answer is yes but nobody can state the finished condition, use Recipe 2 before choosing technology. Do not select the easiest task merely because it makes a good demonstration. Select a modest unit whose disappearance would change the customer's day. It should happen often enough during the pilot to produce evidence, without making frequency itself the value. Source trail: S5 , S12 . See it in practice The gym owner still carries the towels A gym and a laundry The laundry initially proposes a faster ordering page. Its team watches the gym owner prepare an ordinary week. She counts towels, checks the class schedule, changes a quantity, confirms a window, looks for the van, and asks a coach to check the cabinet. The team names the obligation: maintain usable towel stock for the gym's morning opening. Washing is part of that obligation. Remembering whether there will be enough towels is another part. What to remove The owner receives both an email receipt and a message asking whether she saw the email. Neither advances an unresolved decision. The duplicate message can go immediately. Removing it does not require a new AI system. What to preserve The owner wants to greet members and ask how their training is going. The team does not classify those conversations as inefficiency. They are part of the gym's value. What to absorb The pilot covers the weekday opening stock at one location. Weekend events, uniforms, and damaged equipment remain outside it. The laundry and the customer's delegate will carry ordinary replenishment, delivery verification, and approved backup arrangements. The baseline follows ten eligible openings. It records which ones required a quantity message, a delivery check, or a chase. The owner adds two occasions on which she checked without contacting the laundry. The team learns that a low support count had hidden continuing supervision. The bad first choice The team could have automated the receipt email in minutes. That would have improved an internal task while leaving the owner's responsibility largely intact. The chosen boundary follows the customer's desired condition instead. Your version may be a stocked supply cabinet, a prepared meeting room, or a complete weekly project handoff. The test is the same: can you name the ordinary responsibility that moves out of the customer's mind? Your turn Your first recurring obligation Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Customer and one recurring obligation What the customer remembers checks or chases today Work to remove entirely Human participation to preserve and why Pilot boundary and explicit exclusions Baseline period and person who will collect evidence Ready when A colleague can describe the pilot without naming your software, and the customer recognizes the responsibility you intend to carry. I can demonstrate the “Ready when” condition for my service. 02 Define the complete expected condition Make the promised condition specific enough to operate. 1 / Learn the method 2 / See the example 3 / Work on your service Define the complete expected condition Result A written outcome card that lets the customer, delegate, and provider recognize the same finished condition. Bring the chosen obligation and a real example of incomplete service. 1 State what must be true for whom, where, and by when. Include quantity or coverage, quality, timing, location, and usable form when they matter. Replace words such as enough, ready, and handled with a shared operational meaning. 2 Add the coordination condition. Specify which routine choices, followups, and checks the service carries. Otherwise the customer can receive the object while retaining the work that makes it useful. 3 Separate hard constraints from preferences. A required accessible entrance is not equivalent to a preference for a particular room. A provider must not trade a hard constraint away to avoid asking a question. 4 Name evidence of completion. Use an observable result connected to the promise. A sent message proves transmission, not arrival, acceptance, or performance. Recipe 7 will make this distinction operational. 5 Name the owner of an unresolved commitment. If a subcontractor fails, someone still holds the customer's outcome. Include the moment at which a delay changes the options and a decision is needed. 6 Read the card back as a customer. Does it contain the thing you meant to entrust, or merely the provider's favorite deliverable? Resolve the difference before the pilot. Keep the agreed version with its effective date. A useful sentence Maintain [condition] for [customer] at [place and time], within [constraints], with ordinary coordination carried by [owner]. Close each occurrence only when [evidence] supports completion. Bring back [specified unresolved decision]. This is a working service definition, not a claim that every part of complex Expectation has been reduced to a form. It makes a commercial promise concrete enough to operate and learn from. Source trail: S4 , S5 , S8 . Which promise can the service actually verify? Choose an answer to examine the decision. “The towels are handled.” This leaves the completed condition undefined. Two people can agree with the phrase while expecting different quantities, places, or times. “80 usable towels in the designated cabinet by 5:45.” This defines an observable condition for the illustrative gym. The agreement must also name the ordinary coordination the service carries and the evidence that supports closure. “We sent a confirmation.” A confirmation establishes a message. It does not establish the towels in the cabinet. See it in practice The towel outcome card Condition: at least 80 clean, usable towels are in the designated cabinet before 5:45 a.m. on each agreed weekday. Opening is at 6:00. Towels meet the sample quality agreed at onboarding. Used towels are collected without blocking the entrance. Coordination: the provider and authorized delegate manage ordinary quantities, access, confirmation, and approved backup delivery. The owner does not need to reapprove each regular occurrence. Hard constraints: the designated secure entry procedure; the agreed cleanliness standard; the morning deadline. Preferences: the usual driver and folded orientation. A change of driver does not automatically justify interrupting the owner. Evidence: the delivery record identifies the date, cabinet, count, and time. An agreed independent stock check supports that record. A packing slip at the depot is insufficient. Owner: the laundry service lead holds a missed or uncertain delivery until verified completion, approved recovery, or an unresolved decision is returned to the named gym contact. Find the missing sentence An earlier card said only, "Deliver 80 towels every weekday." It did not specify where delivery ended, who held access, or whether the owner had to confirm the count. The service could fulfill its narrow reading while making the owner supervise the result. The revised card adds: ordinary access and stock verification are part of the maintained service. That sentence changes the operating work the provider must organize. What changes later If attendance grows, the old count may stop representing the desired condition. Recipe 3 establishes where the new requirement comes from and who can approve a change. The provider cannot quietly lower the promise when delivery becomes inconvenient. The numbers here are illustrative. Your quantity and deadline must come from the customer's operation and your demonstrated capacity. Your turn Your outcome card Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. What must be true for whom where and by when Ordinary coordination included in the service Hard constraints and preferences stated separately Evidence that would prove the complete condition Accountable owner when performance is unresolved Agreement version effective date and change owner Ready when Two people can evaluate the same occurrence without silently using different definitions of done. I can demonstrate the “Ready when” condition for my service. 03 Maintain the context across time Carry what matters from one occurrence to the next. 1 / Learn the method 2 / See the example 3 / Work on your service Maintain the context across time Result A small, current record that carries what the service needs to know without asking the customer to reconstruct it. Bring the outcome card and the last few changes to a job. 1 List only context that affects performance or authority. Typical items include the delivery location, access arrangements, eligible dates, confirmed constraints, approved contacts, and effective terms. More personal information does not automatically improve service. 2 Give each item a source, an owner, a confirmation date, and a reason it would become stale. A remembered preference and a confirmed requirement should not carry the same status. Preserve uncertainty explicitly. 3 Establish where changes arrive. A changed calendar, a customer instruction, or a supplier update can update the record if the source is authorized. Decide which source prevails when two records disagree. Do not let the newest text win merely because it is newest. 4 Set refresh behavior according to consequence. Recheck volatile facts near the point of commitment. Retain stable facts without repeatedly asking for them. When a necessary fact cannot be confirmed, identify the affected decision instead of sending a broad request to review everything. 5 Record the customer's current understanding as well as operational changes. The system may have learned something the customer has not. A series of small changes can produce a world the customer would no longer recognize. Recipe 9 deals with that accumulated difference. 6 Make continuity portable within the agreed scope. A replacement operator must be able to find the active promise, authorized contacts, unresolved decisions, and next action. A departed employee's private memory is not a service record. Test before proceeding Introduce a plausible change and a stale conflicting record. Ask the operator which instruction governs and why. If the answer depends on asking the customer to repeat the entire brief, the context has not yet been carried. Source trail: S8 , S10 , S11 . See it in practice A meeting changes rooms A recurring team meeting uses Room A. The standing dinner arrangement includes an authorized calendar source, the delivery contact, the serving deadline, the attendance count, and confirmed meal requirements shared for that purpose. On Tuesday the organizer changes the room to B. The calendar update is current and comes from the authorized organizer. An old catering note still says A. The operator updates the delivery instruction, keeps the old value in history, and verifies that the provider accepted the change. The organizer does not need to send the same correction to three people. Updating the authoritative record once is enough because the service carries the downstream consequence. A requirement is uncertain The record also contains "probably vegetarian" from an old conversation. That is an inference, not a confirmed requirement. The service does not turn it into a definitive dietary instruction or infer allergy information. It obtains the necessary confirmed requirements through the agreed organizer before selecting a suitable service. A provider that cannot meet a hard requirement does not receive the order simply because the system prefers a quiet outcome. The operator handoff When the usual service lead is away, the substitute sees the active meeting, current room, accepted provider commitment, verification deadline, and unresolved facts. They do not need to replay a month's chat history. The lesson Memory is valuable only when it supports the present obligation. Unowned notes become stale. Unqualified guesses become surprises. A compact record with sources and change rules can be more useful than a large archive that no one knows how to trust. Your turn Your context record Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Minimum facts this service must retain Authoritative source and owner for each important fact Facts that expire and what triggers a refresh How conflicting instructions are resolved What the customer currently believes remains true What a replacement operator must receive Ready when A routine change reaches the work without a repeated customer briefing, and an uncertain fact remains visibly uncertain until resolved. I can demonstrate the “Ready when” condition for my service. 04 Set bounded standing authority Agree on ordinary action and the decisions that remain personal. 1 / Learn the method 2 / See the example 3 / Work on your service Set bounded standing authority Result An authority card that permits ordinary action and names the boundary requiring a new decision. Bring the outcome card, likely variations, and whoever can grant the authority. 1 Name the principal and authorized representatives. Know who owns the outcome, who can act for them, and how that authority is established. A plausible message is not enough to change a standing arrangement. 2 List actions allowed within the ordinary promise. Include repeat ordering, scheduling, acceptable substitutions, cancellation, and recovery where relevant. An agent should not need to ask whether to perform each action already authorized. 3 Define limits across the whole occurrence and period. Per-action limits alone can permit many small actions to create a large commitment. Include total exposure, timing, location, quantity, information sharing, and any prohibited changes. 4 Specify reversibility and stopping. State how to cancel pending work, prevent duplicate action, revoke access, and stop future occurrences. Some consequences cannot be undone; identify them before granting scope. 5 Define the decisions retained by the customer. These may include a changed standard, a new kind of commitment, an irreversible tradeoff, or a circumstance in which personal presence matters. Confidence in a prediction does not expand authority. 6 Make revision explicit. A customer's answer to one exception is not automatically permission for every future case. Record whether the answer applies once or changes the standing relationship. Test the boundary Run three scenarios: an ordinary action, a recoverable variation, and a proposed action just outside the limit. The first should proceed, the second should recover where authorized, and the third should stop at the relevant decision. A system that asks for all three returns ordinary work to the customer. One that proceeds with all three has ignored the boundary. Source trail: S9 , S10 , S11 , S13 . See it in practice The laundry backup The gym authorizes ordinary replenishment within its agreed weekday schedule. If the primary route is disrupted, the service can use either of two approved backup providers that meet the same towel and access conditions. The authority includes a defined recovery allowance for the week. The operator tracks that total across all orders. Three individually small recovery charges cannot silently exceed the weekly limit. Three decisions Changing the approved driver while keeping the same provider, standard, and delivery window is ordinary. The operator records the change and proceeds. Using an approved backup within the remaining allowance is recovery. The operator acts, checks the result, and retains the evidence. The owner's separate approval is not needed for this occurrence. Using an unapproved provider with a different quality standard is a changed promise. The operator presents the meaningful choice by the time a decision can still protect opening. It cannot call the substitution "equivalent" merely to stay silent. Stop means stop The owner pauses the arrangement for a closure week. The service cancels pending occurrences, obtains cancellation acknowledgments, and marks the standing schedule inactive. A reminder to an employee is insufficient if tomorrow's order is still queued elsewhere. The human responsibility The laundry's service lead owns enforcement of the card. The card does not make a tool accountable or transfer the gym owner's entire business judgment to the provider. It makes a specific delegation durable enough that ordinary action can occur without a new ceremony each morning. Your turn Your authority card Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Principal authorized representatives and verification method Ordinary actions that may proceed without asking again Hard limits including cumulative exposure Approved recovery and permitted substitutions Decisions retained by the customer How authority changes pauses and ends across pending work Ready when The operator can act on an ordinary occurrence, handle an allowed variation, and refuse an out of scope action using the same written authority. I can demonstrate the “Ready when” condition for my service. 05 Make your offer usable by a delegate Make your capability understandable and actionable. 1 / Learn the method 2 / See the example 3 / Work on your service Make your offer usable by a delegate Result A service description and acceptance path that a customer's authorized representative can use without reconstructing the offer. Bring your current website, quotation, and service terms. 1 Describe what you can actually maintain. State the service area, availability, capacity, timing, quality conditions, exclusions, and prerequisites. Distinguish a general capability from capacity reserved for a specific customer. 2 Make the commercial terms determinable. The delegate needs to know the included work, cost basis, limits, variations, cancellation conditions, and when the quoted terms expire. If a tailored quote is needed, make the request and response specific enough to proceed. 3 Provide one dependable way to request, accept, change, and cancel a commitment. A well managed inbox can support a pilot. A structured technical interface may help at scale. Neither is sufficient if nobody owns the unanswered request. 4 Make the information consistent across surfaces. The service page, quote, operator, and booking channel must describe the same offer. Put effective dates on changing facts. A persuasive old page should not outrank current capacity. 5 Return a legible acknowledgment. It should identify the customer, occurrence, agreed condition, terms, current status, and next checkpoint. Receipt of an inquiry is not acceptance of the job. 6 Respect the representative's role. Answer the customer's requirements accurately. Do not attempt to insert new instructions into the delegate's work, invent authority, conceal exclusions, or steer it toward a choice that violates its principal's interests. Test without the sales tour Give the offer to a colleague who has the customer's outcome and authority cards. Can they determine suitability, obtain a binding service commitment through your actual process, and understand how changes work? Record every gap that requires interpretation. This is how discovery changes. A human may still find and choose you. But your business must also be usable when a delegate approaches with an existing obligation. The product's truth and the service's ability to commit become central to that encounter. Source trail: S5 , S9 , S11 . See it in practice A service offer the gym can use The laundry's old page says "Premium linen care for busy professionals" and invites visitors to book a sales call. It does not say whether early delivery is possible or whether the service accepts a standing replenishment arrangement. The revised description names its weekday delivery area, available morning windows, towel standards, usual capacity, and the conditions under which backup service is included. Current availability has an effective date. Exceptions require a specific quote. An authorized delegate submits the gym's location, required condition, schedule, and representative details through the published service address. The operator checks capacity and returns a proposed commitment with complete terms and an expiry time. Acceptance follows the agreed authorization process. Acknowledgment matters The response "We received your request" leaves the outcome uncommitted. A useful acceptance names the first service date, the accepted requirement, the responsible contact, the verification arrangement, and the commitment identifier used for later changes. The gym's delegate can now distinguish inquiry from promise. It knows whether it must continue looking for a provider. What the business should publish Publish the service facts and the route for a specific commitment. Do not publish a customer's private access instructions or claim unlimited capacity. Share only the information necessary for the particular relationship through its agreed channel. The new sales question The laundry still needs a credible way to be discovered. But once approached, its job is to prove fitness for the obligation and accept responsibility. A beautiful website can help explain the service. It cannot replace that operational answer. Your turn Your service offer Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. The condition your offer maintains and its exclusions Current capacity coverage timing and expiry of the offer Terms a delegate needs to compare and accept the offer Channels for request acceptance change and cancellation Fields in a specific commitment acknowledgment Ambiguities found by the colleague who tested the offer Ready when A representative can determine suitability and tell whether you have actually accepted responsibility, without requiring the customer to interpret your offer. I can demonstrate the “Ready when” condition for my service. 06 Carry the promise through action Keep an owner attached to every open commitment. 1 / Learn the method 2 / See the example 3 / Work on your service Carry the promise through action Result A commitment record that remains alive until the outcome is verified, explicitly changed, or properly closed. Bring the offer, authority card, and a real sequence of service events. 1 Give each occurrence a stable identifier. Keep the customer, agreed version, deadline, owner, status, evidence, and next checkpoint together. One shared reference prevents three conversations from becoming three orders. 2 Separate meaningful states. A request can be received, accepted, underway, awaiting verification, recovering, awaiting a decision, or closed. Use words your operators understand. Each transition needs evidence and a next owner; an optimistic label is not evidence. 3 Separate prediction from action. A predicted plan or message can inform the next step. An authorized agent must perform the action. The action needs an acknowledgment or observed consequence. A plausible completion narrative does not close the commitment. 4 Keep a next checkpoint for every open occurrence. It may be a reply deadline, a verification time, or a recovery trigger. An unanswered request cannot be allowed to vanish because no new message arrived. 5 Make retries safe. If an acknowledgment is missing, first determine whether the action already happened. Use the existing reference. Blindly repeating a booking or payment can create duplicates. Where the channel cannot confirm status, assign reconciliation before retrying. 6 Carry amendments and cancellations to every affected party. Record who accepted the new instruction. An updated internal note does not change a supplier's active commitment by itself. Test a dropped acknowledgment Simulate a successful action whose response is lost. Can the operator discover the state without duplicating the action or asking the customer to investigate? Then remove the usual operator for a shift. The substitute should find all open commitments and their next checkpoints. Technology can improve this record, but the first requirement is continuity of responsibility. A customer should not have to become the thread connecting disconnected systems. Source trail: S8 , S9 , S11 . See it in practice One opening and one identifier The illustrative gym service creates occurrence GYM 104 for Tuesday opening. Its record includes the active outcome card, the current count requirement, the authorized provider, the delivery deadline, and the service lead. The primary provider accepts GYM 104. The occurrence moves from requested to accepted. The next checkpoint is confirmation that the delivery is on schedule, early enough for backup action if necessary. A response is lost The ordering channel times out after submission. The operator does not immediately send another order. It queries or contacts the provider using GYM 104. The provider confirms that it accepted that occurrence once. The record is reconciled and work continues. If the provider cannot establish whether it accepted the order, the operator owns that uncertainty. It uses the agreed reconciliation path before any new booking. The owner of the gym does not receive a request to search her email for a receipt. A shift changes The evening operator leaves with two open records: Tuesday is accepted and awaiting delivery evidence; Wednesday requires confirmation of a schedule amendment. Each has a next checkpoint and owner. The morning operator can continue the work without interpreting an unstructured chat history. What closes it At the delivery deadline, GYM 104 still cannot be closed merely because the truck left the depot. It moves through verification. If the evidence is missing or inconsistent, it remains open and triggers Recipe 7 or 8. The record is allowed to become quiet only after the expected condition is supported. Quiet is an operating result, not a status somebody selected to clear a queue. Your turn Your commitment record Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Occurrence identifier and location of the shared record States and the evidence required to enter each state Owner and next checkpoint for every open state How an uncertain action is reconciled before a retry How amendments reach and are accepted by all affected parties What a replacement operator sees at handoff Ready when No commitment can become ownerless, a missing response cannot create a duplicate, and a claim of completion cannot substitute for evidence. I can demonstrate the “Ready when” condition for my service. 07 Verify the result without customer supervision Establish what happened without making the customer watch. 1 / Learn the method 2 / See the example 3 / Work on your service Verify the result without customer supervision Result A completion test performed by the service arrangement, with enough independent evidence to reveal failure. Bring the outcome card and the data or observations your operation can actually obtain. 1 Pair each important condition with observable evidence. Delivery requires evidence at the destination. A complete report requires the right period, inputs, contents, version, and destination. Verification should follow the promise rather than the easiest event to count. 2 Identify where the evidence comes from and how it could be wrong. A provider's completion claim is useful, but a system that checks only its own assertion can repeat the same error twice. Use an independent observation where the consequence justifies it. 3 Check freshness, coverage, and identity. Evidence for yesterday's delivery or another location cannot close today's commitment. A partial observation should remain partial. Missing evidence means unknown, not successful. 4 Assign a verification deadline that leaves room for recovery. Discovering the missing towels after opening protects neither the outcome nor the customer's attention. 5 Choose who handles uncertainty. The provider or delegated operator should resolve ordinary evidentiary gaps through its agreed channels. If the customer must photograph every delivery, you have assigned them a verification job. That may be a temporary pilot stage, but name it accurately. 6 Keep an inspectable history without demanding routine inspection. Retain the commitment, evidence, material changes, and closure reason. Let the customer ask for it. Do not turn every successful check into a notification. Test a convincing false claim Supply a completion record with the wrong date or location. Then provide no record at all. The service should keep the occurrence unresolved, seek the right evidence, and recover or escalate in time. A polished generated summary must not override this test. Source trail: S5 , S8 , S13 , S14 . The van arrived. Is the commitment complete? Choose an answer to examine the decision. Yes, the tracking system says delivered. The status is a claim about an event. Check whether its underlying evidence supports the complete expected condition. Ask the owner to check the cabinet every morning. This can provide evidence, but it gives the ordinary verification obligation back to the customer. Design a dependable verification path the service can carry. Verify the agreed count, condition, place, and time. This connects evidence to the promise. If the evidence is missing or contradictory, someone still owns the unresolved result. See it in practice A cabinet rather than a truck The laundry already knows when its truck leaves. The gym needs towels in a particular cabinet. Those are different conditions, so dispatch data cannot prove completion. For this illustrative pilot, the parties agree to a timestamped delivery count at the cabinet and an independent stock observation from a maintained inventory device. The operator checks that the device is reporting current data and that its count is consistent with the delivery record. This example assumes the device exists and has been tested. If it does not, the business must arrange a suitable staff check or another credible observation. An imaginary sensor is not a design solution. The evidence disagrees The provider claims 80 towels delivered. The independent observation indicates materially less stock. The service lead keeps the occurrence open, checks the location and count, and uses the recovery procedure. The customer's delegate receives the resolved status and evidence through the service record; the owner need not receive a routine success alert. During the pilot An employee may perform a scheduled spot check to test the inventory evidence. That work is recorded as provider verification effort. If the gym owner does it, it is recorded as customer oversight. Neither disappears from the account merely because the operation calls it quality assurance. Evidence has limits A count alone does not prove cleanliness. The service also needs a proportionate quality process and a route for defects discovered in use. Choose verification that fits each material part of the promise, then be honest about the residual uncertainty. The result is confidence grounded in an operating record. It is not mathematical certification that a person experienced zero surprise. Your turn Your verification plan Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Each important condition and the evidence that supports it Evidence source and an error it could share with the action Independent observation or check that can expose that error Freshness identity and completeness checks Verification deadline and owner of unknown results Records retained and how the customer can inspect them Ready when The service distinguishes completed from claimed and unknown, without requiring the customer to verify every ordinary occurrence. I can demonstrate the “Ready when” condition for my service. 08 Recover without exporting the problem Carry ordinary failure through to a usable resolution. 1 / Learn the method 2 / See the example 3 / Work on your service Recover without exporting the problem Result A small set of tested recovery paths that protect the outcome inside standing authority. Bring past failures, approved alternatives, and the limits from Recipe 4. 1 Name likely failures by their consequence. A late truck matters because opening stock may be absent. An unreadable file matters because a decision cannot use it. Work backward from the threatened condition to the earliest useful detection point. 2 Specify the ordinary recovery path and its owner. Include the trigger, permitted action, available alternative, completion evidence, and time remaining. An alternative is not real merely because its name appears on a list; verify availability when you need it. 3 Bound attempts. Repeated retries can consume the remaining window or create duplicates. Set a stopping point for automated attempts and name the operator who reconciles uncertain state. 4 Protect the whole promise. Recovering timing by breaking a hard quality or access constraint does not fulfill the outcome. A change outside standing authority belongs in a decision, even if it is the fastest available option. 5 Keep failed original work from returning as a second action. Cancel or reconcile the first commitment when replacing it. Confirm whether cancellation succeeded. Record any remaining exposure. 6 Learn after recovery. Retain the cause, action, evidence, and customer consequence. Repeatedly using the same emergency path suggests that the ordinary service needs repair. Successful recovery is not permission to leave the cause untouched. Rehearse before relying on it Run one realistic failure while a service operator watches. Include a missing response or unavailable backup. Observe whether the system protects the remaining time, respects the limits, and reaches the right person when its scope ends. The aim is not to prove that failure never occurs. It is to keep predictable variation from automatically becoming the customer's new assignment. Source trail: S8 , S13 , S14 . See it in practice The primary van cannot arrive At 4:45 a.m., the primary provider reports a route failure affecting the 5:45 towel deadline. The service record shows an approved backup, sufficient remaining recovery allowance, and a verified 5:30 arrival option. The operator reserves the backup against the existing occurrence, confirms its capacity and access instructions, and obtains cancellation acknowledgment from the primary provider. It does not leave two active deliveries merely because the backup is urgent. The backup arrives. The same verification standard applies. Evidence supports the required opening condition, and the occurrence closes with its recovery history intact. The owner greets the first member without becoming the dispatcher. When recovery cannot preserve the promise Now change one fact: the backup can arrive only after opening, and no approved alternative can maintain the morning stock. The operator cannot label this resolved. It uses the wake condition with the consequence, remaining choices, deadline, and steps already attempted. The late outcome would change the version of the morning the owner is carrying. Silence would delay the surprise rather than absorb it. After the occurrence If the primary route fails repeatedly, the service lead reviews capacity and revises the operating arrangement. The owner should not be sold perpetual emergency handling as a stable outcome. The record separates two questions: did today's condition remain true, and is the service becoming more reliable? A recovered day may pass the first test while exposing a problem in the second. Your turn Your recovery plan Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Likely failure and the condition it threatens Detection point that leaves time to recover Authorized recovery steps owner and verified alternatives Limits on attempts time and cumulative exposure How the original commitment is canceled or reconciled Evidence of recovery and trigger for revising the service Ready when A rehearsed failure can recover within the promise, or reach the customer as a clear decision before the options disappear. I can demonstrate the “Ready when” condition for my service. 09 Write the wake condition Return for a real decision at the moment it is needed. 1 / Learn the method 2 / See the example 3 / Work on your service Write the wake condition Result A rule for when the service returns to the customer's attention, plus a message that makes the remaining decision clear. Bring the authority card, recovery paths, and the customer's current understanding of the arrangement. 1 Define meaningful change from the customer's perspective. An event can be important operationally and still belong inside ordinary service. Conversely, many small events can add up to a world the customer would no longer recognize. 2 Separate three routes. Handle and log ordinary events. Resolve recoverable variation within authority. Escalate the unresolved consequence or retained decision. A question should not be escalated merely because a machine found it uncertain; the service may be able to obtain the missing evidence itself. 3 Name the right recipient and latest useful time. Choose the person with the relevant authority. A deadline must reflect when choices expire, not just when the software would like an answer. 4 Write the smallest complete decision. Include what changed, why it matters, supporting evidence, what has already been attempted, remaining options, and why the recipient must decide. State what happens if no answer arrives. 5 Write a fallback for nonresponse. Stay within the agreed authority. Preserve reversible options, prevent new out of scope commitments, and route urgent unresolved matters according to the standing arrangement. Silence from the person does not grant new authority. 6 Test accumulated drift. Repeated small substitutions, changes in service quality, or extra charges can change the relationship even when no single occurrence crosses a limit. Compare the present arrangement with what the customer believes they entrusted. Check the bar itself At an agreed review, inspect a sample of both escalated and un-escalated events. Look for needless questions and concealed consequences. The standard is meaningful judgment, not the lowest message count. Source trail: S10 , S14 , S15 . A van fails. An approved backup can still meet the promise. What happens next? Choose an answer to examine the decision. Interrupt the customer about the van. The equipment problem does not yet require a customer decision. Ordinary recovery is already covered by authority. Use the backup and verify the condition. The service carries the ordinary failure within the agreed authority. Retain the record; bring the matter back if an unresolved tradeoff crosses the boundary. Hide the problem and mark the job complete. Quiet is not completion. The service still has to perform, verify, and keep an honest record. See it in practice A decision worthy of interruption The ordinary alert says, "Delivery issue. Please contact support." It tells the gym owner almost nothing and assigns the investigation to her. The useful exception says: "Tomorrow's opening stock cannot be maintained under the current arrangement. The primary route is canceled; both approved backups have confirmed they cannot arrive before 6:30. We checked the on site reserve and it covers only part of opening demand. We need your choice by 5:15: open with the reduced towel offering, or approve the alternate service described below. Its quality differs from the agreed standard. We have not booked it. If there is no answer, we will not change that standard and will use the authorized reserve procedure." The message would include the exact verified quantity, proposed terms, and evidence links. It does not force the owner to open a dashboard to discover why she is needed. The system was not surprised Suppose the operator learned of the delay hours ago. Its own forecast may now be perfectly settled. That does not mean the customer's expectation has changed. The exception concerns the owner's morning, not the machine's latest confidence. A drift review The provider has substituted a different towel format several times. Each substitution was temporarily accepted, but together they now define a different service. The owner should be asked whether to change the standing standard, restore the original, or change providers. Individual approvals do not automatically rewrite the relationship. The wake condition belongs to the customer. The provider can help make it explicit and workable; it should not tune the threshold merely to reduce its own support costs. Your turn Your wake condition Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Changes that would alter the world the customer expects Ordinary events to handle and log without interruption Unresolved decision recipient and latest useful time Message containing consequence evidence attempts and options Authorized fallback when no answer arrives Review that detects both needless alerts and accumulated drift Ready when A recipient can make the remaining decision without reconstructing the case, and the service cannot suppress a consequence merely to appear quiet. I can demonstrate the “Ready when” condition for my service. 10 Earn absence in stages Let the record support a wider delegation. 1 / Learn the method 2 / See the example 3 / Work on your service Earn absence in stages Result A pilot that reduces supervision only as its operating record supports it. Bring the complete service design, test cases, and a customer willing to learn with you. 1 Demonstrate the whole occurrence. Show the maintained condition, action, evidence, and recovery. Include an inconvenient variation. A fluent conversation is not a demonstration of a functioning service. 2 Supervise a bounded set of live occurrences. The provider watches closely and the customer retains agreed approvals. Record the oversight honestly. This is a learning stage rather than a claim of absorption. 3 Move to sampling where the record justifies it. Reduce repeated approvals within established authority. Keep a defined sample review and a path for discovering missed problems. Choose the sample according to variability and consequence, not an attractive percentage. 4 Move ordinary operation to exception handling. The service performs, verifies, and recovers inside the standing relationship. The customer appears for the decisions defined by the wake condition. Continued unnecessary checking is evidence that trust or capability still needs work. 5 Recognize absorption as an earned relationship with the matter. Do not award it as a software badge. The operating record can support withdrawal of ordinary supervision; it cannot dictate a person's experience or prove an exact metaphysical state with a score. 6 Define retreat and repair. After a significant surprise, narrow the affected scope, inspect the cause, restore the promise, and rebuild evidence. Do not reset every unrelated service automatically, but do not dismiss the event as an isolated mistake without understanding it. A small deliberate review Some chosen review of the arrangement can remain useful. That review is itself an attended matter. Keep it distinct from the recurring obligation to watch every occurrence. If reviewing the service recreates the original job, the burden has not been removed. Source trail: S6 , S13 . See it in practice A trial that learns The laundry first demonstrates one ordinary delivery and one simulated route failure. Its verification catches a deliberately incorrect location record. The operator reconciles a duplicate request without making a second order. The customer and provider then agree to a limited live pilot. The provider checks every occurrence internally; the gym owner attends selected reviews and can inspect the complete record. Early customer involvement is recorded as supervision, not presented as quiet success. What permits the next step The team looks for stable completion evidence, honored authority, reliable recovery, and no unresolved missed outcomes. It also asks the owner whether she has been checking on her own. Several clean provider records do not establish absence if the customer remains the hidden monitor. Once the evidence supports a narrower customer role, ordinary confirmations stop. The owner keeps the agreed exception route and a small scheduled review. The trial duration and review frequency are chosen for this service; another business may need a different period or more varied cases. A surprise changes the scope A count was recorded against the wrong cabinet. The team reopens that occurrence, resolves the stock problem, and traces the identity error. It temporarily increases checks for location identity and tests the repair. It does not send the owner every unrelated operational event. The record earns the quiet The owner gradually stops thinking about the morning towels. Nobody asks her to perform trust. The service becomes stable enough that the obligation ceases to keep presenting itself. This is the practical meaning of earning absence: the customer no longer has to keep supplying the supervision your service lacks. Your turn Your trust progression Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Demonstration cases including failure and uncertain evidence Pilot scope duration and customer involvement Evidence required before reducing supervision Sample review owner and what it checks Conditions that require narrowing scope or renewed supervision How private customer checking will be discovered Ready when Each reduction in oversight has a reason grounded in evidence, and a significant failure has a defined path back to a trustworthy arrangement. I can demonstrate the “Ready when” condition for my service. 11 Sell and sustain the whole outcome Include coordination, evidence, and recovery in the business. 1 / Learn the method 2 / See the example 3 / Work on your service Sell and sustain the whole outcome Result A commercial offer whose promise, operating cost, onboarding, and exit all support the same relationship. Bring the current offer and the real work revealed by the pilot. 1 Describe the maintained condition in the sales conversation. Show which remembering, coordination, verification, and recovery responsibilities you carry. Do not claim they disappear if the customer must still perform them. 2 Cost the whole service. Include production, ordinary coordination, evidence collection, recovery capacity, accountable staff, and support. Hidden unpaid labor will eventually return as worse service or more customer work. A subscription does not create absorption by itself. 3 Choose terms that fit the obligation. The payment structure may be per occurrence, periodic, or a combination. State what is included, what constitutes a scope change, and how exceptions are priced or approved. Do not earn money from avoidable interruptions while promising to remove them. 4 Onboard once, then maintain the relationship. Confirm the expected condition, authority, context sources, verification, wake condition, and exit path. Use the customer's existing delegation where possible instead of requiring a fresh account and briefing for every ordinary event. 5 Keep meaningful human contact available. Personal advice, hospitality, learning, and creative exploration may be part of the desired service. Do not hide people behind automation when presence is the point. 6 Make exit work. Pause future occurrences, reconcile open commitments, settle outstanding work, and transfer the customer's authorized service record in a usable form. Revoke access where appropriate. Do not make the customer's absence a reason they cannot understand or leave the arrangement. Test the economics and the promise together If you cannot maintain the claimed condition at the proposed terms, narrow or redesign the offer. Do not quietly remove verification or export recovery to the customer. The business earns a place by sustaining the outcome it sold. Source trail: S5 , S9 , S11 , S13 . See it in practice What the laundry is selling The commodity offer is a quantity of washed towels. The maintained service includes the agreed opening stock, coordination, evidence, and approved recovery. The laundry can explain both clearly without pretending that one is merely a premium label for the other. Its costing includes the service lead's time, verification equipment or staff, backup arrangements, and the work of reconciling uncertain deliveries. During the pilot those costs are measured. The business does not assume AI makes coordination free. An honest offer The proposal states the ordinary service condition, capacity limits, backup coverage, change rules, and cancellation process. A different location or opening schedule triggers a scoped review. The customer can see what they are buying and what remains outside it. The sales conversation uses the pilot record. It shows fulfilled conditions, detected failures, recovery, and remaining limitations. It does not use low message volume alone as proof that the customer can stop looking. A relationship without constant contact The owner may want an occasional conversation about improving the service. That chosen encounter is welcome. It differs from having to answer a morning quantity prompt so the operation can proceed. A clean departure The gym changes location. The laundry confirms the last occurrence it will perform, stops later ones, identifies any pending returns, and shares the agreed service history with the owner's authorized representative. The new provider receives only the information the customer is entitled to transfer and has authorized sharing. Leaving does not require the owner to rediscover every loose end. The quality of the departure is evidence of whether the business ever carried the relationship responsibly. Your turn Your complete commercial offer Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Customer promise and responsibilities included in the offer Production coordination verification and recovery costs Included scope payment structure and change rules One time onboarding and continuing context arrangements Human encounters customers want to preserve Exit steps for future work open commitments records and access Ready when Your price and capacity can sustain the complete promise, and a customer can understand, change, or end the arrangement without taking on a rescue project. I can demonstrate the “Ready when” condition for my service. 12 Measure what the customer stopped carrying Examine both verified outcomes and the work that remains. 1 / Learn the method 2 / See the example 3 / Work on your service Measure what the customer stopped carrying Result A small review that measures fulfilled outcomes alongside customer burden and hidden operating work. Bring the baseline from Recipe 1 and the pilot commitment records. 1 Define the population first. Count all eligible committed occurrences in a fixed period. Keep canceled, changed, missed, and unknown outcomes visible with their reasons. Do not improve a rate by silently dropping hard cases. 2 Measure the promise. Record how many original conditions were verified as met, missed, or unknown. Track authorized changes separately. A renegotiated deadline may be sensible but is not proof that the original deadline was met. 3 Measure demands on the customer. Record routine approvals, repeat explanations, checks, corrections, chases, and necessary exceptions. Ask about private checking. Separate invited human participation and scheduled review from unplanned supervision. 4 Measure recovery and provider effort. Record problems detected before the customer, recovery within authority, repeated failures, and staff time. A lower customer burden can coexist with unsustainable internal work; you need to see both. 5 Compare with a like baseline. Use the same unit, scope, and observation method. Look for a maintained or improved outcome with less ordinary customer burden. Explain changes in demand or scope that make comparison imperfect. 6 Choose one repair. Trace the repeated burden to missing context, unclear authority, weak evidence, poor recovery, or an overpromised service. Change the cause, then review a new set of occurrences. Keep the interpretation honest A quiet success count is useful evidence, not the value of S. Absence of messages is not proof of absence of worry. The strongest operating claim is bounded: in this period, these conditions were verified, these burdens were observed, and these uncertainties remain. Source trail: S5 , S12 , S13 , S14 , S15 . Logins fell. What can you conclude? Choose an answer to examine the decision. Absorption is proven. Fewer logins do not establish fulfilled conditions or the absence of private checking. Inspect outcomes and remaining burdens. The customer is definitely leaving. Absence from an interface may be consistent with the intended service. Look for evidence of a lost need or poor outcomes. The observation needs an outcome and burden review. Yes. A quiet, verified occurrence differs from a quiet failure. Operational counts help review the service; they are not a numerical measurement of S. See it in practice Twenty illustrative openings The trial has 20 committed openings. Seventeen meet the original condition with supporting evidence. Two miss it. One remains unknown because completion evidence cannot be established. The original promise was verified in 17 of 20 occurrences, or 85 percent. Unknown does not become success. Of the 17 verified occurrences, 12 have no observed unplanned customer intervention or reported private checking. The other five involve routine approval or chasing. The conservative quiet and verified result is therefore 12 of 20, or 60 percent. It is an operating observation, not a measured absorption rate. Ask what the totals hide The five burdens point to a repeated uncertainty about extra classes. The expected stock is clear for the ordinary schedule but not for an authorized schedule change. The fix belongs in context and authority, not in a more cheerful reminder message. The two misses require separate investigation. Were they detected with enough time to recover? Did the wake condition reach the right person? A missed outcome remains a miss even if the exception was well written. The unknown occurrence reveals an evidentiary gap. Until resolved, the business cannot use it as a quiet success in a sales story. Compare before claiming improvement The team collects the same measures for a comparable baseline. It also records provider effort. If customer burden falls only because the service lead works unsustainable hours, the next design must address that load before expansion. The review ends with a concrete change: connect authorized schedule updates to stock planning and define the adjustment limit. The next trial tests whether the customer can stop managing that recurring variation. Your turn Your review of outcomes and burden Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Population unit period and number of committed occurrences Verified original outcomes missed outcomes and unknowns Routine customer burdens necessary exceptions and chosen contact Private checking and how it was observed or reported Recoveries repeated defects and provider effort Comparable baseline one repair owner and next review date Ready when You can explain whether the expected condition held and who still carried the work, without treating silence or engagement as a substitute for either. I can demonstrate the “Ready when” condition for my service. 03 / Put the whole service to work Cases, pilot, diagnosis, charter C One morning, from promise to completion Follow the ordinary run, a failed route, and a decision that must return. INTEGRATED CASE / 01 An ordinary morning from beginning to end The following run is illustrative. It brings the twelve recipes together in one occurrence rather than treating them as separate features. The standing relationship The gym expects at least 80 clean, usable towels in its cabinet before 5:45 on agreed weekdays. The service includes ordinary coordination and verification. A current schedule is the source for approved variations. The laundry service lead owns unresolved commitments. The authority card allows ordinary replenishment and two named backups inside agreed limits. It does not allow a lower quality standard or an unapproved supplier. The wake condition covers an unresolved threat to opening, an out of scope tradeoff, or accumulated change to the owner's understanding of the arrangement. The preceding afternoon The service creates the next occurrence from the standing schedule. It checks relevant context and uses the active agreement version. The provider accepts a specific commitment under one identifier. The operator keeps a checkpoint early enough to protect recovery time. Before opening The provider completes the delivery. Verification matches current time, location, count, and the agreed quality process. The evidence is connected to this occurrence, not merely to a route or a day. No material uncertainty remains open. The record closes with the evidence and any ordinary variations. The customer's delegate can inspect that record. The owner receives no success message that demands she notice a responsibility already carried. At the gym The owner welcomes a new member. She does not need to become aware of the service run for the towels to be available. Her attention has not vanished; it is participating in the gym's purpose. At the agreed review The operator reviews a sample, checks for missed failures and repeated recovery, and asks about private customer checking. That deliberate review maintains the relationship. It does not require the owner to approve tomorrow's ordinary order. The business has sold more than clean towels. It has accepted the work that lets the owner expect clean towels without repeatedly taking that responsibility back. INTEGRATED CASE / 02 A failed route and a meaningful return Now put the same service under pressure. The purpose of this exercise is to locate the exact point where the customer belongs in the work. Variation that stays below attention At 4:45 the primary route fails. The operator checks the two approved backups. One can preserve the full condition within the remaining allowance. It accepts the occurrence, the original commitment is canceled, and delivery is independently verified before 5:45. The failure remains in the service record. The owner need not learn it as a new assignment. The operator investigates repeated route trouble separately. This recovery maintains the customer's promise while making the provider's weakness visible internally. Variation that changes the promise In a second version, neither backup can meet the deadline. The operator verifies the remaining reserve, establishes the choices still available, and identifies when those choices expire. The wake message reaches the gym's authorized decision maker. It states the expected shortfall, the evidence, the failed recovery, the remaining options, and the default if there is no response. The service does not ask a vague permission question or send a link to a tracking screen. The owner chooses an opening adjustment. That choice is recorded for this occurrence. It does not silently authorize the same shortfall tomorrow. The original condition was missed; a revised plan was accepted. Both facts belong in the record. The repair after the event The laundry checks why its route and backups shared the same failure. If they depended on the same depot or access window, the supposed redundancy may have been weak. It repairs capacity or narrows the offer before resuming the same promise. What the student should notice Both versions contain machine work, human operations, and records. Only the second requires the customer's judgment during the occurrence. The distinction lies in the consequence for the expected condition and the boundary of authority. A later successful delivery cannot erase the customer's intervention. Keep the history honest. Improve the next occurrence. D Adapt the method to your business Meeting food, a weekly report, and an encounter worth attending. ADAPTATION / 01 Feed the meeting while people meet Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. A meeting organizer wants attendees fed and ready to continue at the agreed time. The business opportunity is to maintain that condition while the organizer participates in the meeting. Define the whole outcome Specify the serving time, location, confirmed attendance, confirmed meal requirements, setup, drinks, cleanup responsibility, and authorized spending limit. Use a qualified provider that can meet the requirements. Do not infer a hard dietary constraint from an old preference or substitute around it without agreement. Give context a home Use the authorized attendance source and organizer's confirmed requirements. Set a cutoff for ordinary changes and a rule for later arrivals. Retain venue access and serving instructions so the organizer does not brief the service repeatedly. Carry the commitment The delegate obtains a specific provider acceptance. The service checks preparation early enough for an alternative. Delivery and setup need evidence at the venue; a sent order is not a fed meeting. Ordinary quantity adjustments and provider alternatives can be allowed within defined limits. Hard meal requirements remain hard. If no authorized option can meet them, the unresolved choice returns in time for a different arrangement. Preserve the occasion The system should not send the organizer photographs of every stage of preparation. A participant's experience may matter; the logistics do not need an audience. The organizer's attention belongs in the meeting. What would fail this design A service that delivers food but requires the organizer to count guests, coordinate entry, find missing utensils, and chase cleanup has transferred only part of the obligation. Identify those loose ends before calling the arrangement absorbed. What is the equivalent of the towel cabinet in this service Which human encounter should the service protect Use Recipes 2, 3, 4, 7, and 9. ADAPTATION / 02 Deliver a report that does not need chasing Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. A manager expects a weekly operating report before a planning meeting. The report should reach the agreed destination, cover the right period, use the authorized data, and be ready for the intended decision. Separate prediction and business evidence A prediction machine may produce a predicted report. Its polished form does not establish that the reported business events occurred. The service must connect factual claims to the underlying records and maintain the distinction between observed results and forecasts. The agent's actions include retrieving authorized inputs, placing the report in the agreed location, and recording the completed delivery. The published report is the artifact in the numerator of the relevant equation. Prediction and action remain distinct categories. Carry the changing context The service retains the reporting period, approved definitions, recipients, cutoff, and source owners. A definition change is recorded explicitly. Missing inputs remain unknown; the service does not invent a plausible number to keep the report quiet. Verification and recovery Check period, completeness, calculation consistency, source identity, version, and destination. A missing input may have an authorized fallback, such as a clearly marked pending item. If that fallback changes the usefulness of the report beyond the agreement, bring back the decision before the meeting. Read the attention correctly The manager may want to study the report. That is the purpose of the deliverable. What should disappear is the need to remember to request it, chase missing sections, correct predictable mistakes, or find the right version. If the manager edits the predicted artifact, do not claim that exact artifact was absorbed. The work may still have been useful. The intervention belongs honestly in the account. Which part of the report should be attended and why Which recurring preparation obligation should disappear Use Recipes 2, 3, 6, 7, and 12. This case shows why absence from logistics must not be confused with absence from meaningful use. ADAPTATION / 03 Protect the encounter that is the product Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. A music teacher wants students to listen closely. A host wants guests to feel welcome. A designer wants a client to explore possibilities. In these businesses, some attention is part of the value itself. The instruction to serve a customer who never looks concerns what can be absorbed around that encounter. Do not design away the very participation the customer sought. A lesson service The intended encounter is a prepared student and teacher working on music at an agreed time. The supporting obligations include scheduling, room availability, materials, payment administration, and known access requirements. The service carries those ordinary arrangements. An authorized calendar change reaches the room and materials plan without the parent or student repeating it. A conflict that cannot be resolved within the standing arrangement returns as a specific choice. What should remain human The teacher attends to hesitation, interpretation, emotion, and learning. The student listens and plays. Those encounters should not be replaced by an automatic progress message merely because the system can generate one. The service may maintain practice materials and recurring logistics, while leaving the teacher and student free to decide what the music requires today. A useful business boundary Ask which parts of the customer journey exist to deliver the encounter and which parts are the encounter. Absorb the former where you can. Improve the latter on its own terms. This distinction also applies to products people enjoy browsing, choosing, or discussing. Delegation creates an available relationship; it does not require every customer to use it for every matter. The encounter our customer actively wants to attend Supporting obligations that currently intrude on it A change that protects participation without replacing it Use Recipes 1, 2, 9, and 11. E Build the operating service Connect responsibility, context, action, time, evidence, and recovery. The workbook should change a live arrangement. The minimum implementation is a complete loop with named responsibility, not an elaborate technical stack. Establish one place for the truth Create the current outcome card, context record, authority card, and occurrence register. They may be documents and a simple work queue at first. Assign an owner who keeps versions and resolves conflicting instructions. Connect the action paths List the real channels through which a representative can request, accept, amend, cancel, and verify the work. Check access and capacity in each. Name an operator for channels that cannot yet be handled reliably by software. Do not assume a chat interface can perform an action simply because it can describe it. Give time an owner Open occurrences need scheduled checkpoints. Someone or something must notice a missing acknowledgment, stale context, or approaching recovery deadline without waiting for the customer to ask. A monitored queue and a service operator can supply that capability during a pilot. Connect evidence to closure Choose the observations that establish each important condition. Make unknown results visible to the operator. Test wrong identifiers, old evidence, partial delivery, and failed verification before trusting the closure rule. Connect recovery to authority Put the approved alternatives, limits, stop rules, and unresolved decision route next to the occurrence. Ensure the person or system performing recovery can actually reach those alternatives. Introduce automation deliberately Automate a demonstrated burden when its context, action, evidence, and limits are understood. Keep prediction output distinct from action results. A technical team may implement structured interfaces, durable state, timed checks, and safe retries; the business must still define what those mechanisms are responsible for. Run the whole service Complete one ordinary occurrence, one recoverable failure, one out of scope decision, one canceled occurrence, and one case with missing evidence. Inspect what happened in the world. An internal status of success is insufficient. F Run a thirty day pilot A sequence for testing the relationship and deciding what comes next. THIRTY DAY PILOT / 01 Build and test the relationship Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Thirty days is an illustrative planning frame, not a guarantee that a service will earn absence in a month. If the obligation occurs infrequently or its consequences require more evidence, extend the pilot. Keep the exit conditions tied to the record. Days one through three Select one customer, one obligation, and one accountable service lead. Complete Recipes 1 and 2. Map the present customer burden, including private checking. Agree what the pilot includes and what remains outside it. Finish this stage with a specific outcome card and a baseline plan. If the customer and provider still mean different things by done, resolve that before connecting tools. Days four through seven Complete context, authority, and offer design. Establish the channels and occurrence record. Confirm real access, capacity, data sources, and provider acceptance. Write the wake condition with the customer. Finish with a service another operator can explain. Do not let the person who built the workflow be its only interpreter. Days eight through fourteen Run rehearsals and a small set of supervised live occurrences. Test uncertain acknowledgments, wrong evidence, ordinary recovery, out of scope variation, and cancellation. Keep customer oversight and provider effort visible. Finish with evidence of the complete loop. A failed rehearsal is useful if it exposes the gap before the customer relies on the service. Repair it and repeat the relevant case. Pilot customer obligation and service lead Baseline period and first live occurrence Three failures we must rehearse before reducing supervision Reduce oversight when the evidence supports it. THIRTY DAY PILOT / 02 Reduce burden and decide what follows Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Days fifteen through twenty one Review the supervised record. Resolve defects in identity, scope, evidence, and recovery. Where the results justify it, stop ordinary customer approvals already covered by standing authority. Continue internal verification and the agreed sample review. Days twenty two through thirty Review every eligible occurrence using Recipe 12. Compare fulfilled conditions, unknown outcomes, customer burdens, necessary exceptions, and provider effort with the baseline. Inspect selected quiet occurrences for concealed failure. Test a clean pause or exit. Confirm that future work actually stops and pending commitments are reconciled. This demonstrates that authority and continuity are real operating properties. Choose the next scope Continue the bounded pilot if the evidence is promising but incomplete. Repair a specific gap if outcomes or trust remain unstable. Expand only the dimensions the record supports, such as another weekday or another equivalent location. A second location may introduce different access, capacity, contacts, or evidence. Treat those differences explicitly. Do not copy a label of absorbed from one service to another. The review decision State the next action, supporting evidence, remaining uncertainty, owner, and date. What is now verified and what remains unknown Which customer responsibility has actually become quieter Continue repair or expand and the evidence for that choice Next owner date and boundary of scope G The failure clinic Twelve symptoms that reveal where the customer or provider still carries the gap. FAILURE CLINIC / 01 When the customer still has to manage The customer keeps asking for status Look first for weak evidence, missed commitments, or an unclear next checkpoint. Ask what the customer is afraid might be happening. Repair the reason to check before adding automated status messages. Use Recipes 6, 7, and 10. Every variation requires approval The standing authority may be vague, too narrow, or inaccessible to the operator. Review repeated questions. Grant a bounded category where the customer wants it delegated; preserve genuine retained decisions. Use Recipes 4 and 9. The customer repeatedly explains the same thing Context has no authoritative home, no owner, or no path into the work. Trace one repeated fact from its original source to each actor. Repair the handoff and expiry rules. Use Recipe 3. The system is quiet but outcomes are uncertain Inspect closure rules and evidence. Unknowns may have been labeled successful, or verification may rely on the same unsupported assertion that triggered the action. Reopen unresolved commitments and establish independent observations where needed. Use Recipes 6 and 7. The service works only when one employee is present That employee is carrying the missing state, authority, or judgment. Observe their work, document the parts that can be made explicit, and equip a substitute. Recognize the judgment that remains theirs. Use Recipes 3, 4, and 6. The provider blames the customer delegate Inspect the accepted commitment and each handoff. A provider cannot accept an outcome and then treat a channel failure as someone else's whole problem. Equally, a provider cannot act beyond authority because the delegate is unreachable. Name the unresolved commitment and follow the agreed fallback. Use Recipes 4, 5, and 9. In every case, locate the obligation that fell back into a person's mind. That is a more useful diagnosis than asking whether the AI model needs to be cleverer. FAILURE CLINIC / 02 When the quiet service stops being good business Recovery is becoming the ordinary process Count repeat causes and internal effort. Backup capacity may be inadequate, the promise may exceed the service's capacity, or context may arrive too late. Repair the primary operation or narrow the offer. Do not make perpetual rescue invisible to management. Use Recipes 8, 11, and 12. No single event breaches a limit but the relationship has changed Compare cumulative cost, substitutions, and delays with the customer's current understanding. Individually allowed changes can create an unfamiliar whole. Bring back the meaningful change and revise the standing agreement explicitly. Use Recipes 3, 4, and 9. Customer engagement falls and the business panics Check whether verified outcomes remain sound and customer burden has fallen. For a service meant to be absorbed, fewer logins can be consistent with success. Look for evidence of a lost need or poor service rather than assuming every absence requires a marketing interruption. Use Recipe 12. The customer feels ignored You may have removed wanted human contact along with routine coordination. Ask which encounters carry value. Restore access, hospitality, advice, or conversation where it belongs. An absorbing service can be easy to reach. Use Recipes 1 and 11. The service is quiet because leaving is difficult Test the exit path. Can the customer stop future work, retrieve the authorized record, and understand open obligations? Repair barriers that turn inattention into captivity. The customer's absence must remain compatible with their agency. Use Recipes 4 and 11. The numbers look better because the definition changed Inspect the denominator of the operating measure, the original promise, and excluded cases. Keep misses and unknowns visible. A revised scope can be sensible; represent it as a revision rather than retrospective success. Use Recipe 12. The business question is whether you can sustain a valuable condition while reducing the customer's ordinary burden. A quiet interface, a busy agent, or a favorable activity count cannot answer that question alone. H Your service charter Bring the completed recipes together into one statement of responsibility. Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. Complete this page after the recipes. Keep it with the active agreement and give the people operating the service access to the supporting records. Duplicate it for each materially different service. Customer obligation complete condition and occurrence boundary Accountable owner and authoritative context Standing authority limits and prohibited substitutions Evidence of completion and owner of unknown results Ordinary recovery and wake condition including deadline Pilot stage review evidence and next decision Pause exit process and agreement version The test is simple to state and demanding to meet: the expected condition continues while the customer participates elsewhere. 04 / Teach, test, and go deeper The exercise and its foundations I The meeting room that was supposedly ready A capstone for teams and students. Work the scenario before revealing the commentary. Think through these prompts or type working notes. Notes are temporary on this page; copy anything you want to keep before leaving. A small training company sells a room preparation service. Before each workshop, the room should have the correct seating, current materials, working display equipment, and agreed access arrangements. The trainer wants to arrive and teach. The current system asks the trainer to confirm the room every morning. It copies the last workshop's attendance count. It marks the job complete when a checklist email is sent. It allows repeated equipment rentals below a per-rental limit but has no total event limit. A different employee handles each late change. During the latest workshop, materials were printed for the wrong course version. The display was unavailable. The trainer saw no alert because the automation labeled both requests sent. The trainer spent the first twenty minutes repairing the setup. Your assignment Design the service for the trainer who should be able to stop looking at room preparation. Keep the teaching encounter attended. Use the recipes and prepare a one page service charter. Write the complete expected condition and hard constraints Identify the authoritative context and ownership gaps Set ordinary authority total limits and an exit or stop rule Replace the completion rule with evidence and recovery Draft the wake condition and one useful exception message Finish by choosing three pilot tests and two operating measures. Explain why neither a sent email nor zero alerts proves the room was ready. Use the answer commentary on the next page after completing your design. After you have worked the scenario Reveal the answer commentary There is more than one sound design. Evaluate whether the proposed service carries the outcome across changing conditions and returns the right decision at the right time. The outcome and context A strong answer specifies room, course version, attendance source, layout, equipment function, materials, access, and readiness time. It includes ordinary coordination. It identifies who can change each source and how late changes reach every operator. Copying the last event without checking current context is a defect. Authority and action Ordinary setup should proceed under standing authority. Permitted replacements must preserve the required teaching conditions. Limits must cover the total event as well as individual rentals. Pausing an event must stop pending setup and reconcile commitments, not merely remove a calendar entry. Evidence and recovery Sent requests remain open until accepted and performed. The correct materials are checked against the current course version. Equipment needs a functional test in the room, early enough to obtain an approved replacement. A timestamped setup record must refer to this event. Missing evidence remains unknown. A useful exception The message identifies which condition cannot be maintained, the teaching consequence, verified evidence, attempted recovery, remaining options, and the decision deadline. It reaches the person authorized to choose. If a workable approved replacement exists, the service uses it without requiring another ordinary confirmation. Tests and measures Useful tests include an outdated course version, a missing equipment acknowledgment, an unavailable display, a late authorized attendance change, and a cancellation. Measure verified original readiness and customer supervision or chasing, keeping misses and unknowns visible. Include provider effort before scaling. The conceptual answer The trainer's repair work shows that preparation returned to attention. The later start does not erase it. The aim is to absorb preparation so the trainer can attend to learners. A service that removes the teaching encounter has misunderstood the desired outcome. The strongest submission states what would count as failure and how the service would discover it before the trainer becomes the monitoring system. J Words used precisely A glossary of the concepts and operating terms used throughout. Absorption In the exact case, the predicted artifact and the completed artifact match, the effective numerator and denominator coincide, Reality equals one, and ln(1) equals zero. No human attention is stolen. The Ideal component condition matters. Actual and Reality Actual is the numerator of the Reality Equation. Reality is the quotient of Actual over Expectation. Use real for ordinary business events rather than using the formal capitalized term loosely. Expectation Predicted and Ideal Expectation is complex: E = P + iI. Predicted is the real component; Ideal is the imaginary component. A service card helps describe a promise operationally; it does not exhaust that structure. Prediction machine and agent A prediction machine predicts an artifact. An agent acts. A tool or product may support both, but a prediction of completion is not the performed action or its evidence. Principal and delegate The principal is the person or organization whose interests and authority govern the delegated work. The delegate represents the principal within the specified scope. Standing authority and wake condition Standing authority defines what may proceed without repeated permission. The wake condition identifies when a consequential change or retained judgment should return to the human. Verification and recovery Verification establishes whether evidence supports the promised condition. Recovery addresses a threatened condition within authority. Unknown evidence is not successful completion. Quiet success This book's operational shorthand for a verified outcome with no observed unplanned customer burden. It is a bounded observation, not a numerical measure of attention or proof of exact absorption. Chosen attention A person may deliberately study a report, enjoy a lesson, inspect a record, or revise a relationship. Removing the obligation to supervise ordinary work does not remove that freedom. K The articles behind the cookbook Fifteen source articles, with an explanation of how each informs the work. The source articles are by John Rector. Links open the published essays. The recipes and business examples in this workbook are applications of the framework, not reported field studies. S1 Worthy of Their Attention The opening article distinguishes making someone look from being worthy of the attention involved in a business relationship. It grounds the customer perspective in the foundation and Recipe 1. S2 Worthy of Their Attention Timing The second article develops timing as a condition of relevance. It supplies the bridge from a worthy subject to the moment a person can receive it. S3 The Timing Hidden Inside Search The third article returns search to first principles. The person approaches while attention is already participating. It underlies the foundation rather than a search marketing strategy. S4 Delegate It The Absorption of Business The fourth article locates the shift from searching to delegating in the Reality Equation. It grounds the distinction between a continuing economic event and a human obligation to attend to it. S5 Serve the Customer Who Is Not Looking The fifth article supplies the gym and laundry example and the changing rules of business. This cookbook develops that argument into operational recipes, cases, and worksheets. S6 No Human Attention Is Stolen The formal account of the predicted artifact, completed artifact, complex Expectation, and exact absorption case. It governs the equation page and the distinction between useful work and absorbed work. S7 Classroom Exercises Completion and Attention Teaching exercises distinguish completion from absorption and clarify that attention can move elsewhere. They inform the foundation, report case, and assessment. S8 The Chat Window Is Not the Future of AI The operational foundation: retain state, recognize when action is appropriate, verify, recover within authority, and surface unresolved exceptions. Recipes 2 through 8 put this into practice. S9 Delegate It The instruction to delegate an outcome and ordinary choices within a standing relationship. It informs authority, service acceptance, and the meeting example. S10 The Wake Condition The customer expectation, rather than the machine confidence alone, governs a meaningful return to attention. It informs Recipe 9 and the review of accumulated drift. S11 The Delegation Boundary Explicit scope, accountable handoffs, and the separation of private capability from shared work. Applied here to context, authority, representatives, and a clean service transition. S12 The Attention Audit Remove unnecessary work before absorbing necessary work. It informs obligation selection and baseline observation. This workbook does not use illustrative attention units as a measured scientific scale. S13 The Trust Gradient Demonstration, supervision, sampling, exception, and absorption describe an earned progression. The record, honored scope, reversibility, and legible history support Recipe 10. S14 The Exception Is the Product A useful exception includes consequence, evidence, attempted recovery, and the remaining judgment. It informs verification, recovery, wake messages, and the failure clinic. S15 Notifications Are Just a Dashboard Broken Into Pieces Routine success notifications can preserve the monitoring burden. Silence alone can also hide failure. The cookbook carries both insights into operation and measurement. The responsibility continues The expected condition holds. The person goes on with life. The work of the book is to make that sentence true for one real service. Prefer a print or editable edition? The same cookbook is also available as a 61 page PDF and a complete editable Word document. These are optional ways to use the material. Print edition · PDF Editable edition · Word John Rector · First edition, October 2026 · Web edition

The same towels.A different obligation.

Open a chapter.Make one service better.

The customer has gone to do something else

What search solved

What the business must carry

Locate absorption in the Reality Equation

A complete artifact

A design principle rather than a dashboard formula

Keep the roles distinct

The customer

The customer delegate

The provider

The accountable operator

Begin with ordinary tools

First ten minutes

Next fifteen minutes

Next fifteen minutes

Final twenty minutes

Choose one recurring obligation

Result

Test before proceeding

A gym and a laundry

What to remove

What to preserve

What to absorb

The bad first choice

Ready when

Define the complete expected condition

Result

A useful sentence

Find the missing sentence

What changes later

Ready when

Maintain the context across time

Result

Test before proceeding

A requirement is uncertain

The operator handoff

The lesson

Ready when

Set bounded standing authority

Result

Test the boundary

Three decisions

Stop means stop

The human responsibility

Ready when

Make your offer usable by a delegate

Result

Test without the sales tour

Acknowledgment matters

What the business should publish

The new sales question

Ready when

Carry the promise through action

Result

Test a dropped acknowledgment

A response is lost

A shift changes

What closes it

Ready when

Verify the result without customer supervision

Result

Test a convincing false claim

The evidence disagrees

During the pilot

Evidence has limits

Ready when

Recover without exporting the problem

Result

Rehearse before relying on it

When recovery cannot preserve the promise

After the occurrence

Ready when

Write the wake condition

Result

Check the bar itself

The system was not surprised

A drift review

Ready when

The same towels.
A different obligation.

Open a chapter.
Make one service better.