In this lecture, we will learn about Product Development Life Cycle. What are the basic steps one should keep in mind while developing their product are explained in the video?

The process begins with the Identification of the Customers, here we understand the biggest demography of their needs, what they need the most, and what constitutes it.

After understanding what customers need, it is important to Define the Problem. Here, problems are given more importance to knowing than the solutions for a better understanding of the situation. These problems are then broken into subproblems and the problem is identified to its very core.

The next step is Solutioning and Use Case. Here the problem is solved for the root cause and user interaction with the product is taken care of. Edge Cases, Error handling, and Metrics of Success are other parts that constitute this point.

The last step of the Product Development Life Cycle is Implementation and Measurement wherein the approaches are looked into, such as MVP, Testing approaches like A|B, Pre-post, Hold out, etc., all of which are detailed in the lecture.

In this lecture, we will learn about Solutioning. Solutioning is concerned with identifying solutions for problems defined, dividing them into MVP and North star phases, discussing with stakeholders, and defining measurement/testing methodology.

Solutions can be divided into two parts: Generic Solutions and Use Cases. Generic Solution: Whenever you are building a solution, think of what you want to build in an ideal world, think without restrictions, and think of a Nirvana solution. Think of the other parts other than primary functioning, etc. These are all the North star solutions.

In MVP Solution we have to ensure that the North star solution is divided into minimum requirements in the first phase, keeping the major customer base in mind while doing this. The Use Cases are explained in detail with an example for better understanding in the lecture.

In this lecture, we will learn about the application of the learned topics through an example. The video deals with recapping the stages in PDLC with the Birth of a famous grocery delivery app.

It started with Identifying Customers. These were the working families in metro cities who have a shortage of time, are ready to pay for their convenience, need quick service, and are mid-aged and tech-savvy,

The next step is Defining the Problem. The problem associated is that the customers can't spare time to get daily groceries and need help with the same. the reasons being that they get free from the office late and a lot of shops are closed and want to be free from chores after a hectic day at the office.

After defining the problem, the next step of the process is Solutioning. This could be building an Internet-based ordering solution to allow anytime/anywhere hassle-free ordering with quicker delivery and identifying who our competitors could be.

After these steps are taken care of, the implementation and measurement are done via MVP and V2 which are detailed in the lecture for a thorough understanding of _ Technical, Operational, and Eventual _ parameters.

The Use cases in adherence to Visualising Customer Journey and Competitor User Journey should be referred for a thorough understanding of the topic.

In this lecture, we will learn about What is a Wireframe and how it is basically used and what can we do using a wireframe and what is the best way to create one.

A wireframe is used when we have to represent a desktop/ mobile application. Basically how the application looks, its functions, etc.

Wireframe is important because it defines the usability of the product. For example, there’s a button to be placed on the screen, and choosing the right position where it's easy for the user to access it, is the kind of decision one makes in a wireframe.

In the further parts of the lectures, Wireframe is explained with suitable examples for better comprehension and understanding.

In this lecture, we will learn how to map a customer’s journey. How satisfied or dissatisfied a user is with an existing set of products.

Here, we try to analyze what a user expects or is unhappy about in the existing products that can be inculcated in the new developing product. Another way of a Customer Journey Map is that when we already have an existing product and we want to improvise on it, we would want to know what part of the product can be improved.

The stages of a customer’s journey are the Motivation to buy the product, Searching for the website that sells those, Browsing the websites, Evaluating the Product, and then Paying for it - described in detail in the video.

It is through this, that we can rationally make Product related decisions.