Deepti Srivastava

At a high level, a 0 --1 product offers a completely new solution or functionality to a user problem, often creating a new market category or sub-category within an exist...

For a new product in a new market, I don’t think you can ever validate the problem space enough. Once you have reasonable confidence that the users (and buyers) exist for...

When setting up any new line of business, revenue projection is an important step to understand the expected outcomes and viability of the business. For new a new product...

Once you have a good picture of your target user persona(s), their goals, tooling needs, and pain points, design sprints are an effective way to brainstorm the user journ...

Usually, there is a pre-determined prioritization framework that your product org should use to prioritize which problems to work on. There are multiple inputs with diffe...

There are multiple definitions out there for "mature products", but it ultimately depends on the product and business leaders in a company to define that as they know the...

Any prioritization exercise needs to start with first having clarity yourself as the Product Manager on the top business goals and related product priorities, and then to...

In general, the main thing I look for when validating any problem or solution is data. As a PM, it is important for you to figure out where to get the right data for what...

For early stage products, a feature or solution is usually ready to ship when it meets the functionality for the main user journey(s) i.e. "golden paths" defined in your ...

Not focussing on the user. I tend to be pretty heavily user-focussed when building products. I believe strongly that without users, you may have cool technology, but you...