post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Product Management

Sunday Rewind: Whose job is it anyway? The rise of Product Ops and why it deserves to be an independent function

Guest Post

Creating metrics that matter

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

How much are product managers getting paid in 2024?

Leading product ops at Delivery Hero with Koen Dubelaar

Connecting fans to creators at Spotify (Dariusz Dziuk, Product Lead, Spotify)

“You’re not as competent as you think” 5 lessons from Ken Chin on navigating a product career (CPO, Spark Networks)

Everything wrong with the product management job market. And how to fix it

Yana is a product owner with 10+ years of experience in developing and growing products. Now she is a CPO in the ed-tech company Netology.
"Netology" is an educational online platform launched in 2011 with revenue in 2022 exceeding 21 million dollars. "Netology" specializes in the training and additional education of professionals in internet marketing, business and management, design and UX, programming, analytics and data science, business education, as well as creative professions and higher education.

Yana Arsyutina

<h2>Product and business strategies &#8211; what&#8217;s the difference?</h2>
Before we delve into the analysis of mistakes, let&#8217;s make sure we have a clear understanding of what product and business strategies entail. A business strategy reflects the company&#8217;s goals and the means of achieving them as defined by the owner and top management. It includes:
<ol>
<li>Goals formulated through metrics: company valuation, revenue, market share, etc.</li>
<li>Time horizon: how long the strategy is developed for, whether it&#8217;s three, five, or ten years.</li>
<li>Description of markets on which the company will operate and grow: listing of markets, boundaries, volumes, development stages, dynamics, competitive analysis.</li>
<li>Description of the business model, commercial, product, and marketing approaches: extracts from commercial, product, and marketing strategies.</li>
<li>Business plan: the company&#8217;s financial model taking into account income and expenses.</li>
<li>Risk and opportunity analysis of the strategy.</li>
</ol>
This approach protects the company from setting goals that are inherently unachievable. From the early stages, the attainability of these goals is tested: whether the market volumes are suitable for expansion, whether there are enough resources, how the economy aligns with different approaches, and so on.
The simpler and more concise the business strategy is formulated, the better it fulfills its function &#8211; ensuring synchronization and a unified context between owners and the management team, as well as providing a unified coordinate system for decision-making within the entire team in the future. Elaborate strategies written in complex language may look impressive but create significant barriers to understanding.
Ideally, a business strategy should be a 10-20 slide document that explains in accessible terms the direction in which the company intends to develop employees at any level. In its most general form, it is a description like: &#8220;The company plans to capture 25% of the market and intends to do so through a product line that focuses on products A, B, and C, utilizing specific marketing approaches.&#8221;
The product strategy focuses on how the company will develop its products. It includes the following elements:
<ol>
<li>Target market and customer segment, analysis of their needs and barriers.</li>
<li>Unique selling proposition, product positioning — the answer to the question of how the company&#8217;s product differs from competitors.</li>
<li>Product architecture — which parts of the product have the greatest impact on the customer experience. For example, in e-commerce, the customer experience is influenced equally by the performance of the delivery service, website convenience, and product assortment. If the store has a limited product range and the courier service performs poorly, even the most advanced search engine in the market alone cannot help achieve high conversions and sales.</li>
</ol>
<h2>The planning horizon in product and business strategy</h2>
On mature markets, such as heavy industry, the strategic business planning horizon can be 10 or 20 years. In digital companies, where processes, technologies, and the market itself change rapidly, it is sufficient to limit the business strategy planning to five years. However, planning ahead for five years at the product level is challenging — customer structures, their needs, and the market change much faster. Therefore, the optimal horizon for a product strategy is 1-2 years.
<h2>Mistakes we made in designing the strategy at Netology</h2>
In our work with strategies at Netology, we approached the process iteratively, making classic mistakes and learning from them. Let me tell you about some of them.
Mistake #1: Creating a strategy for only a part of the product
What we did: We designed a strategy for an isolated part of the product. Yes, we had a formal business strategy, but it was very high-level, lacking the depth of decomposition that would have helped us formulate a cohesive product strategy. By skipping the alignment with the business and several logical levels, we designed a strategy for a separate part of the product — the digital environment. In it, we emphasized the importance of practical tasks. As a result, we implemented many new interactive formats for practicing, such as quizzes, tests, and peer review of students&#8217; homework. Technically, we achieved the goals set in the strategy. However, in practice, it made no sense: the strategy of the neighboring instructional department, which was responsible for creating the actual content, diverged from ours — the functionality turned out to be unnecessary, and the end user did not receive any value.
What this led to: We wasted time designing and implementing product features without achieving significant results. One of the teams achieved their goals, but the product and the company as a whole did not.
What we learned: We need to start working on product strategy by designing the product architecture, gathering all the components that influence the user experience. For example, at Netology, the product architecture consists of:
<ul>
<li>Program lineup: what we teach</li>
<li>Digital environment: technical solutions where students learn</li>
<li>Content and methodology: how we teach</li>
<li>Customer service: how we help and support students in their learning process.</li>
</ul>
The strategies for each component are interconnected and aimed at achieving common goals. We should involve all departments in the product strategy work, set common goals, and synchronize approaches among them.
Mistake #2: Designing a product strategy without a business strategy
What we did: We designed an excellent product strategy, building the product&#8217;s architecture, studying the target audience, selecting positioning, and forming a roadmap to achieve annual goals. However, we completely overlooked aligning with the company&#8217;s business goals and failed to understand what the business owner expected in the long term.
What this led to: We focused on working with a narrow segment of the audience. Yes, we achieved our annual goals, but the segment&#8217;s capacity would not be sufficient to achieve the business&#8217;s long-term goals.
What we learned: We need to start designing product strategies by formulating long-term business goals. We should also synchronize with business owners regarding business goals. For designing product strategy, we need to research the market not only from the perspective of customer needs and the competitive environment but also in terms of market volume, potential, and development stage. If there are no existing studies, we should conduct them ourselves, iteratively test and improve our understanding of the markets we operate in.
Mistake #3: Relying more on business goals than product goals
What we did: We delved into the process of designing the strategy and focused on business goals at the expense of product goals. Essentially, we excluded part of the vision and value of the product from the business strategy.
What this led to: We believed that our main task was to work on the business&#8217;s efficiency. For example, we decided to replace some live webinars with pre-recorded videos to save a significant portion of the budget. However, we realized in time that such an approach could significantly lower the product&#8217;s quality in the long run. We had to find other ways to improve business efficiency without compromising the product.
What we learned: The product is the foundation of the company, and its goals are equally important as the business goals. Therefore, the goals of the business and the product should work in constant harmony.
<h2>Find a balance: build strategies from both top-down and bottom-up approaches.</h2>
Currently, we have reached a structure where both business and product strategies are equally important to us. They rely on and complement each other. Every year in August-September, we enter the process of updating and validating our current strategies: business, product, marketing, and commercial.
The first stage is information preparation and gathering in three directions. Firstly, we collect market information: overall market changes, competitor and customer needs, and emerging trends. Secondly, we conduct an internal retrospective: how close we are to long-term goals, what each department is already doing well, and what can be improved. Thirdly, we review how business owners&#8217; goals and expectations have transformed. This stage can take up to a month.
The second stage is the design of the strategy itself. In a series of strategic sessions involving the CEO and functional leaders, we analyze the information collected in the first stage and sequentially discuss each component of the strategy. This process involves multiple feedback loops, typically comprising 7-10 meetings on average. The result is a comprehensive document with updates on the company&#8217;s overall goals for the next five years, as well as the product and marketing strategy components.
Since key department leaders are involved in writing the strategy, it becomes easier for them to transmit the information to employees and collaborate with them on creating annual plans. These plans should not only be synchronized with each other but also contribute to achieving the desired results within five years.
Once the strategy is formulated, it is presented publicly within the company. Typically, the CEO takes on this task and provides updates on the current status every six months to show how close the company is getting to the desired outcome.
<img decoding="async" src="https://www.mindtheproduct.com/wp-content/uploads/2023/08/6734eff4-60b9-4c47-9038-70f4deec8d16_0720320netology10738.jpg" alt="" />
<h2>How to maximize your results</h2>
<ol>
<li>Product and business strategies should be developed in sync with each other: both the business and the products should strike a balance between quality and economic efficiency. It is important to consider the goals of the owners, the needs of the customers, and the overall market trends.</li>
<li>The company&#8217;s strategy should protect employees from making incorrect global decisions. Even if you later decide to deviate from the initial strategy, you will already have an understanding of which direction to move in and which mistakes to avoid.</li>
<li>The strategy should be a simple document that is understandable to all employees. It is crucial to publicly highlight and discuss it within the company: any strategies created without the involvement of the people who will implement them have no value.</li>
<li>When building strategies and annual plans, it is important to avoid the trap of &#8220;my team&#8221; versus &#8220;their team&#8221;. In complex products, all elements of the company impact the overall results and user experience, making synchronization a key component of all processes.</li>
<li>There is no need to fear the daunting word &#8220;strategy&#8221;. Any strategy is better than no strategy at all.</li>
</ol>
<h3>Discover more case studies on Mind the Product</h3>
<ul>
<li><a href="https://www.mindtheproduct.com/a-case-study-the-journey-to-becoming-a-product-led-company/" target="_blank" rel="noopener">A case study: The journey to becoming a product-led company</a></li>
<li><a href="https://www.mindtheproduct.com/building-a-digital-product-organisation-brick-by-brick-by-nils-michaelis/" target="_blank" rel="noopener">Building a digital product organisation, brick by brick by Nils Michaelis</a></li>
<li><a href="https://www.mindtheproduct.com/a-case-study-how-to-produce-a-winning-app-redesign/" target="_blank" rel="noopener">A case study: how to produce a winning app redesign</a></li>
</ul>

core/freeform

Common transformation pitfalls by Marty Cagan

Using principles to make better decisions faster by Martin Eriksson

How to build for creators by Peter Yang

How to navigate tricky work relationships

Organizing around complex products at the intersection of physical and digital by Matthew Cornford

A case study: How to develop product and business strategies

Yana Arsyutina

Read more

Comments