To do a great job as a product manager or Scrum product owner, you will benefit from two skill sets: a product-specific and a generic one. As their name suggests, product-specific capabilities focus on a specific product or product category. They include a deep understanding of the users with their needs, the competition, and the market trends. They also require you to have a deep knowledge of the product itself, including its value proposition, key features, user journeys, business goals, and KPIs. Finally, they imply an insight into how the company works and how things get done—what the company goals are, which processes are used, and who the decision makers and influencers are. As product-specific skills are crucial, I find that many product people strive to develop these capabilities. But as important as they are, they are not enough.
In addition to deep product skills, you require generic or transferable product management capabilities, such as, effectively capturing the product’s value proposition, segmenting the market, validating product strategy assumptions, selecting the right KPIs, prioritising the product backlog, and analysing user feedback and data. These skills are not specific to an individual product, but transferable. They equip you with the expertise to methodically solve common product management challenges and they enable you to move between jobs and verticals if you wish to do so.
Balancing the specific and generic skills leads to a T-shaped skills profile and makes you a T-shaped product person as the following picture shows. [1]
The horizontal bar is the ability to effectively apply product management concepts, techniques, and tools to different products in different markets and companies. The vertical bar on the T above represents the depth of related skills and expertise specific product, product line, or product portfolio.
Strong horizontal skills enable you to work methodically and manage different products in different companies. As these skills form a large set, I like to divide them into three subgroups: strategic, tactical, and leadership capabilities, as the picture below shows.
Strategic skills include the ability to develop an effective product strategy, actionable roadmap, and working business model. Tactical skills help you capture requirements, manage the product backlog, and validate ideas for new features and feature enhancements. Leadership skills enable you to effectively guide the development team and lead the stakeholders, create an inspiring vision, and reach sustainable agreements, to name just a few.
To become a competent product professional, you should strive to develop all three types of skills—leadership, strategy, and tactics. Even if you currently fill a tactical product role, increasing your product leadership and product strategy skills will help with your current job: You will be able to collaborate more effectively with the individual who sets the vision and decides the product strategy and earn their respect and trust.
Additionally, it will enhance your employability, enable you to progress your career and take on a role that includes strategic responsibilities in the future. And competent and well-skilled product people increase the chances of innovating successfully and maximising the benefits digital products provide.
To get started, explore how strong your skills in each of the three groups are. Ask yourself, for example, how much you know about creating and validating a product strategy, about product roadmapping, and business model development. Then focus on those skills where improvements will help you most with your current job. Here are some of the questions it asks you:
Deep product-specific skills are important to make the right product decision and move your product in the right direction. Here are some activities that I find helpful to strengthen this skillset:
[1] As far as I know, my colleague Ellen Gottesdiener was the first person to suggest that product people should be T-shaped, see her article 5 Ways to Recognize a Great Product Manager.
It may not be pleasant to experience, but conflict is necessary to innovate successfully. Without…
Developing a winning product strategy is hard. Keeping the strategy relevant and achieving continued product…
The product roadmap is a popular product management tool that communicates how a product is…
The product strategy is probably the most important artefact in product management. But how do…
A product team is a cross-functional group whose members work together to achieve product success.…
The most amazing product strategy and product roadmap are ineffective if the stakeholders don’t support…
View Comments
Roman’s insights are about product development, strategy establishment, commercialization, etc. It is very helpful in learning core business skills. Please also advise on content related to offline PO in addition to digital PO. Thanks.
Thanks for sharing your comment, Kim. I find a person in charge of an analogue, hardware-based product benefits from most of the skills discussed in the article. To which extent business acumen will be beneficial depends on the type of product: Revenue-generating products, especially those that directly create revenue, require solid business skills including the ability to generate and adapt a business model and to create a financial forecast. Hope this helps.
"Test competing offerings. This helps you understand if your product is properly differentiated." I like this tip. It's important to understand where your product stands in the marketplace, and what your differentiating value props are.
Thanks for your feedback Emily. You may find my post on using the Strategy Canvas helpful in order to ensure that your product is properly differentiated.
In case the product vision and strategy is defined at say the top management level, would that hinder the product owner's effort in bringing out the desired product. ?
How could the vision and strategy makers be brought in tune with the current product. ?
Hi Rahul, Great questions that are difficult to answer briefly. I generally recommend that the person in charge of the product is also responsible for its vision and strategy. This is particularly helpful when bigger changes are happening to your product, for example, when it is brand-new or young, or when you extend its life cycle, as this minimises the risk that the strategic and tactical product decisions aren't aligned. To ensure management's buy-in and understanding, I suggest a collaborative strategising approach in my book Strategize, where the management sponsor participates in strategy creation and review workshops. Does this help?
Awesome post Roman.. Have never seem such a lucid description of T- shaped skills for product managers/owners
Thanks for your feedback Srinath. Glad that you liked the post.
Hi Roman,
Interesting blog post. I notice that you categorise vertical skills as product related skills/knowledge. This is very restricted to the area you work in and generally won't transfer between sectors or companies very well.
I was wondering what are your thoughts on technical skills for product owners? Would you consider this a vertical skill set or more horizontal?
I'm at an early stage of my product management career and I'm coming across a lot of job roles that I think I would be capable for which require a BA. As I started my career doing an apprenticeship I actually don't have a degree. Do you think it would be worthwhile for me to study towards a technical degree in Computer Science?
Hi Aaron, Thanks for your feedback and question. I consider an understanding of software technology, like object orientation, design patterns, machine learning frameworks and algorithms, and development practices such as test-first, refactoring, and continuous integration and delivery as vertical skills: they are applicable to many digital products. Having an understanding of the technologies that are specific to your product is a vertical skill, for instance, Objective-C, Xcode, Cocoa, and UIKit for an iOS app.
If it's worthwhile for you to increase your technical knowledge depends on the role you play (or want to play) and the product you look after, as I discuss in the post "Do Product Owners Need Technical Skills?".
Does this help?