Resources > Articles

Why Product Launch Checklists Don’t Work

product checklist

A common request I hear is for a product launch checklist. When I ask how the checklist will be used, I either get the “That was a stupid question” look or the response is “I don’t want to forget something important”. Checklists work great for chores. Make your bed. Brush your teeth. Take the garbage out. Not so much for product launches.

checklist
Photo By Glenn Carstens-Peters on Unsplash

The reason is that a product launch checklist – a todo list if you prefer – makes sense in the context of a specific product launch strategy. Generic product launch checklists that are downloaded from the web are built with a set of assumptions in mind that may have little in common with your next launch or are so broad you don’t know what you should focus on. Let me illustrate my point.

When you launch the first version of your software product your goal is to get buyers to become customers. Through heroic measures you manage to launch and get it out the door. The product is good but operationally things could be a whole lot better. Important deliverables are forgotten. Communication to the field is spotty. Finance has difficulty booking early sales. Shouting and finger pointing ensues.

To address the problem you assemble a product launch checklist. You visit each operational department and get their perspective on what is needed for a product launch. The checklist contains all the deliverables and activities you want to remember for the next launch. Then comes the next version of the product. It’s improved and expected to grow revenue to new heights. You pull out the trusty product launch checklist and follow it with confidence.

The launch event occurs and selling starts. Then something unexpected happens. New buyers are converting to customers but you discover that existing customers are not upgrading to the new version. Why? You followed the checklist. Your team is happy with the deliverables. There is significant value in the new version for existing customers.

The problem is that the product launch checklist was created within the context of a strategy of launching a new product to a new market segment. It doesn’t take into consideration that existing customers are a different buying target with different wants and needs. In this situation there are two distinct targets to influence: those who are buying and those who are upgrading. They have different buying criteria and require a different approach.

Start by determining the goals of the launch, taking each target within the market segment into consideration. Choose the best launch strategy to maximize the goals for each target. Then build your product launch checklist to focus on the deliverables and activities needed to achieve the launch goals.

Other Resources in this Series

Most Recent

The image features the term use scenario being revealed underneath a ripped piece of paper
Article

What is a Use Scenario [ +7 Examples]

The purpose of drafting use scenarios is to help your development and design teams to start thinking about solutions. Context is the foundation of innovation, and you’ll be providing a tool that will be the starting point for collaborative and productive meetings.
Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.
Article

Use Scenarios are Stories That Provide Context

The problem with today’s user stories is that they aren’t interesting. And they aren’t stories. The solution is use scenarios. It’s a narrative. It explains the problem in the form of a real-life story.
Article

Benefits of Bundle Pricing

Bundle pricing is simply a strategy where services or products are packaged together for one (often reduced) price rather than priced separately. This article covers some benefits of bundle pricing followed by a system for getting started.
Article

A Quick Guide to Value-Based Pricing

Value-based pricing begins with knowing the customer’s willingness to pay based on the perceived value of your product. You can charge less than a customer’s willingness to pay, and they feel like they’ve received an

OTHER ArticleS

The image features the term use scenario being revealed underneath a ripped piece of paper
Article

What is a Use Scenario [ +7 Examples]

The purpose of drafting use scenarios is to help your development and design teams to start thinking about solutions. Context is the foundation of innovation, and you’ll be providing a tool that will be the starting point for collaborative and productive meetings.
Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Subscribe

Subscribe

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

First Name*
Last Name*
Email Address*
Phone
Company
Job Title
Location
How can we help you?
Preferred method of contact
Privacy Policy*
Map Your Message to Its Audience with the Communication Compass
Map Your Message to Its Audience with the Communication Compass
Ensure your message hits the mark. This eBook helps you visually map communication styles so you can tailor your design story to a stakeholder or business partner.

Download Ebook

Demystifying Data Projects: A Guide for Business Leaders
While data science is a competitive advantage, data isn’t magic. Learn how to make magic happen by partnering more effectively with data professionals. This eBook delves into types of data projects, sample questions, tools and methods, key points and cautions—so stakeholders like you can initiate data projects with real business impact.

Download Ebook

Define Ebook Thumbnail
What’s the difference between a successful data analysis project and one that falls flat? 

Before you begin working with the data, you need to understand what you’re solving for. Gathering context and aligning around goals with your stakeholders from the outset will help you avoid disconnects and deliver actionable insights. Discover the most vital questions to ask before embarking on a data analysis project in our in-depth guide, “Define: Laying the Foundation for Successful Data Analysis.”

Download Ebook

Download Now