A quick reply can promise very little or far too much. It may confirm that a message arrived, identify who is handling it or commit somebody to an answer. Those are different arrangements. The person waiting needs to know which one they have.
In Chapter 16 of Infinite Upside, Vijay Sheth wants help with communication to make him easier to reach. Later, he wants to arrive at a family occasion with fewer decisions waiting and put the phone away. Both wishes need an arrangement behind them. Faster replies alone could leave him reachable for even more unfinished decisions.
What can the other person rely on?
Consider an invented exhibition-design studio. On Tuesday evening, a client asks for two display counters instead of the one in the approved plan. Fabrication is due to begin Thursday morning. The studio needs an approved layout by Wednesday at 3 p.m. to keep the existing production slot.
The owner is away that evening. Mina, the project lead, has agreed to review the request Wednesday morning and send the client an update by 10 a.m. She has the approved drawings and access to the shop schedule. The venue still needs to confirm the space available.
A reply saying “Absolutely, we’ll sort it” could sound as though the change has already been agreed. A reply saying only “Received” would leave the client guessing whether anyone is checking the change or whether the original plan still applies.
An illustrative reply could say:
“Mina has your request and will check the layout and production slot tomorrow morning. She’ll update you by 10. The current approved plan stays in place until we confirm a change.”
That message promises a particular next contact from someone who has accepted the work. It does not promise that both counters will fit or that the change has been approved. The client can still ask whether that timing meets their own need.
An update can contain an unresolved answer
At 10 a.m., suppose Mina has checked the shop schedule but the venue has not answered. Keeping the update promise means telling the client what is known, what remains open and when the pending choice becomes consequential. It does not require inventing certainty to make the reply look complete.
The studio still needs approval by 3 p.m. Mina needs to find out how long drawing and checking the revised layout will take, then bring the client a choice before that preparation window disappears. Keeping the original design may preserve the slot. A later change may need a different production date. The client’s acceptance of either arrangement remains separate from the studio proposing it.
A succession of punctual updates can still leave the important decision too late. Judge the communication by whether the next person had a useful choice while they could still make it.
For a response arrangement of your own, name who can do the next piece of work, what they can decide and when they will return with something useful. If nobody has accepted that responsibility, an automatic acknowledgment should not imply that someone has.
Do not make people infer the deadline
The sender can create pressure without intending an immediate answer. In their 2021 research on email urgency, Laura Giurge and Vanessa Bohns found that recipients overestimated how quickly senders expected replies to nonurgent work emails sent outside normal working hours. Brief notes making the sender’s expectations explicit reduced that bias in their studies.
That finding concerns nonurgent work email. The studio’s production deadline still needs its own plan. A routine question sent on Sunday and a customer problem that will remove a useful option before morning should not inherit the same response expectation.
If the owner sends a routine idea to Mina after dinner, they can say when they actually want it considered. “For our Thursday review” supplies a different instruction from a message that merely arrives at an unusual hour. The owner also has to behave consistently with it. Asking at breakfast why the idea has not been handled would make the stated timing unreliable.
Give the other person the timing you mean, rather than leave them to infer it from your sending habits. Do the same when requesting something urgent. Explain what needs to happen and what is lost if it waits.
Leave a real route for what cannot wait
Being away from routine decisions can coexist with being available for something important. In the book, a message from family may matter urgently without a commercial deadline attached. A system organized only around business due dates would miss part of what Sheth wants it to protect.
Agree which situations should interrupt an absence and who can reach you. Keep the arrangement understandable to the people using it. A relative should not need to present a business case for wanting you there. A colleague should not need to label every ordinary question urgent to get a decision the role requires.
A faster substantive response can be worth arranging. Suppose the same studio has a separate approved delivery booked for that evening. The driver reaches the venue, finds the assigned loading entrance locked and must unload before access ends at 8 p.m. An acknowledgment followed by a morning update would miss the delivery window.
The studio has agreed evening delivery support with the client. Its on-duty coordinator has accepted the shift, has the driver’s and venue manager’s numbers, and can authorize another entrance within the venue’s approved access plan. She contacts the manager, confirms which entrance can be used and tells the driver where to go. If none is available, she brings the client the remaining delivery options while they can still choose. The quick response is useful because someone can act on an existing obligation.
That cover needs working time and a named relief person when the coordinator is unavailable. It should not depend on her answering every message during every evening. The founder absence test examines the responsibility behind that arrangement.
After an afternoon away, look at a few actual messages. Did routine work wait until the agreed time without penalty? Did a consequential issue reach someone able to handle it? Were you present for the occasion you meant to attend? Those answers say more than the speed of the first acknowledgment.
Read alongside the book
Chapter 16, A Company That Can Think; Chapter 17, Enough to Enjoy, More to Build.
Original commentary and discussion material. Read the full personal accounts in Infinite Upside: Building Wealth With Room to Live, by Vijay Sheth.
Check the responsibility behind the response
Could the next decision happen without the founder?