“Whatever happened to having delivery sign off on quotes before they go out?”<\/p>\n
At an illustrative services firm, someone asks this about seven weeks after the decision was made, and the room has the same reaction every room has: a pause, then partial recall, then three people offering different accounts of where it got to. Everyone is answering honestly, yet their accounts do not quite agree.<\/p>\n
That pause is the most useful thing in the meeting, and it is worth investigating before the agenda moves on. Working backwards from an absence turns out to be a faster diagnostic than working forwards from a plan, because the absence is a fact and the plan was an intention.<\/p>\n
Begin with the last stage. If delivery had been signing off on quotes for the past seven weeks, where would that be visible?<\/p>\n
In this trace the answer arrives quickly and it is uncomfortable: nowhere in particular. A signed-off quote and an unsigned one leave the same trace in the firm’s systems. There is no field, no folder, no step that a colleague could glance at to know. Which means that even in the version of history where this worked perfectly, only the two people involved could have confirmed it.<\/p>\n
That is worth sitting with before going further back. A commitment whose completion leaves no trace has a peculiar property: success and failure leave the same evidence from the outside. Everything else you find walking backwards is downstream of that.<\/p>\n
The next question going backwards is what the work depended on. Here, delivery sign-off needed the delivery lead to see quotes before they were sent, and quotes were being drafted and sent in a single sitting by whoever was closest to the client.<\/p>\n
So the commitment required a change to how quotes get written, and changing the drafting workflow belonged to someone other than the delivery lead who was expected to approve the quote. This stayed below the surface, because the meeting discussed the sign-off and the drafting habit lived somewhere else entirely.<\/p>\n
Dependencies have a way of being obvious in retrospect and invisible in the room. The colleagues best placed to spot this dependency were drafting the quotes. They were absent because the meeting had been framed as an approval discussion.<\/p>\n
Going back another step: when was this supposed to start?<\/p>\n
The recap says from next month<\/em>. The delivery lead, asked directly, remembers it as something to introduce once the current project push settled. Each recollection is faithful to a different interpretation of the same phrase. The phrase was said in a room and interpreted twice, and no one confirmed which reading held, because confirming felt like distrust among colleagues who trust each other.<\/p>\n This is where a great many commitments come apart, and it rarely looks like disagreement. It looks like two reasonable people carrying two compatible-sounding versions of the same sentence.<\/p>\n The final step back is the meeting itself. The recap names the decision. It names no person, and reading the transcript, no one in the room ever said “I will.”<\/p>\n The delivery lead nodded, and nodding in a meeting where a decision concerns your function is normally taken as acceptance. It is a genuine signal and a weak one. Nodding signals agreement, but it does not create an obligation that can later be checked, and it leaves the room with everyone believing the matter is settled \u2014 which is precisely what makes it dangerous. Ambiguity that produces visible disagreement gets resolved. Ambiguity that produces universal nodding leaves the room looking settled until somebody asks what happened.<\/p>\n Walking backwards passed five moments in reverse order. Turned the right way round, they are the path a commitment has to travel:<\/p>\n Said \u2192 assigned \u2192 dated \u2192 unblocked \u2192 verified.<\/strong><\/p>\n The decision is stated. One named person takes it. A real date or trigger is agreed with that person directly. Whatever it depends on is cleared or given its own owner. And completion becomes visible to somebody who was not in the room.<\/p>\n This is the Commitment Trail, and reconstructing it backwards makes something visible that a forward plan hides. Each moment failed for its own reason \u2014 an unrecorded nod, an ambiguous phrase, an absent drafting habit, an invisible outcome \u2014 and any single repair would have exposed the next. Clarifying the assignment would have exposed the missing date. Fixing the date would then have exposed the drafting dependency. The moments are sequential, so the earliest break is the one worth repairing first.<\/p>\n Two decisions taken in the same room can behave completely differently afterwards, and the reason is usually structural: it comes down to where the change lives.<\/p>\n A change to a template arrives with an owner attached, because templates already belong to someone. Its completion is inspectable: open a recent document and the change is there or it is absent. Assignment and verification come included with the choice of where to put it.<\/p>\n A change to how people behave arrives with neither. It has no default owner, no natural moment of completion, and nowhere a colleague could look. Every one of the five moments has to be supplied deliberately \u2014 by a team that has just watched a similar decision succeed with no visible effort, which makes the extra care feel unnecessary at exactly the wrong moment.<\/p>\n The prediction is therefore available before the meeting ends. The more a decision depends on people remembering to act differently, the more deliberately its owner, date and evidence of completion must be designed.<\/p>\n The recap of that original meeting was correct. It recorded what was said, and what was said was accurate.<\/p>\n A useful record should also preserve what remained unresolved: who changes the drafting workflow, when the rule begins, and where sign-off becomes visible. Polishing those uncertainties out of the recap does not resolve them; it only hides them.<\/p>\n Everything the trace uncovered happened after the meeting ended: a nod interpreted, a phrase read two ways, a dependency in another team’s habits, an outcome with nowhere to appear. All of it occurred where no one was taking minutes, and none of it would appear in a better-written summary, because a summary of a meeting can only contain the meeting.<\/p>\n The record is complete precisely where the risk is lowest, and silent where execution begins. Meeting notes preserve what was said; confirming ownership, fixing deadlines, clearing dependencies and making completion visible often happen after the room has emptied. This is why a team can improve its recaps for a year without improving delivery \u2014 the document was already doing its job.<\/p>\n Choose one thing your team agreed to a month or two ago that quietly did not occur. The absence makes it a better subject than a success, because there is a definite fact to work back from.<\/p>\n Then walk backwards, asking four questions in this order:<\/p>\n Stop at the first question with an unsatisfying answer. That is the earliest break. Repair it first, because every later failure may be a consequence of it. The exercise takes about fifteen minutes and it usually produces an uncomfortable pattern: Most teams repeatedly break at the same moment<\/a>, and knowing where your team usually breaks is worth more than recovering a single decision. Knowing which moment is where the operations system<\/a> starts, and the diagnostic<\/a> names it in writing.<\/p>\n","protected":false},"excerpt":{"rendered":" “Whatever happened to having delivery sign off on quotes before they go out?” At an illustrative services firm, someone asks this about seven weeks after the decision was made, and the room has the same reaction every room has: a pause, then partial recall, then three people offering different accounts of where it got to. Everyone is answering honestly, yet their accounts do not quite agree. That pause is the most useful thing in the meeting, and it is worth investigating before the agenda moves on. Working backwards from an absence turns out to be a faster diagnostic than working forwards from a plan, because the absence is a fact and the plan was an intention. Start at the end and ask who would have seen it Begin with the last stage. If delivery had been signing off on quotes for the past seven weeks, where would that be visible? In this trace the answer arrives quickly and it is uncomfortable: nowhere in particular. A signed-off quote and an unsigned one leave the same trace in the firm’s systems. There is no field, no folder, no step that a colleague could glance at to know. Which means that even in the version of history where this worked perfectly, only the two people involved could have confirmed it. That is worth sitting with before going further back. A commitment whose completion leaves no trace has a peculiar property: success and failure leave the same evidence from the outside. Everything else you find walking backwards is downstream of that. Keep walking back: what stood in the way The next question going backwards is what the work depended on. Here, delivery sign-off needed the delivery lead to see quotes before they were sent, and quotes were being drafted and sent in a single sitting by whoever was closest to the client. So the commitment required a change to how quotes get written, and changing the drafting workflow belonged to someone other than the delivery lead who was expected to approve the quote. This stayed below the surface, because the meeting discussed the sign-off and the drafting habit lived somewhere else entirely. Dependencies have a way of being obvious in retrospect and invisible in the room. The colleagues best placed to spot this dependency were drafting the quotes. They were absent because the meeting had been framed as an approval discussion. Further back: the date two people heard differently Going back another step: when was this supposed to start? The recap says from next month. The delivery lead, asked directly, remembers it as something to introduce once the current project push settled. Each recollection is faithful to a different interpretation of the same phrase. The phrase was said in a room and interpreted twice, and no one confirmed which reading held, because confirming felt like distrust among colleagues who trust each other. This is where a great many commitments come apart, and it rarely looks like disagreement. It looks like two reasonable people carrying two compatible-sounding versions of the same sentence. To the beginning: who actually took it The final step back is the meeting itself. The recap names the decision. It names no person, and reading the transcript, no one in the room ever said “I will.” The delivery lead nodded, and nodding in a meeting where a decision concerns your function is normally taken as acceptance. It is a genuine signal and a weak one. Nodding signals agreement, but it does not create an obligation that can later be checked, and it leaves the room with everyone believing the matter is settled \u2014 which is precisely what makes it dangerous. Ambiguity that produces visible disagreement gets resolved. Ambiguity that produces universal nodding leaves the room looking settled until somebody asks what happened. The Commitment Trail Walking backwards passed five moments in reverse order. Turned the right way round, they are the path a commitment has to travel: Said \u2192 assigned \u2192 dated \u2192 unblocked \u2192 verified. The decision is stated. One named person takes it. A real date or trigger is agreed with that person directly. Whatever it depends on is cleared or given its own owner. And completion becomes visible to somebody who was not in the room. This is the Commitment Trail, and reconstructing it backwards makes something visible that a forward plan hides. Each moment failed for its own reason \u2014 an unrecorded nod, an ambiguous phrase, an absent drafting habit, an invisible outcome \u2014 and any single repair would have exposed the next. Clarifying the assignment would have exposed the missing date. Fixing the date would then have exposed the drafting dependency. The moments are sequential, so the earliest break is the one worth repairing first. Some commitments leave evidence by design Two decisions taken in the same room can behave completely differently afterwards, and the reason is usually structural: it comes down to where the change lives. A change to a template arrives with an owner attached, because templates already belong to someone. Its completion is inspectable: open a recent document and the change is there or it is absent. Assignment and verification come included with the choice of where to put it. A change to how people behave arrives with neither. It has no default owner, no natural moment of completion, and nowhere a colleague could look. Every one of the five moments has to be supplied deliberately \u2014 by a team that has just watched a similar decision succeed with no visible effort, which makes the extra care feel unnecessary at exactly the wrong moment. The prediction is therefore available before the meeting ends. The more a decision depends on people remembering to act differently, the more deliberately its owner, date and evidence of completion must be designed. What a recap can see, and where it stops The recap of that original meeting was correct. It recorded what was said, and what was said was accurate. A useful record should also preserve what remained unresolved: who changes the drafting workflow, when the rule begins, and where sign-off becomes visible. Polishing those uncertainties out of the recap does not resolve them; it only hides them. Everything the trace uncovered happened after the meeting ended: a nod interpreted, a phrase read two ways, a dependency in another team’s habits, an outcome with nowhere to appear. All of it occurred where no one was taking minutes, and none of it would appear in a better-written summary, because a summary of a meeting can only contain the meeting. The record is complete precisely where the risk is lowest, and silent where execution begins. Meeting notes preserve what was said; confirming ownership, fixing deadlines, clearing dependencies and making completion visible often happen after the room has emptied. This is why a team can improve its recaps for a year without improving delivery \u2014 the document was already doing its job. Take something that did not happen Choose one thing your team agreed to a month or two ago that quietly did not occur. The absence makes it a better subject than a success, because there is a definite fact to work back from. Then walk backwards, asking four questions in this order: If this had worked, who outside the conversation would have been able to see it? What did it depend on, and who owned that? What date was explicitly agreed with the responsible person, rather than merely mentioned in their presence? Who explicitly accepted responsibility? Stop at the first question with an unsatisfying answer. That is the earliest break. Repair it first, because every later failure may be a consequence of it. The exercise takes about fifteen minutes and it usually produces an uncomfortable pattern: Most teams repeatedly break at the same moment, and knowing where your team usually breaks is worth more than recovering a single decision. Knowing which moment is where the operations system starts, and the diagnostic names it in writing.<\/p>\n","protected":false},"author":113,"featured_media":34803,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"drb_seo_title":"Why Meeting Decisions Stall After the Recap","drb_seo_desc":"The notes are accurate and nothing moved. Follow one decision from what was said to where completion becomes visible, and find the exact point it stopped.","footnotes":""},"categories":[1629],"tags":[],"class_list":["post-34228","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-systems-operations"],"_links":{"self":[{"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/posts\/34228","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/users\/113"}],"replies":[{"embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/comments?post=34228"}],"version-history":[{"count":5,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/posts\/34228\/revisions"}],"predecessor-version":[{"id":34789,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/posts\/34228\/revisions\/34789"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/media\/34803"}],"wp:attachment":[{"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/media?parent=34228"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/categories?post=34228"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/tags?post=34228"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}To the beginning: who actually took it<\/h2>\n
The Commitment Trail<\/h2>\n
Some commitments leave evidence by design<\/h2>\n
What a recap can see, and where it stops<\/h2>\n
Take something that did not happen<\/h2>\n
\n