---
title: "Essays on delivery governance · DeliverySheet"
description: "Essays on delivery governance: shaping demands before committing, sizing capacity honestly, and closing what you promised."
canonical_url: "https://www.deliverysheet.com/blog"
meta:
  author: "Tan Gravam"
  "og:description": "Essays on delivery governance: shaping demands before committing, sizing capacity honestly, and closing what you promised."
  "og:image": "https://www.deliverysheet.com/og-card-v2.png"
  "og:image:alt": "DeliverySheet: a committed one-pager with its stamp, and the line \"From vague demand to a clear delivery decision.\""
  "og:image:height": "630"
  "og:image:type": image/png
  "og:image:width": "1200"
  "og:title": "Essays on delivery governance — DeliverySheet"
  "twitter:description": "Essays on delivery governance for engineering managers, written while building DeliverySheet."
  "twitter:image": "https://www.deliverysheet.com/og-card-v2.png"
  "twitter:title": "Essays on delivery governance — DeliverySheet"
---

> Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt)

# **Writing **

Notes on delivery governance, written while building DeliverySheet. Opinionated, specific, and about the part of the job that happens before the work starts — deciding what to commit to.

[Follow by RSS](https://www.deliverysheet.com/blog/rss.xml) [ The same points, as cartoons](https://www.deliverysheet.com/cartoons)

## [Turning a request into a decision](https://www.deliverysheet.com/topics/intake)

What arrives is a sentence from someone who wants something. What you need is a thing that can be decided on. [Start with turning a request into a decision →](https://www.deliverysheet.com/topics/intake)

- 10 October 2026 · 5 min read ### [How a platform team should take requests from other teams](https://www.deliverysheet.com/blog/platform-team-intake)

  An intake process for platform, data and other shared teams: split support from change requests, ask for the need, decide weekly and publish the list.
- 8 October 2026 · 7 min read ### [How to write a one-page project brief](https://www.deliverysheet.com/blog/one-page-project-brief)

  The six questions a one-page project brief answers, a weak and a strong line for each, what to leave out, and a plain-text template to copy.
- 8 October 2026 · 7 min read ### [AI project requests: what to ask first](https://www.deliverysheet.com/blog/ai-project-requests)

  How to evaluate an AI use case before committing a team: the ordinary request bar, plus four questions about the task, the data, quality and failure.
- 25 September 2026 · 9 min read ### [Declining a request by email: seven scripts to copy](https://www.deliverysheet.com/blog/declining-a-request-email-templates)

  Seven copy-paste emails for saying no: decline, park with a review date, ask what is missing, offer a smaller yes, redirect, answer sales, or tell a customer.
- 21 August 2026 · 5 min read ### [The engineering intake process, end to end](https://www.deliverysheet.com/blog/engineering-intake-process)

  The work intake process for an engineering team: one door, two questions, four recorded exits. No triage committee, no twelve-field form.
- 21 August 2026 · 5 min read ### [An intake form template with two required fields](https://www.deliverysheet.com/blog/intake-form-template)

  A copy-paste intake form template for engineering teams: two required questions, one optional date, and the four exits every request must reach.
- 21 August 2026 · 4 min read ### [Triage is deciding what happens next, not sorting by size](https://www.deliverysheet.com/blog/triaging-engineering-requests)

  Request triage fails when it produces an ordering instead of decisions. The four exits, who sits in the room, and the fifteen-minute version.
- 21 August 2026 · 4 min read ### [The side channel is rational](https://www.deliverysheet.com/blog/the-side-channel)

  Requests arrive as DMs because the door leads to silence. Policing Slack fixes nothing; making the door the fastest path to an answer does.
- 21 August 2026 · 4 min read ### [Five honest alternatives to the intake spreadsheet](https://www.deliverysheet.com/blog/spreadsheet-intake-alternatives)

  Keep the sheet, move to Airtable or Notion, run a Jira intake project, add JPD, or adopt enforced states — the case for each, stated first.
- 7 August 2026 · 4 min read ### [An intake form is a door, not a net](https://www.deliverysheet.com/blog/the-intake-form-is-a-door)

  Most intake forms are nets — they catch everything and decide nothing. What the form should actually ask, and the one property that makes it work.
- 7 August 2026 · 5 min read ### [Demand management is deciding, not collecting](https://www.deliverysheet.com/blog/what-is-demand-management)

  An intake queue records wishes. Demand management shapes them, refuses some on the record, and commits the rest against capacity.
- 7 August 2026 · 5 min read ### [Backlog bankruptcy: 400 unrecorded nos](https://www.deliverysheet.com/blog/backlog-bankruptcy)

  A 400-item backlog is 400 decisions nobody recorded. Closing it is a batch of recorded declines and parks with reasons — not a purge.
- 6 August 2026 · 5 min read ### [Separate the facts from the assumptions before you plan anything](https://www.deliverysheet.com/blog/known-facts-assumptions-unknowns)

  Requests arrive as a blend of what is known, what is assumed and what nobody has checked. Written in one voice, the assumptions get treated as facts.
- 6 August 2026 · 6 min read ### [Saying no is a decision. Record it like one.](https://www.deliverysheet.com/blog/saying-no-is-a-recorded-decision)

  Most requests that never get built were never actually declined — they were left to rot in a backlog. That costs more than a clear no.
- 6 August 2026 · 4 min read ### [What makes a request shapeable](https://www.deliverysheet.com/blog/what-makes-a-request-shapeable)

  Not every message is a demand. The floor is low but it is real: a need, plus either who it affects or what happens if nothing changes.
- 6 August 2026 · 6 min read ### [Not every request should enter the process](https://www.deliverysheet.com/blog/not-every-request-is-a-demand)

  A bar at intake is usually described as bureaucracy. One sentence wide, applied at the door, it is the cheapest quality control a delivery process has.
- 6 August 2026 · 6 min read ### ["SSO" is a topic, not a request](https://www.deliverysheet.com/blog/a-topic-is-not-a-request)

  Half of what arrives in an intake queue is a subject area wearing the grammar of a request. The test that separates them takes five seconds.
- 6 August 2026 · 6 min read ### [Waiting on information is a state, not silence](https://www.deliverysheet.com/blog/waiting-on-information-is-a-state)

  Most requests that die never got refused. They got asked a question and then quietly stopped existing. Waiting has to be a state with an owner and a date.
- 6 August 2026 · 4 min read ### [How to say no to a stakeholder](https://www.deliverysheet.com/blog/how-to-say-no-to-a-stakeholder)

  The slow maybe costs more relationship than a fast no. What a good refusal contains, and how to deliver one to someone senior without burning anything.
- 6 August 2026 · 3 min read ### [Moving delivery governance out of the spreadsheet](https://www.deliverysheet.com/blog/moving-out-of-the-spreadsheet)

  The trigger is not row count. What actually migrates when you move intake and capacity out of a sheet — and the one thing you genuinely give up.

## [Deciding what to commit to](https://www.deliverysheet.com/topics/commit)

What has to be true before a request becomes a promise, and what to do with the ones that never should. [Start with deciding what to commit to →](https://www.deliverysheet.com/topics/commit)

- 10 October 2026 · 5 min read ### [Putting a project on hold: a review date, or it is a no](https://www.deliverysheet.com/blog/putting-a-project-on-hold)

  How to put a project or request on hold honestly: a review date or an explicit indefinite hold, what to write down, and what happens on the review date.
- 10 October 2026 · 5 min read ### [Pushing back on an unrealistic deadline: three offers, not one no](https://www.deliverysheet.com/blog/pushing-back-on-an-unrealistic-deadline)

  How to push back on a deadline that will not hold: find out what kind of date it is, get a figure the team owns, and bring three offers instead of one no.
- 10 October 2026 · 4 min read ### [Fixed scope or fixed date: pick one before you commit](https://www.deliverysheet.com/blog/fixed-scope-or-fixed-date)

  A commitment can hold two of scope, date and capacity. How to choose which one flexes, how to write it into the commitment, and what to do when it moves.
- 9 October 2026 · 6 min read ### [How much process does a request need? Four paths, chosen in a minute](https://www.deliverysheet.com/blog/how-much-process-a-request-needs)

  Right-size approval by what a wrong commitment would cost: three questions, and four paths from a light confirmation to full planning to a recorded exception.
- 4 October 2026 · 6 min read ### [How to prioritise tech debt against features](https://www.deliverysheet.com/blog/prioritising-tech-debt-against-features)

  Tech debt loses planning because it arrives with no problem, outcome or cost of delay. Shape it like any demand, and know what evidence makes it win.
- 21 August 2026 · 5 min read ### [When everything is a priority, run the capacity line](https://www.deliverysheet.com/blog/when-everything-is-a-priority)

  "It's all P1" is not a prioritisation failure — it is a missing constraint. What changes when priorities have to fit under a per-team capacity line.
- 21 August 2026 · 4 min read ### [Sprint commitment vs forecast: the argument is at the wrong level](https://www.deliverysheet.com/blog/sprint-commitment-vs-forecast)

  Scrum replaced sprint commitments with forecasts for good reasons. The organisation still needs commitments — one level up, where promises are made.
- 21 August 2026 · 3 min read ### [OKRs point. Commitments deliver.](https://www.deliverysheet.com/blog/okrs-and-commitments)

  An OKR names a direction; it doesn't promise anyone anything specific. Why teams that run on OKRs alone still miss dates — and what fills the gap.
- 21 August 2026 · 5 min read ### [The date sales already promised](https://www.deliverysheet.com/blog/the-date-sales-already-promised)

  The customer has the date, engineering has the surprise. How to take a pre-promised commitment without pretending it was your decision.
- 7 August 2026 · 5 min read ### [A definition of ready for commitments, not tickets](https://www.deliverysheet.com/blog/definition-of-ready-for-commitments)

  A sprint definition of ready checks tickets. The one that matters checks promises — the bar a demand clears before people and a date are committed.
- 7 August 2026 · 5 min read ### [The mid-quarter ask is an edit, not an addition](https://www.deliverysheet.com/blog/the-mid-quarter-ask)

  Capacity did not grow when the urgent ask arrived. A mid-quarter request is an edit to a named commitment — the honest record names what it displaces.
- 7 August 2026 · 5 min read ### [You don't need a scoring framework](https://www.deliverysheet.com/blog/you-dont-need-a-scoring-framework)

  RICE and WSJF rank unshaped demands to two decimal places. A readiness bar plus a visible capacity line does the work the score pretends to do.
- 6 August 2026 · 5 min read ### [What a decision-ready demand actually contains](https://www.deliverysheet.com/blog/decision-ready-demand)

  Not a template — the six things that must be established before a request can honestly become a commitment, and how to tell when one is missing.
- 6 August 2026 · 5 min read ### [What goes in the quarter, and who decides](https://www.deliverysheet.com/blog/what-goes-in-the-quarter)

  Quarterly planning fails as arithmetic before politics: capacity treated as a total, and no record of what you are not doing.
- 6 August 2026 · 4 min read ### [An owner is a person, not a team](https://www.deliverysheet.com/blog/an-owner-is-a-person)

  A team name in the owner field means the decision has no address — and the failure shows up at exactly the moment a judgement call is needed.
- 6 August 2026 · 4 min read ### [Quarter planning without the theatre](https://www.deliverysheet.com/blog/quarter-planning-without-the-theatre)

  A working quarter plan is a set of commitments the delivering teams agreed to — not a ranked wishlist. The meeting, the agenda, and what to stop doing.
- 5 August 2026 · 6 min read ### [You will commit before you are ready. Make it cost four fields.](https://www.deliverysheet.com/blog/early-commitment-exception)

  Banning early commitments does not stop them, it hides them. Recording them takes a minute and converts an invisible gamble into a named decision.
- 4 August 2026 · 5 min read ### [Why delivery commitments slip before a single line of code](https://www.deliverysheet.com/blog/why-delivery-commitments-slip-before-code)

  Most missed delivery dates are decided weeks before the work starts — when a request becomes a commitment without anyone checking it was ready.

## [Capacity and what to measure](https://www.deliverysheet.com/topics/capacity)

Sizing work in units that survive a budget meeting, and measuring allocation instead of surveillance. [Start with capacity and what to measure →](https://www.deliverysheet.com/topics/capacity)

- 10 October 2026 · 5 min read ### [How to justify engineering headcount: show what was turned away](https://www.deliverysheet.com/blog/justifying-engineering-headcount)

  A headcount case rests on four numbers: the team's honest capacity, what it committed and delivered, what was declined for capacity, and what that cost.
- 9 October 2026 · 7 min read ### [Capacity planning when one team serves several product lines](https://www.deliverysheet.com/blog/capacity-planning-across-product-lines)

  Capacity planning for an engineering org with several product lines: plan the teams, rank across lines once per shared team. A worked example in FTE-months.
- 4 October 2026 · 6 min read ### [How much capacity to reserve for unplanned work](https://www.deliverysheet.com/blog/unplanned-work-capacity-reserve)

  Measure each team's interrupt rate over the last two quarters, hold the reserve as a named line, and decide now what happens when it runs out.
- 21 August 2026 · 5 min read ### [A capacity planning template that fits on one sheet](https://www.deliverysheet.com/blog/capacity-planning-template)

  The five columns a capacity plan actually needs, per team — and the two failures no spreadsheet template can fix, whatever you add to it.
- 21 August 2026 · 3 min read ### [Ten projects in flight is a queue pretending to be progress](https://www.deliverysheet.com/blog/too-many-projects-in-flight)

  Running everything in parallel feels like motion and delivers like a queue. What the in-flight count costs, and the sequencing that fixes it.
- 7 August 2026 · 5 min read ### [An estimate is not a commitment](https://www.deliverysheet.com/blog/an-estimate-is-not-a-commitment)

  A range with low confidence leaves the team and arrives upstairs as a date. What stops the hardening is making the promise a separate, recorded act.
- 7 August 2026 · 6 min read ### [Capacity planning for engineering teams](https://www.deliverysheet.com/blog/capacity-planning-for-engineering-teams)

  How to plan engineering capacity for a quarter in four steps: each team's real capacity in FTE-months, sizing work, and what to do with what does not fit.
- 6 August 2026 · 5 min read ### [Estimating capacity when you don't know enough yet](https://www.deliverysheet.com/blog/estimating-capacity-you-dont-have-yet)

  The honest answers to "how big is this?" are a range, a range with low confidence, and "I need to look first".
- 6 August 2026 · 4 min read ### [When a team is over-committed, say which thing slips](https://www.deliverysheet.com/blog/when-a-team-is-over-committed)

  The honest response to too much work is not more effort or a re-estimate. It is naming which commitment moves, and telling the person who was promised it.
- 6 August 2026 · 4 min read ### [Forecast what work will cost. Do not track what it did.](https://www.deliverysheet.com/blog/cost-forecasting-not-cost-tracking)

  Finance needs a number before the work starts. That is a forecasting problem, and solving it with time tracking answers a different question badly.
- 4 August 2026 · 5 min read ### [Allocation, not consumption: what an engineering manager should measure](https://www.deliverysheet.com/blog/allocation-not-consumption)

  The case for measuring what people are committed to rather than what they spend their hours on — and why consumption metrics degrade the data they read.
- 4 August 2026 · 6 min read ### [FTE-months: a capacity unit you can defend in a budget meeting](https://www.deliverysheet.com/blog/fte-months-capacity-unit)

  Story points do not survive contact with finance. FTE-months are coarse, boring, and convert directly into the two answers leadership asks for.

## [After the commitment](https://www.deliverysheet.com/topics/deliver)

Keeping a promise visible while it is being kept, closing it honestly, and learning something the next demand can use. [Start with after the commitment →](https://www.deliverysheet.com/topics/deliver)

- 10 October 2026 · 5 min read ### [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.
- 10 October 2026 · 5 min read ### [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.
- 8 October 2026 · 7 min read ### [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.
- 8 October 2026 · 7 min read ### [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.
- 4 October 2026 · 6 min read ### [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.
- 4 October 2026 · 6 min read ### [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.
- 21 August 2026 · 3 min read ### [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.
- 7 August 2026 · 2 min read ### [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.
- 7 August 2026 · 5 min read ### [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.
- 7 August 2026 · 5 min read ### [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.
- 6 August 2026 · 4 min read ### [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.
- 6 August 2026 · 4 min read ### ["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.
- 6 August 2026 · 4 min read ### [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.
- 6 August 2026 · 4 min read ### [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.

## [Planning that stays honest](https://www.deliverysheet.com/topics/planning)

Separating fact from assumption, modelling cross-cutting work, and knowing where AI belongs. [Start with planning that stays honest →](https://www.deliverysheet.com/topics/planning)

- 10 October 2026 · 4 min read ### [A risk register that gets read: mitigate it, accept it, or it blocks](https://www.deliverysheet.com/blog/risk-register-that-gets-read)

  A project risk register in five columns, the three ways a risk can leave it, and the rule that makes people read it: a serious open risk blocks the commitment.
- 10 October 2026 · 5 min read ### [How to run a pre-mortem: forty-five minutes before you commit](https://www.deliverysheet.com/blog/how-to-run-a-pre-mortem)

  A project pre-mortem in 45 minutes: imagine the failure, write reasons alone, pick the fatal ones, and turn each into a risk, a dependency or a cut.
- 4 October 2026 · 6 min read ### [Delivery roadmap: how to build one that survives the quarter](https://www.deliverysheet.com/blog/how-to-build-a-delivery-roadmap)

  How to build a delivery roadmap from commitments: the five columns, a worked example, the update rhythm, and the three ways a roadmap rots.
- 21 August 2026 · 4 min read ### [The RAID log, minus the theatre](https://www.deliverysheet.com/blog/raid-log-without-the-theatre)

  Risks, assumptions, issues, dependencies — the RAID log is the right instinct wrapped in the wrong ritual. What to keep, and what a log can't hold.
- 7 August 2026 · 5 min read ### [A discovery is a decision with a deadline](https://www.deliverysheet.com/blog/discovery-is-a-decision-with-a-deadline)

  A spike that never ends is a parking lot. What separates discovery from research is a time-box, a target date, and a conclusion someone must record.
- 6 August 2026 · 5 min read ### [AI should draft and challenge. It should not decide.](https://www.deliverysheet.com/blog/ai-should-suggest-not-decide)

  Where an LLM genuinely helps in delivery planning, where it must not be trusted, and the design rule that keeps the two apart.
- 6 August 2026 · 4 min read ### [The dependency you don't own](https://www.deliverysheet.com/blog/the-dependency-you-dont-own)

  Most delivery risk sits in work another team has to do for you — and the usual tracking treats it exactly like work you control.
- 6 August 2026 · 4 min read ### [A decision without a record is a decision you will make again](https://www.deliverysheet.com/blog/decisions-need-a-record)

  Teams re-litigate the same architectural and scoping calls every few months, because what was recorded was the outcome and never the reasoning behind it.
- 6 August 2026 · 4 min read ### [Scope is mostly what you're not doing](https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing)

  An in-scope list describes an intention. The out-of-scope list is what actually holds when someone asks for one more thing in week six.
- 5 August 2026 · 6 min read ### ["No known risks" has to be a valid answer](https://www.deliverysheet.com/blog/no-known-risks-is-an-answer)

  Planning templates that only accept filled-in fields get filled in. The result is a risk register full of fiction, which is worse than an empty one.
- 4 August 2026 · 5 min read ### [Vertical and horizontal work: the distinction planning tools miss](https://www.deliverysheet.com/blog/vertical-and-horizontal-work)

  Delivery streams and cross-cutting concerns behave differently, need different capacity models, and fail differently. Most tools call both an "epic".

```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/blog#webpage","@type":"WebPage","description":"Essays on delivery governance: shaping demands before committing, sizing capacity honestly, and closing what you promised.","name":"Writing — DeliverySheet","url":"https://www.deliverysheet.com/blog","isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/blog"]}],"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/blog#/schema/item-list/1","@type":"ItemList","itemListElement":[{"@type":"Article","headline":"Putting a project on hold: a review date, or it is a no","description":"How to put a project or request on hold honestly: a review date or an explicit indefinite hold, what to write down, and what happens on the review date.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/putting-a-project-on-hold","position":1},{"@type":"Article","headline":"A risk register that gets read: mitigate it, accept it, or it blocks","description":"A project risk register in five columns, the three ways a risk can leave it, and the rule that makes people read it: a serious open risk blocks the commitment.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/risk-register-that-gets-read","position":2},{"@type":"Article","headline":"Pushing back on an unrealistic deadline: three offers, not one no","description":"How to push back on a deadline that will not hold: find out what kind of date it is, get a figure the team owns, and bring three offers instead of one no.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/pushing-back-on-an-unrealistic-deadline","position":3},{"@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.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/say-do-ratio-delivery-predictability","position":4},{"@type":"Article","headline":"Fixed scope or fixed date: pick one before you commit","description":"A commitment can hold two of scope, date and capacity. How to choose which one flexes, how to write it into the commitment, and what to do when it moves.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/fixed-scope-or-fixed-date","position":5},{"@type":"Article","headline":"How to justify engineering headcount: show what was turned away","description":"A headcount case rests on four numbers: the team's honest capacity, what it committed and delivered, what was declined for capacity, and what that cost.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/justifying-engineering-headcount","position":6},{"@type":"Article","headline":"How a platform team should take requests from other teams","description":"An intake process for platform, data and other shared teams: split support from change requests, ask for the need, decide weekly and publish the list.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/platform-team-intake","position":7},{"@type":"Article","headline":"How to run a pre-mortem: forty-five minutes before you commit","description":"A project pre-mortem in 45 minutes: imagine the failure, write reasons alone, pick the fatal ones, and turn each into a risk, a dependency or a cut.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/how-to-run-a-pre-mortem","position":8},{"@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.","datePublished":"2026-10-10","url":"https://www.deliverysheet.com/blog/project-status-meeting-agenda","position":9},{"@type":"Article","headline":"Capacity planning when one team serves several product lines","description":"Capacity planning for an engineering org with several product lines: plan the teams, rank across lines once per shared team. A worked example in FTE-months.","datePublished":"2026-10-09","url":"https://www.deliverysheet.com/blog/capacity-planning-across-product-lines","position":10},{"@type":"Article","headline":"How much process does a request need? Four paths, chosen in a minute","description":"Right-size approval by what a wrong commitment would cost: three questions, and four paths from a light confirmation to full planning to a recorded exception.","datePublished":"2026-10-09","url":"https://www.deliverysheet.com/blog/how-much-process-a-request-needs","position":11},{"@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.","datePublished":"2026-10-08","url":"https://www.deliverysheet.com/blog/lessons-learned-template","position":12},{"@type":"Article","headline":"How to write a one-page project brief","description":"The six questions a one-page project brief answers, a weak and a strong line for each, what to leave out, and a plain-text template to copy.","datePublished":"2026-10-08","url":"https://www.deliverysheet.com/blog/one-page-project-brief","position":13},{"@type":"Article","headline":"AI project requests: what to ask first","description":"How to evaluate an AI use case before committing a team: the ordinary request bar, plus four questions about the task, the data, quality and failure.","datePublished":"2026-10-08","url":"https://www.deliverysheet.com/blog/ai-project-requests","position":14},{"@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.","datePublished":"2026-10-08","url":"https://www.deliverysheet.com/blog/telling-stakeholders-a-project-is-late","position":15},{"@type":"Article","headline":"Delivery roadmap: how to build one that survives the quarter","description":"How to build a delivery roadmap from commitments: the five columns, a worked example, the update rhythm, and the three ways a roadmap rots.","datePublished":"2026-10-04","url":"https://www.deliverysheet.com/blog/how-to-build-a-delivery-roadmap","position":16},{"@type":"Article","headline":"How to prioritise tech debt against features","description":"Tech debt loses planning because it arrives with no problem, outcome or cost of delay. Shape it like any demand, and know what evidence makes it win.","datePublished":"2026-10-04","url":"https://www.deliverysheet.com/blog/prioritising-tech-debt-against-features","position":17},{"@type":"Article","headline":"How much capacity to reserve for unplanned work","description":"Measure each team's interrupt rate over the last two quarters, hold the reserve as a named line, and decide now what happens when it runs out.","datePublished":"2026-10-04","url":"https://www.deliverysheet.com/blog/unplanned-work-capacity-reserve","position":18},{"@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.","datePublished":"2026-10-04","url":"https://www.deliverysheet.com/blog/change-request-process","position":19},{"@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.","datePublished":"2026-10-04","url":"https://www.deliverysheet.com/blog/when-to-stop-a-committed-project","position":20},{"@type":"Article","headline":"Declining a request by email: seven scripts to copy","description":"Seven copy-paste emails for saying no: decline, park with a review date, ask what is missing, offer a smaller yes, redirect, answer sales, or tell a customer.","datePublished":"2026-09-25","url":"https://www.deliverysheet.com/blog/declining-a-request-email-templates","position":21},{"@type":"Article","headline":"The engineering intake process, end to end","description":"The work intake process for an engineering team: one door, two questions, four recorded exits. No triage committee, no twelve-field form.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/engineering-intake-process","position":22},{"@type":"Article","headline":"An intake form template with two required fields","description":"A copy-paste intake form template for engineering teams: two required questions, one optional date, and the four exits every request must reach.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/intake-form-template","position":23},{"@type":"Article","headline":"A capacity planning template that fits on one sheet","description":"The five columns a capacity plan actually needs, per team — and the two failures no spreadsheet template can fix, whatever you add to it.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/capacity-planning-template","position":24},{"@type":"Article","headline":"When everything is a priority, run the capacity line","description":"\"It's all P1\" is not a prioritisation failure — it is a missing constraint. What changes when priorities have to fit under a per-team capacity line.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/when-everything-is-a-priority","position":25},{"@type":"Article","headline":"Triage is deciding what happens next, not sorting by size","description":"Request triage fails when it produces an ordering instead of decisions. The four exits, who sits in the room, and the fifteen-minute version.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/triaging-engineering-requests","position":26},{"@type":"Article","headline":"Sprint commitment vs forecast: the argument is at the wrong level","description":"Scrum replaced sprint commitments with forecasts for good reasons. The organisation still needs commitments — one level up, where promises are made.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/sprint-commitment-vs-forecast","position":27},{"@type":"Article","headline":"The RAID log, minus the theatre","description":"Risks, assumptions, issues, dependencies — the RAID log is the right instinct wrapped in the wrong ritual. What to keep, and what a log can't hold.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/raid-log-without-the-theatre","position":28},{"@type":"Article","headline":"OKRs point. Commitments deliver.","description":"An OKR names a direction; it doesn't promise anyone anything specific. Why teams that run on OKRs alone still miss dates — and what fills the gap.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/okrs-and-commitments","position":29},{"@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.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/engineering-status-report","position":30},{"@type":"Article","headline":"Ten projects in flight is a queue pretending to be progress","description":"Running everything in parallel feels like motion and delivers like a queue. What the in-flight count costs, and the sequencing that fixes it.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/too-many-projects-in-flight","position":31},{"@type":"Article","headline":"The date sales already promised","description":"The customer has the date, engineering has the surprise. How to take a pre-promised commitment without pretending it was your decision.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/the-date-sales-already-promised","position":32},{"@type":"Article","headline":"The side channel is rational","description":"Requests arrive as DMs because the door leads to silence. Policing Slack fixes nothing; making the door the fastest path to an answer does.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/the-side-channel","position":33},{"@type":"Article","headline":"Five honest alternatives to the intake spreadsheet","description":"Keep the sheet, move to Airtable or Notion, run a Jira intake project, add JPD, or adopt enforced states — the case for each, stated first.","datePublished":"2026-08-21","url":"https://www.deliverysheet.com/blog/spreadsheet-intake-alternatives","position":34},{"@type":"Article","headline":"An intake form is a door, not a net","description":"Most intake forms are nets — they catch everything and decide nothing. What the form should actually ask, and the one property that makes it work.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door","position":35},{"@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.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close","position":36},{"@type":"Article","headline":"Demand management is deciding, not collecting","description":"An intake queue records wishes. Demand management shapes them, refuses some on the record, and commits the rest against capacity.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/what-is-demand-management","position":37},{"@type":"Article","headline":"A discovery is a decision with a deadline","description":"A spike that never ends is a parking lot. What separates discovery from research is a time-box, a target date, and a conclusion someone must record.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/discovery-is-a-decision-with-a-deadline","position":38},{"@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.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/reporting-delivery-to-leadership","position":39},{"@type":"Article","headline":"A definition of ready for commitments, not tickets","description":"A sprint definition of ready checks tickets. The one that matters checks promises — the bar a demand clears before people and a date are committed.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/definition-of-ready-for-commitments","position":40},{"@type":"Article","headline":"An estimate is not a commitment","description":"A range with low confidence leaves the team and arrives upstairs as a date. What stops the hardening is making the promise a separate, recorded act.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/an-estimate-is-not-a-commitment","position":41},{"@type":"Article","headline":"The mid-quarter ask is an edit, not an addition","description":"Capacity did not grow when the urgent ask arrived. A mid-quarter request is an edit to a named commitment — the honest record names what it displaces.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/the-mid-quarter-ask","position":42},{"@type":"Article","headline":"You don't need a scoring framework","description":"RICE and WSJF rank unshaped demands to two decimal places. A readiness bar plus a visible capacity line does the work the score pretends to do.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/you-dont-need-a-scoring-framework","position":43},{"@type":"Article","headline":"Backlog bankruptcy: 400 unrecorded nos","description":"A 400-item backlog is 400 decisions nobody recorded. Closing it is a batch of recorded declines and parks with reasons — not a purge.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/backlog-bankruptcy","position":44},{"@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.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/quarter-end-count-the-exceptions","position":45},{"@type":"Article","headline":"Capacity planning for engineering teams","description":"How to plan engineering capacity for a quarter in four steps: each team's real capacity in FTE-months, sizing work, and what to do with what does not fit.","datePublished":"2026-08-07","url":"https://www.deliverysheet.com/blog/capacity-planning-for-engineering-teams","position":46},{"@type":"Article","headline":"Separate the facts from the assumptions before you plan anything","description":"Requests arrive as a blend of what is known, what is assumed and what nobody has checked. Written in one voice, the assumptions get treated as facts.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/known-facts-assumptions-unknowns","position":47},{"@type":"Article","headline":"AI should draft and challenge. It should not decide.","description":"Where an LLM genuinely helps in delivery planning, where it must not be trusted, and the design rule that keeps the two apart.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/ai-should-suggest-not-decide","position":48},{"@type":"Article","headline":"Saying no is a decision. Record it like one.","description":"Most requests that never get built were never actually declined — they were left to rot in a backlog. That costs more than a clear no.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/saying-no-is-a-recorded-decision","position":49},{"@type":"Article","headline":"Estimating capacity when you don't know enough yet","description":"The honest answers to \"how big is this?\" are a range, a range with low confidence, and \"I need to look first\".","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/estimating-capacity-you-dont-have-yet","position":50},{"@type":"Article","headline":"What a decision-ready demand actually contains","description":"Not a template — the six things that must be established before a request can honestly become a commitment, and how to tell when one is missing.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/decision-ready-demand","position":51},{"@type":"Article","headline":"The dependency you don't own","description":"Most delivery risk sits in work another team has to do for you — and the usual tracking treats it exactly like work you control.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/the-dependency-you-dont-own","position":52},{"@type":"Article","headline":"What goes in the quarter, and who decides","description":"Quarterly planning fails as arithmetic before politics: capacity treated as a total, and no record of what you are not doing.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/what-goes-in-the-quarter","position":53},{"@type":"Article","headline":"When a team is over-committed, say which thing slips","description":"The honest response to too much work is not more effort or a re-estimate. It is naming which commitment moves, and telling the person who was promised it.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/when-a-team-is-over-committed","position":54},{"@type":"Article","headline":"A decision without a record is a decision you will make again","description":"Teams re-litigate the same architectural and scoping calls every few months, because what was recorded was the outcome and never the reasoning behind it.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/decisions-need-a-record","position":55},{"@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.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/rag-status-is-a-judgement","position":56},{"@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.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/delivered-is-not-an-outcome","position":57},{"@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.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/a-retrospective-that-isnt-theatre","position":58},{"@type":"Article","headline":"What makes a request shapeable","description":"Not every message is a demand. The floor is low but it is real: a need, plus either who it affects or what happens if nothing changes.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/what-makes-a-request-shapeable","position":59},{"@type":"Article","headline":"Forecast what work will cost. Do not track what it did.","description":"Finance needs a number before the work starts. That is a forecasting problem, and solving it with time tracking answers a different question badly.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/cost-forecasting-not-cost-tracking","position":60},{"@type":"Article","headline":"Scope is mostly what you're not doing","description":"An in-scope list describes an intention. The out-of-scope list is what actually holds when someone asks for one more thing in week six.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing","position":61},{"@type":"Article","headline":"An owner is a person, not a team","description":"A team name in the owner field means the decision has no address — and the failure shows up at exactly the moment a judgement call is needed.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/an-owner-is-a-person","position":62},{"@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.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/what-complete-should-mean","position":63},{"@type":"Article","headline":"Not every request should enter the process","description":"A bar at intake is usually described as bureaucracy. One sentence wide, applied at the door, it is the cheapest quality control a delivery process has.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/not-every-request-is-a-demand","position":64},{"@type":"Article","headline":"\"SSO\" is a topic, not a request","description":"Half of what arrives in an intake queue is a subject area wearing the grammar of a request. The test that separates them takes five seconds.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/a-topic-is-not-a-request","position":65},{"@type":"Article","headline":"Waiting on information is a state, not silence","description":"Most requests that die never got refused. They got asked a question and then quietly stopped existing. Waiting has to be a state with an owner and a date.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/waiting-on-information-is-a-state","position":66},{"@type":"Article","headline":"How to say no to a stakeholder","description":"The slow maybe costs more relationship than a fast no. What a good refusal contains, and how to deliver one to someone senior without burning anything.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/how-to-say-no-to-a-stakeholder","position":67},{"@type":"Article","headline":"Quarter planning without the theatre","description":"A working quarter plan is a set of commitments the delivering teams agreed to — not a ranked wishlist. The meeting, the agenda, and what to stop doing.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/quarter-planning-without-the-theatre","position":68},{"@type":"Article","headline":"Moving delivery governance out of the spreadsheet","description":"The trigger is not row count. What actually migrates when you move intake and capacity out of a sheet — and the one thing you genuinely give up.","datePublished":"2026-08-06","url":"https://www.deliverysheet.com/blog/moving-out-of-the-spreadsheet","position":69},{"@type":"Article","headline":"\"No known risks\" has to be a valid answer","description":"Planning templates that only accept filled-in fields get filled in. The result is a risk register full of fiction, which is worse than an empty one.","datePublished":"2026-08-05","url":"https://www.deliverysheet.com/blog/no-known-risks-is-an-answer","position":70},{"@type":"Article","headline":"You will commit before you are ready. Make it cost four fields.","description":"Banning early commitments does not stop them, it hides them. Recording them takes a minute and converts an invisible gamble into a named decision.","datePublished":"2026-08-05","url":"https://www.deliverysheet.com/blog/early-commitment-exception","position":71},{"@type":"Article","headline":"Why delivery commitments slip before a single line of code","description":"Most missed delivery dates are decided weeks before the work starts — when a request becomes a commitment without anyone checking it was ready.","datePublished":"2026-08-04","url":"https://www.deliverysheet.com/blog/why-delivery-commitments-slip-before-code","position":72},{"@type":"Article","headline":"Vertical and horizontal work: the distinction planning tools miss","description":"Delivery streams and cross-cutting concerns behave differently, need different capacity models, and fail differently. Most tools call both an \"epic\".","datePublished":"2026-08-04","url":"https://www.deliverysheet.com/blog/vertical-and-horizontal-work","position":73},{"@type":"Article","headline":"Allocation, not consumption: what an engineering manager should measure","description":"The case for measuring what people are committed to rather than what they spend their hours on — and why consumption metrics degrade the data they read.","datePublished":"2026-08-04","url":"https://www.deliverysheet.com/blog/allocation-not-consumption","position":74},{"@type":"Article","headline":"FTE-months: a capacity unit you can defend in a budget meeting","description":"Story points do not survive contact with finance. FTE-months are coarse, boring, and convert directly into the two answers leadership asks for.","datePublished":"2026-08-04","url":"https://www.deliverysheet.com/blog/fte-months-capacity-unit","position":75}]},{"@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"}]}
```

## Sitemap

See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.