One of the ongoing challenges that we face as Product Managers is that we’re primarily charged with predicting customer and user behavior. We’re constantly asked to come up with new ideas, new features, and new designs that we “know” will delight our users, or at the very least satisfy them. But the fact is, predicting human behavior is incredibly difficult — there are many thousands of people who have spent hundreds of years trying to figure out why people do what they do (they’re called psychologists, sociologists, and anthropologists), and we’re still making educated guesses at best. So, what are some of the challenges that we face?
A couple years ago, shortly after I launched the blog, I posted my first New Year’s Resolutions for Product Managers, which was a big hit. Somehow it slipped my mind to update it for 2016, but here I am with an update as we roll into the new year…one as full of uncertainties as it is full of opportunities! Without further ado, here are five new resolutions for Product Managers moving into 2017…
I’ve touched on User Stories on several occasions, my favorite being Why Your User Stories Suck! Today I’m here to share with you a very common, yet very commonly overlooked, way to check each and every User Story on your backlog to see whether or not it’s really “ready” for your Dev teams. One of the most frequent causes of delays and slowdowns in most Agile implementations that I’ve seen comes from a lack of balance in the User Stories that the team is being given to deliver — stories that are too big, or which are dictates, or which just exist on the backlog because “someone asked for it”. What we need to do as Product Managers is to occasionally take a close look at each of our backlog items and make sure that they meet the INVEST criteria — Independent, Negotiable, Valuable, Estimable, Small, and Testable. If we do this simple gut-check on a regular basis, we’re far more likely to see our teams succeed and to reduce the amount of time wasted in long, drawn-out planning sessions.
At some point in every interview that you have, the people on the other side of the table will inevitably pose the ultimate question to you: “So, do you have any questions for us?” There are hundreds of guides out there that list out the kinds of questions that you should ask in general, but due to the nature and uncertainty that comes with Product Management positions, I think there are several very specific questions that a savvy candidate should pose to their potential employer. Far too often, we fail to take full advantage of this opportunity, and though it’s certain that there will be some amount of spin put into the answers that you receive, no Product Manager should leave an interview without asking these five questions:
I’m often asked what I think makes a successful Product Manager, and after giving it some thought, I’ve narrowed it down to one key factor: Clarity. When applied to our daily jobs, this can mean any number of things: clarity of communication, clarity of purpose, driving discussions to clarity, or even insisting on clarity from others. But to me, clarity is perhaps the number one indicator of whether or not something that you’re doing is going to be successful. After all, if it’s not clear why, how, or for whom you’re doing something, can you actually measure your success or failure? Some companies thrive on a culture that lacks clarity — perhaps because a lack of clarity often goes hand-in-hand with a lack of responsibility and accountability.
Let’s look at some ways that clarity drives us to be successful in everything that we do…
One of the most fundamental requirements to be a great Product Manager is getting outside the four walls of your office and engaging with your market, your prospects, and your customers directly. Unfortunately, in all too many companies, this is more difficult than it should be, if not utterly impossible. This is usually blamed on too many in-person meetings, too little budget, or just all-around too little time to step outside and engage directly with the people using your product. But it’s a simple fact that the only way that you’re going to uncover the best ideas, the hidden problems that will separate you from your competition, and establish the rapport that you need to validate the solutions that your teams come up with as quickly and cheaply as possible. Here are some ideas for you to consider when you’re trying to figure out how to get outside and engage with your market!
Asking for Forgiveness is Better than Permission
Remember, it’s your job to keep your finger on the pulse of your market. It’s your job to dig deep and uncover unspoken needs that you can use as fuel for innovation. It’s your job to seek out people who can give you valuable feedback, who can tell you all of their problems and issues, and who will honestly review and validate your proposed solutions.
Do you apologize for doing your job? I hope not!
So you shouldn’t apologize for figuring out when and where to insert yourself into the work that other teams are doing. Or for poking around to figure out when, where, and how those teams engage with the market and your customers. The key is to figure out what it is that you offer the other teams — what value you add to their conversations. Maybe your sales team needs someone more technical on-hand to answer specific questions or to run demos for their prospects? Maybe your marketing team needs an extra eye on the copy that’s about to go out. Maybe your support or services teams need some hands-on assistance with customer issues or integration/launch work.
All of these are things to keep an eye on, and doors that you can use to open your engagement with the market…
Once you’ve figured out how other teams engage with your customers, it’s up to you to create the opportunities and take advantage of them. If you’re trying to work with your sales team, find out when their account reviews happen, and make sure that they know you’re interested in attending — offer to be a silent attendee, maybe even the scribe for the meeting, taking notes. After you’ve got a couple of those reviews down, speak up and ask clarifying questions — but make sure that whatever you say is in support of your team and your product. Nothing will kill your attendance at sales-related meetings faster than sinking a deal or souring a renewal.
As for Marketing, the surest way to get your pass to attend industry events is to offer to help out with the transportation, setup, and/or teardown. All of these things are time-consuming and exhausting, and Marketing teams rarely have enough resources to ensure that it all gets taken care of on their own. If you can attach yourself to these efforts, you’ll wind up seeing marketing fight for the budget to send you and for the time away from the office — not a bad place to be at all!
And keep in mind that you don’t have to rely on other teams and other people to create these opportunities — you can usually find at least one event that happens locally that you can attend to establish some relationships with those in the market. While these may not be quite as fancy as some of the bigger events, they provide a low-key, off-hours chance to meet and engage with your market, your customers, and your prospects.
Build Your Own Relationships
So…you’ve figure out how others engage with the market, created some opportunities, and capitalized on them to establish some relationships — now what?
It’s not enough to just know people, nor is it enough to just meet people. Rather, you have to cultivate these relationships so that they’re actually useful to you. Knowing someone and being able to call them and get feedback on your proposed solutions, mockups, wireframes, or even just ideas…are entirely different things. Treat these relationships like a sales team would treat their leads — cultivate them and make sure that you’re maintaining a regular schedule of contact with them. Ensure that you’re bringing value to those contacts as well as extracting value from them — you can’t just call them every month and ask for their input; you’ve got to show a little bit in order to get them to tell. Figure out what interests them most, and what you can share, and manage their expectations as well as those of the other teams that you’re working with. It’s your job to remain in contact with your market and your customers, but you have to do so in a way that doesn’t foul a pending sales deal, that doesn’t contradict the marketing message that’s out there, and that doesn’t endanger your own job by sharing confidential information with the wrong people.
Communicate often, communicate with value, and build a strong relationship built on mutual value, mutual trust, and mutual respect.
The single most powerful tool that Product Managers have to make products that amaze and delight their users is to figure out what problems their customers have that they don’t even realize are causing them pain. Most people didn’t understand the benefits of 1,000 songs in their pocket when Apple first introduced the iPod back in the day, but MP3 players have now merged with our cell-phones and morphed into online streaming services to provide an ever-present library of whatever music strikes our fancy at the time. Sure, they weren’t the first, nor were they the fanciest, but Jobs and Co. tapped into something important — the latent need for us to have our music with us, wherever we were, in a package small enough to slip into our pocket.
There’s a lot of truth to be found in the classic mis-attributed (and possibly entirely fabricated) “Henry Ford” quote, “If I’d asked people what they’d wanted, they’d have said a faster horse.” People know what their obvious pains are, what the problems are that they experience every day — but most people only examine those pains at a very superficial layer. Someone who tells you they want a better way to manage the password on their work computer, for example, might never consider how much simpler it could be to simply add a biometric fingerprint scanner to their desk that would save them both time and effort. Customers focus on their current pain, and want that solved immediately — and they’re satisfied when you do so for them. But they’re amazed when you discover a problem that they didn’t even know they had, and deliver that solution from the word “go”.
It’s the difference between evolution and revolution, between iteration and innovation.