We can break down the problem: 1) what: what cargo? Is this item of high value? Is it affected by time? 2) why: Why go through the cave? Delivery, so the core demands of delivery 3) who: Who asked this question? driver? boss? People from government departments? The job function email list core demands of different people will change, and the solutions will also be different. For example, people in government departments may care more about the safety and smoothness job function email list of traffic, while bosses care about costs, and drivers care about whether they can complete tasks on time. 4)
Where: is the destination far away? Is there any job function email list other way to go? Are detours expensive? Think from a cost perspective. 5) What is the frequency of this scene (low frequency and high frequency, if it is high frequency, then you can try to solve the job function email list problem completely, such as expansion)? 6) Is this scene urgent (if urgent, even part of the cargo can be discarded)? Such questions are very common in product interviews, so we usually need to cultivate product thinking.
Only do things once to find feasible solutions, and repeatedly do things to find optimal solutions. If we collect and analyze information, we will get a lot of job function email list solutions, which will give us more opportunities for choice. We need to make a value judgment on job function email list each scheme in combination with the scenarios, so as to select the optimal scheme. We must also learn to "give up", find the core needs of users, build products around the core needs, and remove redundant functions.