Match What You Can Build with What People Need
Product-out starts product planning from a company’s capabilities or ideas; market-in starts from customer needs. These terms describe starting points, rather than mutually exclusive development methods.
A technical capability still needs a useful context. A popular request still needs feasible economics and a workable delivery model.
Connect Capabilities to a Use Case
For image recognition, identify the user and task. A proposal to reduce inspection time also needs observation of work required to resolve incorrect classifications.
GOV.UK distinguishes a user problem from a specified solution. (GOV.UK: User needs) Describe the useful change rather than making adoption of the technology the goal.
Examine Demand and Delivery Constraints
Record the situation, frequency, and current workaround behind requests. Investigate comparable users before treating one person’s preference as market demand.
List staffing, costs, and maintenance. Interest and actual purchases differ, so expressions of enthusiasm alone cannot establish viable economics.
Test Value and Operations in a Limited Scope
Limit the workflow and trial period, measuring user outcomes and delivery workload. Reasons for abandonment can reveal problems in either the explanation or the product.
A product website should state capabilities, conditions, and what happens after signup. Show the use case alongside the technology.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To publish a website explaining your product’s use cases and conditions, give SpreadSite a try!
Build a website with SpreadSite →