Product Inception: Defining the Who, What, Why, and How of a Digital Product
Every product should begin with a problem that needs to be solved. Product Inception is the process by which we pin down the problem in concrete terms and determine how we are going to solve it—all before writing a single line of code. Representatives from the design and development team as well as stakeholders must be present throughout the process in order for Product Inception to be effective. By the end of a Product Inception session, everyone should be on the same page about where we're going, why we're going there, and how we are going to arrive at our destination. In our series of posts, we explore different aspects of the Product Inception process in order to demonstrate how we do things here at sophilabs.
Why do we believe in Product Inception?
Product Inception is crucial to developing a product that truly solves the problem we intended to solve and helps users meet their goals. Even if a problem seems obvious, there are always multiple perspectives to consider; there may be aspects of a problem we can't see until a stakeholder brings it to our attention. In addition, everyone may have a different idea about what an effective solution looks like. Product Inception, then, brings everyone to the table so we can come up with a unified vision for the product and agree on a road map to take us there. The collaborative nature of Product Inception ensures that we include everyone's point of view, thus allowing us to produce ideas that are even better than what each of us could have thought of individually.