Skip to main content

It is hard to be a Tech Product Manager, but it is even more difficult to be an effective one

Background


Nobody is born a product manager. In the technology space many of us have grown into the product management role after being software engineers, software architects, marketing specialists, or similar roles.

Different academic backgrounds can help in the role, some product managers have engineering degrees, others business degrees, and there are numerous examples of product managers coming for many other disciplines.

The challenge is that Product Managers require to pay attention to a wide range of concerns around the product, ranging from market research, to business analysis, to software/hardware development, to UX design, to project management, to pricing, to commercialization, and others.
Making it difficult to strike a good balance between wide visibility and deep expertise.

We will talk about this in the following paragraphs but my experience tells me that the secret is to dynamically switch gears on-demand between the high-level wide vision and deep-diving into tactical details depending on the specific moment in the product life-cycle journey.

Skill Set

Product managers often have to deal with the following concerns:

  • Market/Consumer Research
  • Competitive Analysis
  • Business Analysis and Strategy
  • Business Modeling and Finances
  • Requirements Gathering and Rationalization
  • Usability Studies and User Experience Design
  • Technical Design, Feasibility, and Cost/Time Forecast
  • Regulatory and Legal 
  • Technical POC and Prototyping
  • Project Program Management
  • Engineering and Development Life-cycle Management
  • Testing and QA
  • Marcom
  • Performance Metrics
  • Continuous Improvement
  • and others.

By now I am sure you may have heard many times the phrase "A Product Manager is a mini CEO of her/his product", and there is a great deal of truth in that statement.

As you know, it is very unlikely that the same person can be an expert in all the mentioned above concerns at the same time, in the same way that a CEO does not need to be an expert in every single aspect of her/his company.

However having a decent level of skills and experience in 2 or 3 of these areas of concern is key to managing products. If you are only a software engineer then you better polish yourself more in the business side. In the same way if you are an interaction designer then pick some coding skills, or if you are a marketing pro you will benefit from some usability and tech knowledge.

The wider your knowledge, the easier it will be to cover the 360 degrees around your product. 

Generalist Versus Specialist

The previous paragraph may initially suggest that Product Managers are generalists (as the CEOs are), and I will argue that is partially true.

Why do I say partially? Because in my opinion there is a great advantage for a product manager to be a bit deep in at least 2 or 3 of the skills listed above (or whatever ones apply to a particular product).
In my experience, product managers gain a lot of traction when they have a few areas of expertise in which they can partner side-by-side with some key functions and accelerate work and results.

There is no strict rule on which of the product areas one should be skillful on, determining that is more for each of us to decide based on our existing skills, our potential skills, and their match with the type of products that we want to manage.

For instance if you are managing high tech products, some level of technical thinking and skills will be necessary to get more traction in your role. Similarly, if you are managing entertainment products, some level of knowledge of the creative process and the mechanics of the entertainment business will help.

This last concept is leading us to the next paragraph, in which we make the distinction between generic skills and the notion of Domain Expertise.

Domain Expertise

There is an additional dimension that is key for product managers, the notion of domain expertise.
If you are managing an insurance product then it is key to understand the insurance business and the insurance customer.

What happens if I want or have to manage -for instance- a healthcare product and I have zero experience in the healthcare field? Am I unable to do the job? No, you definitively can, but you better invest most of your initial energy and time on learning the market, the consumer, the competitors, the value chain, the distribution, the existing IP, the regulations, and other key aspects of the healthcare business domain.

Do not worry, none of us were born experts in a particular business, industry branch, market, or customer segment. Problem spaces have to be learnt one day, at that is OK.
I would even argue that both of the following principles are valid:
  1. A product manager with tons of expertise in a specific domain can bring substantial value to the table very quickly.
  2. Conversely, a product manager with no prior experience in the domain but with strong generic product management skills (and perhaps with expertise in adjacent domains) can bring a fresh new look to the problem space, and can provide innovative techniques to address the problem that can lead into disruption.
In fact, in my opinion, staying decades in a single business domain may not be very healthy for a well rounded product manager.
It is exciting to develop deep expertise in one domain, master it, launch great products, drive revenue, etc., but it is not a bad idea to eventually move to a new challenge in another business domain. 
Such change is a great way of bringing lateral thinking and cross pollination to the next product management job.
It also shows a great degree of adaptability, which is a great skill in the professional profile of a product manager.


Ultimately

At the end of the day, what I consider essential in a product manager is being a true advocate of the customer, knowing the product user very well, and being passionate about helping that user to solve her/his needs or desires in the best possible -and profitable- way.

Without that passion for customer advocacy any other skill will get diluted, I will even say that  without that obsession for helping the target customer there is no Product Management.

Obviously, the passion alone may not be enough, here is where those skills in 2 or 3 specific areas become handy. Combine that with some domain expertise and high customer advocacy, and you will become a highly effective Product Manager.









Popular posts from this blog

Cloud, SaaS, PaaS, and IaaS Adoption Trends and Forecast

At this point it is clear that the term "Cloud" transcended the buzz word and is already the label of an attractive $100B+ market. Cloud Computing represents the top enterprise IT spending in 2015, even beyond other hot growing technologies like Mobile and IoT. Not just that, budgets for Cloud offerings may even double in 2016. And if we talk about the other two hot tech trends, it is not a surprise that about three quarters of the IoT and Mobile offerings have also a Cloud component. Let me share with you my own direct experiences and my interpretation of some key Cloud Computing statistics over the last few years as well as the trends for the next two or three. In every case contrasting the numbers with qualitative data points and insights. Let's then dissect the Cloud universe in the typical 3 tiers, starting from the bottom... Infrastructure as a Service (IaaS) In 3 years IaaS will represent: ~35% of cloud use cases (compared with a ~65% of PaaS + SaaS)...

Wearables: The quest for the missing killer app?

I am a happy Fitbit user for more than a year and a half now, recently my family gave me a Samsung Gear S as a present, so at this point you can already subscribe me to the list of the ones who bought into the wearable computing promise, the Internet of Things (IoT), and the Internet of Everything (IoE). Source: Fitbit.com I use my Fitbit band almost all the time, I also use a very often its excellent smart phone app and the linked cloud service. I use the band/app/cloud trio mostly for everyday health tracking and casual sports. I believe that this device is a clear, simple, and pragmatic example of the the Internet of Things (IoT) potential. Fitbit has very active community of third party developers creating even more and specialized value for Fitbit product owners, check the list of cool and useful Fitbit apps in their Partnerships page. The FitBit's OTB mobile app is already a killer app, and many of the third party ones too, making the whole device + apps + service...

Informal Catalog of Business Models for Internet of Things (IoT)

This article mostly contains public knowledge, however seeing the data compiled all together in this way may help to rationalize it and apply it in a more rigorous way. I hope this express catalog helps others the same way it helps me. By running new hypothetical product concepts or existing offerings through these "filters" helps to understand their strengths and weaknesses. Which monetization models would you add to the following list? Selling IoT devices for end users I this case the device in itself delivers the key functional capabilities, with enough customer value to pay for its price tag. Many time these products leverage existing infrastructures such as Wi-Fi, a Smart Phone, etc. Even if this model centers around the IoT device, a software and/or cloud service may be necessary as a companion for a rounded UX. Software and/or services put more pressure on R&D and ongoing operational cost, and consequently in ...