Skip to main content

Are today’s organizations creating hardworking Idiots?

Update on December 2011
----------------
The links provided don't seem to work, but the message is still valid.
----------------

I recently discovered this site www.slowleadership.com. It has got good articles related to, and on leadership. I like the quality of the articles here and have subscribed to the site in my RSS reader.

Out of the many articles in the site, i want to point out one article to start with. It is ' Are today’s organizations creating hardworking Idiots? The premise of the article is that organizations today are creating lot of yes men , through the way they operate and their focus.

I believe that the article is hard hitting and makes the serious reader, a bit un comfortable too. From my more than 10 years of work experience, i confidently say that there is lot of truth in what is said.

I have given below a few quotes from the article.

The dumbing down of organizations isn’t caused by poor educational standards or faulty recruitment. It’s due mostly to the crazy pace that is set, and the obsessive focus on the most obvious, rigidly short-term objectives. The result is a sharp increase in hardworking idiots: people who are coerced into long hours and constant busyness, while being systematically forced to act like idiots by the culture around them.

Don’t ask questions. Don’t cause problems by thinking, or waste time on coming up with new ideas. Don’t think about the future, or try to anticipate problems before they arise. Just keep at it, do exactly what is expected of you, and always get the most done in the least amount of time and at the lowest cost.

I think that even a fairly cursory look around most organizations today would confirm the accuracy of this observation. Consider all the time wasted in unnecessary meetings. The obsessive emphasis on staying in touch, regardless of need. The torrents of e-mails, most of which are simply copies of documents of no direct relevance to the people to whom they are sent. The constant collecting of data for no clear reason. Management by numbers and motivation by numerically-based performance measures. Trust replaced by obsessive control and leadership by forced ranking of subordinates against vague criteria determined by committees with no idea of the specific circumstances.
You do not need ethical insight or human understanding to operate a machine, and machines are how many of today’s leaders see their organization: machines for making quick profits, not civilized communities of people working together to a common end. We can only hope some organizations at least see the error of their ways before the hardworking idiot becomes the commonest creature in the hierarchy.

If you are a leader or a manager responsible for a team of people and care about them, i ask you to read the complete article here.

Comments

Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …