--- title: "An EM's first 90 days: one honest close · DeliverySheet" description: "New engineering managers instrument velocity first. The record that actually builds trust is one commitment, closed honestly against what was promised." canonical_url: "https://www.deliverysheet.com/blog/first-90-days-one-honest-close" last_updated: 2026-08-07 meta: author: "Tan Gravam" "og:description": "New engineering managers instrument velocity first. The record that actually builds trust is one commitment, closed honestly against what was promised." "og:image": "https://www.deliverysheet.com/_og/s/o_2e046f8443ec1d05.png" "og:image:alt": "Your first 90 days: aim for one honest close — DeliverySheet essay card" "og:image:height": "600" "og:image:type": image/png "og:image:width": "1200" "og:title": "Your first 90 days: aim for one honest close — DeliverySheet" "twitter:description": "New engineering managers instrument velocity first. The record that actually builds trust is one commitment, closed honestly against what was promised." "twitter:image": "https://www.deliverysheet.com/_og/s/o_2e046f8443ec1d05.png" "twitter:image:alt": "Your first 90 days: aim for one honest close — DeliverySheet essay card" "twitter:title": "Your first 90 days: aim for one honest close — DeliverySheet" --- > Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt) [← All writing](https://www.deliverysheet.com/blog) # **Your first 90 days: aim for one honest close** 7 August 2026 · 2 min read · by [Tan Gravam](https://www.deliverysheet.com/about) ## **What should a new engineering manager focus on in the first 90 days?** **The short answer ** In your first 90 days as an engineering manager, aim to produce one artifact: a commitment made with evidence and closed honestly against what was promised. First thirty days, watch the door — where requests actually arrive, and what is promised without anyone checking readiness. Second thirty, shape and refuse in the open: state what a request still needs before it can be promised, and record the nos. Final thirty, close something — delivered, delivered with exclusions, or not delivered, with the difference written down. One honest close teaches leadership more about your judgement than a quarter of green dashboards, because it is checkable and the dashboards are not. The standard advice for a new engineering manager's first quarter is to instrument things: velocity, cycle time, DORA metrics, a dashboard for the leadership review. All of it measures work in flight. None of it measures the thing your judgement will actually be evaluated on — whether what you promise happens, and whether anyone can check. So aim your first ninety days at producing one artifact instead: a commitment made with evidence, and closed honestly against what was promised. Everything else in this essay is just the staging for that. ## Days 1–30: watch the door Don't change anything yet. Find where requests actually arrive — the form everyone bypasses, the Slack channel, the sentence at the end of the leadership call — and watch what happens to them. Count two things: how many requests were *promised* before anyone established an owner, a size and the open questions; and how many were never answered at all. Those two numbers are your baseline, and they are almost certainly worse than anyone in the room believes. ## Days 31–60: shape and refuse in the open Now start holding a bar, visibly. When a request arrives thin, say what it still needs before it can be promised — not as obstruction, as a [named list](https://www.deliverysheet.com/blog/decision-ready-demand): the problem apart from the proposed solution, an owner, a first capacity figure, the dependencies, the unknowns written down. And when the answer is no or not-now, [record it](https://www.deliverysheet.com/blog/saying-no-is-a-recorded-decision) with the reason. You are not building process for its own sake; you are building the evidence trail your one [honest close](https://www.deliverysheet.com/glossary/honest-close) will sit on. ## Days 61–90: close something Pick a commitment that will finish inside the window and close it explicitly: [delivered, delivered with exclusions, or not delivered](https://www.deliverysheet.com/blog/delivered-is-not-an-outcome) — with what differed from the promise written next to the promise itself, and one lesson worth keeping. If the quarter went badly, close it badly *on the record*. A visible "not delivered, here is what we learned" is a stronger opening position than a dashboard that stayed green while the date slipped. ## Why one close beats a quarter of dashboards Because it is checkable. Leadership cannot verify a velocity chart and mostly knows it; what they can verify is whether the thing you said in planning matches the thing you said at the close. The first time those two statements line up — including the differences, stated by you before anyone asked — you have something no dashboard produces: a reason to be believed the next time you commit. That compounds. Ninety days is enough to start it, and only if the close is honest. 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) Not ready for that? Play [eight rounds of Request or topic?](https://www.deliverysheet.com/spot-the-request) It takes two minutes and needs no sign-up. ## **More on after the commitment** [Read the overview: After the commitment: tracking, closing and learning →](https://www.deliverysheet.com/topics/deliver) - [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. - [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. - [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. ```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/first-90-days-one-honest-close#webpage","dateModified":"2026-08-07","datePublished":"2026-08-07","description":"New engineering managers instrument velocity first. The record that actually builds trust is one commitment, closed honestly against what was promised.","name":"An EM's first 90 days: one honest close","url":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close","@type":["WebPage","FAQPage"],"breadcrumb":{"@id":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"mainEntity":[{"@id":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close#/schema/question/1"}],"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/blog/first-90-days-one-honest-close"]}],"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/first-90-days-one-honest-close#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":"Your first 90 days: aim for one honest close","item":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close","position":3}]},{"@id":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close#article","@type":"Article","dateModified":"2026-08-07","datePublished":"2026-08-07","description":"New engineering managers instrument velocity first. The record that actually builds trust is one commitment, closed honestly against what was promised.","headline":"Your first 90 days: aim for one honest close","inLanguage":"en","thumbnailUrl":"https://www.deliverysheet.com/_og/s/o_2e046f8443ec1d05.png","author":{"@id":"https://www.deliverysheet.com/about#person"},"image":{"@id":"https://www.deliverysheet.com/#/schema/image/1"},"isPartOf":{"@id":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close#webpage"},"keywords":["engineering management","onboarding","delivery"],"mainEntityOfPage":{"@id":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close#webpage"},"publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/first-90-days-one-honest-close#/schema/question/1","@type":"Question","inLanguage":"en","name":"What should a new engineering manager focus on in the first 90 days?","acceptedAnswer":{"@type":"Answer","text":"In your first 90 days as an engineering manager, aim to produce one artifact: a commitment made with evidence and closed honestly against what was promised. First thirty days, watch the door — where requests actually arrive, and what is promised without anyone checking readiness. Second thirty, shape and refuse in the open: state what a request still needs before it can be promised, and record the nos. Final thirty, close something — delivered, delivered with exclusions, or not delivered, with the difference written down. One honest close teaches leadership more about your judgement than a quarter of green dashboards, because it is checkable and the dashboards are not."}},{"@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_2e046f8443ec1d05.png","inLanguage":"en","url":"https://www.deliverysheet.com/_og/s/o_2e046f8443ec1d05.png"}]} ``` ## Sitemap See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.