--- title: "Tracking, closing and learning · DeliverySheet" description: "What happens once the promise is made — status that says something, an outcome that is not just done, and a retrospective that is not theatre." canonical_url: "https://www.deliverysheet.com/topics/deliver" last_updated: 2026-10-10 meta: author: "Tan Gravam" "og:description": "What happens once the promise is made — status that says something, an outcome that is not just done, and a retrospective that is not theatre." "og:image": "https://www.deliverysheet.com/_og/s/o_30f997b4838710d2.png" "og:image:alt": "After the commitment: tracking, closing and learning — DeliverySheet topic card" "og:image:height": "600" "og:image:type": image/png "og:image:width": "1200" "og:title": "After the commitment: tracking, closing and learning — DeliverySheet" "twitter:description": "What happens once the promise is made — status that says something, an outcome that is not just done, and a retrospective that is not theatre." "twitter:image": "https://www.deliverysheet.com/_og/s/o_30f997b4838710d2.png" "twitter:image:alt": "After the commitment: tracking, closing and learning — DeliverySheet topic card" "twitter:title": "After the commitment: tracking, closing and learning — DeliverySheet" --- > Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt) [← All writing](https://www.deliverysheet.com/blog) **Topic ** # **After the commitment: tracking, closing and learning** ## **How do you keep a delivery commitment honest after it is made?** **The short answer ** Once work is committed, three things keep the promise honest. Report status as a judgement with a reason rather than a colour, so that green means someone decided it was green. Close the commitment with an explicit outcome that names what shipped and, when the result was not clean, what differed from what was promised — not a binary done. And require a written lesson before a demand is complete, because a thumbs-up records that a retrospective happened rather than what was learned. Each of the three exists to stop the previous one from quietly becoming a formality. Almost everything written about delivery governance stops at the moment the commitment is made. That is where the interesting decision is — but it is not where the promise is kept or broken, and a process that goes quiet after the yes is a process that cannot tell you whether its yeses were any good. ## Status has to carry its reasoning A [colour on a board](https://www.deliverysheet.com/glossary/rag-status) decays fast, because reporting amber costs a conversation and reporting green costs nothing. Everything drifts green and then goes red without passing through amber, which is the tell. What survives is the sentence underneath: what changed, what is now different from the plan, and what decision or help is needed. Ask for those and the colour becomes honest as a side effect, because it is hard to write "green" directly above "the security review is unscheduled and needed by the 14th". ## Closing is a comparison, not a checkbox "Done" throws away the only data worth keeping: how the [outcome differed from the promise](https://www.deliverysheet.com/glossary/delivery-outcome). Without that delta you cannot answer whether your estimates run light, whether early commitments miss more often, or whether one team's "high confidence" means what another's does. Three closes rather than one — delivered as committed, delivered with exclusions, not delivered — and the difference recorded whenever the result was not clean. ## One written lesson beats a full report Retrospectives fail by producing alignment rather than memory. The narrow fix is a single sentence answering what you now know that you did not know when you committed, attached to the demand it came from rather than filed under the ceremony. Required, so it happens; cheap, so it happens honestly. A verdict alone records that a retrospective occurred, not what was learned. Each of the three exists to stop the previous one becoming a formality: reasoning keeps status meaningful, an honest close keeps the reasoning checkable, and a required lesson keeps the close worth having a year later. ## **The full argument ** Keeping a promise visible while it is being kept, closing it honestly, and learning something the next demand can use. - [**The say/do ratio: measuring delivery predictability without scoring people**](https://www.deliverysheet.com/blog/say-do-ratio-delivery-predictability) The say/do ratio is commitments kept over commitments made. Three ways the number lies, how to count it from a record, and why it never sits next to a name. - [**A project status meeting agenda that makes decisions**](https://www.deliverysheet.com/blog/project-status-meeting-agenda) A 30-minute status meeting agenda: written updates first, then what changed, the decisions needed, changes to what was promised, and who is silent. - [**Lessons learned: a template and examples**](https://www.deliverysheet.com/blog/lessons-learned-template) A three-sentence lessons learned template, six examples in weak and strong form, and how a lesson differs from a sprint retrospective and a post-mortem. - [**How to tell stakeholders a project is late**](https://www.deliverysheet.com/blog/telling-stakeholders-a-project-is-late) When to tell stakeholders a project is delayed, the four parts of the message, and five project delay emails to copy, from a new date to a stop. - [**A change request process that fits on one page**](https://www.deliverysheet.com/blog/change-request-process) A lightweight change request process: what a request must state, who decides, and when to re-baseline with a reason. With a copyable checklist. - [**When to stop a project you already committed to**](https://www.deliverysheet.com/blog/when-to-stop-a-committed-project) Sunk cost, the three signals that justify cancelling, kill criteria set at commitment time, and how to close a stopped project honestly. - [**The status report that answers questions**](https://www.deliverysheet.com/blog/engineering-status-report) The four-part status report leadership can actually use: committed, closed honestly, at risk with reasons, and exceptions. Copy the shape. - [**Your first 90 days: aim for one honest close**](https://www.deliverysheet.com/blog/first-90-days-one-honest-close) New engineering managers instrument velocity first. The record that actually builds trust is one commitment, closed honestly against what was promised. - [**Reporting delivery to leadership: promises, not activity**](https://www.deliverysheet.com/blog/reporting-delivery-to-leadership) Activity lists answer no question leadership has. Report promises against outcomes: what was committed, what closed honestly, what slipped and why. - [**Close the quarter by counting the exceptions**](https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions) Three counts close a quarter: honest closes, slips with named differences, and early-commitment exceptions. Each changes next quarter's line. - [**Green is a judgement, not a colour**](https://www.deliverysheet.com/blog/rag-status-is-a-judgement) Status reporting decays into a colour nobody believes. What makes it useful again is requiring the reason, not the rating. - [**"Delivered" is not an outcome**](https://www.deliverysheet.com/blog/delivered-is-not-an-outcome) Closing a commitment with a checkbox loses the only information worth keeping: what shipped, and how it differed from what was promised. - [**A retrospective that isn't theatre**](https://www.deliverysheet.com/blog/a-retrospective-that-isnt-theatre) Most retrospectives produce agreement and no memory. The one-question format: require one written lesson, attached to the work it came from. - [**What "complete" should mean**](https://www.deliverysheet.com/blog/what-complete-should-mean) Most systems call work complete when it stops. A more useful definition: complete when the outcome is recorded and something was learned. Defined in the glossary: [Re-baseline](https://www.deliverysheet.com/glossary/re-baseline), [Delivery outcome](https://www.deliverysheet.com/glossary/delivery-outcome), [RAG status](https://www.deliverysheet.com/glossary/rag-status), [Honest close](https://www.deliverysheet.com/glossary/honest-close) I'm Tan Gravam. I build **DeliverySheet** — it takes a vague work request to a clear delivery decision, so the shape, owner, capacity, dependencies and open questions are on the table before anyone commits people or a date. $189/month per workspace, unlimited members. 7-day free trial — card required, cancel before it ends and you're not charged. I answer the support email myself. [**Start 7-day trial **](https://www.deliverysheet.com/login?next=/app) [**See pricing **](https://www.deliverysheet.com/pricing) [**Glossary **](https://www.deliverysheet.com/glossary) ```json {"@context":"https://schema.org","@graph":[{"@id":"https://www.deliverysheet.com/#website","@type":"WebSite","description":"Turn raw work requests into structured, decision-ready demands before you commit people, budget, or a date. AI-assisted shaping, planning and commitment governance for engineering leaders.","name":"DeliverySheet","url":"https://www.deliverysheet.com/","publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/topics/deliver#webpage","dateModified":"2026-10-10","datePublished":"2026-08-05","description":"What happens once the promise is made — status that says something, an outcome that is not just done, and a retrospective that is not theatre.","name":"Tracking, closing and learning","url":"https://www.deliverysheet.com/topics/deliver","@type":["WebPage","FAQPage"],"breadcrumb":{"@id":"https://www.deliverysheet.com/topics/deliver#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"mainEntity":[{"@id":"https://www.deliverysheet.com/topics/deliver#/schema/question/1"}],"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/topics/deliver"]}],"primaryImageOfPage":{"@id":"https://www.deliverysheet.com/#logo"}},{"@id":"https://www.deliverysheet.com/#identity","@type":"Organization","alternateName":"Delivery Sheet","description":"Turn raw work requests into structured, decision-ready demands before you commit people, budget, or a date.","name":"DeliverySheet","url":"https://www.deliverysheet.com","founder":{"@type":"Person","@id":"https://www.deliverysheet.com/about#person","name":"Tan Gravam"},"logo":{"@id":"https://www.deliverysheet.com/#logo"}},{"@id":"https://www.deliverysheet.com/topics/deliver#breadcrumb","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","name":"Home","item":"https://www.deliverysheet.com","position":1},{"@type":"ListItem","name":"Writing","item":"https://www.deliverysheet.com/blog","position":2},{"@type":"ListItem","name":"After the commitment: tracking, closing and learning","item":"https://www.deliverysheet.com/topics/deliver","position":3}]},{"@id":"https://www.deliverysheet.com/topics/deliver#article","@type":"Article","dateModified":"2026-10-10","datePublished":"2026-08-05","description":"What happens once the promise is made — status that says something, an outcome that is not just done, and a retrospective that is not theatre.","headline":"After the commitment: tracking, closing and learning","inLanguage":"en","thumbnailUrl":"https://www.deliverysheet.com/_og/s/o_30f997b4838710d2.png","author":{"@id":"https://www.deliverysheet.com/about#person"},"image":{"@id":"https://www.deliverysheet.com/#/schema/image/1"},"isPartOf":{"@id":"https://www.deliverysheet.com/topics/deliver#webpage"},"mainEntityOfPage":{"@id":"https://www.deliverysheet.com/topics/deliver#webpage"},"publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/topics/deliver#/schema/question/1","@type":"Question","inLanguage":"en","name":"How do you keep a delivery commitment honest after it is made?","acceptedAnswer":{"@type":"Answer","text":"Once work is committed, three things keep the promise honest. Report status as a judgement with a reason rather than a colour, so that green means someone decided it was green. Close the commitment with an explicit outcome that names what shipped and, when the result was not clean, what differed from what was promised — not a binary done. And require a written lesson before a demand is complete, because a thumbs-up records that a retrospective happened rather than what was learned. Each of the three exists to stop the previous one from quietly becoming a formality."}},{"@id":"https://www.deliverysheet.com/topics/deliver#/schema/item-list/1","@type":"ItemList","itemListElement":[{"@type":"Article","headline":"The say/do ratio: measuring delivery predictability without scoring people","description":"The say/do ratio is commitments kept over commitments made. Three ways the number lies, how to count it from a record, and why it never sits next to a name.","url":"https://www.deliverysheet.com/blog/say-do-ratio-delivery-predictability","position":1},{"@type":"Article","headline":"A project status meeting agenda that makes decisions","description":"A 30-minute status meeting agenda: written updates first, then what changed, the decisions needed, changes to what was promised, and who is silent.","url":"https://www.deliverysheet.com/blog/project-status-meeting-agenda","position":2},{"@type":"Article","headline":"Lessons learned: a template and examples","description":"A three-sentence lessons learned template, six examples in weak and strong form, and how a lesson differs from a sprint retrospective and a post-mortem.","url":"https://www.deliverysheet.com/blog/lessons-learned-template","position":3},{"@type":"Article","headline":"How to tell stakeholders a project is late","description":"When to tell stakeholders a project is delayed, the four parts of the message, and five project delay emails to copy, from a new date to a stop.","url":"https://www.deliverysheet.com/blog/telling-stakeholders-a-project-is-late","position":4},{"@type":"Article","headline":"A change request process that fits on one page","description":"A lightweight change request process: what a request must state, who decides, and when to re-baseline with a reason. With a copyable checklist.","url":"https://www.deliverysheet.com/blog/change-request-process","position":5},{"@type":"Article","headline":"When to stop a project you already committed to","description":"Sunk cost, the three signals that justify cancelling, kill criteria set at commitment time, and how to close a stopped project honestly.","url":"https://www.deliverysheet.com/blog/when-to-stop-a-committed-project","position":6},{"@type":"Article","headline":"The status report that answers questions","description":"The four-part status report leadership can actually use: committed, closed honestly, at risk with reasons, and exceptions. Copy the shape.","url":"https://www.deliverysheet.com/blog/engineering-status-report","position":7},{"@type":"Article","headline":"Your first 90 days: aim for one honest close","description":"New engineering managers instrument velocity first. The record that actually builds trust is one commitment, closed honestly against what was promised.","url":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close","position":8},{"@type":"Article","headline":"Reporting delivery to leadership: promises, not activity","description":"Activity lists answer no question leadership has. Report promises against outcomes: what was committed, what closed honestly, what slipped and why.","url":"https://www.deliverysheet.com/blog/reporting-delivery-to-leadership","position":9},{"@type":"Article","headline":"Close the quarter by counting the exceptions","description":"Three counts close a quarter: honest closes, slips with named differences, and early-commitment exceptions. Each changes next quarter's line.","url":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions","position":10},{"@type":"Article","headline":"Green is a judgement, not a colour","description":"Status reporting decays into a colour nobody believes. What makes it useful again is requiring the reason, not the rating.","url":"https://www.deliverysheet.com/blog/rag-status-is-a-judgement","position":11},{"@type":"Article","headline":"\"Delivered\" is not an outcome","description":"Closing a commitment with a checkbox loses the only information worth keeping: what shipped, and how it differed from what was promised.","url":"https://www.deliverysheet.com/blog/delivered-is-not-an-outcome","position":12},{"@type":"Article","headline":"A retrospective that isn't theatre","description":"Most retrospectives produce agreement and no memory. The one-question format: require one written lesson, attached to the work it came from.","url":"https://www.deliverysheet.com/blog/a-retrospective-that-isnt-theatre","position":13},{"@type":"Article","headline":"What \"complete\" should mean","description":"Most systems call work complete when it stops. A more useful definition: complete when the outcome is recorded and something was learned.","url":"https://www.deliverysheet.com/blog/what-complete-should-mean","position":14}]},{"@id":"https://www.deliverysheet.com/about#person","@type":"Person","jobTitle":"Founder","name":"Tan Gravam","url":"https://www.deliverysheet.com/about","sameAs":["https://gravam.com","https://twitter.com/TanGravam","https://github.com/TanGravam"]},{"@id":"https://www.deliverysheet.com/#logo","@type":"ImageObject","caption":"DeliverySheet","contentUrl":"https://www.deliverysheet.com/logo.png","inLanguage":"en","url":"https://www.deliverysheet.com/logo.png"},{"@id":"https://www.deliverysheet.com/#/schema/image/1","@type":"ImageObject","contentUrl":"https://www.deliverysheet.com/_og/s/o_30f997b4838710d2.png","inLanguage":"en","url":"https://www.deliverysheet.com/_og/s/o_30f997b4838710d2.png"}]} ``` ## Sitemap See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.