It’s New Years again and time to take stock of things in our lives. As we know, the two rules of Personal Kanban are to Visualize Your Work and Limit Your Work-In-Progress (WIP).One of the most important factors in limiting or controlling our WIP is understanding our work - this includes appreciating our work, when we’ve completed it, and what we did to complete it.2014 has been a pretty tough year for me personally and when I look back on the last 12 months I tend to view it in my own pessimism bias.But Timehop, an app I have on my Galaxy Tab, keeps thwarting my pessimism and it’s doing it by confronting me with facts. Simply confronting me with what actually happened one, two, three, four, and five years ago. Timehop is an automated long-range Retrospective.Right now it is nearly exactly one year since I stood in my office in Seattle and drew the image above. See? That’s right now.If you would have asked me, I would have said that was at least two years ago. It’s significant because it means that those drawings led to the Modus Cooperandi Problem Solving System, about a dozen Lunch&Learns where we taught customers the process, and a great partnership with Riot Games to create a complete version of it.When we have sour notes, we tend to allow those notes to overwhelm our interpretation of the entire song. We can have one long very pleasant event and then something happens at the end and we say, “That just ruined the whole thing for me.” I was allowing this last year to be painted with a broad brush because I was focused on a few particularly painful episodes.Timehop, here, served as my visual control, sampling my social media past and showing me what I have actually been doing. What other visual controls are you employing beyond your Personal Kanban to keep track of the good work you’ve done?
Getting Beyond Done–When to Archive
“When do I remove tickets from the DONE column?”The short answer is, every week or so, try to have a short retrospective with your team or alone (if you are working by yourself). When you have the meeting, review what’s happened and archive as you do.Some of the tasks in your DONE column will spark introspection, some won’t. (Hopefully you don’t have to ponder all your work).As you discuss the tasks, you can move them into your ARCHIVE where you store completed tasks. Or, if you are so inclined, you can throw them away.In the video, the ARCHIVE is part of the software. With a physical board you can have your archive be a file folder or a shoebox.
The Retrospective Column
When we make our work and our process explicit, and we do retrospectives, it makes sense to have a retrospective column in our Personal Kanban. The thought here is fairly simple: at the beginning of each day move tasks from Complete into Retrospective. Then, at the end of the week (or whenever you wish) take a look at the tasks in the Retrospective column. They will remind you what you did over the retrospective period.
This is also handy if you need to do your timesheets every week and want to actually remember what you accomplished.
Am I Productive, Efficient, or Effective?
Productivity: having the power to produceEfficiency: the ratio of the output to the input of any systemEffectiveness: being able to bring about a desired result
Personal Kanban is considered a Productivity tool, because it gives us the power to produce more. It is likewise said to increase Efficiency by limiting WIP and increasing focus which means we expend less energy to affect results. This in turn boosts our Effectiveness by providing the information necessary to make better decisions and act on them.Often people have bursts of productivity, efficiency, or effectiveness – but because they aren’t paying attention to what they're doing, these events are sometimes dismissed as happy accidents. Personal Kanban makes your work explicit, meaning it constantly shows you what you are doing and what you could be doing. This helps you interpret your options and prioritize you tasks based on current conditions. Personal Kanban also lets us balance productivity, efficiency, and effectiveness, and turn them into three parts of the same machine.Individually, bursts look like this:
Bursts of productivity – You get a lot done, but is it the right stuff?
Bursts of efficiency – Work is easily done, but is it focused for maximum effect?
Bursts of effectiveness – The right work is done at the right time … this time. Is this process repeatable?
I call these bursts “hero” events. Over time, things get screwed up and you have to call in a “hero” to fix them quickly. That hero may be you, a temp worker, a consultant, or a friend. But you identify a need so late in the game that you need to work above and beyond to complete the task at hand.What’s funny is that after these hero events, we feel good. And because we feel good, we think, “That was awesome!” and we ascribe the event to something exceptional. Something that just couldn’t possibly happen every day.During a recent project in Washington, D.C., I worked alongside members of the Intelligence Community. More than one of them told me that people in the IC who allegedly had cushy desk jobs inside the Beltway, routinely volunteered for live fire assignments.These people specifically volunteered to be in harm’s way.Why? Because it was a period of sustained productivity, efficiency, and effectiveness. People did not have the "luxury" to relentlessly and constantly prioritize. In the field there is no choice but to constantly re-evaluate conditions and re-prioritize actions. Because picking the most important task was the only way to survive, the only way to complete the mission.There was a mission. There was survival. And those two conjoined drivers created a great deal of focus.Hopefully we don't have to risk our lives simply to focus on our work. Personal Kanban provides the structure to allow us to choose the right work for maximum effect repeatably.For more on how to choose the "right" work, and then how to make sure your processes are repeatable see Prioritization and Retrospectives.Photo by Randy Son of Robert.
The "Man, That Was Awful" Approach to Personal Kanban
Kanban is meant to be epiphany heavy, but process light. These approaches are meant to provide simple means to visualize how your work actually flows. Some tasks are going to be horrible. They are going to take longer than you expect, be harder to complete than anticipated, or even just really annoy you.In life, you want to do things that make you happy and not do things that don't. So why not start noticing what you don't like to do or what takes you away from doing the things you like?The MAN THAT WAS AWFUL approach is simple. When you finish a task and it was in anyway unpleasant - set it aside. Then, later, take a look at the tasks that were unpleasant and look for patterns. Were the people involved the same? Was it a resource issue? Do you just hate doing those kinds of things?After you see the patterns you can make choices like:
when to delegate
when to refuse work
what processes you might want to recreate
if you want a new career
to cry
Again, the point here is to make what you are doing explicit. Hopefully bad things will initially fall into some patterns that you can consider and reshape. Awful tasks should become less and less common as you can spot them coming and learn ways to deflect them.Photo by _Boris