From ‘Taylorism’ to ‘Druckerism’

From ‘Taylorism’ to ‘Druckerism’

It is an undisputed fact that Frederick Taylor’s work, ‘Principles of Scientific Management’ was path breaking and that it forms the basis of most of Modern Management’s theories. What is indeed creditable is that these Principles are still relevant, at least in manufacturing and engineering type of work, even a century after they were published.

The question which needs to be asked is how relevant are his principles for knowledge work like software development. This is because knowledge work is fundamentally quite different from manufacturing and engineering type of work, in the following ways:

  • It is created in the mind of a person and not on a machine. Machine and technology are just tools to reflect what the mind has conjured
  • It is not repetitive in nature and needs creativity, as each piece of work is Today many are beginning to see software development as a ‘Craft’
  • Output may not have any correlation with Outcome. A 100 page book may be more valuable than a 200 page book
  • Doing it in an iterative way leads to a better outcome. It is quite unlikely that a blogger will write the blog which is fully satisfactory in the first draft itself.

Taylor’s Principles appear to be based on the following beliefs, whose relevance for knowledge work is highly questionable.

  1. Money is an excellent motivator

While money is important for every person regardless of the type of work, it is now fairly well established that knowledge workers excel when they are Intrinsically motivated. According to Daniel Pink the 3 variables which influence Intrinsic Motivation are Autonomy, Mastery and Purpose. (reference https://www.ted.com/talks/dan_pink_on_motivation?language=en). Money needs to be a factor which is ‘taken off the table’, for the Intrinsic motivators to work. But once it is off the table, it ceases it’s importance as a motivator.

  1. Efficiency is the most important outcome to aim at

Knowledge work, by definition, is not repetitive so how does one measure efficiency of work where each output is unique? While there is definitely room to enhance efficiency even in knowledge work, what efficiency and productivity standards can be set for such type of work? What is most important as an Outcome in knowledge work is Value to the intended audience.

  1. Managers should ‘Think’ and Workers should ‘Do’

The implicit assumption behind this belief appears to be that work is based on physical activity, and that thinking will distract the worker from doing the physical activity in the most efficient way possible. In knowledge work, given that it happens in the mind, the Thinker and Doer needs to be the same person, i.e. someone cannot think for someone else

  1. Workers need to be supervised

Supervision may  be needed when production needs to happen at maximum efficiency and when adherence to rules and working methods is critical. How can one Supervise someone who is thinking or having a discussion? Is it even necessary? It’s quite appalling to hear of organizations which track how much time an employee has been away from the computer. Is the expectation that the employee should be typing the code all the time? Sure, forecasts are important for knowledge work, and these should be provided. But is Supervision needed once the forecast is available?

  1. Rules, based on scientific studies, are needed for performing the job most optimally

While rules and scientific methods for optimal working ways may help in repetitive type of work, how does one decide what is the optimal way to think creatively? For work which is iterative in nature, i.e. the state of the output cannot be exactly forecast/visualized upfront, the question to ask is whether stringent rules and methods make any sense.

So why are many organizations still using Taylorism to deal with knowledge work? One of the key factors appears to be that the curriculum taught in both Engineering and Business schools is highly skewed towards Taylorism, and not enough towards ‘Druckerism’. Another reason could be that Managers are resisting to change as they (mistakenly) fear loss of control. The third could simply be fear of the unknown.

Peter Drucker, another brilliant mind in the field of Management, was a pioneer in recognizing not only that knowledge will gain in prominence significantly, but also it needs to be managed quite differently. Rick Wartzman, in an article published in HBR, (https://hbr.org/2014/10/what-peter-drucker-knew-about-2020) has said “Sadly, judging from the way most of our institutions are run, we are still struggling to catch up with the reality Drucker foresaw”.

Drucker outlined six aspects to more effectively run an organization of knowledge workers, which are mentioned in the HBR article stated above. It is not surprising that these resonate very closely with Agile Values and Principles.

Moving from ‘Taylorism’ to ‘Druckerism’ is long overdue, both in academics and in industry, at least for knowledge work.

Keen to know your thoughts/comments.

Narayana Rao KVSS

Professor (Retired), NITIE - Now IIM Mumbai - Offering FREE IE ONLINE Course Notes

2 年

March - F.W. Taylor (Birthday - 20 March 1856) Month of Industrial Engineering and Productivity Management. https://nraoiekc.blogspot.com/2023/03/march-fw-taylor-month-of-industrial.html

回复

I enjoyed this. As much as we've moved to knowledge based society our org structures are largely the same. It's disappointing. Was 2020 too optimistic?

Seshagiri Sriram

IT Architect | Consultant | Trainer

9 年

Hi Sunil, This is a nice article. External cultural biases also play a role in degree of adoption of one over another. Rigid hierarchical societies would prefer "Taylorism" . The influence of Taylorism can still be felt in schools where test scores are highly emphasized. The child being the father of the man - this implies that a large number of people entering the workforce cannot make the paradigm shift easily.

Yuri Tan, P.Eng

Avionics Software Design Assurance and Process Assurance Engineer

9 年

1. Money is an excellent motivator: Money is but one motivator but perhaps a greater motivator for the knowledge worker is the freedom to work when and where the urge strikes. For the manager to allow the worker to work outside the office and outside of office hours means trusting that the worker will get work done. 2. Efficiency is the most important outcome: Efficiency is trying to get the most output for the least input. But how do you quantify knowledge and ideas? Is there a measurable unit of knowledge or ideas? Effectiveness is probably the better outcome: Is the outcome useful? 3. Managers should ‘Think’ and Workers should ‘Do’: Workers must be allowed to think, when and where the urge strikes. You cannot command someone to think because the mind cannot be turned on and off like a light switch. 4. Workers need to be supervised: If you agree with the definition of "manage and direct" or "command and control", then you cannot agree that knowledge workers need to be supervised; you cannot command a worker to start or stop thinking. Knowledge workers may be moderated to ensure that ideas are aimed toward a solution for a given problem. It has been said that managing software developers is analogous to herding cats. 5. Rules, based on scientific studies, are needed for performing the job most optimally: The traditional command and control method of management will not work with knowledge workers; some other management methodology must be tried.

要查看或添加评论,请登录

Sunil Mundra的更多文章

  • The power of a small gesture

    The power of a small gesture

    Today I got the opportunity to give a talk to the students doing their Master’s degree at my Alma Mater, viz. School of…

    9 条评论
  • Distributed Development Enablers Part 2: Process

    Distributed Development Enablers Part 2: Process

    In this series of articles on Distributed Development, this is the third article. The first article was about…

  • Distributed Development Enablers Part 1: People

    Distributed Development Enablers Part 1: People

    Having examined the Challenges of Distributed Development (https://www.linkedin.

    6 条评论
  • Challenges Faced in Distributed Development

    Challenges Faced in Distributed Development

    By definition, Distributed Development is difficult due to the ‘tyranny of distance’. In fact, in the early days of…

    14 条评论
  • The Implicit Agile Principles

    The Implicit Agile Principles

    The essence of Agile is supposed to be brought out by the Manifesto and 12 principles. However, there are few…

    13 条评论
  • Be Like Salt

    Be Like Salt

    What does salt have to do with consulting? Please read my blog, published by ThoughtWorks, to find out. https://www.

    11 条评论
  • Where is code created?

    Where is code created?

    Are you surprised by this question? You are thinking the answer is so obvious, isn’t it? Of course, the code is created…

    14 条评论
  • Maximizing Benefits from Agile Adoption/Transformation

    Maximizing Benefits from Agile Adoption/Transformation

    Given that being Agile has a direct correlation with business benefits, viz. Time to Market, Efficiency, Quality and…

    19 条评论
  • Doing vs. Being Agile

    Doing vs. Being Agile

    Many teams believe they are Agile because they are following the prescribed Agile practices. E.

    43 条评论

社区洞察

其他会员也浏览了