In addition to the needs that already job function email list xist in the client's original plan, such "urgent needs" are often presented with very little consideration. Sometimes even seemingly insignificant changes can cause unexpected chaos to job function email list the entire system. So at this time, what should the product manager do to satisfy customers without harming the original system,
Dragging down the progress of the project, and job function email list not burying himself in the hole? Having stepped on countless pits, I have summed up three points of attention, hoping to help reduce the hassle of dealing with urgent needs. 01 The principle job function email list of simplification What is the easiest way to do it? This is a problem that product managers need to think
About first when receiving urgent needs, that is, from the overall consideration of the system, how to meet customer needs with the smallest job function email list changes. For example, if you can reuse existing components, you won't do repeated development; if job function email list you can only modify the front end, you won't move the background; if you can only add fields,