Owning projects
Driving projects to launch
Kickoffs, status, dependencies, unblocking, launch checklists, and a finish decision-makers recognize as shipped.
Writing code is necessary and nowhere near sufficient. Shipping means a named person drove the work through ambiguity, dependencies, and attention gaps until decision-makers agreed it was done — launched, celebrated, and owned in production. If estimation is the forecast, execution is the weekly practice of turning that forecast into a launch. SDE2s are trusted to own this for a feature. SDE3s own it for messier, cross-team problems.
You do not need a title to run the ritual: kickoff notes, weekly status, dependency tickets, launch checklist, retro, and the "we shipped" note with a metric. In reviews, "I shipped X on date with Y metric" beats "I contributed to many threads." For behavioral interviews, keep two or three project stories with stakes, blockers, and the actions you took to unblock — especially escalations and scope cuts, not only coding heroics.
When the honest status is red, surface a decision: cut to a thinner MVP, move the date, pause, or add help. Present burn versus remaining work, dependency ETA, and user impact of delay. Heroic silence converts a recoverable miss into a trust crisis.
| Option | When it fits |
|---|---|
| Cut to a thinner MVP | The core hypothesis can still be tested |
| Move the date | Scope is fixed by compliance or contract |
| Pause or cancel | Opportunity cost exceeds remaining value |
| Add help | Early enough that onboarding cost pays off |
You do not need to invent a fourth option on nights and weekends. Leadership can choose among those four. They cannot choose if you only say "it's hard."
Concepts in this section
Read them in order.
| Step | Concept | What it answers |
|---|---|---|
| 1 | DRI and kickoff | Who owns the outcome, and what does "shipped" mean? |
| 2 | Green, yellow, red status | How do you forecast launch without surprising people? |
| 3 | Dependencies and unblocking | What do you do when another team holds the date? |
| 4 | Launch readiness | What must be true before the flag goes to 100%? |
Decision-makers cannot read your diff. They can read a demo of the milestone, a metric moving, a launch note that says what changed for users, and a short doc that names who owns it now. Budget time for that. An un-celebrated launch is not a ship in a large company — the organization never registered that the risk retired and you can be trusted with the next one.
Common mistakes
- No DRI — status meetings without ownership.
- Green status as a social habit.
- Waiting politely forever on dependencies.
- Launching without alerts or a rollback.
- Doing the work but never making the outcome legible to decision-makers.
Key takeaways
- One DRI holds the end-to-end picture. Without that, projects stall by default.
- Status is green/yellow/red about the outcome, with asks and dates.
- Manage dependencies with tickets, cadence, and kind escalation plus options.
- Launch means monitoring, rollback, docs, a recognized finish, and a steady-state owner.
Further learning
How to ship projects at big tech companies (Sean Goedecke)What I think about when I'm lead engineer on a projectseangoedecke.com The Software Engineer's Guidebook (Gergely Orosz)Navigating senior, tech lead, staff and principal positions at tech companies and startups.The Software Engineer
Pragmatic Engineer conversation with Sean Goedecke on what "shipped" means:
Related
Estimation and planning
Breaking work into small tasks, estimating with ranges, de-risking early, and communicating slips before they become surprises.
Launching products and features
Launch tiers, betas, checklists and measuring whether a launch worked.
Written and verbal communication
Lead with the point, write for skimmers, and adjust depth for engineers, PMs and executives.