Why you should write more than one product press release.

Explore

Try It

Below is an example of how to run this process efficiently with your team. You start by writing two or three different versions of the press release. In the

React to Press Releases Variations⁠

try to tease apart tradeoffs you foresee, and articulate them as customer problems you may solve as part of the press release.

The next steps is to invite your team. You can gather reactions and ask the team to articulate their own reflections and opinions in the

Deeper Reflections & Rationale⁠

table. I find it helpful to ask each team member for their conviction level on their feedback. This simple column makes it clear how strongly to read and dig into their feedback.

How to Use

⁠

Copy this doc

⁠

and remove the descriptions to use the template below.

The

Press Release Template⁠

page will get automatically populated when you add new rows / options to the

React to Press Releases Variations⁠

table below.

React to Press Releases Variations

React to Press Releases Variations

Option

Press Release

Love

Unsure

No Thanks

Option #1

Title

[ Write the headline or title to the post ]

Problem

[ Describe the problem in 1-2 plain language sentences ]

Solution

[ Describe the solution in 1-2 plain language sentences ]

Customer Quote

[ Write an ideal customer quote ]

Option #2

Title

[ Write the headline or title to the post ]

Problem

[ Describe the problem in 1-2 plain language sentences ]

Solution

[ Describe the solution in 1-2 plain language sentences ]

Customer Quote

[ Write an ideal customer quote ]

Option #3

Title

[ Write the headline or title to the post ]

Problem

[ Describe the problem in 1-2 plain language sentences ]

Solution

[ Describe the solution in 1-2 plain language sentences ]

Customer Quote

[ Write an ideal customer quote ]

There are no rows in this table

⁠

Deeper Reflections & Rationale

Deeper Reflections & Rationale

Feedback

Conviction Level

Person

I really like the direction in

@Option #1

⁠

, particularly the focus on the problem of user onboarding.

⁠

@Option #2

⁠

makes me think we’re solving the user’s problems in the wrong sequence since I think they care about onboarding themselves before onboarding their team.

@Option #3

⁠

is interesting, but I don’t think it’s worth solving now.

I wonder if there is a way to combine the focus on onboarding from

@Option #1

⁠

with the sequencing implied in

@Option #2

⁠

Medium

Lane Shackleton

There are no rows in this table

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.