DRI and kickoff

Writing code is necessary and nowhere near sufficient. In a company of any size, shipping means a named person drove the work through ambiguity, dependencies, and attention gaps until decision-makers agreed it was done. Sean Goedecke's framing is useful: projects almost always ship because one person makes them ship. That person is not writing every line. They hold the end-to-end picture and refuse to let the default state — stall — win.

In a big company, code on main is not enough. Shipped usually means: the intended users can use it, decision-makers know it launched, monitoring says it is healthy, and someone is clearly on the hook when it breaks. Teams that optimize for merge rate produce a graveyard of half-flagged features.

Hold a private test every Friday: If leadership asked whether this project could go to 100% today, what would stop us? Whatever answer you give is your real backlog.

Walking through a kickoff

Do not start coding into a fog. A short kickoff (30–45 minutes, or a crisp written brief) should lock:

Write the notes where the team already looks. Link the design doc and the milestone list. Invite the skeptical stakeholder — security reviewer, dependency lead — early, while changing the plan is still cheap.

Kickoff is also a social contract. You are asking for attention and priority. If nobody important shows up and nobody reads the notes, the project is already under-sponsored. Fix sponsorship before you dig a deep technical hole.

Common mistakes

• No DRI. Status meetings without ownership. The project stalls by default.
• Coding before goals and non-goals. Fog produces the wrong system.
• Ignoring empty kickoff attendance. That is a sponsorship bug, not a calendar quirk.

Check yourself

Two tech leads "kind of" share a project. Who is the DRI?

Nobody. Pick one person who knows whether it could ship today.

Leadership asks if you can go to 100% today. You think of three blockers. What is that list?

Your real backlog — not the tidy tickets that feel productive.

Key takeaways

• One DRI holds the end-to-end picture. Without that, projects stall.
• Shipped means users, monitoring, recognition, and a named owner — not only merge.
• Kick off with goals, non-goals, owners, milestones, and a communication plan.
• Empty kickoff attendance is under-sponsorship. Fix that first.

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

Next: weekly status.