Work in blockage mode and in increasing blockage mode
For simplicity, let's take a conveyor belt production. The conveyor is traditionally divided into sections (into multiple sections). At each section of the conveyor there is an employee who performs a certain process or takes the position of "observer" - a standard manager. Imagine a picture: in such a production, in the middle of a shift, someone missed a certain moment and everything on the conveyor falls to the floor. This is where the Ass begins. Everyone runs, fusses and curses the culprit and urgently tries to come up with "something".
Option two is considered a logical "something":
We stop the conveyor and all together we rake the blockage.
We continue to work raking somehow because there is some very important (only in the opinion of the top management) reason. They say you will stop, then you have to wait an hour for it to warm up, and this is a loss of money and the collapse of everything.
If we follow the first path, then the result is usually the same - we cleared the blockage, picked up the pace, returned to work - continued to work for quality. The money is dripping, the bosses are satisfied, the customer grumbled about the failure to meet the deadline, but eventually got the result and calmed down.
What if we go the second way? Right!
The blockage grows, and if the blockage grows, then all the fate is knocked out of the general pace, the details are made longer, the customers become angrier, the bosses yell and everyone stays together after the shift and rakes up a fairly grown heap, in some cases more than one day!
Or people are trying to adapt to the situation so that other areas suffer less and the blockage is raked up, i.e. run across from more distant sites and begin to rake from the beginning site by site, otherwise the result will go for hours and days to them, and kicks in the ass from observers, higher authorities and the customer fly more and more painfully .. well, or more offensive.
We will transfer the plant to a typical IT services company
A conveyor is a well-oiled chain from "wishlist" to "some cool thing" for the customer.
Segments (longest possible chain):
The client himself is the initial link in the conveyor, which gives out needs as a generator of random ideas or, extremely rarely, clearly formulated and well-thought-out “wishes”. As a rule, they are afraid to stop him because of the very "very important reason" - they say the client will leave us, then we will not return.
( ) - , .
- , . " ", , «, ».
- , , . 2-3 , «, ! , » , « , ». .
- , « » . , , .
, , . .
. – « , ». ? , , . , «». , , .
. ( ). ? , , « » ( «», ).
. - , .. , . ? , , . , .. 15 « » 3 3, ( ).
. . , , , , – , , ( !) ? , , , « » « , , », , 99% .
. , , . ? « , , , , - » #3. : , - - .. IT , 3 , .
:
, - . - , , . , , "", "", " ", - . "" ( ), . .
. , , , .
: -, . - . -, : , . -, . , . : " ", " ", " ", , . -, , . - : , , . . : " , , , ". : , . , - ( ).
. , , , . . , " " " , ". , , .. /. , , . , - , .
. , , . , . . - /, / . - . - . / . - . / .
If the Customer has a blockage, then either the blockage is justified by a blockage in one of the sections, or by the fact that the Customer has little time due to its internal processes. If this is a blockage due to other areas, then the answers are higher, but if these are internal processes, then you need to try to find a more unloaded representative of the Customer who can accept tasks or divide tasks into categories and identify those responsible for each category.
These are the thoughts that were in my head. I look forward to your feedback. Glory to the Hayters.