How processes kill processing of teams
I had always had this idea in my mind that processes were made in order to make things work in a smooth and better organized way till recently I had certain different experiences, that have prompted me in coming up with this post. Processes should be introduced and adopted only if they make improvement to the organization. When we talk about the organization, it is people that I am pointing. At last, it is people or teams, whose efforts bring out these results. Expert implementers should always take care and do a study about the team and its nature, before a process could be decided to be adopted. Else, it could turn over the other way, where process kills out the functioning of the team.
Typically people come ahead with ideas to improve the working methodology and style of functioning, so that the organization could have more benefit from the team. None of the companies or institutions would like to implement a process that would introduce the team into a formal change in ways, till there is any return from this decision. Without any outcome, what is the concept behind initiating something? What it would lead into is introduce disturbances within the team causing anarchy. I think that none of the companies would be interested in putting their organization into such troubles.
There were times where I have heard people talking aggressively about processes, as if it were processes which provided outcome to their clients. They better find a different audience. I heard someone fighting team for keeping the name of a file that needs to be kept as a reference. What difference does it make if we call it a knowledge base or a knowledge bank? I had no idea why this person was adamant with the decision about the name. It didn’t take another minute before issue arose within the team. All of the members start grouping and fighting against the person. The issue here is that this took over the pace and efficiency of his team.
At times, introducing bad ideas hit back with really bad outcomes. Implementing inappropriate processes are also of the same seriousness. I have seen a company closing its operations within the country, because its people management team had introduced some processes which introduced some kind of laziness or reluctance towards work. This needs to be thought about, way before the process adaptation level. Else, it could result in bitter results because we are in between a set of thinking minds. We cannot adopt Agile methodology of software development just because it is new, but only if it is worthy adapting. Each person is of a different nature and with a different thought process. What a proper way to introduce something better should be to discuss it within the team which need to work along with it. That would help us get diverse views from diverse angles.
Typically people come ahead with ideas to improve the working methodology and style of functioning, so that the organization could have more benefit from the team. None of the companies or institutions would like to implement a process that would introduce the team into a formal change in ways, till there is any return from this decision. Without any outcome, what is the concept behind initiating something? What it would lead into is introduce disturbances within the team causing anarchy. I think that none of the companies would be interested in putting their organization into such troubles.
There were times where I have heard people talking aggressively about processes, as if it were processes which provided outcome to their clients. They better find a different audience. I heard someone fighting team for keeping the name of a file that needs to be kept as a reference. What difference does it make if we call it a knowledge base or a knowledge bank? I had no idea why this person was adamant with the decision about the name. It didn’t take another minute before issue arose within the team. All of the members start grouping and fighting against the person. The issue here is that this took over the pace and efficiency of his team.
At times, introducing bad ideas hit back with really bad outcomes. Implementing inappropriate processes are also of the same seriousness. I have seen a company closing its operations within the country, because its people management team had introduced some processes which introduced some kind of laziness or reluctance towards work. This needs to be thought about, way before the process adaptation level. Else, it could result in bitter results because we are in between a set of thinking minds. We cannot adopt Agile methodology of software development just because it is new, but only if it is worthy adapting. Each person is of a different nature and with a different thought process. What a proper way to introduce something better should be to discuss it within the team which need to work along with it. That would help us get diverse views from diverse angles.
|
|
