The calendar as kanban

Are you one of those people whose day is driven by the latest email someone has lobbed into your inbox? Do you feel like you’re chronically a half-step slow in managing your work? If so, try using your calendar as a kanban. (For the lean...
Continue Reading

Subscribe to the TimeBack Newsletter

TimeBack Unchained! August 9, 4pm: The Lean Nation Radio Show

I will be a guest on The Lean Nation radio show on August 9 from 4-5pm on 790 AM Talk and Business, hosted by (the always dapper) Karl Wadensten.

We’re going to discuss how lean principles translate to good leadership.  This topic was inspired by a guest post I did for Mark Graban’s Lean Blog, titled “You Don’t Have to be Lean to be Good.”

You can listen to my appearance live on 790AM (Citadel Broadcasting, ABC Affiliate) in Providence, RI.  The show is also globally available via a live audio stream at 790business.com.  I would love to hear your opinions and answer your questions on this topic or others, so feel free to call in to the show.  The call-in number is 401-437-5000 or toll free at 888-345-0790.

Can’t tune in live?  The podcast will be available after the show, so you can have my dulcet tones put you to sleep while you’re sitting on the airport tarmac.

5S to Relax, Part Deux

Kevin Meyer recently connected his own experience using a smaller desk with a Wall Street Journal article on an architect who believes that a lack of visual clutter allows you to relax. Both of their feelings echo what many of my clients say when we clean off their desks and start organizing their information: they can concentrate, they can focus, they can “breathe.”

Now, I’ve been preaching the virtues of 5S for both your workspace and your information for a long time (here, here, and here, for example), but recently I’ve been wondering whether I’ve been pushing that too hard. Jamie Flinchbaugh has written persuasively that reflexively rolling out a 5S program at the beginning of a lean transformation because “it’s always the first step” doesn’t make a lot of sense. He argues that it’s far more important to understand the problem you’re trying to solve, and then choosing the right tool to solve it. 5S might be that tool. Or it might not.

Kevin’s post and the WSJ article reminds me that (for many knowledge workers, at least) one of the most serious problems is the inability to find blocks of uninterrupted time for concentrated thinking. Maintaining focus amidst the maelstrom of distractions and interruptions is incredibly difficult. But there’s no reason to make it any harder than it has to be. A robust 5S program for all the information that washes up on your desk like white collar flotsam and jetsam is a great way to help increase the amount of concentrated work you can do.

As Kevin says, “minimize to achieve the elegance and peacefulness of simplicity.” Or in other words, 5S it.

Leadership vs. Management

I’ve become quite a fan of Bob Sutton’s blog recently. In addition to presenting interesting research that you probably haven’t heard about, he’s irreverent and funny. (No more so than in his post on the “asshole collar.”) So I paid attention when he wrote that

one of the dangers of talking about leadership versus management is that the implication is that leadership is this important high status activity and management is the shit work done by the little people.  My view (and there is plenty of evidence to support it) is that effective management — the work done by the collection of bosses and their followers in an organization, if you will — is probably most crucial to success. After all, they are the people who turn dreams into reality.

This comment brought me back to the examples of lean leadership at Lantech and Group Health that I’ve learned about. In these companies, senior execs — leaders — have standard work that involves regular visits to the gemba and communication with the line workers. Even though they’re responsible for the grand vision and strategy, they also know the nitty gritty of daily work. Sutton says that they realize they have a

deep understanding of the little details required to make [the grand vision] work — or if they don’t, they have the wisdom to surround themselves with people who can offset their weaknesses and who have the courage to argue with them when there is no clear path between their dreams and reality.

Sutton cites Medtronic’s Bill George, Xerox’s Anne Mulcahy, Pixar’s Brad Bird, Steve Jobs, and Francis Ford Coppola as leaders who understand this. (Bill George spent about 75% of his time during his first 9 months on the job watching surgeons put Medtronic devices in patients and talking with doctors and nurses, patients, families, and hospital executives to learn about customers and users of his products.) I don’t know if any of these folks are considered “lean” leaders, but by this definition of leadership, at least, there’s not much difference between being good and being lean. (Something I touched on in this post for Mark Graban’s Lean Blog as well.)

I think that one of the great benefits of the various lean tools is that they help leadership get deep into the weeds. Value stream maps, A3s, and the fundamental principle of “go and see” is all about understanding the details of daily life for front line workers and managers. These tools make management part of leadership.

Information overload vs. filter failure

I’m a big fan of Nathan Zeldes’ blog. Aside from his seminal piece on “Infomania,” he’s a clear-eyed observer of the email hell in which most corporate employees find themselves trapped. Recently, he rebutted Clay Shirky’s argument (here and here) that “It’s not information overload. It’s filter failure.”

Shirky’s maintains that (since Gutenberg at least) there’s always been more information than any individual could possibly process — but it’s not a problem, because as long as reading it all isn’t mandatory, who cares? But Zeldes rejects that argument. As he says,

It is not that there’s a lot of information; it is that there’s a lot more information that we are expected to read than we have time to read it in. It’s about the dissonance between that requirement and our ability to comply with it, and this requirement was not there in Alexandria or in Gutenberg’s Europe: you were free to read only what you wanted to and had time for. This is what has changed, not just the filtering….there is an expectation (express or implied) that you must go through all the mail in your Inbox.

I think Zeldes is exactly correct in this analysis. And to his credit, he points out that along with the obvious reasons for the growth of email (it’s free, easy, and instant), there are powerful cultural reasons as well: CYA, publish or perish, mistrust, escalation, and so on.

Okay, these aren’t exactly Copernican insights here. So what?

Well, as Jamie Flinchbaugh constantly reminds me in regards to A3s, getting the problem statement right is at least half the battle. And I think that the problem statement, “I/We have too much email” isn’t very good. After all, how do you define “too much”?

Instead, I think it’s worth asking questions like “Why is so much communication done via email?” Or, picking up on Zeldes’ point, “Why are we expected to read all that mail?” These questions lead to much more interesting — and fruitful — conversations about corporate culture, service level agreements, allocation of authority, etc.

In an earlier post, I talked about how Peter Drucker viewed an excess of meetings as a sign of a dysfunctional organization. He wrote that

Too many meetings always bespeak poor structure of jobs and the wrong organizational components. . . if people in an organization find themselves in meetings a quarter of their time or more — there is time-wasting malorganization.

Too many meetings signify that work that should be in one job or in one component is spread over several jobs or several components. They signify that responsibility is diffused and information is not addressed to the people that need it.

I wonder if you could say the same thing about too much email. Yes, when you’re collaborating with teams located in different offices around the world email is a incredibly useful communication tool. But lord knows that there are plenty of people, teams, and companies that don’t have that convenient excuse.

The root causes behind our biblical email plague are myriad — and almost certainly don’t involve something we can’t fix, like a vengeful god. Asking questions that reveal the root causes can help you take appropriate countermeasures. It’s a better approach than blaming email on “filter failure,” or meekly accepting the worsening status quo.

The problem with priorities.

Ron Ashkenas posted a thoughtful piece on the problem with priorities a few months ago. He tells a story of the head of a large hospital who asked his direct reports to make an index card for each of the projects they were working on.  One hundred fifty cards (!) later, it became apparent why so few of the projects were moving towards completion — with so many projects drawing on the same resources of time and attention, nothing could get finished. Moreover, these senior managers were reluctant to formally drop any of the projects because they felt that all of them were important.

But as the old saying goes, if everything is a priority, then nothing is. Something is either the priority or it’s not.

This reminded me of something that Merlin Mann once wrote:

Making something a BIG RED TOP TOP BIG HIGHEST #1 PRIORITY changes nothing but text styling. If it were really important, it’d already be done. Period. Think about it.

Example. When my daughter falls down and screams, I don’t ask her to wait while I grab a list to determine which of seven notional levels of “priority” I should assign to her need for instantaneous care and affection. Everything stops, and she gets taken care of. Conversely – and this is really the important part – everything else in the universe can wait.

I’ve written before about the necessity of understanding your “production capacity.” If you had infinite time and infinite resources (energy, money, focus), you wouldn’t really need to worry about your production capacity. You’d just keep working and get everything done. You’d rescue your daughter and analyze last month’s sales figures. No problem.

Unfortunately, you don’t have infinite time and resources. (Or if you did, you wouldn’t be working right now. You’d be on a yacht docked at your own private Caribbean island.) So you have to make choices. You have to choose your priority for the hour or day or week or year.

My wife has gradually been learning this lesson. Recently, she’s been a bit better at saying no, and has been spending a bit more time on her “great work.” Patient care comes first as always — there’s no letup in the number of procedures she’s doing each day — but she’s shelved almost all of her academic work and a significant amount of her administrative work. Equally important, she’s less stressed about the stuff that she’s not doing.

Remember: either your project is the priority or it’s not. Period.

Delegating with a Kanban

A partner in the tax practice of a law firm asked me, “How can I keep better track of the work the associates are doing? And how can I stay on top of the work I’ve delegated to them?”

Tracking work that others are doing is a common problem, particularly in a high-priced law firm, where the clients want answers to their questions at the most inopportune times — like the middle of dinner, or just after you’ve settled into watching Toy Story 1 & 2 with your kids. To be fair, if you’re charging them $800 per hour, you should be ready to answer those questions. However, hounding your team to get you that information — especially when they’re watching Toy Story with their kids — is a sure way to get your firm de-listed from the “100 Best Places To Work.”

So what can you do?

Inspired by Lee Fried at Group Health Cooperative, and by Jim Benson over at Personal Kanban, I realized that the kanban is an ideal answer. (For those readers who don’t know what a kanban is, for the purposes of this post, just think of it as a white board or bulletin board that’s visible in the work area.)

Put each person’s name down the left side of the kanban and create a row for each of them. Put the task they’re assigned in the next column, and the expected completion date next to that. If you want to be fancy, you can even include some symbol that indicates about how far along they are in completing the work. Have another column that holds a simple red/green signal that indicates they’re on track or they’ve fallen behind. And that’s it.

What you’ve created is a simple visual management tool that allows you to quickly see how each person is doing. Here’s an example of what it might look like:

Sample delegation kanban

In this screenshot, I’ve adopted Jim’s approach (and terminology) by breaking work into three buckets: “To Do,” “Doing,” and “Done.” This added information helps provide context for where you are in a larger project.

There’s nothing earth-shaking about this approach, but I think it falls into the sweet spot between something that’s too small for full-blown project management software, and something that’s to big for a one-person task list. Having it prominently posted ensures that the work doesn’t disappear into a computer file. And the red/green status bar enables someone to signal for help without having to schedule a formal meeting.

One very easy way to work faster.

Personal Kanban Traffic JamIt’s a little disappointing, really. I really thought I was being so smart and creative.

I read Pete Abilla’s recent post about Little’s Law, software development, and queue management, and I thought — “Hey! I bet you could apply this concept to argue against multitasking and overloading one’s calendar! Little’s Law proves that if you do that, it will actually take longer to get your work done!”

And then I realized that Pete had beaten me to this flash of insight by, oh, about three years. There it is, in semi-permanent electrons, back in April of 2007:

A common result for multi-taskers is that simultaneous projects or items are spawned.  Multi-threaded is sometimes the analogy here.  But, unlike machines, people have a difficult time completing multi-threaded processes.  The end result is that projects and efforts are not complete, time runs shorter and shorter, and demands continue to pile up.  Think of everything I’ve just described as Work-in-Process (WIP).  So, using Little’s Law above, as WIP grows, then Throughput decreases. Translation: As we multi-task, we start several projects, complete only a few, WIP grows, Cycle Time eventually lengthens, and we are less productive.

(By the way, although this is the money quote, the whole post is worth reading. He’s far more eloquent on Little’s Law than I ever could be. Plus, I can’t figure out how to insert the Greek letter Lambda in a blog post.)

I think that Pete’s point makes a good case for using a tool like a kanban or your calendar to manage the amount of work you take on. If you don’t match your production capacity (which is to say, the limits on your time and attention) with the amount of work you take on, you’ve got a recipe for stress and slower work.

Jim Benson, over at Personal Kanban (where “It’s hip to limit your WIP.”), tells this story beautifully in his “Personal Kanban 101″ Slideshare presentation. The picture above (from that presentation) makes Pete Abilla’s point about Little’s Law visual.

Jim’s point is that the motorcyclist is the last, little, five minute task that you agreed to do. . . but of course, in a completely clogged day, it can’t get done quickly at all. And a kanban (his solution), or rigorous use of the calendar (my solution, so far) is a way to ensure that you don’t get yourself into this situation — where five minute tasks can’t get done, where the cycle time for your work lengthens, where frustration and unfulfilled promises mount.

Okay, so my idea about Little’s Law and multitasking wasn’t original. I stand on the shoulders of giants, and all that. But if it brings a bit more attention to Pete Abilla’s orginal post, so much the better.

Lean and the power of communication.

I attended the LEI’s Lean Healthcare Transformation Summit last week in Orlando and was impressed by all the attendees’ dedication to improvement. The problems with our healthcare system — and the healthcare insurance system — are legion, but seeing the accomplishments of this group gives me some measure of hope that things might actually get better.

Amidst all the value stream maps and photos of 5S initiatives, one thing that really hit me was how communication lies at the heart of so much of lean. From kanbans to value stream maps, from daily huddles to managerial standard work from 5S to A3s, I kept seeing how clear, concise, and consistent communication eliminates waste, creates value, and focuses activity and attention on what’s important. When you think about it, a kanban is a form of communication that tells someone that something needs to be done at a certain time. Value stream maps are a kind of visual communication that helps reduce misunderstandings. Daily huddles are clearly about communication of problems (and solutions), while manager standard work is a way to routinize and clarify communication up, down, and across an organization. 5S is a way to help communicate abnormalities in a process or place. A3s are an elegant and concise method of communicating just about anything. And you can’t go to any lean plant or office without seeing visual management boards that essentially are just forms of communication.

So this got me thinking about the waste of time, effort, and energy that goes into what passes for communication in most organizations. You know — confusing emails with no clear purpose. Voice mails that don’t answer questions, but instead just ask you to “call me back” (and race through the telephone number at the end). Soul-sucking meetings that serve no point except the aggrandizement of the organizer’s ego. Proposals and reports that deforest half of Brazil without telling a coherent story. That’s a colossal amount of waste.

By no means am I diminishing the importance of the lean tools that are so often discussed. But it does make you wonder: what would happen if we spent even just a little time on improving the quality of the communication within and between organizational silos?

Does the internet make you smarter or dumber? Yes.

Friday’s Wall Street Journal ran an interesting feature: side-by-side articles on whether the internet makes you smarter or dumber. Clay Shirky advocated smarter, while Nicholas Carr (who’s in the news for the release of his latest book) argued for dumber. My answer to the question? Yes, it does.

Both authors make compelling arguments for their point, and I think that both arguments are valid. What’s not in question, from my perspective, is that the way we use the internet — as an always on, constant companion for communication, entertainment, and information — can be terribly destructive to our ability to get on with our jobs. And our lives.

I’m not a Luddite by any means. I don’t propose that we go back to the pre-internet world, or even the 56K dial-up modem. The internet is much too valuable an invention for that. (And having just laboriously completed some rudimentary carpentry work without power tools, I’m all in favor of technology.) But it’s important to recognize that there must be a time and place to use the off button. To be unplugged. To be fully present, without distractions. The fact is, as I’ve (and many others have) written about ad nauseum, we’re incapable of multitasking:

When we’re constantly distracted and interrupted, as we tend to be online, our brains are unable to forge the strong and expansive neural connections that give depth and distinctiveness to our thinking. We become mere signal-processing units, quickly shepherding disjointed bits of information into and then out of short-term memory.

And yet I see legions of businesspeople and healthcare workers trying to process complex information (spreadsheets, budgets, medical records, etc.) while allowing themselves to be interrupted by the phone or email, or just as damagingly, by self-inflicted interruptions (Hey, I wonder what the score of the Mets game is…). This can’t be a good thing. I’m not the only one who thinks so, either: one of the most popular features of the word processing program Scrivener is “full screen mode,” which blacks out everything on your computer screen except the document you’re working on. And WriteRoom is a word processing program which has as its only selling point, “distraction-free writing.”

(I’m not dissing these products, by the way. But I do wonder why we need a product to mimic the appearance of being disconnected when we could just, you know, actually disconnect ourselves. Is it so hard to turn off Outlook and Firefox?)

A few years ago I made a vow that when my wife comes home from work, I close my computer. For the most part, I’ve lived up to that promise — and that’s something I’m really, really proud of. I don’t write that to sound holier-than-thou. (You know, “Look how great I am! I can turn off my email!”) I write it because I know how tough it is to unplug the ethernet cable. I also know that as a result, I talk to my wife a lot more than I used to — and that’s a really good thing.

All this is to say that the question isn’t whether the internet makes you dumber or smarter. It’s whether you can unplug and provide yourself with the time and quiet to focus on whatever it is that’s really important.

The downside of automation

Nathan Zeldes, former Intel engineer and author of the seminal paper on Infomania, argues that IT tools can reduce productivity. He doesn’t suggest that computers and information technology, writ large, is a bad thing (he’s an Intel guy, after all), but rather that any specific IT tool might not be good for the organization.

He describes a typical situation:

I’ve seen many an MD cursing under their breath while struggling to enter my examination data and conclusions into a new computerized system. Instead of scribbling a few illegible lines on paper and chucking it into a manila file, to be processed later by an assistant, they had to use an unfamiliar and possibly ill-designed piece of technology, and it took them much longer. And because of this they had less time to apply their real value added, their precious ability to cure the sick.

Zeldes isn’t advocating a return to the 50s, complete with pink collars, steno pads, and 3-martini lunches. (Although, who knows – he might be a fan of Mad Men.) He realizes that the benefits of IT are enormous. But I think he raises an interesting issue: the downside of IT systems and automation.

Zeldes says that usually technology

gets deployed with little attention to the wider implications. Thus, if a tool enables the manager or engineer to do the admin’s work, the temptation to remove the admin and become “lean” and “efficient” is great. But the fact is, an admin is paid much less than a highly skilled engineer or manager (or surgeon); and the latter only has so many hours in a day, which may be better used for doing higher level tasks. This is not to say that we can’t streamline some of the work by having it done by the manager; the question is which part, and to what extent. As is often the case, it’s pretty much about identifying the correct balance.

Toyota is famous for being very slow to introduce new, expensive, technology: they never want to automate a broken process. That slowness to add technology also enables the company to understand how it will affect the value stream, and whether that’s wise.

When I see companies leaping at technological solutions for time and attention management, I have a feeling that they’re in for a big disappointment. Buying a piece of software isn’t a cure for poor work flow any more than buying a bigger pair of pants is a cure for your weight problem. Understanding the root cause(s), developing multiple countermeasures, and going through several PDCA cycles is a more reliable route to success.