A business usually has two reasons for doing a thing: one that sounds good and a real one. The product manager will think of the real reason. Their job is about finding monetizable market opportunities. Business results matter and acquiring new customers and increasing average revenue per user is part of the monetization equation.
But all of us, being idealists at heart, like to think of motives that sound good. So, in order to make it sound appealing, we talk in terms of what customers want. There is an approach called "working backwards" that is widely used at Amazon. Work backwards from the customer, rather than starting with an idea for a product and trying to bolt customers onto it. Because value springs out of what customers fu...
Posted on July 27th, 2017
Software development has become a strategic priority for all companies in today’s digital era. In turn, the product management role has expanded. The product manager of today is wearing many hats, using a broad knowledge base to define the problem-solution-fit, make trade-off decisions, bringing together cross-functional teams, ensuring alignment between diverse functions, while still commanding the respect of engineering.
Required skills include a grounding in customer experience, market orientation, business acumen, technical skills and soft skills. That's not all, the product-management role will continue to evolve toward a deeper focus on data and a greater influence on nonproduct decisions.
Jackof All Trades, Master of None O...
Posted on July 11th, 2017
Wish lists are a pain.
It looks like a small request – at best. It comes top down, it guts your strategy, it unbalances all the hard work you put in prioritising and forces you to make difficult trade-offs.
Great news: you need to validate that it’s actually useful and/or important,
Less-great news: If they clearly aren’t important enough to be done, then they don’t belong on the backlog. Your job is to break the news.
Some of my stakeholders have tried everything to eviscerate a backlog: Last minute esoteric requests with intense pressure on me to say “yes", contradicting established objectives and priorities, discrediting the customer need/personas, questioning prioritization techniques …they just end up forcing me to take meas...
Posted on May 6th, 2017
Product management is empirical, verifiable by observation, experience, and practice. I’m amazed at how calculated and theoretical some make it be. Put yourself into the right critical thinking mindset, do some customer research, think through your market and validate if there is a product opportunity. In a great market, your product doesn’t need to be the best; it just has to basically work. In a terrible market, you can have the best product in the world and it won’t matter . If there’s no customer need, everything else falls apart . Move on! Find another market.
Just another day in Vietnam. No big deal.
I’ll draw a comparison to photo-journalism. Eddie Adams’s 1969 prize-winning photo shows a chief of the South Vietnamese poli...
Posted on February 27th, 2017
Make the right hard calls. Prioritize ruthlessly. As a product leader, you’re most often evaluated by your ability to make difficult trade-offs quickly. When considering new features to enhance the existing product, what are the critical elements to look for? In the following lines, I’ll describe a process around decision making which you can use as a repeatable and sustainable methodology to constantly make important product decisions. Yes - you won’t have to rely on gut feelings or get trumped by the loudest voice in the room.
Great product managers say no
Research is the center around which all of the other dynamics of product management find their orbit. Spend as much time as necessary to become an expert in all details rela...
Posted on January 21st, 2017
It's bad when big decisions are made without context, or with little explanation. It’s worst when you're told that there are no master plans, that success will no longer be about delivering product features. Success will be about customer value learnings and adapting the strategy accordingly (read: there is no product strategy).
Instead of executing on strategy we will look for one.
Instead of making complex plans that are based on a lot of assumptions we will sketch out a hypotheses and test via constant adjustments called pivots (changing course with one foot anchored to the ground). We will go from failure to failure, adapting, deciding whether to pivot or persevere.
It’s a methodology made popular by Eric Ries called the Lean...
Posted on December 26th, 2016
You’re the one who will tell people what should be built and why. So why was it so tough to get engagement from the technical teams? Because people need to buy into your vision and engineers should understand the ‘why’ behind their work and how it relates back to delivering customer value.
Nothing creates greater misalignment in an organization and slows execution speed than a conflict of vision and values. In the end, no buy-in leads to no delivery.
Listening is about leading with your ears instead of your mouth
A common mistake is to declare that you’re the “CEO" of the product. That stance leads product managers to anchor too heavily on their own vantage point, insufficiently adjusting to others’ perspective. The fact is, one le...
Posted on December 19th, 2016
I lead a team and we deliver ‘product like’ hardcore digital platforms. The outputs of our work are non-marketing products. Like a restaurant's mobile app that lets you order your meal ahead of time for example. People always think that product managers operate this very critical, high-leverage function that, when executed correctly, greatly facilitates the leap past prototypes into a steady return of profits. These are products with revenue models tied to the technology. But there are some who offer the product approach as a service where products are shipped without the purpose of becoming sole revenue generators.
Offering Product Management as a service often means translating an emerging product Strategy/Vision into an amazing c...
Posted on December 17th, 2016
As a rule, when products go wrong, everyone has contributed in some important way. I was asked how I’ve had so much success keeping product expectations in check?
There are as many product management approaches as there are weight loss programs. Most will help, many will keep you stranded in a world of theory and make you forget that software development is mostly about cultivating personal relationships. The key is to start any initiative’s first encounters with the assumption that you don’t know squat about it. That approach will help you see the other side’s perspective more accurately. Some call it customer research, customer listening, internal expert interviews. I call this your opportunity to understand various perspectives. ...
Posted on November 20th, 2016
Three years ago I was asked to join Edelman to orchestrate the turnaround of their North American technology group. With my March anniversary I thought I’d share a few things learned about leadership, management and working in a company whose norms and culture don’t align with what one would see in a software company.
As the “CEO" of the technology organization, ultimately accountable for the team’s results I provided vision not just for the technology team but the whole organization. I established processes and practices for realizing that vision, set the bar for quality and decided on the kind of work environment to foster. Many of these I brought with me to validate along the way while others I learned the hard way.
Posted on November 16th, 2016