You will learn:
→ what types of PMs are there in IT (Project, Product, and Program), and what are their differences
→ how product managers differ from each other: grades, specialization, product type, interaction model in the product, area of ​​responsibility
→ who are the "11 friends of the product manager", or, in other words, people in their environment in an international company

What it looks like:
→ You take one PM typical description and understand what it really means step by step

What students say about the lesson:
→ Alexandra: "It's useful, it highlighted for myself the role of the product manager in the team more clearly."
→ Efim: "The format of reviewing through the working day and environment is very clear and goes down well."

Not taking everything for granted but challenging everything is an important PM skill. It's not enough to say that everything is undefined, you have to build a lot of product hypotheses and then prioritize and validate them.

You will learn:
→ the JTBD methodology to build hypotheses
→ JTBD scoring
→ competitor identification
→ job and sub-jobs

What it looks like:
→ formulate JTBD for several cases
→ calculate their priority using a template in Google Sheets
→ apply the acquired knowledge to the clothing rental use case
→ average completion time is 2 hours

What students say about the lesson:
→ Bogdan: "I'm sitting here happy as an elephant. Practice is really important."
→ Kate: "The situations are very realistic, like from life. The presentation of the material is fun:) I enjoyed thinking about it."
→ Max: "The lesson is great and to the point! Interactive situations - very interesting and useful."

Defining and launching an MVP is one of the pillars of product work because it allows you to try hypotheses, spending days instead of years and hundreds instead of millions of investments. MVP is your new approach to any project and any feature.

You will learn:
→ several examples of MVPs of top companies
→ MVP structure and MVP Canvas Template

What it looks like:
→ step by step filling out the MVP Canvas for a clothing rental startup
→ you apply the MVP approach for a separate feature
→ at the end - a convenient MVP checklist for use at work
→ the chapter will take about two hours to work with

What students say about the lesson:
→ Maria: "A lot of practice, a powerful simulator for the MVP lesson, cool!".
→ Julie: "Thanks for the lesson! Lots of useful information that can be applied at work right now."

The given market analysis methodology helps you to estimate your ability to scale your business and the limits of your growth.

You will learn:
→ the basics of the acquisition funnel
→ TAM, SAM, SOM definitions
→ methodology of calculating the scale of your business

What it looks like:
→ you'll play around with the acquisition funnel's model
→ you'll have to make a difficult and unpopular decision

• → the chapter will take about an hour to work with

What students say about the lesson:

• Yulia: "I liked to directly count and "touch" the example. It was very clear, thank you!".
• Mike: "Clear metrics. A big plus is that you immediately get a base for comparison and a link to the benchmarks."
• Dilara: "Thank you very much! It was interesting, lively, vital, practical and everything was to the point!".

In this chapter, you'll learn the basics of unit economics and build a simple but flexible unit economics model.

You will learn:
→ the definition of unit economics
→ ideas on how to select a unit
→ costs classification and allocation rules

What it looks like:
→ allocate the gross economic metrics to a unit
→ model different scenarios in Google Sheet
→ make a decision to scale (or not to scale) the product based on data

→ the chapter will take about 2.5 hours to work with

What students say about the lesson:

Mikhail: "A great introduction to unit economics!".

Agne: "I liked the lesson + there was a lot of practice. Practice is the best thing for such lessons."

Alene: "Thank you very much for providing the files with calculations! It really helps and simplifies working with numbers."

Product development is impossible without the use of product analytics. It's not enough to know metrics, you need to solve real cases and touch analytics systems with your own hands.

You will learn:

• You touch the ground with product analytics

What it looks like:

• We analyze the theory on the simulator and immediately practice.
• We learn what kinds of analytical systems are available and why to use them. We are consciously not attached to any one analytics system.
• We solve cases in the Mixpanel product analytics system.

What students say about the lesson:

Alex: "Cool lesson. Thank you. I really miss this - I've never used tools like these. It was interesting - to delve into this interface and so on."
Julie: "To touch a real product analytics tool in person - it's exciting."

For a PM, it is critical to set up the team's operational activities, because this is the only way ideas can turn into working code and features. We will analyze three mechanisms of planning: short-term (sprints), medium-term (OKR), and long-term (vision/mission).

You will learn:
→ how to ask the right questions to your user stories
→ how to prepare for spring planning
→ how to prioritize the backlog with the most popular impact-effort method
→ what your backlog looks like in real Trello and ClickUp tools
→ what are story points and how to set them correctly

What it looks like:
→ help the tech lead prioritize the backlog by asking the right questions
→ learn to choose the right impact scores
→ work with Google Sheets template impact-effort prioritization
→ choose which tasks to take into the sprint, taking into account the velocity of the team
→ the lesson will take from 2 to 3 hours

What students say about the lesson:

Alexandra: "The practice is great, there are many diverse questions, also aimed at different metrics and situations, I liked it!".
Michele: "A wonderful simulator! The idea of ​​conducting training through a simulator is the best!"

If a product manager can only do one thing, they should focus on setting ambitious goals (the most important part of the strategy). In this chapter, we learn how to set mid-term goals using an OKR tool and long-term goals using a mission/vision tool.

