JIT Action Items for the Office Worker

Your ads will be inserted here by

Easy Plugin for AdSense.

Please go to the plugin admin page to
Paste your ad code OR
Suppress this ad slot.

Just in time.

Picture this. You are reviewing a list of tasks that was assigned to colleagues in your business. You remind one of the task owners their action item is due tomorrow and they respond, “I have it on my list, but I’m operating just-in-time.”

This happened to me recently. The word choice “just in time” (JIT) is from a Lean concept in which production output is managed by when the customer requests delivery rather than when the producer can complete the task. Most office workers today don’t match-up their behavior with Lean Principles. But even if you aren’t a Lean practitioner, there is tangible value to considering the JIT approach.   One of the primary goals of JIT is to eliminate waste by not working or storing excess inventory. For this blog post, I’m writing about assignments, tasks, and action items for office personnel. Think of excess inventory as assignments that are completed but never used or maybe action items that are started but never finished. That is considered waste and our time is too valuable to spend it producing work that doesn’t add value for the customer.

Three ways to structure a task list for JIT delivery in the office:

1. Purge non-value added activities.

 

 

So often we spend our time prioritizing tasks to stack rank them for the order they should be worked. With ‘Lean’ thinking the first question should be “do the results of this activity add value for the customer or is it a necessary non-value added activity?” (i.e. compliance task). My experience with tasks prioritized low is over time they eventually fall off the list because they are no longer needed. This most often means it was never a value added activity and just clutter on the backlog (unnecessary inventory). It’s a good idea to review the backlog of tasks on some recurring interval to purge non-value added activities.

2. Group items into buckets already covered by standard work activities.

Your ads will be inserted here by

Easy Plugin for AdSense.

Please go to the plugin admin page to
Paste your ad code OR
Suppress this ad slot.

 

 

Some action items may fit into already established recurring work activities where standards and time allotments exist. If that is the case, then it’s not necessary to create additional time for one-off production of work output. An example of this recently happened to me. A compliance control required the review of at-risk vendors and documentation of the results. I already had time assigned on my calendar for a quarterly review of security and risk related items as part of a security committee agenda. Rather than add a new task for myself, this compliance control was added a responsibility of the Security and Risk Committee. The concept for this idea is to examine recurring activities already part of standard routines. Some assigned tasks may naturally fall into those routines and intervals.

3. Use a calendar of due dates to help with priority sequencing.

 

 

Putting due dates for action items on a calendar provides several nice features for structuring work. It enables the ability to preview the calendar for upcoming work (Daily or Weekly) which triggers work execution. The concept of JIT relies on keeping inventory of unused work at a minimum. With this thought in mind, try to avoid having active progress on work that isn’t due because it may take away time from working on tasks that are due.  The challenge with this method is estimating how long a task will take to complete and being able to work through unplanned interruptions.


So being a JIT employee isn’t quite like being a Jedi employee. But then again, if you can consistently deliver action items in the expected time frame, it won’t take long to reach Jedi status in your office.

Onward and upward!

Photo Credit: Philip West via Creative Commons.

Revisiting – What are you known for?

Your ads will be inserted here by

Easy Plugin for AdSense.

Please go to the plugin admin page to
Paste your ad code OR
Suppress this ad slot.

Deja Vu

I recorded a few rambling thoughts one day after work this week. That’s how many of my blog posts originate. Things happen through the course of a day that stick with me into the evening. When I jot down my thoughts, I see interactions with people, process observations, desires for a better solutions, and things I want to change.

This week I looked over my notes and thought, “What do I want to be known for?” It’s a question I knew I had asked myself in the past. Three years ago, I wrote a post entitled What are you known for?  In that post I expressed my desire to be known more for providing solutions over following processes. I’m a practitioner of following processes, but the process itself isn’t bigger than the results it provides.

Dr. No

Fast forward to today. The Information Technology landscape is increasingly burdened with applying more security and availability controls to keep customers data safe and to achieve compliance with standards. But compliance is never convenient. The IT guy is caught in the cross hairs of a battle between making the work environment more secure and the extra burden it places on other employees. Burden in this context means restrictions. Lots of them.  

Traditionally, IT has been known as Dr. No. There are restrictions on what hardware employees can use and what software they can install; Internet sites are blocked, software can’t be downloaded, etc. This is the seed that birthed Shadow IT where departments arrange and install software outside the approvals and processes of their local IT group.

A better way

I’ve had too many experiences in my career watching people telling someone else they can’t do something for one reason or another. It’s not only frustrating; it drains the energy and motivation of those involved.

But it doesn’t have to be this way in every situation.

A better partner explains the constraints of the problem and solution. Instead of ending a discussion with ‘no’, he or she will offer alternatives for a solution.

 

“We can’t do that for you, but what we can do is this…..”

“That’s not possible, but I know a way that is….”

“We are prohibited by policy/contract/compliance control from doing that, but there a few different ways to accomplish something similar….”

 

Of course, the person on the receiving end has to be able to compromise and think about the solution in different way as well. It takes two to make the partnership happen.

If you are a solution provider, don’t stop at the word ‘no’.

If you are a solution receiver, be open to alternative ways of doing things.

What do you want to be known for?

Onward and upward!