" "

visual control

Dominant and Secondary Projects

At Modus we now have a posted, dominant project at all times.

Make dominant projects visible

We post it as a large sticky on the wall. This is the banner saying “If you pull something and have any choice whatsoever, pull it from this backlog.”

This giant kanban token conveys our current organizational focus and promotes completion of that project.

Only when something is completed, does Modus receive any value from it.

This is why long projects with cumbersome deliverables are so difficult for companies and the people in them: long projects require long wait times to realize value.

As the anticipation for completion builds and we meet the inevitable disruptions in schedule, we are disappointed. As we are disappointed, our desire to work, our culture, and the quality of our work suffer.

Providing a constant reminder with a visual control, not just at the standup meeting (which is not a visual control), of the day’s focus has helped considerably.

I’ve noticed that Urgent but not Important tasks like answering emails, dealing with texts, and impromptu conversations not only derail us from the task at hand, but also the day’s focus. I’ve witnessed in others and myself that when we’re interrupted, we often don’t go back to what we were working on, but onto another interruption. After an unexpected phone call, we might suddenly find ourselves checking e-mail.

It seems that any break in flow, breaks the flow.

The visual reminder of major focus helps return us to the day’s project.

This is the fourth post in the series - Are You Just Doing Things.  You can read the previous post here.

Written in Mesa, Arizona

Motivation Through Visualization: Seeing What is Really Important

Visualizing What is Important

When we wake up in the morning, we have a pretty good idea what we want to get done that day. To make those daily goals explicit, we created the Today (link) column for Personal Kanban.Our Personal Kanban serves many functions:

  • It tracks our current work;

  • It shows what we’re excelling at;

  • It shows where we may be falling behind;

  • It gives us an appreciation for our context;

  • It lets us know when we’re overloaded and could use help; and

  • It shows the status of our projects.

But our Personal Kanban can also inspire us. For me, there is one major goal I have that drives almost everything else I do. It’s very personal and important to me, so we put it in the Modus Cooperandi Personal Kanban as a reminder. That’s what I’m working for. It’s that yellow task up there, cryptically labeled “H4M&D.”For me, H4M&D gets a little closer every day. Even though the ticket doesn’t move, if I can close out my day with the understanding that I truly am a little closer to that goal, then the day has been a success. Granted, some days I move only the tiniest bit closer, but closer is still closer.I would recommend that you be judicious when putting anything like this in your Personal Kanban - make sure it is that important. You don’t want to clutter your board with 20 bits of inspiration that  get in the way of your work.Use your Personal Kanban to inspire. Make your inspiration visible and begin to work towards it. Like mine, some of your goals can be audacious. Keeping them visual is keeping them relevant. It helps you pull the right tasks, slog through the hard ones, enjoy the easy ones, and see them all in the context of your greater goals.

The Psychology of Kanban (Video)

In November, 2010, Jim Benson spoke at the Oredev conference in Malmo, Sweden on Energizing the Individual Coder and the Psychology of Kanban.Clarity Means Completion: The Psychology of Kanban - Jim Benson from Øredev on Vimeo..

How We Interact with Kanban (Video)

In November, 2010, Jim Benson spoke at the Oredev conference in Malmo, Sweden on Energizing the Individual Coder and the Psychology of Kanban.Personal Kanban: Optimizing the Individual Coder - Jim Benson from Øredev on Vimeo.

Would You, Could You on a Plane?

As a matter of fact, yes.I boarded the first leg of my flight from Seattle to Hanoi. I had 19 hours of flying ahead of me. I also had a backlog, and no wifi. Agile Zen was not going to be useful for me. So, I opened Open Office Writer and made a quick table.I had a series of things to do, but with a few constraints. The first was that I was likely to fall asleep at some point, so I wanted to knock out the most important task first. The second was that I had a list of commitments I'd made over the week and needed to make good on them. Fortunately, I have a 17 hour battery and a 4 hour battery as backup, so I had enough juice to cover me.In no particular order I wrote down my work. I had 14 papers to read for Hanoi, so I began with those.  I knew that not finishing them first would mean I'd read them when I was too tired to retain anything. Then I went to work on the feature sets for the new software projects. Finally I ended with blog posts (of which this is one).In the end, I had a full accounting of what I'd done - so I could make sure that the files and work completed in-flight made it to the appropriate people and after-action steps were taken.I want to point out again, you don't need special hardware or software, you just need to visualize your work, limit your WIP, and prioritize.

" "