You will learn:
→ why we need Objectives and Key Results at all
→ how to set the right OKRs
→ what are the most common mistakes when setting OKRs
→ what is a vision and why a PM needs it
→ how vision differs from mission
→ how to define them for the company, department, and team

What it looks like:
→ help Jr. PM and Marketing specialist to set goals for their projects
→ together with the Principal PM, connect the OKRs of the team, departments, and the whole company
→ help Principal PM set a crisp vision for teams and established companies
→ fill out a detailed vision statement template for the messenger team of a large company

→ the lesson will take from 1 to 3 hours

What students say about the lesson:

Mila: "Cool practical exercises aimed at calculations and understanding! I really like them!".

Oleksandr: "I can't wait to put OKR into practice! The simulator really helps to organize the information received in the lecture, find gaps and understand the topic more deeply."

Serge: "I really like the quality of the additional materials."

In short, it is suitable for IT specialists to upgrade their role/increase their salary, for rookie PMs to practice, and for entrepreneurs to structure their approach to the development of their startup. Now let us give you a bit more details.

Our basic courses are suitable for specialists who are already somehow connected with the world of IT development (marketers, programmers, project managers, team leaders), who decided to move to a leadership position and determine “what to build”, and not just “how”. The role of a leader means greater responsibility and a new salary (of course, not on the first day). A basic understanding of IT terms will allow IT professionals to ask deeper questions and, at the end of the course, be truly prepared to lead a team.

PM skills will also be useful for those who want to remain in their position, improving leadership clarity and a structured approach to the project.

The course will benefit rookie PMs, as it will help them connect diverse skills into a single picture and get a lot of practice, which beginners usually lack. Moreover, if you desire to work in an international company and aspire to create products that change the world, you've found the right place: we have a lot to share.

Moreover, the course will help aspiring entrepreneurs structure the development of their ideas. Since PMs are quite similar to entrepreneurs, just under the company's wing, we teach exactly how to make the project take off.

For people who are rather far from IT, the course may be less useful since it will be difficult to apply it in practice and, therefore, get the maximum benefit. But perseverance moves mountains, so it’s your choice.

The approximate length of the course is 40 hours: 14 lessons on a simulator. If you study for an hour and a half a day, you can complete the course in 27-40 days.

The modules "Product Planning and OKRs" and "Product Discovery" are included in the basic course "Fundamentals of Product Management." If you would like to receive the full course program, please contact us, and we will give you a discount.

The cases are really real and reflect the diversity of products in the industry: not everyone has a "website" or a "store". In the "Fundamentals" course, we cover the clothes rental start-up; in the "Tech for PM" simulator, we will look at a taxi ordering app (like Uber), a music service (like Spotify), and a food delivery app. In the simulator "A/B testing" we will dive into experiments on the Meditation service, and in "Product Discovery" we will analyze the business of renting clothes.

The more cases you solve (and not just read/watch), the more experienced a product manager you become. There is no other way.

One of the distinctive features of ProductDo is that all our courses are packaged in a simulator format. We can say that this is an important element of our product vision. The simulator as a learning tool has many wonderful properties:
- it requires constant active participation of the student. In order to move forward, you need to choose some action or answer a question every time.
- it allows you to give detailed feedback on any action: You can justify the preferred option with links and examples
- it allows you to move at your own pace and does not burden those who do not really like to work in a group with unnecessary communication.

Usually, they teach like this: theory → practice. If you have mastered the theory well, then you do the practice 100% or so. We have a completely different methodology. We start with a practical task that needs to be solved (and if the course suits you, then you don't know how to do it yet). Only when you have tried to solve the problem, we bring up some theory behind it. We believe that the cycle: trying to think independently → making a decision → feedback on a decision is a very effective way to master new material, especially for those who have already reached some professional level.

If you want to try the simulator format, take a free lesson. It contains questions from different areas of product management. At the same time, you can evaluate which skills you already have enough pumped, and which can be further enhanced.

We help by giving you a bunch of practical tasks and sharing our mistakes and experiences. We have already built so many products that with our examples we can help you formulate your area (more technical or more payment, related to ML / AI, or sales, etc.). We believe that a good PM chooses their favorite product themselves and does not need to be led by the hand.

The entire history of the simulator with comments and answers is saved. Access to the materials remains forever.

Yes, students who have successfully passed the course may generate a certificate and proudly add it to their LinkedIn profile to Licenses & Certifications, or upload it to Facebook in the Schools section.

Yet do keep in mind that upon applying to a product company, certificates do not really increase the chances of being hired, at least in our practice. If a resume mentions a certain course, then this may raise questions about what the candidate really knows right now. Therefore, you need to solve problems and develop skills, and not chase certificates. Fortunately, our courses have enough practice.

You can be sure of the materials' quality and our mentors' experience. We've been teaching for many years, and we have thousands of happy PMs. Feel free to take a look at the student reviews for verification.

If you passed less than 30% of tasks of the simulator you could refund your money in full.