The trap of Bureaucracy
From the PM Mex Corner Blog
by Humberto Ramos
PM trends, challenges and hot topics, as seen from Mexico corner
Recent Posts
¿Como reportas avances de un proyecto Scrum ante una PMO?
La “Asignación de culpas” conduce a la parálisis en los proyectos
El Gato Muerto
Where are the real PM Gurus?
Todos quieren ser
Categories
Agile,
Bureaucracy,
Chapters,
Español,
Ethics,
Leadership,
PMO,
Sátira,
Scrum,
Spanish,
Volunteering
Date
Any of us should feel uncomfortable working in an immature environment, where success is just a matter of luck or the ability of a few very talented People. On the other hand, while trying to implement formal procedures, for example for a PMO, we are always under the threat of the bureaucracy trap.
Bureaucracy has become a bad word. But it was a good one, it was introduced to define the method of government of an organization where order and procedures existed. Max Weber (German sociologist) defined bureaucracy as the systematic processes and organized hierarchies necessary to maintain order, maximize efficiency and eliminate favoritism.
So bureaucracy was created by men as an instrument to help organize in a more mature manner human endeavors. However as any human made stuff, bureaucracy can be used for good or for bad. The bad usage of bureaucracy appears when it is used to justify its existence rather than used as a support to obtain final goal accomplished.
In the case of a PMO, a bureaucracy governance is established. No matter how lean, any procedure is a bureaucracy instrument. If this procedures serve more to justify the existence of the PMO rather than achieving the final goal (the project done on time on budget), then we have fallen in the trap of bureaucracy.
More harm will come: When individuals are faced to the demons of delays, paperwork and low value procedures, resistance to the new procedures increases. The argument is that the PMO is an office of useless work and low value added procedures… and they are right. Because the PMO has fallen in the bureaucracy trap. The trap is completed when the organizations arrive to the consensus that "less process is better" and "no process at all then even better". The whole organization has fallen in the trap… they have not evolutioned to a better way of doing thing, but they are back to old edges.
All PM professional need to be vigilant to not be caught in the trap. The final end is to get projects done within specifications on time, so on… and procedures are just facilitating instruments. If they are not facilitating then they should be corrected, but not removed. Removing formal procedures is the final stage of the bureaucracy trap. In order to avoid dealing with Frankenstein, burn the monster! and go back to medieval times. Correcting procedures is the way out, not removing them.
Posted on: January 04, 2016 05:29 PM |
Permalink
Comments (3)
Please login or join to subscribe to this item
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates
New Westminster, British Columbia, Canada
Very Interesting Humberto and I do agree with you. There is a good quote for this for Javier Pascual Salcedo: "Bureaucracy is the art of making the possible impossible."
I appreciate that you used the word bureaucracy. Humans have a tendency to let a word become akin to cussing. Then we find some new word to describe the same thing, rather than addressing the actual problem, which is that people let things get out of control.
Andy Kaufman
Host| People and Projects Podcast
Lake Zurich, Il, USA
One of my favorite hires over the years was a database analyst. He had an often repeated maxim: "Volume screws up everything!"
That is certainly relevant to data, but it also applies to so many other areas. Managing a team of 10 is more difficult than a team of 2. Managing a portfolio of 350 programs and projects is more challenging than 5. Leading an organization with 10 locations around the world is entirely different than having everyone co-located. Growth and expansion is typically good--but the DBA's point is that it often comes at a higher cost than we realize.
Finding a way to optimize while scaling is a continual challenge for leaders. Bureaucracy has gotten a bad name because, too often, we create (as you say) Frankensteins. Too many layers, over-encumbered processes, too little empowerment, competing agendas.
I love the agile emphasis on "just enough".... Just enough process. Just enough oversight. Just enough structure. Just enough review points. Just enough communication. It's a subjective notion, but it's a constant reminder that we need to avoid the bureaucracy trap you nicely talked about in your post.
Thank you for being such a helpful voice in this community, Humberto!
Please Login/Register to leave a comment.