At four on Friday, Daniel has had three answers from Mara and just as many reasons to ask her again next week. In this hypothetical studio, Mara has spent the afternoon answering questions that had accumulated during a client visit. Could a supplier replace a standard fitting? Did a draft email sound right? Could a small delivery be booked a day earlier? She answered each question quickly. Everyone thanked her, and the jobs moved forward. On the office board, the afternoon’s delays appeared to have been resolved.
Daniel knew what that recovery had cost. He had understood the fitting issue well enough to recommend the same part Mara approved. He had written the email twice: first in his own words, then in what he guessed would be hers. The supplier’s available delivery dates were already open on his screen. He did not need more time or enthusiasm. What he needed was confidence that Mara would respect his authority to make those decisions after she reviewed them.
What a quick answer leaves unresolved
A founder’s responsiveness can get work moving while leaving the business dependent on the same approval next time. Each rescue reinforces the habit that made it necessary. Being needed begins to hurt the business when answering today’s questions leaves employees with the same reasons to ask again tomorrow.
There is a fair objection: Mara may have caught something Daniel missed. If the replacement fitting had breached the client’s accepted specification, stopping the order would have protected the work. Counting messages cannot tell Mara which approvals are unnecessary. Nor does Daniel’s confidence that he can predict her answer establish that he has authority to decide.
In a possible scenario, Mara makes no public announcement about delegation. Instead, she asks Daniel to show her the three questions as they stood before she replied. Together, they examine the standard each decision had to meet, any authority Daniel lacked, and any commitment that had to be honored. The ‘finish’ requirement turns out to be in an old email rather than in the current drawing pack. The draft email was factually correct; Mara’s revision was merely concerned with its tone. The delivery request stays with Mara because a specific client agreement names who may confirm handover dates.
No decision-making authority has changed hands. The change is more modest: their next discussion will start with what the decision requires, rather than whether Mara is available.
In another version of the story, Mara’s approval was necessary. Suppose the supplier order required a client approval Daniel had not seen, and Mara caught the omission when she replied. Her intervention would then have protected a promise to the client. The appropriate lesson from this would then be to give Daniel access to the approved specification or retain the required approval, rather than treat the order as a routine decision.
When approval protects a real obligation
Both versions look like a busy founder saving a stalled afternoon. Understanding the difference requires examining the information and obligations behind the original request. Nobody in the studio can establish whether approval was necessary simply by how relieved they feel at five o’clock. They will need to examine the original request, the rule that applied and the consequence of acting without approval. Reviewing those records is less satisfying than clearing a full inbox, but it can change next week’s work.
Daniel goes home having completed the week’s work, and Mara goes home having answered everything. Both have been productive, but neither yet has evidence that Monday will be different. True change begins by examining that gap: the difference between clearing a queue and changing why the queue exists.



