Part 2: Build Your Career

“It was so glaringly, wonderfully obvious. Make a product for people who already saw the need and felt the pain daily.

It’s just like how many marketing, sales, and creative teams often don’t talk to engineering. Too many numbers. Too black and white. Too many geeks in one room geeking out.

But I wanted to understand the squishy stuff and the geeky stuff. And I liked all of it. I could also translate back and forth—explain the squish to engineers, translate the 1s and 0s to the creatives. I could synthesize all the pieces and keep the whole company in my head.

Makers often focus on the shiny object—the product they’re building—and forget about the rest of the journey until they’re almost ready to deliver it to the customer. But customers see it all, experience it all. They’re the ones taking the journey, step-by-step. And they can easily stumble and fall when a step is missing or misaligned.

Your product’s story is its design, its features, images and videos, quotes from customers, tips from reviewers, conversations with support agents. It’s the sum of what people see and feel about this thing that you’ve created.

And the story doesn’t just exist to sell your product. It’s there to help you define it, understand it, and understand your customers. It’s what you say to investors to convince them to give you money, and to new employees to convince them to join your team, and to partners to convince them to work with you, and to the press to convince them to care. And then, eventually, it’s what you tell customers to convince them to want what you’re selling.

And it all starts with “why.”

Why does this thing need to exist? Why does it matter? Why will people need it? Why will they love it?

Building a product is like making a song.

The band is composed of marketing, sales, engineering, support, manufacturing, PR, legal. And the product manager is the producer—making sure everyone knows the melody, that nobody is out of tune and everyone is doing their part. They’re the only person who can see and hear how all the pieces are coming together, so they can tell when there’s too much bassoon or when a drum solo’s going on too long, when features get out of whack or people get so caught up in their own project that they forget the big picture.

But they’re also not directing everything. Their job isn’t to be CEO of the product—or, God forbid, what some companies call the “product owner.” They can’t single-handedly dictate what will and will not make it in. Sometimes they’ll have the final opinion, sometimes they’ll have to say “no,” sometimes they’ll have to direct from the front. But that should be rare. Mostly they empower the team. They help everyone understand the context of what the customer needs, then work together to make the right choices. If a product manager is making all the decisions, then they are not a good product manager.