The bedtime rule, often called the Ten-Minute Bedtime Rule, shows up in product circles through frameworks like those promoted by consultants drawing from books such as “The Effective Executive” and later PM training programs. It instructs teams to close the day by writing a short list of observations, model outputs, or user signals before sleep. The claim is that this tidy capture step turns scattered input into retained knowledge without extra overhead.
The rule breaks once AI features ship because the input no longer arrives as discrete daily packets. Live agents generate continuous streams of partial answers, edge-case refusals, and volunteer rephrasings that arrive at 11 p.m. and again at 6 a.m. The ten-minute window cannot sort which of those outputs already changed the product behavior that same afternoon.
This separation between capture and action worked when product cycles moved in weeks. AI rollouts compress the cycle to hours, so the habit of parking insights for later review creates lag that users feel immediately.
This is the foundational misread that causes product teams to treat learning as an after-hours activity rather than the material that must alter the next deployment.
John Wesley’s three rules offer the needed lens. He told early Methodists to do no harm, do good, and stay in love with God through ordinary disciplines. Applied to product work, the rules become filters that decide which incoming signal requires an immediate change to the shipped system rather than another note in a document.
Why the bedtime rule breaks once live agents ship
At SermonCentral we released a simple agent that suggested age-appropriate rephrasings for children’s ministry scripts. Within two days the agent began softening references to judgment in ways that matched the tone of one large church network but clashed with another. The bedtime list captured the pattern on night one. By night three the mismatch had already reached volunteers who printed the scripts and used them.
The ten-minute capture recorded the observation correctly. It did not trigger any rollback or prompt adjustment because the rule treats the note as sufficient. In practice the agent continued producing the same softened language until a manual review three days later.
Real usage data from the smallest churches showed the problem first. Those volunteers do not file tickets. They simply stop returning to the tool. The bedtime list had no mechanism to surface that drop-off against the agent’s output log.
Wesley’s rules turn raw model output into a decision filter
The first rule, do no harm, forces a check against the most vulnerable user before any output stays live. For the children’s script agent this meant asking whether a suggested rephrasing would confuse a new volunteer who had never taught the story before. If the answer was unclear, the output route changed to a flagged review queue rather than direct suggestion.
The second rule, do good, asks what concrete action the output should enable that day. In the Bible Gateway experiments this looked like requiring every model suggestion to point toward a next step the reader could take on the same visit, such as a short audio clip or a parallel passage. Outputs that only added information without enabling that step were suppressed.
The third rule, stay in love with God through ordinary disciplines, maps to keeping the product tied to the actual rhythm of ministry work. For agents this meant testing whether the suggestion still made sense when the user had only seven minutes between services. Many clever completions failed that test and were removed.
These filters run at decision time, not at the end of the day. They force the product manager to judge the output against live constraints rather than collect it for later sorting.
What replaces the bedtime rule: ownership transfer
The shift is from recording an insight to assigning the change it requires. When an agent surfaces a new refusal pattern, the next step is not a note but a one-line ownership statement that names the person who will adjust the prompt or the guardrail before the next deployment window.
At one rollout the team moved from end-of-day summaries to a shared log that required each entry to include the exact parameter or content rule that would change as a result. Entries without that line were deleted after twenty-four hours. The volume of notes dropped sharply, but the number of actual prompt changes rose.
This transfer also surfaces when the input should not change the product at all. Some model behaviors look novel in the moment yet match patterns already handled by existing volunteer workflows. Wesley’s first rule catches those cases quickly because the test is whether harm would occur if nothing changed.
Even classic guidance on healthy routines assumes a stable input, which is exactly why the bedtime rule fails once shipped AI behavior keeps shifting.
Your Turn: Apply This Today
- Pick the single AI feature now in production that produces the most daily output and add a one-question harm check to its review log before any new suggestion reaches users.
- Require every model experiment this week to name the exact deployment parameter or content rule that will change if the experiment succeeds, and delete any experiment notes that omit that line.
- Run the do-good test on three recent agent outputs by asking whether each one points a volunteer to an action they can finish in the same session; remove any that do not.
- Review the last forty-eight hours of agent logs against the seven-minute volunteer window and flag any suggestion that requires more context than a printed page can hold.
- Assign ownership for the top three recurring edge cases you logged this week by writing the owner’s name and the next deployment date next to each case.
- Delete every capture note older than seven days that has not produced a shipped change, then move the remaining items into the live decision queue.
The CPO Who Captured What the Spreadsheet Missed shows what happens when raw signals stay disconnected from decisions. The Trust Layer No One Budgets For traces how unfiltered agent behavior erodes volunteer confidence over time.
I consult with product leaders on AI feature rollouts, input filtering for live decisions, and ownership transfer in ministry-facing tools. Let’s talk.