Anticipating Absence: Why

The Coronavirus Pandemic is now officially frightening. It threatens us all, to varying degrees, with sickness and loss. Generally, the threat to knowledge workers — personally — isn't as acute as is the threat to, say, first responders, leisure industry workers, or those whose employers must close or curtail operations. Still, disruptions in knowledge work will likely have widespread and costly effects for years to come. And all of us will feel those effects.

A significant and yet manageable part of the problem arises from pandemic-induced absences of knowledge workers. Knowledge workers include engineers, scientists, designers, programmers, physicians, pharmacists, architects, accountants, attorneys, paralegals, academics, and any other workers who are required to "think for a living."

When knowledge workers fall ill, their work is interrupted. In some cases, that interruption can be very costly to society financially. But those interruptions can also degrade the Earth's environment, cause unnecessary injuries, and cost lives. We can limit these effects by anticipating absences, and modifying the way we conduct knowledge work during pandemics.

In this post I'll Interruptions in knowledge work can
have very serious effects on the
health of the planet, and the health
of people who depend on the products
knowledge workers producesuggest how interruptions in knowledge work can have very serious effects on the health of the planet, and the health of people who depend on the products knowledge workers produce. And I'll survey some reasons why knowledge work is so difficult to defend against pandemic disruptions. In the next post I'll suggest a strategy for limiting these disruptions, and therefore limiting their effects.

The consequences of knowledge work disruptions

Consider items as critical as the computers found in modern automobile or truck engine compartments. These computers run software. And that software, like all software from time to time, has defects commonly called "bugs." Some bugs affect the vehicle's operating efficiency. And some bugs are much more critical, affecting, for example, the ability of the vehicle to stop without locking its brakes. Bugs that affect vehicle efficiency cause unnecessarily high fuel consumption, which can degrade the Earth's environment unnecessarily. Other bugs, though extremely rare, are acutely safety-critical, and present very real risk of injury or loss of life.

Repairing most bugs requires the attention of people — knowledge workers who might be software engineers, testers, or project managers, to name just a few. And in this pandemic, people get sick. Some of them recover quickly. Some might be unable to return to work for weeks or months. Some might not return at all. Some might not survive. We can anticipate these absences, not person-by-person, but statistically speaking. Absences will happen. And when absences happen, work is disrupted. Those disruptions delay the work of knowledge workers.

In our example of automotive control software, delaying the repair of bugs that limit efficiency causes a delay in reduction of fuel consumption. Delays in repair of a safety-critical defect can cost lives.

Repairing automotive control software is just one of many tasks knowledge workers perform. We can probably estimate the effects of, say, 5% of the knowledge workforce missing a month of work in the next year. I haven't done that, but the potential effects are frightening.

Why knowledge work is so vulnerable to disruption

In general, replacing workers who fall ill is often a matter of finding enough people with the necessary skills and experience. That task can become difficult when demand for qualified people is high. We're already seeing this in some occupations, such as nurses or respiratory therapists. Shortage of qualified people is a serious problem, and for knowledge workers, it's just the beginning of the trouble.

Knowledge workers are a bit different. When a new person takes over for a knowledge worker who has fallen ill, that new person must determine the current state of the work underway. Skill and experience do help, but they are not enough. Determining the current state of that work might be difficult indeed.

For example, suppose the work underway is a re-design of a troubled subsystem of our automotive software. And suppose that the person who has fallen ill is the lead architect of that effort. I'll call her Alicia. We might try to find a replacement for Alicia, but unless she has left behind copious notes about vision, intentions, and discarded approaches, her replacement might have difficulty replicating what Alicia had in mind. And if Alicia has been intubated and cannot speak, communicating with her will be slow and difficult.

In many of these situations, the wisest course is to just halt the effort until the absent individuals recover. Halts are indeed disruptive, but the alternative can be worse. If we don't halt the work, the risk is that Alicia's replacement might not be able to determine what Alicia had in mind. If he or she cannot do so, and pushes forward anyway, the end result might lack the coherence and elegance that are necessary for a reliable, maintainable, extensible product. The consequences can be severe and they can last for years.

Replacing a knowledge worker, even temporarily, is unlikely to go well unless the replacement as access to detailed knowledge of the state of the work. In my next post, I'll suggest a strategy and several tactics for capturing that knowledge.   Next issue in this series   Top    Next Issue

Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Project Management:

Nine Positive Indicators of Negative Progress

Project status reports rarely acknowledge negative progress until after it becomes undeniable. But projects do sometimes move backwards, outside of our awareness. What are the warning signs that negative progress might be underway?

Backtracking in Incremental Problem Solving

Incremental problem solving is fashionable these days. Whether called evolutionary, incremental, or iterative, the approach entails unique risks. Managing those risks sometimes requires counterintuitive action.

How to Make Good Guesses: Strategy

Making good guesses — guessing right — is often regarded as a talent that cannot be taught. Like most things, it probably does take talent to be among the first rank of those who make conjectures. But being in the second rank is pretty good, too, and we can learn how to do that.

Guidelines for Sharing "Resources"

Often, team members belong to several different teams. The leaders of teams whose members have divided responsibilities must sometimes contend with each other for the efforts and energies of the people they share. Here are some suggestions for sharing people effectively.

Checklists: Conventional or Auditable

Checklists help us remember the steps of complicated procedures, and the order in which we must execute them. The simplest form is the conventional checklist. But when we need a record of what we've done, we need an auditable checklist.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info