<h1 class="pgc-h-arrow-right" data-track="2" > what is product thinking? </h1>
As a front-line developer, have you all experienced the experience of arguing with the product, and even in the end, no one can convince anyone, and can only raise the problem. In the end, the boss will come forward to solve it, and in most cases the boss can really solve it in some way, and it is a mutually acceptable solution. At this time, most of the students may think that the boss's authority, status led to this result. In fact, this is very inaccurate (there may be some reasons but definitely not the main reason) in fact, it is more that each boss has a stronger product power than the first-line development, can understand each other's demands and grasp the contradictions and give solutions. At the same time, the expression is easier for each other to accept, which leads to the final boss you see out of the horse, the problem is solved, as if your own point of view continues to be maintained, while the other party also leaves room. So what does this important ability come from here? In fact, I think it is more of a product thinking way.
From here, we can see that product thinking is a way of thinking that continuously maximizes value through scientific methodology, but it may be a bit hollow to say that it is a bit empty, in the form of product iteration based on everyday product technology, and more importantly, product thinking.
<h1 class="pgc-h-arrow-right" data-track="5" >2 Why do technicians have to have product thinking? </h1>
1 Limitations of the technical perspective
I feel that the demand raised by the product is meaningless, does not help the business, and is a chicken rib demand;
Question Why do the demand for products change every day? Very reduced work efficiency;
I felt that the idea of the product was crazy and unprofessional. Completely without considering the feasibility of the system, it is basically impossible to implement it;
I feel that the product's scheme is not comprehensive at all, and such obvious logical loopholes have not been considered;
.......
In daily work, as a programmer, have you often heard the above complaints, in fact, a small part of the product may indeed be immature due to experience, but more have you ever thought that it is due to the collision of product thinking and engineer thinking, resulting in everyone's perception of the same thing is different, from their respective points of view will feel difficult to understand. First, let's look at a set of product thinking and the comparison of technical thinking.
For example, before the Hema warehousing product reviewed a live fresh warehouse according to the needs of the box out of the warehouse, the general awareness is that for live goods (such as fish, crabs, etc.) directly in the box as a unit for warehouse management. But here there are several unavoidable problems if you start from the engineer's thinking:
1. The scene of box in and out of the box does not exist in the previous storage system of Hema and is unknown whether it is implementable (HOW, technology first);
2, the whole link should be adapted to this transformation, the transformation point will be very large, difficult to achieve (pay attention to details, solutions);
3. For scenarios with less or more goods, inventory reconciliation involving upstream and downstream links will be very troublesome, and it will not be aligned at all in extreme scenarios (perfect plot);
In response to these problems, the R&D side carried out the demand return, and the product business alignment plan and risk were reviewed again. But from a product perspective it's a completely different scenario:
1. Boxing and going out did not exist before, does not mean that it will not exist now and in the future. This is the business scenario that is really needed offline, and hema warehousing needs to expand this kind of capability (WHY, user value);
2. The full link transformation has a large construction period, and the construction period can be sorted out for normal scheduling iteration (iterative thinking);
3. Abnormal scenes are small probability events, and cannot affect the advanced advancement of the entire project because of small probability events. A really small amount of anomalous data is pocketed by the business itself. (Overall view, completion is more important than perfection);
Here, because the product and technology are not from the same angle, it will bring natural conflicts, and it will be difficult to understand where the other party's demands and problem points are after the emotions are brought in, and whether there is a relatively reliable solution after the synthesis of the two. Here, if the technician changes the perspective and uses product thinking to cope with this demand, will it be more appropriate to communicate in this way?
1, recognize the box in and out is a new ability, let the product determine the business value to expand such capabilities. It is also a complement to the inventory capacity of existing warehousing systems.
2, inform the product has psychological expectations, the cost of the full-link transformation program will be relatively high, the time consumption will be relatively long. See if it's acceptable, and if it's not, try an intermediate solution.
3. If the technical side invests a lot of cost to transform the link, it is necessary for the product and business to recognize the technical value and input-output ratio of this matter.
When communicating in this way, the technical side of the product will be clearly told the problem points and concerns, so that when both parties recognize the value and necessity of this need, they will work together to move forward together. Back to this example, in fact, if the programmer has product thinking, you can think about the problem from the perspective of the product, it is easy to communicate and cooperate with the product team to cultivate a more harmonious working relationship, and it is more conducive to improving work efficiency.
2 Advantages of technicians after improving product strength
Let's take a look at what work advantages can technology bring to technicians in addition to being more easier to communicate after the technology has product thinking?
Abstract ability believes that everyone does technology more or less, and it is often used in writing code. But abstracting according to what is already there and abstracting from the future are two completely different abilities. When technicians have a product perspective, it is easier to find abstract angles and express abstract concepts. For example, we have recently received a product appeal for the weighing of the intelligent scale of the large warehouse processing (the weight of the raw material in the processing process is recorded through the system) If the simple abstraction may be the weighing task, the raw material can be weighed and the finished product can be weighed. If you have product thinking after communicating with the product, you will ask what problem does this weighing mainly solve? What step is it in the actual operation industry? At this time, you may think of a process in combination with the MES system, and you will carry out an abstraction of a process task. But here we consider the expression, is it necessary to make everyone more aware of what the process is? Here there will be a natural analog refinement, filming, labeling and other practical links can be expressed through the process, and then combined with the scene he applied, such a future-oriented process model can be gradually precipitated, but also convenient for future expansion (interested students can also understand how the essence loading unit in the lower warehouse is unified induction precipitation in the face of the past, how the future is abstractly expanded, which is a very classic abstract example).
Cultivate thinking ability, improve the angle, and make it easier to see the essence of the problem. If you think about the fundamental attributes of things with product thinking to express the fundamental attributes of things, do you mostly start from these three perspectives:
1. Give a clear definition;
2. Make accurate and simple analogies;
3. Make a subtle analogy;
You have always had this habit at work, and when you encounter difficulties, you will take your thoughts into your own hands instead of handing them over to others. This is a thing that is more tiring at the moment, but it is very cool for the future, and maintaining a certain curiosity and imagination to think will make you harvest more growth. There is a classic line in the movie "The Godfather": "People who spend half a second to see through the essence of things, and people who spend a lifetime can't see the essence of things, are doomed to a completely different fate."
What does a better global view, here for technicians, mean?
1, of course, to improve the proficiency of the system, not only for the current module you are responsible for, but also for the upstream and downstream links of the system you are responsible for also have a considerable understanding. This will give you more opportunities to take on greater responsibilities.
2, clearly know the need to do this, the value of the project, know why to do it, rather than simply execute the machine. I will think about the necessity of demand from the perspective of demand rationality, input-output ratio, etc.
3. It is easier to know how to reflect the value and know what the focus of the project is? Know how to precipitate data, elaborate and achieve goals from a system perspective.
4, better through technology to create business value-added, technical students if they have product power will be easier to find the optimization points in the product, and create a lot of business value. For example, before the preferred grid warehouse for the central warehouse delivery container for secondary distribution to the site, the technical side found that here can be for the goods in the container distribution relationship can be disrupted (the overall distribution relationship is unchanged) to reduce the number of distributions. This one technical small point alone reduces the number of distributions on the grid warehouse site by 12%. Another example: before the B2C warehouse picking and broadcasting, it was to pick up a SKU to enter a roadway, if there are multiple SKUs in the roadway that need to be turned back many times; the technical side has product thinking and then gives a better product experience through subtle changes, and abstractly classifies the two actions of total picking and distribution. Unified general picking, and then distribution method, to avoid the problem of picking personnel going back and forth multiple times under the way of general picking and distribution, and improve the efficiency of the picker by 14% on the spot.
<h1 class="pgc-h-arrow-right" data-track="39" > how to improve product power</h1>
1 A shift in thinking
At different stages of thinking, we must make progress in the perspective of the problem. Being able to respond to changes in the specific performance layer and abstracting the underlying concepts and capabilities (for example, the process of complex evolution of warehousing systems is more about the continuous evolution of capacity & human efficiency & cost & digitalization) to constantly exercise their thinking habits, so as to improve the boundaries of thinking. Recently, I was reading a book on product law and took some notes, which I think are worth paying attention to and constantly learning and improving our technical personnel
Essential thinking: The first principle is calculated from the beginning, using only the most basic facts as the basis, and then deducing layer by layer to draw conclusions. Putting aside what others do, how to do it in the past to get a different perspective (refusing to be influenced by the design of similar products and not understanding the design of similar products are two different things) The serial questioning method is a means to clarify past ideas and key links, help quickly judge and produce new ideas.
Relative thinking: daylight and shadows, making things bright is not necessarily to enhance its brightness, by turning down the surrounding environment. This is a kind of reverse thinking. Success and failure, strengths and weaknesses are all temporary, relative concepts. There are two important perspectives to look at: relationship and time
Abstract thinking: There will be conflicts between idiots and God, and the problem view from a higher abstract perspective and the user's instinctive level of view. If you look at different localities can be switched is more important ability. Concreteness and abstraction are like the process by which points are constantly shrunk as an airplane takes off. Think more about new elements (capabilities) than new features, elements can build functionality.
Systems Thinking: The Status of Feedback. The feedback system model is a basic abstract model that essentially designs feedback. Thinking that all extreme and abnormal paths are small probability phenomena.
Evolutionary Thinking: Bottom-Up Design. Minimalism is the foundation of evolution, and a good framework is focused and easy to put away.
2 A small step in reality
Seeing this, you may ask and say so many soft thinking and methodological related views. If you look at it from the perspective of landing, how to improve in your usual work? How to subtly change your thinking?
Universal routine: read more books, cultivate their own knowledge reserves; do more summaries, express what they have learned as systematically as possible, which is also to further consolidate their knowledge achievements; do more sharing, if a knowledge point you can not only understand by yourself, but also let everyone understand what you say, what your thinking is, which will further enhance your structured thinking & expression ability;
Stay curious: This is something I would like to express in my usual work not to limit myself to my boundaries, not to be satisfied with the work assigned to you, but to explore more parts of the work assigned to you to expand your field capabilities. Basic requirements: after listing a project in which you are responsible for one of the modules, whether you can cover your upstream and downstream problems, whether you can locate the cause and assist in solving the problems online in time; the other is to maintain the exploration of the surrounding areas, compare the work content and thinking of the surrounding students to see what part of the ability they still lack, and what targeted improvements they can do. For example, when working, a classmate may be responsible for the picking practice part of the warehouse: has you understood the main process of the picking order generation part? Do you know the design of the packaging section? Do you know the main ways and constraints of basket shipping? Do you know the interaction nodes and main data of documents outside the warehousing system?
Zoom in a little more to the point where you usually care about the life experiences of others in addition to work? Do you turn a deaf ear to everything from international news to peripheral intranet gossip? This will put you in a state of information blockage, which over time will lead to rigid thinking. Therefore, you must maintain your curiosity, ensure the breadth of your knowledge reserve, and keep your thinking in an active state.
Think more about the nature of product requirements, at least first think more in the PRD review, and understand more about the reasons behind product design. For example, if there is a user's need to lose weight, what would you think of? What ordinary people may think of is weight loss, but what should be thought of under product thinking is that he wants a more beautiful appearance? Maybe he needs to find a partner? Probably want to improve your social status?
Keep more associations, exercise imagination, and usually receive the demand of the product, can you relate to the existing capabilities of the system, and can you combine the existing system to achieve the optimal solution to the requirements? Here is an example of warehousing system picking: before the Hema processing center had a demand for picking goods according to goods, to the effect that when the picker saw the goods in the warehouse, he could actively select the goods to pick the goods, and the demand for picking goods according to the goods was a relatively simple appeal from the product side. What is the general association here?
a. The first reaction to receive this demand is generally to directly select the pick list returned to the user according to the commodity, and then let the user make a selection (and need to change the relevant index of the pick order);
b. Thinking of the overall situation, if you think deeply about the real-time scheduling of the picking task operation in the B2C warehouse, you can think of it here to use the task scheduling to achieve is more in line with the planning of the warehouse to operate the global scheduling?
c. Thinking about the bottlenecks and optimization points of the existing system, the current scheduling selects queue pull tasks according to the partitioning & task capabilities, which is essentially a kind of "real-time sorting" and can only be pulled preferentially based on configuration. In fact, we should also expand the "selection ability" of task scheduling, such as this time by commodity request, which is actually a selection ability within the queue. In addition to the L1 level of the ability to select different queues when obtaining tasks, we should have the ability to select L2 levels inside the queue, to enrich the other scheduling mode of our task scheduling center on the practical side (and the ability to sort the level);
d. Finally, combining the past and the possible future, except for picking by commodity, the way the previous DPS picking & label picking went through the task queue to pull through the temporary filtering should not be a long-term approach. Including the subsequent possible picking by location (laneway warehouse location inside the partition, real-time acquisition of the optimal picking order according to the human position), picking by sales order (which order is timed out of the emergency to increase the priority), etc., the essence is based on the real-time practical action to have the L2 dimension selection ability, whether it can use this demand to build a foundation to achieve the ability;
e. Finally, some abstract induction suggestions are given, changes in picking practice, human factors, and dynamic selection. When generating tasks, it has the dynamic ability to produce normally and operate (the ability to select insertion is selected according to human factors), if it is not configured, it defaults to using the sorting ability of the original queue.
Of course, this is just an example of association, and the final decision may also consider various factors such as input-output ratio. Keeping your imagination is a good way to increase the depth of your thinking, both for programmers and product managers. What we have to do is to develop habits and let our thinking grow with our imagination.
Author | Row Creek
Original link: http://click.aliyun.com/m/1000294612/
This article is the original content of Alibaba Cloud and may not be reproduced without permission.