Exercise 2: Why Committing to "When" Beats an Invented Number or Silence — Possible Solution ==================================================================== WHY AN INVENTED NUMBER FAILS ------------------------------ An invented timeline, offered purely to sound reassuring before the problem is actually understood, is exactly the "reassuring guess" backup1's own Chapter 9 warned against. It feels satisfying to hear in the moment, but per this chapter's own reasoning, "a broken promise damages trust more than an honest, uncertain estimate ever would" - if the guess turns out wrong, which is likely since it wasn't based on real information, the user now has a second problem (a broken promise) layered on top of the first. WHY SILENCE FAILS TOO ------------------------------ Staying silent about timing provides no information at all, which per this chapter's own Chapter 3 opening reasoning (Exercise 1) is exactly what allows uncertainty to build into frustration - the user has nothing to judge progress against and no way to distinguish "still being worked on" from "forgotten." WHY "I'LL UPDATE YOU BY [SPECIFIC TIME]" AVOIDS BOTH FAILURES ------------------------------ This statement makes no claim about the actual resolution timeline, which the technician genuinely doesn't know yet - so it can't become a broken promise about something outside their current knowledge. But it does make a specific, checkable commitment about something the technician can actually control: when the next piece of real information will arrive. Unlike silence, this gives the user something concrete to expect and a specific point at which they can reasonably follow up if needed. WHY THIS IS GENUINELY DIFFERENT FROM BOTH ALTERNATIVES, NOT A MIDPOINT BETWEEN THEM ------------------------------ An invented number and silence both fail because they either promise something not actually known, or offer nothing at all. This statement succeeds specifically because it commits only to what's actually within the technician's control (when they'll check back in), while being fully honest that the actual answer isn't known yet - a distinct third option rather than a compromise between the other two. WHY THIS WORKS AS AN ANSWER ------------------------------ It explains specifically why an invented number risks becoming a broken promise, explains why silence allows uncertainty to build unchecked, and explains why committing to a specific update time avoids both failure modes by only promising what's genuinely within the technician's control.