Knowledge-Worker Productivity: The Biggest Challenge
Traditional approaches to improving productivity may not be applicable to knowledge workers.

Knowledge-Worker Productivity: The Biggest Challenge

This is the latest issue of my newsletter. Each week I cover the latest research and perspectives on developer productivity.


This week I’m summarizing Peter Drucker’s?Knowledge-Worker Productivity: The Biggest Challenge, a paper published in 1999 that is just as relevant today. In this paper, Drucker describes the key distinctions between the productivity of manual workers and that of knowledge workers. In doing so, he shows how organizations must move beyond past approaches to improving productivity.?

“The most important contribution of management in the 20th century was the fifty-fold increase in the productivity of the manual worker in manufacturing. The most important contribution management needs to make in the 21st century is similarly to increase the productivity of knowledge work and knowledge workers. The most valuable assets of a 20th-century company was its production equipment. The most valuable asset of a 21st-century institution (whether business or non-business) will be its knowledge workers and their productivity.”

My summary of the paper

To set the stage, Drucker gives an overview of the key advancements made to productivity throughout history:?

  • Throughout history there have been several advances in what we today call “productivity” (the term itself is around fifty years old). There were advances to what was called “capital”—referring to new methods and new technologies—and advances to “labor”—the productivity of the worker. However, throughout history it has been understood that improving productivity was only achieved by working harder or working longer hours.?
  • Prominent thinkers during this time showed that?there is no such thing as “skill” in manual work: there is only simple, repetitive motions.?What makes manual workers more productive is the way these motions are put together, organized, and executed. Every method during the past hundred years that has raised manual worker productivity has been based on these principles.?

Drucker says that “the central challenge is no longer to make manual work more productive—after all, we know how to do it. The central challenge will be to make knowledge workers more productive.”?

What distinguishes knowledge worker productivity?

Drucker outlines the major factors that distinguish knowledge worker productivity. Each of the following requirements is almost the exact opposite of what is needed to increase the productivity of the manual worker.?

1. Knowledge worker productivity demands that we ask the question: “What is the task?”

None of the people who work on manual-worker productivity ever asked, “What is the manual worker supposed to do?” Their only question was: “How does the manual worker best do the job?”

For knowledge work, the key question is: what is the task? In a hospital, it is the nurse’s decision whether to spend time at the patient's bed or to spend time filling out papers. Engineers are constantly being pulled from their task to attend meetings or help others. In sales, it is the sales person’s job to determine whether to spend time working on their pitch, providing supporting materials to customers, or reaching out to new prospects. All of that is to say that first requirement in tackling knowledge work is to find out what task needs to be done, and only knowledge workers themselves can answer that question. Therefore, improving productivity begins with knowledge workers asking themselves?What is your task? What should you be expected to contribute??What hampers you in doing your task, and should that be eliminated??

Nurses in a major hospital were asked these questions. They were sharply divided as to what their task was, with one group saying “patient care” and another saying “satisfying the physicians.” However, they were in complete agreement on the things that made them unproductive. They called them “chores”—paperwork, arranging flowers, answering the phone calls of patients’ relatives, answering the patients’ bells, and so on. All—or nearly all—of these could be turned over to a non-nurse floor clerk, paid a fraction of a nurse’s pay. The productivity of the nurses on the floor immediately more than doubled, as measured by the time nurses spent at the patients’ beds. Patient satisfaction more than doubled and turnover of nurses (which had been catastrophically high) almost disappeared—all within four months.”

2. Knowledge workers are responsible for their own contribution

It is the knowledge worker’s decision what they should be held accountable for in terms of quality and quantity with respect to time and cost. Knowledge workers have to have autonomy, and that entails responsibility. Additionally, continuous innovation and learning have to be built into the knowledge workers’ job.

3.?Quality matters as much as quantity in knowledge work

Quality matters in manual work, of course, as there is usually a certain minimum standard of quality. In knowledge work, quality is not a minimum or restraint: “Quality is the essence of the output.” Productivity of knowledge work therefore has to aim first at obtaining quality—and not minimum quality but optimum if not maximum quality.

“Productivity of the knowledge worker is not—at least not primarily—a matter of the quantity of output. Quality is at least as important.”

This means we have to learn to?define quality, which Drucker suggests can be achieved by first defining the task. An organization that emphasizes reducing failures will define their tasks differently than one that emphasizes producing breakthroughs, and thus they will also define quality differently.?

4. Knowledge worker productivity requires that the knowledge worker is both seen and treated as an “asset” rather than a ”cost.”?

Another key difference between the productivity of knowledge workers and that of manual workers is how they are considered by businesses: manual workers are seen as a?cost, and knowledge workers must be considered an?asset.

As Drucker puts it: employees who do manual work do not own the means of production. They may have a lot of valuable experience, but that experience is valuable only at the place where they work. Knowledge workers, however, own the means of production. “That knowledge between their ears is a totally portable and enormous capital asset.”?

What about knowledge workers who also do manual work?

