The human factor in the implementation of processes and tools, or which succeed better tools? Rookie Author Alexander Where succeed better tools? What a strange question – of course, where there is similar tools and technology! Can tell the reader and will be only partly right. If a customer has a similar technology and tools, it is often the only hindrance as psychologically, each of us reject all things new. There are several factors that have a negative on the process of introduction, we mention only the most important: duration of the instrument – the most obvious factor – the longer – the more used, the more difficult to move on new. Age specialist – is the most interesting factor, which in itself is absolutely nothing said. That is, the introduction can make a minor adjustment for age, but only with the first factor can be speak of a substantial effect on the outcome. Satisfaction with current tools – a factor, "but to me, and so anything goes," You can call blocking – it affects the outcome. It was the objective criteria, consideration of which would be incomplete without such powerful subjective as reluctance to move to the new technology because it provides more in-depth oversight of the Executive elementary sabotage …
The implementation should take into account all factors and prepare measures to reduce their impact on the final result. A sample? I want to give you an example from real life on the subject. So, we have a company that experienced a series of acquisitions. Staff consists of specialists from different companies. Age – totally promiscuous, but dominates the middle peasants.
No organization has no process. True, the leadership stayed in their confidence presence. At some point in time everything inside it became clear that without processes and automation tools can not – the company itself felt on all the problems of a chaotic approach: Do not expect the assembly are given to the wrong customers; Documentation errors is manually log errors in the word; metrics are not collected, there is no Planning (or rather have a plan that no one adheres to) Tasks for the developer hang orally, and so on …