(Note: a modified version of this article first appeared in the Harvard Business Review. You can read that version, with more links to related articles, here.)

————————————————————————————————————————————————————

Leaders in organizations are always seeking to improve employee productivity (including their own). All too often, that quest goes no further than time management training provided by the HR department. Those classes cover the pros and cons of Inbox Zero, the Pomodoro technique, the Eisenhower matrixGetting Things Done, and countless other approaches that tantalize us with visions of the promised land of peak productivity. Given that people are still overwhelmed by work, buried in email, and unable to focus on critical priorities, it’s safe to say that these productivity hacks don’t hack it. 

The problem isn’t with the intrinsic logic of any of these approaches. It’s that they fail to account for the simple fact that most people don’t work in isolation. They work in complex organizations defined by interdependencies among people—and it’s these interdependencies that have the greatest effect on personal productivity. You can be an email ninja, but with the explosion of email (not to mention instant messages, Twitter direct messages, Slack messages, and countless other communication tools), you’ll never be fast enough to deal with all the incoming communication. Similarly, your personal urgent/important Eisenhower categories fall apart when the CEO asks you to do stop what you’re doing and handle something right now. 

As legendary statistician and management consultant W. Edwards Deming argued in his book Out of the Crisis, 94% of most problems and possibilities for improvement belong to the system, not the individual. I would argue that most productivity improvements belong there as well. Personal productivity systems are certainly useful, but the most effective antidote to low productivity and inefficiency must be implemented at the system level, not the individual level. 

Here are four countermeasures that will help reduce the systemic load on personal productivity:

1. Tier your huddles: Many highly productive organizations have instituted a system of tiered daily huddles, with a clear escalation sequence for all problems. The first huddle consisting of front line workers begins at the start of the workday. The next huddle, consisting of supervisors, follows 30 minutes later. Managers meet 30 minutes after that, followed by directors, VPs, and finally the executive team. Problems are addressed at the lowest possible level. If a decision can’t be reached, the issue is escalated to the next level. This system improves the linkage between the C-suite and the front lines; it accelerates decision making; and perhaps most importantly, it improves productivity by reducing the number of scattershot emails about a variety of problems. 

2. Make work visible: Most of the work in an office environment is invisible—it’s buried in people’s computers or their heads. As a result, it’s difficult to know what people are working on or whether they’re overloaded and unable to take on more tasks. Physical or virtual task boards (such as Trello, Asana, Airtable, Zenkit, etc.), where every task is represented by a card specifying who is handling it (and its status) enables a more equitable distribution of work. It also eliminates both countless status check emails and the need to cover that topic in meetings. The principle investigator of a medical research lab I worked with instituted just such a system, and found that work got done faster and with dramatically less effort. 

In a related fashion, making downtime visible is equally helpful. In working with the Boston Consulting Group, Harvard’s Leslie Perlow found that implementing “predictable time off” (i.e., afternoons or evenings totally disconnected from work and wireless devices, agreed-upon email blackout times, or uninterrupted work blocks) led to greater job satisfaction and better work-life balance without compromising client service. In this case, “predictability” serves the same purpose as “visibility”—it allows workers to see what colleagues are doing, and to react accordingly. 

3. Define the “bat signal”: Batman fans will remember that Commissioner Gordon summoned Batman with the image of a bat projected in the night sky. The bat signal was reserved for times of crisis (as when the Joker was on the loose), not when a scofflaw failed to pay a parking ticket. As Marshall McLuhan famously said, “the medium is the message.” Unfortunately, most organizations don’t have a similar way of indicating an issue is a true emergency. With no agreement on what communication medium to use, workers are forced to check all digital messaging channels to ensure that nothing slips through the cracks. That’s toxic to productivity. Companies can make work easier for people if they specified channels for urgent and non-urgent issues. 

A medical device manufacturer I worked with set up the following communication protocol to clarify what tool to use in each situation. The benefit was dramatic, as they were liberated from the need to check all incoming emails for urgent issues. They could focus on work requiring deep, uninterrupted thought, secure in the knowledge that they only needed to pay attention to text messages or phone calls. Note that it’s not important what communication protocol they chose; it’s simply important that they had a system. 

 
 

4. Align responsibility with authority: Workers are often made responsible for tasks but aren’t given the authority to deliver results. This misalignment leads to frustration, stress, and overburden. For example, at a $500M footwear company I worked with, the founder and CEO—long removed from his role in product development—decided that he didn’t like a particular style his product team had designed. He diverted a container that was en route to the US with $400,000 worth of shoes to Africa, where he unloaded everything at a loss. The VP of product development was not only demoralized, he had to scramble at the last minute to adjust for the CEO’s decision. The rule is simple: if an employee is responsible for an outcome, she should have the authority to make the necessary decisions, without being forced into an endless string of emails, meetings, or presentations. 

WL Gore’s “lattice” structure of management is an excellent example of an organization that has implemented this idea. The $3 billion company broadly distributes leadership responsibility throughout the organization, allowing employees to make “above the waterline” (i.e., low-risk) decisions on their own, and only requiring approvals for “below the waterline” (high-risk) decisions. While it might be difficult for another company to copy Gore’s management model, it’s an example of the kind of thinking that can improve individual—and organizational—productivity.  

The pursuit of individual productivity healthy and worthwhile. However, unless you work independently outside of an organization, the benefits of most productivity tricks will be limited. To make a real impact on individual performance, you have to work at the system level. 

1 Comment