What is your first step in developing a 0-1 product?

"0-1 product development" is the idea of building something from nothing. That is, you have an abstract customer or business problem you need to solve and no solution for it (0) and, as a PM, you need to figure out the first attempt at a solution (1) to address the problem. An example from my own career is Notebooks, a product I helped ship at Abstract - we had a meaningful number of customers abandoning our initial offering due to changes in the product design tooling landscape, and we needed t ...Read More

0 -1 product development refers to building a new product or service line from scratch (0) to bringing its first iteration into the hands of customers and users (1) The first step to develop a 0-1 product is to deeply understand the market need. I look at this from the buyer perspective, the end user perspective, and the competitive landscape perspective. Unless you understand, what's needed, what exists, what's missing, and what will differentiate your solution and validate your need to exist, ...Read More

Part of the fun of building something 0-1 is that you have a green field in front of you — you can build anything! (Or that's what we wish as PMS....) As much fun as it would be to the world is your product oyster, constraints help provide focus and a direction. I see the first step is making sure that you and stakeholders are aligned on what a goal or success looks like. And usually, that comes in the form of a metric that you're trying to move.  If you work for an ecommerce company, you'll mak ...Read More

I will share first two steps that I follow. Step 1: Is this problem worth solving? 1.1 Problem definition and user segmentation B2B product: A business customer must have a genuine painpoint that they are willing to pay for. Some problems are not big enough problems, hence not high priorirty for the business users, these are not worth pursuing. Fine tune the problems till they hit   B>B>C: The business user/stakeholder may have rightly identified a problem but may not have the best ideas i ...Read More

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 existing large market.   The top thing in developing a 0--1 product is validating that there is a real user need in the market that will be served/solved by this new product, and, that the need is big enough to build a viable business around it. Identifying/defining the top user persona for the product – their motivations, goals, too ...Read More

I have a very simple framework for building 0-1 product - IVC framework Identify: The first step in developing any product or feature is to identify the user's needs. Hence, your goal should be to talk to as many users as you possibly can to understand what they say, do, think, and feel. This also helps you learn who you are solving for and who you are not solving for and create a problem statement 2. Validate Building Conviction by testing Discovery, MVP, market analysis, possible conversion. D ...Read More

"0 to 1 product" refers to building a completely new product from scratch, rather than improving or scaling an existing one. The term was popularized by Peter Thiel in his book Zero to One, where "0 to 1" signifies creating something truly novel - going from nothing (0) to something (1). This is inherently an ambiguous process with uncertain outcomes. The first and most critical aspect is to validate the initial product thesis ("problem statement") and underlying demand for a solution to this pr ...Read More

0-1 product refers to building a new type of product or capability - new to the company (Tableau Prep) or new altogether but possible because of technology or market forces (think social networking). The first step is to identify an underserved customer pain point that is aligned with your business objectives. Some questions to ask to get here:- Where do we think there's whitespace or change in the market?- Who’s underserved or facing new challenges (e.g., due to tech shifts, regulation, budget ...Read More

Creating an entirely new product or entering a new market, the first steps typically involves conducting thorough market research and validating the product idea. Here's a breakdown of the initial steps: Identify a Market Opportunity: Start by identifying a potential market opportunity where you believe there is a gap or unmet need. This can involve researching market trends, analyzing customer pain points, and exploring emerging technologies or industries. Define Target Customers: Clearly defin ...Read More

Here are some steps I would consider: Customer and end user issues: conduct early stage interviews to understand the end user personas, their goals, pain points and unmet needs Define the market size and ensure there is a large enough need for the product. Some financial modeling is needed to ensure the product will be viable. Define success measures: What would it take for the product to be successful? What are the top metrics you will go after? Build out a MVP: if possible, build a MVP product ...Read More

The first step in developing a 0-1 product is to deeply immerse yourself in the problem space and understand the users experiencing this problem. This foundational understanding is crucial as it ensures that the product development is user-centered and data-driven. By starting with a thorough grasp of the problem and user needs, you minimize the risk of building something that fails to address genuine demands, maximizing resource efficiency and adaptability in your development process. Here's th ...Read More

Start by forming assumptions and making hypotheses around the desirability, feasibility, and viability of your new product. Then validate those assumptions, learn and iterate. Desirability assumptions could be Is the product addressing a problem that the customer is facing? Always look at how big the problem is in customers' lives and how much time, money, and headache it saves. What is at stake if the problem goes unsolved? How frequent is the problem? Building a product for a one-time problem ...Read More

The first step isn't building, it's figuring out the problem you're solving. Too many founders jump into development without validating the core issue. Id start with customer discovery: talk to potential users, understand their pain points, and map out the unmet needs in the market. What matters is that youre solving for real users and not chasing tech trends. If you don’t have a crystal-clear understanding of the problem, your product will end up as a solution in search of a problem. Build fast ...Read More