Dear IT Director,
One of my long-term vendors messed up last week, and we are dealing with the fallout. They know my company really well and I don’t want to look for a different vendor.
Angry in Akron
I feel your pain. Anyone that uses vendors has dealt with this problem. One of their people makes a mistake that causes extra work for your team. They push a problem into production that impacts your users. They build something that requires rework that blows your budget and schedule. They supply a person who just isn’t up to the normal skill level.
There are a few things we can do when this happens, and, yes, one of those options is finding a new vendor. Let’s walk through them.Read More
IT folks all know the drill. Someone calls the Help Desk to report that some spreadsheet or program isn’t working. The Help Desk can’t solve the problem and escalates it. After much conversation, we realize that we have discovered another Shadow IT orphan. The creator of the complex spreadsheet or, worse, a VB6 program, is long gone. The users have been using it for years, not knowing it is a time bomb.
The expectations on IT at that point are to become the adopting parents. Sometimes we can get lucky and foist a spreadsheet off on Finance to have them try to figure it out, but that doesn’t work very often. But the programs? Sigh, those we have to deal with.
As IT Leaders, we are continually making a wide range of decisions. There are all the normal people & business decisions that leaders need to make. Then there are the technology decisions that need to be made faster and faster. Throw in all the changes in consumer technology changes that are making their way into the business world. IT Leaders makes many decisions each day.
Big decisions, little decisions, simple decisions, complex decisions.
How can we stay on top of them all?
Dear IT Director,
My company is growing, and we got behind on orders. We have been doing a lot of work to catch up, but it is hard to tell if we are making any headway. My boss asked me if I have any ideas.
Confused in Cincinnati
Increasing late orders is a tough situation to be in, especially if revenue is growing. We have to deal with more orders than we have ever seen, and we need to catch up on late orders. If you focus on one of those, the other gets worse. Customers get cranky. When you hear about businesses not surviving their own success, this may be part of the cause.
I suggest the concept of Late-Days. This provides a single, trackable number that quantifies the size and age of the late pile. For each order, add up the number of days late. If you have variety in the size of your orders, you can tweak this by multiplying by the dollars or quantity of the order. As a bonus, we can use this concept for other late things besides sales, hint – how is your IT to-do list?
Before we get to an example, why is Late-Days useful? In my experience, not all overdue is created equally. Since there is never one silver bullet to fix overdue, we need to approach each situation differently. Ten orders that are weeks late differs from fifty orders that are days late. The solutions you try will be different in each case. Late-Days quantifies that for us in a way that helps us understand if we are making a difference.
While the number of late orders is the primary metric, it doesn’t really tell much of a story about what those lines are like. Days-Late gives a little more information.
First, the math. The simplest way is to add up the days late for each late order.
As I mentioned before, you can add a dollar or quantity multiplier if those vary in your situation. I’ll also remind you that no single metric holds all the answers. Late-Days is a simple metric to add to your mix of metrics.
How can we use Late-Days to monitor our progress?
Let’s look at the scenario I mentioned above: ten orders that are weeks overdue and fifty orders that are days overdue. We might have a Late-Days of 357 for the first and 128 for the second. By themselves, these numbers are not helpful. But when you track this metric over time, you will see changes. And that tells you if you are winning or losing.
Track Late-Days every day and work to make the number lower. The goal, of course, is zero.
The hard part is figuring out how to ship all those late orders, AND to ship all new orders on time. Late-Days provides a useful number to know if you are making progress.
Good Luck Confused,
The IT Director
Managing ourselves can be harder than managing others. In related news, doctors and nurses make terrible patients. I’m married to a nurse, so I know this to be true. It is easy to wave it off, convinced that we are in good shape and don’t need any help.
Improving as a leader is a lifelong journey. As a leader, we are never as good as we think we are. But take heart, because we probably aren’t as bad as we think we are.
There are four things that are necessary to be a good IT leader. There are other important leadership skills, of course, but these are ones I believe are specifically helpful for IT leaders. Here is a brief explanation of the four.Read More
Dear IT Director,
Help! We are running around with our hair on fire, working on too many business projects. Our IT processes need help, but we don’t have any time to improve them.
Overwhelmed in Omaha
I feel your pain. The list of changes the business needs is long and you want to get it done faster. At the same time, you and your team know how to improve your processes to become more efficient. But there is no time. How do you stop working on the business tasks to improve IT?
In a previous article on Focus & Finish, I covered The Myth of Multitasking. This article goes into some detail on how to make Focus & finish a reality.
When I first proposed to the team that we needed to only have 1-3 active Change Requests at a time, we all struggled to make it happen. We kept getting clogged up with too many active tasks.
After looking closer at the problem, I identified some challenges and solutions. Here are a few.
I stared at the list of requests the team was working on. Seven people, ninety-three active requests. Over ten active requests for each person. The team was working hard, but it felt like we weren’t making progress. Requests were not getting completed, and it felt like we were the bottleneck.
The IT department’s to-do list is always longer than its capacity to complete those tasks. This is intentional. A properly managed company will not have excess capacity in its service groups like Finance, HR, or IT. I have yet to discover a company that does not have an IT backlog.
Getting that work done is a challenge. There is always pressure to do more. Those with requests in the backlog will keep pushing to get their requests completed. We complicate this by having too many projects or tasks active at the same time. We are always multitasking, trying to keep all the juggling balls up in the air.
All too often, we fail.
The answer is to have fewer tasks active at a time and make sure that they get completed before starting something new. Let’s start with the real problem: multi-tasking.Read More
The concept of Technical Debt has been around for decades. Originating in the software development area, Technical Debt describes the accumulation of “we should probably fix that” places in the code. However, Technical Debt does not just apply to software, it applies to the entire IT world. Hardware, software, infrastructure, security, and applications all have their technical debt.
Technical Debt is a little like Schrodinger’s Cat, as it may or may not be there. Some technical debt is never a problem. Some of it blows up spectacularly. Some assumptions we make are fine. Others aren’t.
Here are some well-known examples:Read More