Product teams know a lot about their products. It is a requirement for doing the job well. It can also be a curse. Why, you ask? Because you cannot know what you do not know. (Yes, a bit of a riddle.) This is one of the best things about a SWOT analysis — it forces your product team to step back and consider your product and the market from a different perspective. Read more…
It starts off with the best intentions. You are planning an upcoming release and notice that the support documentation needs to be updated. You could turn to a teammate and ask them to jump in. But instead you think, “I’ll just do it this once — it will be quicker this way.” Before you know it, you are spending lots of time in an area where your colleagues are experts. You have become the fix-it product manager.
Do you like to focus on the big picture — or get down in the details? It is true that our brains tend to favor one side or the other. But if you are a product manager your answer to this question should be “both.” Growing a successful product requires both top-down and bottom-up planning.
There are certain phrases that make a product manager cringe. For me, it is when customers refer to the process of submitting feedback as throwing ideas into a “black hole.” Ouch. I never want a customer to feel this way. This is one reason why our team at Aha! created a new goal this year: zero unreviewed customer ideas. Seriously.
I have some bad news. And it will not be surprising for most product managers. Our job frequently involves telling people things they do not want to hear. In fact, I would say the job of a product manager involves more difficult conversations than most. Even communicating what some would consider very bad news.
It was my first week as a new product manager. There were already a ton of feature requests coming in from different teams. Most were partially defined and very few were prioritized. I was drowning in requests. There was also a pile of customer ideas that needed review, release timelines to plan, the list went on. Where to start?
I spent an hour driving three miles. Welcome to Los Angeles — that was my commute. I was working as a product manager at an e-commerce company on the west side. Some call the area “Silicon Beach.” Most days it felt more like “Silicon Gridlock.” But there was something that eased the frustration.
“What are you planning to deliver in the second half of the year?” We were wrapping up a meeting with our customer advisory group when someone asked me this question. As a product manager, I should have known how to answer. Unfortunately, I caused more confusion than good. Here is what happened.
I learned a hard lesson early in my career — one that I never forgot. I was working on product strategy for a media company. Third-party studies showed that prospective customers were interested in a new content format. So we decided to revamp the site. When the mockups were ready, we interviewed our existing customers to get their take on the new look. And boy, am I glad we did.
“What kind of product manager will you be this year?” This was THE QUESTION that smacked me early on in my career. I had just come back from a holiday break and was catching up with my boss. I wanted to give a strong reply, but I needed time to unpack the question.
Great product managers ask questions — lots of them. But product managers need to answer questions too. And the more complex the work, the more questions abound. When I was working at another SaaS company in the HR space a few years ago, this became very clear.