First, give conclusions that can be used for decision-making
The start-up phase should result in problem definition, target user, core process, business rules, prototype, initial scope and acceptance calibration. External product roles can be used to perform methodological and documentation work, but they cannot be a substitute for an enterprise's judgement of its client, price, process and risk.
What conditions need to be identified before judgement is made?
The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.
Suggested order of advance
First, we'll be clear about the target and the border.
Designate internal operations managers and assess the rhythm.
Validation Key Dependence
Interview users and organize tasks, pain points and existing alternatives.
Development of assessable outcomes
Production of low-cost prototypes to validate core processes and rules.
Make sure you decide the next step with the real results.
The first freeze, the acceptance criteria, is then developed in an iterative manner.
How do you understand it in the actual business?
The entrepreneur has a service appointment idea, but no job. He or she is interviewed first for 10 target users, drawing appointment, payment, and compliance processes, using a clickable prototype to validate them, and developing a minimum closed loop; and he or she is responsible for business trade-offs, with an external team responsible for product analysis and engineering delivery.
The easiest pit to step on.
Make UI design the same as product design.
There's no one in the house who's making decisions.
The prototype is developed without validation to develop a large number of backstage and edge functions
How should we end up receiving and confirming?
After the start-up, the team should have consistent records of users, problems, core processes, initial scope, suspension of development items and acceptance standards.
When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.