My process listed every step and made my team put off starting any of them

Early in my product leadership, I drafted a 20-page process document that outlined all the steps of the product launch process from the idea’s inception to successful use by a real customer. This document pulled together the steps and activities we already did, albeit unevenly and sometimes late. The leadership was excited to see the process in concrete form and optimistic about smoother launches. The team was glad to see the list they could count on and be accountable for.

When it came time to use the process to start a new release project, the product managers slowed down as they considered the length of the document and the weight of the process when they could see all the steps on paper.

The immediate cost

Several release projects all slowed at the same time.

Some of the steps were new to some people, but every step was familiar to someone on the team.

The novelty was seeing them all together with full description on paper. Before we had the process document, people who had done the work before carried the steps in their memory. People who hadn’t done it before didn’t know some steps existed.

One product manager put off a release project for a month over the copyright step, expecting long forms on a government website. All it took was an email to our longest-tenured admin, who’d been doing it for years.

Cutting steps would have been faster

I felt internal and external pressure to lighten the load by cutting steps. Cutting steps or having “lite” versions for some types of releases would have sped things up. These versions would skip steps before the project started.

A lite version could skip a step that was critical to the release, like bringing a technical writer up to speed or a patent check for a new feature.

I wanted the product managers to develop judgment on the product process.

Keeping the steps improved the team’s judgment

I created a companion document that showed past releases of various kinds and which steps applied. There were patch release examples with 8 steps next to a new product launch with 40 steps.

As I worked through the process with a product manager for their release, we invited people who had done the work into the conversation. Some process steps turned out to be a heads-up email to a colleague or a quick check-in with a department head.

Once the product managers started using the process, they realized that some steps were small and easy, while a few were complex and time-consuming.

My product managers grew in experience and confidence applying the process. With every step of the process in front of them, they learned which ones a release could skip, and they could say why.

Resources, Not More Work