My expectations of engineering initiative owners
One of the things I love about the culture on the teams I lead is that there is a high degree of individual ownership. Most of the engineers on my teams are full stack and are expected to be the main drivers of getting initiatives that they own shipped to our customers. Sometimes this responsibility can be overwhelming and we might forget to make sure some aspect of the initiative has been executed properly. I made this checklist to help initiative owners understand what's expected of them when they lead an initiative and even what exceeding those expectations might look like.
Owning an initiative means making sure each of these questions gets answered, not doing every task yourself. Not every question applies to every initiative, and "no" is often a perfectly good answer. "We don't need an RFC because the change is small and easy to reverse" is fine; never having asked the question is not. I recommend going through the list at kickoff, at a midpoint check-in, again before launch, and once more after launch. It also works well as a self-review when performance reviews come around.
Meeting Expectations
Here is a non-exhaustive list of questions you should be asking yourself to help ensure you are meeting expectations as an initiative owner:
- Planning
- Have you read the Product Requirements Document (PRD), and do you understand the problem we're solving, why it matters now, how Product will measure success, and what is out of scope?
- If the feature is an experiment, do you understand the hypothesis and how we'll decide whether it worked?
- Do we need an RFC (Request For Comment)?
- Has an epic been created?
- Have the work items been broken down into stories and estimated?
- Have we tried to break up the work so that at least two people have a solid understanding of the problem and solution?
- Could another running experiment or a feature being developed in parallel conflict with this one or skew its results?
- Are we making sure that we're not adding too much logic to the client instead of the backend, where it can change without an app release and stays consistent across clients?
- Have we thought about how the solution will scale? For example, do we need certain indexes or rate-limiting?
- Communication
- Have we reached out to the appropriate stakeholders (e.g. Product, Marketing, Customer Support, Finance, Legal) to gather ideas, context, and feedback?
- Are stakeholders getting regular status updates?
- Are risks, scope changes, and slipping dates being raised as soon as we know about them?
- Are the epic and its stories up to date so that anyone can see where things stand?
- Execution
- Are draft PRs being created as soon as possible so that there is transparency and we can course-correct early if necessary?
- Have unit tests, integration tests, and/or end-to-end tests been added?
- Have the author and main reviewer both tested the changes locally, and has the author described in the PR how they were tested?
- Does the feature require manual testing and if so, are those manual test cases ready to be executed?
- Have the necessary pieces been put in place so that we can test in staging and/or production?
- Monitoring
- Have we added enough logging so that we can understand what's happening?
- Are we capturing system metrics that we can analyze and use with alerting?
- Have alerts been set up so that we can know when the system is not behaving in a way we expect?
- Does whoever gets alerted know what to do when an alert fires, for example by following a runbook?
- Do we need a dashboard to centralize system metrics and information?
- Have we added the necessary eventing so that we can monitor performance from a product perspective?
- Rollout
- Is there a rollout plan, including whether the feature should be behind an experiment or feature flag, released to internal users first, or ramped up by percentage?
- Is there a plan for rolling back if something goes wrong?
- Are migrations and backfills safe to run, and are the changes backwards compatible?
- Will older versions of our clients, such as mobile apps, continue to work?
- Have Customer Support and Marketing been told what's launching and when?
- Presentation
- Have you demoed the initiative?
- Did you clearly explain the "why" before getting into the "how"?
- Are you able to efficiently transfer knowledge about the system to other team members through discussion and documentation?
- Post-launch
- Has the feature been verified in production?
- Have we checked the results against the success metrics?
- Have feature flags, losing experiment variants, and dead code been cleaned up?
Exceeding Expectations
Here is a non-exhaustive list of questions that may be asked to determine if you've exceeded expectations while leading an initiative:
- Have you surfaced any opportunities to improve the product through your technical insight into the system?
- Is the solution architected better than one would expect, so that it runs in less time, uses fewer resources, scales more easily, or costs less than a typical implementation would?
- Did you find a way to deliver value earlier, such as a smaller first version or a phased launch?
- Did you spot risks early and deal with them before they became problems?
- Did you recommend cutting scope, changing direction, or stopping when the data or the cost called for it?
- Were you able to meet all expectations with less guidance than one would expect?
- Have you built or found dashboards for your initiative's product metrics and made checking them a regular habit?
- Did you help a teammate grow by mentoring them through part of the work?
- Did you leave shared tooling or processes better than you found them?
- Can others learn or borrow from the system you've helped construct?
- Are there important lessons you've learned through the process that you've shared with the rest of the team?
- Were you able to accomplish a personal growth goal through working on the initiative?
The goal of this checklist isn't to turn ownership into paperwork. It's to make sure nothing important gets missed, so that you can spend your energy on the parts of the initiative that are actually hard.