Skip to main content

What Makes You The Number 1 Product Manager?

Image
By
Listen:

Amazon often does this thing where they start with the customer instead of just coming up with a product and then trying to figure out how to sell it. They call it "working backwards." This strategy totally works for any product decisions, but it's especially important when they're making something new.

The Press Release Exercise

When it comes to launching new stuff, product managers usually start by writing a press release for customers. This press release is all about their pain points, how current solutions fall short, and how the new product is going to crush it. If the benefits don't get customers excited, the product manager needs to keep tweaking the press release until it sounds super awesome. It's way easier and cheaper to make changes to a press release than it is to change the product itself.

Here’s a template I use to describe a new service or product:

  • Main header: The product name anyone directly understands, like “Ultra-compact power charger”
  • Subheading: One subtitle, not more than 150 chars, like “Never run out of power for your mobiles”
  • Short overview: A summary, direct and logical. The customer will never read it all, so keep it short.
  • Problem: What does the product solve? Add data, market studies, etc, Like: “over 60% of mobile device users run out of power daily and can’t recharge in time”
  • Solution: How does your product solve that particular problem? Write that in two short, nice written sentences.
  • Quote from a sparring partner: Getting a quote from a peer might be a sign that there is a market (for the powerbank in the example I doubt, since the market is flooded)
  • Starting point: An easy explanation of how to get this thing rolling.
  • Hypothetical customer review: Provide a hypothetical review describing the experienced benefit.
  • CTA: Where to get it, or where to find more information.

How To Write Your Press Release

First, it's an internal press release, but you can also send it to design partners and customers participating in your product discovery program (if you have one) to get feedback. 

So, you're writing a press release now. Make it short and simple. Keep your paragraphs to 3-4 sentences, and don't go into too much detail. Think like your customer. Figure out what they need, want, and dream about. Make your product or service fit those needs and come up with a convincing argument for why they should choose you. Show them how your deal meets their needs and makes their lives better. If you're struggling to describe the value and why the customer should buy it, it might be a sign that your idea is going to fail hard.

Besides writing, I have a thing for crafting press releases in a special style I call "Family talk." The idea is this: At the family's dinner you got asked what you’re doing, and you explain the product to your kids and parents. Listen to what they tell you from what they understand, that's the essence of "Family talk”. It cuts out the technical and product related jargon we all use.

I often ask PM's to write me a tweet (Xeed?) about the product. If they are worked the way backwards, with the distilled message, that should be easy.  

What’s the sense behind this exercise?

When a project gets going, the press release is the red line. It's there to keep the product team on track. They can always refer to it and ask themselves, "Are we making what we said we would in the press release?" If they find themselves spending time and money on features not mentioned in the press release (a.k.a. overbuilding), they need to take a step back and figure out why.

This way, we make sure that the product we're building is focused on giving customers what they want. We don't want to create a bunch of extra stuff that no one needs, which just adds to the development time and costs more money to maintain. And let's be real, those extra features probably won't add much value for the customers anyway (at least not enough to mention in the press release).

TL;DR

The product teams at Amazon use a strategy called "working backwards”. Instead of starting with a product and trying to sell it to customers, they start with what the customers need.

Using that strategy you know you're building something people actually want. Think of it like writing a press release for your customers, describing the benefits and how it solves their problems in an unique way. If you can't write a clear message explaining in a short way why it's valuable, then the product idea is going to fail.
Labels:

Comments

Post a Comment

Popular posts from this blog

Deal with corrupted messages in Apache Kafka

By
Under some strange circumstances, it can happen that a message in a Kafka topic is corrupted. This often happens when using 3rd party frameworks with Kafka. In addition, Kafka < 0.9 does not have a lock on Log.read() at the consumer read level, but does have a lock on Log.write(). This can lead to a rare race condition as described in KAKFA-2477 [1]. A likely log entry looks like this: ERROR Error processing message, stopping consumer: (kafka.tools.ConsoleConsumer$) kafka.message.InvalidMessageException: Message is corrupt (stored crc = xxxxxxxxxx, computed crc = yyyyyyyyyy Kafka-Tools Kafka stores the offset of each consumer in Zookeeper. To read the offsets, Kafka provides handy tools [2]. But you can also use zkCli.sh, at least to display the consumer and the stored offsets. First we need to find the consumer for a topic (> Kafka 0.9): bin/kafka-consumer-groups.sh --zookeeper management01:2181 --describe --group test Prior to Kafka 0.9, the only way to get this in...
Post a Comment
Read more

Beyond Ctrl+F - Use LLM's For PDF Analysis

By
PDFs are everywhere, seemingly indestructible, and present in our daily lives at all thinkable and unthinkable positions. We've all got mountains of them, and even companies shouting about "digital transformation" haven't managed to escape their clutches. Now, I'm a product guy, not a document management guru. But I started thinking: if PDFs are omnipresent in our existence, why not throw some cutting-edge AI at the problem? Maybe Large Language Models (LLMs) and Retrieval Augmented Generation (RAG) could be the answer. Don't get me wrong, PDF search indexes like Solr exist, but they're basically glorified Ctrl+F. They point you to the right file, but don't actually help you understand what's in it. And sure, Microsoft Fabric's got some fancy PDF Q&A stuff, but it's a complex beast with a hefty price tag. That's why I decided to experiment with LLMs and RAG. My idea? An intelligent knowledge base built on top of our existing P...
Post a Comment
Read more

Run Llama3 (or any LLM / SLM) on Your MacBook in 2024

By
I'm gonna be real with you: the Cloud and SaaS / PaaS is great... until it isn't. When you're elbow-deep in doing something with the likes of ChatGPT or Gemini or whatever, the last thing you need is your AI assistant starts choking (It seems that upper network connection was reset) because 5G or the local WiFi crapped out or some server halfway across the world is having a meltdown(s). That's why I'm all about running large language models (LLMs) like Llama3 locally. Yep, right on your trusty MacBook. Sure, the cloud's got its perks, but here's why local is the way to go, especially for me: Privacy:  When you're brainstorming the next big thing, you don't want your ideas floating around on some random server. Keeping your data local means it's  yours , and that's a level of control I can get behind. Offline = Uninterrupted Flow:  Whether you're on a plane, at a coffee shop with spotty wifi, or jus...
Post a Comment
Read more