A very large number of knowledge workers do both knowledge work and manual work. Drucker calls them “technologists.” This group includes people who apply knowledge of the highest order. Drucker gives an example of a surgeon:

“Surgeons preparing for an operation to correct a brain aneurysm before it produces a lethal brain hemorrhage, spend hours in diagnosis before they cut—and that requires specialized knowledge of the highest order. Again, during the surgery, an unexpected complication may occur which calls for theoretical knowledge and judgment, both of the very highest order. However, the surgery itself is manual work—and manual work consisting of repetitive, manual operations in which the emphasis is on speed, accuracy, and uniformity. These operations are studied, organized, learned, and practiced exactly like any manual work.”

Making this group productive requires treating them as knowledge workers, which includes:?

  • Asking the question “What is the task?”—the key question in making every knowledge worker more productive.?
  • Giving individuals full responsibility for completing the task, which includes delivering quality. This requires knowledge first, and then the manual part of the job can be completed.

“Above all, technologists have to be treated as knowledge workers. No matter how important the manual part of their work, the focus has to be on making the technologist knowledgeable, responsible, and productive as a knowledge worker.”

The final section of the paper calls for more work to understand how to measure productivity. Drucker concludes that an organization’s ability to survive will increasingly depend on their comparative advantage in making the knowledge worker more productive.?



That’s it for this week! I'd love to know your thoughts in the comments below.?You can also subscribe to this newsletter on?LinkedIn?or?Substack.



P.S.?Since the release of DevEx paper, many people have asked me for advice on how to design and run effective DevEx surveys.?This guide?by DX is a great resource.?

Pramod Verma

Senior Manager @ Steel Authority of India Limited

3 个月

Thanks for your insights. Knowledge worker's productivity can be measured by the results due to his/her decisions/actions. In a team environment where each other's work impact the overall result, proper mapping needs to be done for everyone's contribution in terms of actions/decision. In knowledge work any seemingly insignificant action makes a lot of difference, so a proper weightage needs to be given to it , because such action may come after a lot of thought and study and person's background.

回复
Paulo André

CTO at Resquared (YC W21)

1 年

Prescient. One of my favorite papers ever. Glad you’re covering it, Abi!

Paul Salmon

Agile Coach - Ways of Working at ASB Bank

1 年

Peter Drucker coined the term "knowledge work" in 1959 and this 1999 paper on knowledge worker productivity is unfortunately still sorely needed today. Often knowledge workers are still treated as production workers with a focus on quantity delivered over impact / value / quality delivered. An example I like is that producing 10% more PowerPoint presentations in a month in not necessarily a good thing.

Dimitar Bakardzhiev

Efficient Product Development

1 年

The quote regarding 'skill' needs correcting. The accurate statement is:"...They all celebrated “skill.” Taylor showed that in manual work there is no such thing. There are only simple, repetitive motions. What makes them more productive is knowledge, that is, the way the simple, unskilled motions are put together, organized, and executed. " The key word here is 'knowledge,' particularly the knowledge workers lacked before starting a task—the knowledge they needed to gather to successfully complete it. This distinguishes 'manual' workers from 'knowledge' workers. For manual workers, much of the required knowledge is built into the machines they operate and the detailed procedures they follow. Conversely, knowledge workers need to engage in extensive knowledge acquisition as their tasks often demand a higher degree of problem-solving, and innovation. Have you ever considered a software project as a universe of undiscovered knowledge? The knowledge can be broadly categorized into two types: - WHAT needs to be done - HOW to accomplish the WHAT. Software development isn't just about coding. It's a knowledge quest, a journey through an unknown universe where each discovered information bit brings you closer to your destination.

Jorge Fernández Rodríguez

Senior Software Engineer interested in DevEx, helping others grow, Software Architecture, team and org performance and dynamics. Motivated to collaborate in the fight against climate change, occasional article writer

1 年

Several times I was amazed of somebody delivering so much work at fast pace. after some time, teams having to spend a lot of time rework the huge mess... In very few specific occasions can that be worth it

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

Abi Noda的更多文章

  • Backstage is dominating the developer portal market

    Backstage is dominating the developer portal market

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    30 条评论
  • Attending an academic research conference

    Attending an academic research conference

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    1 条评论
  • Accelerating engineering velocity at Block

    Accelerating engineering velocity at Block

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    4 条评论
  • Rolling out developer productivity metrics

    Rolling out developer productivity metrics

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    4 条评论
  • Software Quality

    Software Quality

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    8 条评论
  • Measuring developer productivity: A clear-eyed view

    Measuring developer productivity: A clear-eyed view

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    3 条评论
  • Getting exec buy-in for developer productivity initiatives

    Getting exec buy-in for developer productivity initiatives

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    4 条评论
  • The best of engineering enablement in 2024

    The best of engineering enablement in 2024

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    3 条评论
  • 2024 benchmarks for the DX Core 4

    2024 benchmarks for the DX Core 4

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    8 条评论
  • Introducing the DX Core 4

    Introducing the DX Core 4

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    15 条评论

社区洞察

其他会员也浏览了