It has been 30+ months since the last article was published. At present, this company is responsible for 15+ projects (not counting the process optimization of some unsuccessful projects). The efficient work efficiency/communication efficiency allows me to be responsible for multiple projects at the same time. A project and the mind is not stuck in traffic.
Nearly 4 years of working experience in platform products, and approaching the node of job replacement, I have sorted out some personal thoughts and gains during this period and shared them with you.
Foreword: Due to different industries/company/departments, the competencies required for different product positions are different. But abstractly, all (product) jobs provide problem-solving skills. Of course the problems are different, but there is always the same approach/thought to solve the problem.
Broadly speaking, there are three steps to solving a problem, in order:
Analyze the key
provide the solution
Loop iterations (analyze/solve/validate new problems)
1. Analysis of the problem
In terms of analysis, there is a famous stalk <How to put an elephant in the refrigerator? >. Everyone knows the answer <open the refrigerator door, put the elephant in, close the refrigerator door>, so let's discuss this question.
1. Refine the process
The first step in analyzing a problem is, of course, to refine the problem first. A problem that is imaginative does not mean that the problem itself is 100% imaginary. A bad TV may just be a problem with a certain part. We can also help to open and close the door when zooming in like a refrigerator.
Unfortunately, the first reaction of most people is to deny the problem in its entirety. And once the problem is denied, the value of the problem solver is also denied (or becomes the point of view of the person who raised the problem), after all, no one wants to pay for an unsolvable problem.
Going back to the stalk of enlarging the elephant into the refrigerator, after refining the process, the problem becomes much clearer.
Open the refrigerator door - doable (low cost)
Putting the Elephant in - Difficulty (high cost)
Close the refrigerator door - it works (low cost)
Then split the second step, transport the elephant from somewhere to the refrigerator, and guide it in. The more subdivided the process, the clearer the problem to be solved, and accordingly, the clearer the method to solve the problem.
2. How detailed is it?
My answer is that it's enough to be as detailed as it can be solved, or as far as you know. This is divided into two steps and can be solved. The problem is solved, and it is meaningless to continue to detail, unless there is an alternative solution to country email list reduce the cost.
Doing the best you can is a self-comforting choice. The size of the information/knowledge capacity is equal to a person's IQ/ability/value level to a certain extent. Don't ask too much of yourself on things beyond your ability, otherwise it will only bring you frustration.
And doing the best you can, it's not easy to do this. This requires us to understand what we know and make inferences from one case to another. In the work scenario, this requires us to be able to give an answer with the lowest cost in combination with the past content of the project / the plan being implemented / the possible future planning.