post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Podcast

How CX works with Product at Ikea – Hanneke Hoogewerf (Sr Strategic Experience Designer, IKEA)

Artificial intelligence (AI)

Generative UI for product managers: A new frontier

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! 🎉

Join us at #mtpcon London in 2025 – mark your calendars

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

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

Deep dive: Crafting your product vision and mission

5 ways to invent and simplify as an AI/ML product manager

Started as an engineer, I got my degree in physics and worked for a while in small tech companies developing particle accelerators, antennas, and consumer electronics. Slowly I transitioned to a Team Leader and then to a Product Manager in a big food delivery service. Now I combine my skills in a startup founder role.

Founder

Evgeny Savin

<p>I believe that product managers should take the time to discuss new product hypotheses and planned features with the engineers they work with. It helps them to be able to plan a project <a href="https://www.mindtheproduct.com/category/product-roadmap/" target="”_blank”" rel="”noopener” noopener noreferrer">roadmap</a> as precisely as possible. I&#8217;ve also found that there are a number of hard skills which product managers can learn which can benefit their product skills.</p>
<p>I came into product management after a career as a physicist and a hardware engineer. I now work at Russian multinational <a href="https://en.wikipedia.org/wiki/Yandex" target="”_blank”" rel="”noopener” noopener noreferrer">Yandex</a> to develop digital products and services alongside engineers and other product people. I work with back-end developers and I find we can implement new product features more easily if I can predict and plan with programmers those technical features which our users will never see.</p>
<h2>Pros and Cons of Working With Engineering</h2>
<p>We have two main goals:</p>
<ol>
<li>To keep the digital service evolving by bringing out new product features for the customer</li>
<li>To make the service as reliable as possible so that the user experience is smooth and enjoyable</li>
</ol>
<p>This means that our feature backlog contains both product and technical tasks. Some technical tasks may be solved when product tasks are implemented, but this means that the feature may be delivered much later than the business expected.</p>
<p>How can this be rectified? I try to see the technical aspects of any feature and use them for scoring, such as E (Ease) in <a href="https://www.mindtheproduct.com/three-simple-ways-to-make-product-prioritisation-easier/" target="”_blank”" rel="”noopener” noopener noreferrer">ICE scoring model</a>. Of course, it’s impossible to foresee all potential technical problems so I also discuss all new product ideas with my engineering colleagues. They help me to modify the original ideas to make them simpler and more efficient. We find that when we build a new backlog and figure out our deadlines, our combined estimates are usually much closer to reality than our separate technical and project estimates.</p>
<p>But I&#8217;ve found that it pays not to be too involved! I think digging deep into the technical parts of all the new features can shift your product perspective. You need to be involved just enough to see in advance which technical teams and services will be involved in the product implementations, so you can estimate deadlines closely enough.</p>
<h2>How I Plan the Backlog</h2>
<p>In my experience, some hard digital skills can help you and your teams to implement new product features and services faster and more efficiently. Saying that, I prefer to first plan and create <a href="https://www.mindtheproduct.com/the-meaning-of-mvp-correcting-common-misconceptions/" target="”_blank”" rel="”noopener” noopener noreferrer">an MVP</a> and then run it for a while to see how the customer and the business interact with it. I can then polish the service depending on all new requirements and observations. I find it saves a lot of time for programmers which they can use on other features or on making the service more reliable. But as the product manager, it means that I need to maintain the service for some time, so I need to know some basic programming.</p>
<figure id="attachment_20056" aria-describedby="caption-attachment-20056" style="width: 981px" class="wp-caption aligncenter"><img loading="lazy" decoding="async" class="wp-image-20056 " src="https://www.mindtheproduct.com/wp-content/uploads/2020/05/programming-shutterstock_1404621860-300x178.jpg" alt="" width="981" height="582" srcset="https://www.mindtheproduct.com/wp-content/uploads/2020/05/programming-shutterstock_1404621860-300x178.jpg 300w, https://www.mindtheproduct.com/wp-content/uploads/2020/05/programming-shutterstock_1404621860-768x456.jpg 768w, https://www.mindtheproduct.com/wp-content/uploads/2020/05/programming-shutterstock_1404621860-1024x607.jpg 1024w" sizes="(max-width: 981px) 100vw, 981px" /><figcaption id="caption-attachment-20056" class="wp-caption-text">Image: Shutterstock</figcaption></figure>
<h2>What to Learn</h2>
<h4>SQL</h4>
<p>I find that I need to be able to work with collected data and make some quick data-driven decisions. I can use SQL to prove my point, see how people use our features, and so score new ideas.</p>
<h4>APIs and working with Terminal</h4>
<p>Most of our digital services are based on APIs, where some part of the service asks another part to execute a specific code with provided data and get a result. You can play with APIs and estimate feature performance. I find that usually new ideas emerge during these tests. I suggest checking how data transfer protocols (like http) work, what POST and GET requests are, and how to use curl in your terminal.</p>
<h4>Python, Jupyter Notebook and Basic Packages to Work With Data</h4>
<p>Simple manipulation with data can save you time. You can work with app reviews, and plot essential data. I suggest installing Anaconda, Python3, and playing a bit with lessons in Python programming and data visualizations. I found useful packages to be Pandas (playing with tables), NumPy (manipulating data), and Matplotlib (plotting data).</p>
<h4>Instruments for Data Visualization</h4>
<p>I find it’s super useful to control the health of your service. How many people are online compared to a week ago? Has revenue changed today compared to yesterday? How many negative reviews have you received today in the App Store?  There are many more questions which may be specific to your service. You can plot all interesting product details on the dashboards and spot the problem even before some technical alerts will go off. There are many tools to plot dashboards, like Splunk or Grafana. Just check which is mostly used by your engineers and try to use it for your metrics.</p>
<h4>Basic Website Creation Packages Such as Flask</h4>
<p>Flask is a Python package that helps you to build simple websites. There are lots of tutorials on YouTube you can follow to build some sample websites. I’ve used it to help me understand basic interactions between the front-end and back-end, and later to build simple interfaces to check how the MVP performs.</p>
<h2>Tips for Product Managers</h2>
<ol>
<li>If you are a product manager, try to spend time with engineers. Your colleagues have a lot of insights into the product.</li>
<li>While planning and scoring product tasks, think about technical complications. This will make your deadlines more realistic.</li>
<li>Research which instruments and tools are used within your team or company and spend some time to research them at a basic level. It will help you save time when you want to check logs, plot data or request an API.</li>
</ol>

Skills to Make Working With Engineers Easier

Evgeny Savin

Read more

Comments