Visualize Your Past

Visualization Retrospective

Happening right now

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?

Personal Kanban & Some Goodies About Your Brain

Simple Personal Kanban

Sharing some thoughts around my weekly homework from my neuroscience studies

Knowledge work is all about attention. Unfortunately that is a scarce resource, easily high jacked by any distraction. Multitasking, i.e. using focused attention on two different targets basically does not exist. What you are able to do is to do a lot of things on autopilot (i.e. walking, breathing, looking) while your executive network (incl. working memory) is doing something else (i.e. discussing). When you think you are multitasking you are actually attention switching, with a high cost in performance. For this you will allocate attention toward or away from interference, maintain relevant memory in mind, and reactivate representations if the maintenance of what you are doing is disrupted (Clapp et al, 2010). So when you are working with a need for cognitive logical thinking, minimizing any distractions is a great preventive method.Kanban is a method for managing knowledge work with an emphasis on just-in-time delivery while not overloading the team members. The core mechanisms in Kanban is to start where you are at, work in an evolutionary and incremental way to develop the system, limit the work in progress, and finish one thing before starting another. (Wikipedia, Kanban, 29.10.2014).While Kanban is used on a team/organizational level and longer time spans, the same logic applies on personal level and short time spans, too. From a neuroscience perspective, Kanban is too interesting to fit in a 300 words homework.

A couple of Kanban-insights from the neuroscience perspective

• Limiting the number of similar things you work on will lessen the cost of attention switching and thus positively impact performance on the task at hand. (a no brainer) (Clapp et al, 2010).

• Focused attention means you are using your long-term learning mechanisms (Medial temporal areas) to encode the experience. This makes the knowledge accessible by conscious thought later on (vs. using striatal habit learning, creating more unconscious and automatic learning). (Forde et al, 2006)

• A “healthy” backlog is genius from a neuroscience perspective. Attending to an issue (backlog item) then leaving it with the knowledge of that you will return to it, seems to activate your unconscious processing. So while you are consciously focused on your work in progress (WIP), your unconscious works on items, which you know you will attend to later. (Backlog) (Ritter & Dijksterhuis, 2014)

Kanban definitely requires more in-depth analyzing from the neuroscience perspective. My hunch is that Kanban fits many of our biological & neuronal requirements, so I will definitely be dissecting Kanban some more in my studies.Where’s the scalpel?/Riina

References

1. Clapp, W.C, Rubens, M.T., Gazzaley A. ,(2010),  Mechanisms of Working Memory Disruption by External Interference, Cerebral Cortex, April, 20:859-872

2. Foerde, K. , Knowlton, B. J., Poldrack, R.A.(2006), Modulation of competing memory systems by distraction. PNAS, August 1, 2006, vol. 103, 31, p 11778-11783.

3. Ritter, S.M., DIjksterhuis, A., (2014), Creativity – the unconscious foundations of the incubation period, Frontiers in Human Neuroscience, April, Vol 8:215, p.1-10.

Picture: Photo credit: o.tacke / Foter / CC BY

Take the RealWIP Test

Write Down Your WIP

If you are already using Personal Kanban or another kanban system, you are likely at least thinking about limiting your work-in-progress (WIP). You are likely finding that challenging.We know that the more work we take on, the more our brains' resources are taxed. That tax limits our ability to focus, to process, and to complete quality work. We want to limit our work-in-progress so that we can finish quickly and with quality.One thing to remember is that if it were easy to limit WIP, we’d all be doing it already. Limiting WIP is challenging in a world filled with demands and distractions. Often we’ll be watching our Personal Kanban and, as long as there’s three things in DOING, we’ll feel pretty good about ourselves.Then, one day, we’ll catch ourselves working on something that isn’t in DOING and we’ll realize … oh no, I have hidden WIP.Hidden WIP is that work you do all the time that you don’t tell your board about.So it’s helpful once a week to sit down and write down your WIP.  Simply write down everything you are really doing right now. Write down everything you are currently working on or is making you think. (You may be starting tasks before you pull them). See what that real load is. If you work with a team or manage them, sit down and do this with the team.You’ll be surprised at how much work you are actually taking on.I can’t stress how important this is even for experienced kanban users. I visit teams and counsel individuals regularly who are overloaded with work and have very nice WIP-limited Personal Kanban boards. Their hidden WIP is killing them.So, sit down, write down your real WIP and do something about it.

READY COLUMN: Breaking Out Projects

Kanban

Lots of tickets in our READY column make a jumbled mess. We’re not sure how close we are to completion or what ticket to pull next, Breaking your work into projects in the READY column lets you see both. You can sequence work (pull the rightmost ticket), see how many tickets are left in the project, and see what projects are ripe for rapid completion.You can also create better strategies. For example: Sunday can be the day to nuke the “CLEAN GARAGE” project.  But maybe Saturday is the day you look over the tickets and figure out what you need to get from the hardware store for both the CLEAN GARAGE and the RENO BASEMENT projects. One trip to the hardware store gets you a power washer, broom, and shelving for the garage and a drill and sledgehammer for the basement.Without having the tickets in orderly swimlanes, we instead would have a disordered jumble which is much harder to manage.This is the final post in the Personal Kanban Tips series.  You can read all the previous posts by clicking on the links below.DONE COLUMN: How Does Your Work Make You Feel?DONE COLUMN: Daily / Weekly ReviewPROMISES COLUMN: Make Good On Your PromisesTHE NEW STUFF COLUMN: What's Just Come In?READY COLUMN: Ticket Aging

READY COLUMN: Ticket Aging

Kanban

In our last post, we discussed a NEW STUFF column. In this post, we are being even more explicit, noting in our Personal Kanban how old tickets on the board are.We have seen, even on our own boards, that tickets can linger on the board for six months, eight months, even a year! That’s simply too much time.What we also see is that if tickets aren’t done within the month they’re put on the Personal Kanban, they probably won’t get done. You’re better off making a second board called “Things I might want to do some day” (What in GTD would be a “someday” task) and getting off the Personal Kanban.An easy way to see this is to make three or four swimlanes in your READY column, each labeled by month. Here you see the months are JUNE, JULY, and AUGUST. This shows us, at any point in time, what tasks are aging or maybe old enough to simply discard.It also lets us see, over time, the types of tickets we tend to put on the board but never get around to. That’s important because people are skilled procrastinators. If one of those old tickets is “schedule physical” or “talk to Uncle Louie” we know the ticket didn’t age out - we’re not prioritizing effectively.Watching tickets age tells us a lot about what we choose to do, what we choose to put off, and what we wish we could do but is never going to happen.Seeing that explicitly can teach each of us what plans we can make that will likely succeed and which will likely falter or never make it out of the gate.This is the fifth post in the Personal Kanban Tips series.  You can read the fourth post - THE NEW STUFF COLUMN: What's Just Come In? here.