“IT will never be fast enough, because business units will always want results sooner.” Best Buy Exec Points Toward Next-Gen IT, GlobalCIO by Chris Murphy,

“Some customers complain that they’re already dealing with too many updates to their applications, even in the cloud.” Pros And Cons of Microsoft’s ERP-In-The-Cloud Plan, by Doug Henschen.

Information Week, April 9, 2012.

OK, which one is it? You want a lot of changes fast, but when we give them to you, you tell us that we are changing too much too often!

Has this ever happen to you?

Sadly, not enough people get to manage this kind of “successful” situation. But when we finally got organizations performing well, one of the somewhat amazing results was the sudden customer push-back of “too much, too fast.”

The challenges of success then is … to be successful with it. In the IT field it is often surprisingly easy to be suddenly successful.

I’ve related other experiences, such as with test and quality organizations, where these organizations reacted poorly to a significant increase in quality. While we all strive for “faster, faster, more, more, quality, quality” it is often a shock to many when we achieve it.

See related:  Want To Stress Your Test Team? Give Them Quality!

So my lesson learned was, yeah, I want to be fast, feature rich with rock solid quality, but I have to deliver it to the customer in a way that they can handle. Just because they say “faster!, faster!” don’t assume that they can actually handle it or that they will automatically sing our praises when we do it. It is sometimes just too easy and too safe to demand something that appears unattainable.

 It is just too easy to demand something that appears unattainable

We had called a meeting for our Asian markets test teams. We had been reminding them and everyone for weeks that the milestone for the start of regional testing was fast coming. We were now ready, but the Asian market manager seemed confused. She asked me why were we asking for testing now. It was months before the product was to be shipped, she said.

I was in-turn a bit confused by her question, but I simply reminded her that this was the schedule and that this was how much time they had needed in the past (and had agreed to) to complete their product testing in the region.

She went quiet for a few moments. Finally, she said that she knew that was the schedule, but no other product had ever actually ask them to start on the scheduled start date. She asked if the prototypes were ready in volume and if the hardware and software had passed their readiness reviews. I confirmed all of those items and the managers in charge of those activities were in the meeting in case she needed additional details to get started.

After a few more moments of awkward discussion, she finally admitted that they had simply not prepared and she had expected to have a few more months before they really had to get going. Her team was not ready and it would be weeks before they could be, if they got started preparing now. Even then they would be short of resources but they could at least get started.

See related: One Great Way Of Using Your Staff Hours

We kicked off the European region testing a few weeks later and the regional manager had heard we had started Asia “almost” on time. I could tell he was a bit harried but he had quickly lined up contractors to do the testing (“Bruce, are you sure this is really going to happen?”). His region started testing on time. We delivered the product on time to our first and largest customer in Europe. The Asian region delivered a couple of weeks late to their first customer (which was still a huge win as we typically delivered months late).

I’ve also experienced a customer who went from regularly berating us because we never delivered system updates on time nor in good working condition to telling us they didn’t want to take a system update because we had too many changes. Our many changes would be too disruptive to their business processes they claimed — as if it was our fault they had requested so many changes!

I had a budget director, who always blamed my department for why the overall budget was late, ask me diplomatically to continue to review my budget for another week past the deadline. Since my department’s budget had always been the last one to get in and was always late, his reason for missing his budget updates each year was because of my department. When we finally delivered on time, he was not ready. In fact it took him a few years before he could take my annual budget submission on time.

Bring about change in a manner the organization can handle

We always want to get faster and be more efficient with time. At least I always want to and we’ve been successful at doing just that. But because someone is constantly and loudly saying “faster, faster” doesn’t always mean they can really accommodate such a fast and furious pace. It is our job as project managers to bring about change and improvement in a manner the organization can actually and smartly handle. So, don’t be too surprised when a customer gets “big eyes” when you tell them that you have what they asked for when they asked for it.

Have you ever delivered a project only to find the customer was not ready for it even after they regularly pushed for its fast delivery?