Self Help

“I love those automated attendants, recorded voice answering machines and the endless opportunities I get to push my own buttons whenever I make a call looking for someone to help me.”

Said no one, ever.

It has been well documented for some time that customer satisfaction is adversely affected whenever a customer has to deal with or must navigate through one of those automated phone answering systems. Normally when they call, they have a question, or need help with an issue. They want to talk to someone. Otherwise they would have just sent a text. Or accessed the company web page and sent an email. But no, they had hit a threshold where this type of technological linking was not good enough. They wanted to ask another human being to help them. And yet despite their need for support and desire for human interaction, they are denied.

The problem is so rampant that there are now commercials by certain companies appearing on network television espousing the point that when you call them, you actually get to speak to “a real human being”. Some companies now feel that it is now a competitive differentiator that they will have a real live human being answer your call and that you actually get to talk to them when you call them. It is interesting how quickly times changed initially to the automated systems, and then just how quickly they are changing back. There can only be one reason for this service technology whiplash.


Companies originally saw these systems as opportunities to reduce the cost of support by in effect making the customer responsible for some of their own issue or support request. They would need fewer support people if they could make customers work a little bit in the identification of the type of issue they were calling about. Fewer people needed for support equated to reducing the cost of support. This is always thought of as a good idea for the bottom line.

What they learned was that for the most part customers didn’t really like this type of automated system. It may have saved the company money in their support costs, but it made their customers unhappy. And unhappy customers were not as likely to buy more equipment or products from the vendor that made them use an automated attendant system when they needed support. This is normally thought of as a bad thing for both the top and bottom lines.

Companies learned, or actually relearned the old adage:
“Penny wise and Dollar foolish”. (It is actually “Penny wise and Pound Foolish”, but, I live in Texas, USA, so I have taken a foreign exchange liberty here.)

They may have saved a few pennies with the automated systems which enabled them to reduce the number of people required to deliver customer support, but it ended up costing them many dollars in lost sales from their customers who were not particularly impressed or happy with the support that they got.

Now we have companies advertising that they are using people to answer their service calls, just like everyone used to do thirty plus years ago. Go figure.

While it is interesting to discuss the migratory aspects of the types of customer service and support, I think it might be time to discuss a group that may not have fared so well in the evolution of support: The Employee.

It is no secret that companies must spend significant amounts of money, time and effort supporting their own communications and networking needs. Every company has a corporate network. Every employee has a Personal Computer. The employee productivity gains that have been created are enormous and well documented.

It has also put an enormous strain on and demand for corporate Information Technologies (IT) teams for support by these employees. Security and the ability to keep hackers out has almost become an industry unto itself. Requests for networking, applications, upgrades and support continue to grow as the complexity of what is required by the corporate knowledge worker increases. In the age of Virtual Offices (VOs) the demand to deliver these services to locations outside the classic organization structure or office has boomed.

And what is the diametrically opposed force that companies must deal with in this time of burgeoning employee technology demands?

The desire to reduce, or at least limit the growth of Information Technology support costs.

Companies are facing explosive demand for new and innovative Information Technologies applications and services by their own people in order to continue to generate ever better productivity, but are having to temper responding to this demand due to a desire to keep their IT costs in check. There are many innovative ways that companies are dealing with this issue, and unfortunately there are also several ways that may not be considered quite so innovative.

When I was in college, I once had a physics professor who was preparing us for a rather extensive round of midterm exams. He informed us that once the test was passed out that there would be no talking. He also said that if we had any questions we would be encouraged to raise our hands. He noted that by raising our hands above our heads, blood would obey the laws of gravity and flow out of our arms. This would in turn increase blood flow to our brains. This in turn would cause an increase our brain activities in the firing of synapses and neuron transmission, which in turn should enable us to solve the problem on our own.

I am not sure, but I think the gist of his comments were that we were not to ask him questions, because it was a test.

I am concerned that many of the IT leadership of many businesses today seem to ascribe to the same school of thought when it comes to staff support. If you don’t believe me, try and find the internal organizational phone number to call and actually talk to someone real time if you need IT help with you technology based connections. Emails and instant messaging are by far the preferred mode of communication if you need help. And if by some chance you do locate the telephone number for IT support, I think you have guessed it: You get to deal with the corporate IT automated attendant.

It seems that what was once done for you as a valued productivity asset of the company, when it comes to new applications and upgrades, are now being pushed down to you to try and do on your own. The new definition for employee service seems to include unlimited numbers of IT based emails with directions on how to update, upload and upscope the many new, mandatory or desirable IT capabilities.

Sort of a raise your hand and hope for increased blood flow to the brain when it comes to IT support.

I think part of the reason for this internal support shift is that the cost of IT and support is a very identifiable amount. There are direct numbers, budgets and staff associated with it. In budgeting and costing terms, it has become a very identifiable target. There is a defined amount being spent and as such becomes a prime candidate for cost reduction.

The issue that arises is that for every identified and quantified dollar that is saved from the IT budget, there is not a specific quantifiable amount of incremental time or lost productivity that can be identified or captured by the employees, as they are forced to pick up the slack. The measurable IT budget is reduced and a real dollar cost reduction is recognized. But it is far more difficult to measure how much is “spent” when all the additional hours that all the individual employees must now spend completing these IT tasks are totaled up.

An extra hour or two, here and there spent by each employee doing what was once an IT task gets lost in the count. The employee’s work load doesn’t decrease to accommodate this new additional effort. The deadlines aren’t extended because there is now more to do. It’s just another issue to deal with.

Just like happy customers are known to buy more products, happy employees are known to be more productive. However, employee productivity is something of a subjective measurement where IT budgets are very quantitative. This leaves the decision in the realm of reducing a measurable budget, known quantity at the risk of reducing an unmeasurable, unknown employee satisfaction and productivity quantity.

When the cost of cost reductions is reviewed in such a manner, it is best to expect continued pressure on corporate IT budgets for the foreseeable future.

I think it is probably safe to assume that there will be a point where there is a recognition of the value of supporting employee satisfaction and productivity via increased, direct tool and technology support. My guess is that corporations are probably getting close to that tipping point.

When bellwether companies such as Yahoo! and IBM have already decided that there is in fact greater value to the company when employees interact with each other in the office as opposed to the convenience of working via Virtual Offices, it probably isn’t too far a leap to think that they will also recognize that the small, but highly visible investment in the IT resources to support them is also probably money very well spent.

The Five Stages of Change…..and Grief

A friend of mine asked me to look over a document that he was going to issue to his most prized customers. He wanted to prepare them on how he saw things were going to change in the coming (if not already here) digital world. I was flattered. Normally the only people who ask for my opinion are some of my myopic golf buddies when they are having trouble reading a putt. My friend wanted to make sure that his message was not viewed as just another document to be scanned and thrown on the pile of other documents his customers read. As usual, this got me to thinking about how we can relate to and react to the now inevitably changing processes, as they continue to barrel down the tracks at us.

As is also usual I first went out and looked around to see if there was anything written on the five stages of change. I wanted to know if I was capturing some original thought or possibly just rehashing something that someone else had already said. It was with only a modicum of surprise that I did indeed fine information on the five stages of change. According to the article I found, the five stages of change are: precontemplation, contemplation, preparation, action, maintenance. I correctly assumed that anything that includes both precontemplation and contemplation in its description is somehow academic in nature and not fully business oriented. You too can see this at:

I have never really encountered “precontemplation” in a business environment, but I will now be on the lookout for it. Most of the time I am both surprised and thrilled if I run across anything that even resembles contemplation, let alone precontemplation. For those of you wondering what precontemplation is, it is the point in time when people are not even considering (contemplating) change.

I had to look it up because I didn’t know either.

The five stages of change that I want to deal with are a little more basic and deal more with the human factor associated with change. They are, denial, anger, bargaining, depression and acceptance. Some of you may recognize these five stages of change also as the five stages of Grief. Since there is very little in business these days that causes more grief than change, I think that they are most appropriate.

I have had the opportunity to be a change agent in several different roles for several different organizations. I have found that the two primary reasons that businesses need to change are: The business is doing well and it is anticipated that the market will require the change, or, the business is not doing well and the change is required by the market if the performance is to improve.

Pretty simple, huh?

In either instance, you are almost guaranteed that the universal initial response by those who must change will be denial. They are already doing everything in accordance with both their objectives and the existing process. It will be others who must change, not them. And they are usually at least partially correct. However, I have found that the proper response to such a denial is that others will also change, not just them.

Denial can be one of the longest lasting stages of the change process. Too many times change is seen as an invalidation of what the business has been doing. This not and should not be the case. All business environments are dynamic. Change is an inevitable requirement.

I promised myself that I would try to avoid platitudes of that type. I guess I will continue to try and promise myself that after that last statement.

The next stage in the change process is anger. If denial is not the longest stage of the process, then anger is. When people are made to do something that they don’t particularly want to do, they do tend to get emotional and this usually translates to a little angry. They can also perhaps be a little angry that they were not the ones that recognized the necessity of the change, or that they were not the ones that proposed the change, or even perhaps that the change occurred on a Tuesday as opposed to a Monday or Wednesday.

The idea here is that the response to change can be emotional. And the first rule of dealing with an emotional response is to not get emotional in return. Understand why the response is present, but don’t slow down or alter course.

So now everyone is denying that a change is necessary, and they are now also angry that you are not paying attention to their denials. What’s next?

Bargaining is next. This is an interesting stage in the change-grief process. It denotes the understanding that some change is going to occur. It is also the beginning of the internalization process for that change. It is the methodology by which people begin to take ownership of the change.

It is always good to engage in the change-bargaining process because no one has a corner on the market for good ideas. You never know where the next one will be coming from. Listening to the team that is preparing to change is always beneficial. There is one thing to remember though:

It is not a negotiation.

There may be pieces and parts of proposals that can and should be incorporated into the change process, and there may be those that may best be ignored. Most organizations will not change of their own volition. It takes someone to change them. And it will take will power to overcome the inherent resistance to the desired change.

Once the bargaining is done, along with all the associated renting of clothing, gnashing of teeth and general keening, there is usually a quiet period. This is where the depressing truth of the pending change sets in. It’s going to happen. People will have to change the way they do things. There may even be pending changes to the people themselves.

It will be up to the change leadership to do two primary activities during this period. The first is to make sure that the period between the acknowledgement of the pending change and the actual implementation of it is minimized. It is up to the leader to keep this stage of the change process as short as possible. They need to minimize the length of this negative effect.

The second is to continuously communicate with the changing team during this time and process. Over communicate. Be visible. The change leader must assume the responsibility for moving the team, not just the process, forward at this time.

Finally, if everything has gone right, and the implementation of the change has begun, there should be the final stage of the change-grief process: acceptance. And as with almost every other stage in this process, there will be varying levels of acceptance. Some will embrace the change and move forward with it, and some will begrudgingly go along with it. The only way to make sure that all are on the same page is to take one more additional step.


What was the reason for the change? Why was everyone put through the grief inducing process? What was the outcome of the system before the change as opposed to the now current outcomes?

In short, show the team what the benefit of the change was. Look at the business performance before and after. Document what is was before, what the implemented change was and what the performance is after.

The idea is to close off the change-grief process with a review that (hopefully) shows that all the effort was in fact worth it to the business. Having a final review of what was the situation and performance before the change and what the new baseline is after the change closes the loop with the team that has gone through the change.

There is no doubt that change induces grief into an organization. Even the prospect of change can and will generate grief. I think that organizations might have a little better response to change if they focused more on dealing with it as grief instead of just change. While the idea of change has its own connotations, it does not engender the appropriate management response. Change is almost an intellectual concept.

Dealing with the organizational upset generated by change from a grief point of view enables management to understand more of the human response and emotion that is created. After all we like to think of change on organizational levels, but it is really on the human level within the organization that the meaningful changes actually take place.


One of the hottest debates going on in business these days is the debate regarding what work, if any, will stay in the supposedly high cost country and what work will be sent to the supposedly low cost country. This is the function that is usually referred to as off-shoring. There are many factors that seem to be taken into account with this decision, but there are also several factors that don’t seem to be included. It appears that the only major factor that companies really consider in the off-shoring decision is the relative wage differential of the existent workforce versus the prospective workforce. Having gone through, worked with and reviewed some of these types of working environments, it has made me wonder if there are other factors that should be reviewed before these decisions get made.

The bottom line in all of these out-sourcing or off-shoring decisions seems to be doing what is perceived as best for the organization’s bottom line. This is also somewhat subjective depending on which of the shores you find yourself. The idea is to save money. All other factors will be dealt with or considered in due course. And one of the best ways to save money is to try and reduce the cost of your labor associated with the function in question. Are there other people in other places in the world that can and will be paid less per person to do the work in question?

On the surface the answer to this question is almost always “yes”.

If the only factor to be considered is the wage rate paid to the resources doing the work, then the decision is always an easy one.

But things are usually never that easy.

The first jobs to experience this sort of movement were the production and manufacturing jobs. Production lines and repetitive functions were sent elsewhere. Business cases were built containing the incremental cost of building a new factory as well as the reduced cost associated with the low-cost labor to staff it. Questions were answered about how long the pay-back was on the needed off-shoring investment and decisions were made. Factories and production lines were built in these low-cost countries. The production of simple and basic products was then moved.

I am not going to continue too far down this line of thinking because we all know where it goes. More and more, and more production functions have been off-shored. These are finite directed positions that perform repetitive processes at a fixed rate, to create large numbers of similar products.

Let’s now fast forward a few decades.

Almost every business function is now subject to the discussions associated with which shore it should be on. One of the biggest issues associated with any proposed move now, is that the work being considered is usually more variable than the production work of the past, and it is more subjective in its execution.

While a production line will move along at a fixed rate enabling all participants in the production line to work at the same rate, the same cannot, and should not be said about knowledge based disciplines. Do all people who write software code, or design hardware do it at the same speed? Are they all equally proficient at their respective disciplines? Are all accountants or financial managers at the same competency level?

On an even more basic level, do all locations have the same financial drives, work culture, language fluency and associated work styles when it comes to delivering the required work products? Remember now we are discussing complex or service oriented work products, not physical products such as consumer electronics or other real goods.

It is no longer just a question of the difference in the hourly wage rates, or salaries of the teams involved. The question now moves into the somewhat murkier areas of work force effectiveness and work force efficiency.

Efficiency and effectiveness refers to how many resources it takes in each relative location to accomplish the desired work, and how long it takes them to do it. Too many times it is assumed that one workforce is as proficient as another. This might have been the case on the fixed speed production line (after appropriate training and time to come up to speed), but is it correct to apply these same principles to non-production line types of work and service products?

This is neither a case for or against the off-shoring and cost reduction push. These are tidal type forces that will continue until some sort of economic equilibrium is reached. This is more a question of identifying, accepting and analyzing the total costs associated with each proposed workforce location decision.

Just because it takes ten highly motivated, well educated, relatively expensive resources in one global location to deliver a satisfactory work product, does not mean that it will take the same number of similarly motivated, similarly educated relatively inexpensive resources in another global location to deliver the same work product in the same amount of time.

Research has shown that it usually takes more people, and more time for the lower waged (and supposedly lower cost) locations to accomplish the same tasks and deliver the same work products. (

What this means is that it is not just the relative cost of each hour of work that must be examined in the off-shoring decision. It is also the relative number of hours of work that are required at each location that must be included in the equation. That means that the relative number of people (spending hours on the work) and the length of time that they spend (how many hours) should also be taken into account.

If it takes five people one month to do the work at a higher cost location, and it takes eight people two months to do the work at lower cost location, the resulting total cost of work delivery may yield a very different work location decision that just the straight hourly wage comparison that has been so popular in the past.

On the other hand, it should be noted that if the relative wage differential is great enough, even these types of labor inefficiencies can be overcome.

I try to focus on real and definable costs. The relative number of hours used and the relative wage rates at each location in question are either known or can be estimated with some relative amount of accuracy. These are usually real numbers that deliver real relative costs. As always there are other factors that can be associated with the off-shoring question. I’ll list a few of them, but as they are less quantifiable in their effect, it will be difficult assign an actual value to them.

Are there incremental but hard to quantify costs associated with the increased complexity of the operations, IT, infrastructure and security associated with an off-shoring. In today’s hacker infested world one would think that adding facilities and resources in other global locations would have an effect on these types of costs. However, it is hard to add them into any comparative costing discussion.

There are considerations that should be observed regarding the relative quality of the work product generated in each location. Are there bugs in the software? Are there differences in the way customer support is provided that affect customer satisfaction? These are difficult issues to quantify, at least prior to having to try and resolve them.

Communications will also become more difficult. What was once a real-time conversation may now become a series of emails, depending on the relative time zones associated with the differing locations, potentially across multiple days. The overall speed at which things are accomplished, or issues resolved can become problematic.

The cost of management should also be expected to increase as well. At least initially, expatriate management will need to be present at the off-shore site to setup the new functions and oversee them. Depending on how things progress, their presence could extend over a significant period.

For those of you not familiar with the expatriate role, these people are expensive. They are normally paid at the “high cost” location salary rate, and their expenses for staying in the low-cost location are usually also covered by the company. They are in effect paid close to twice for the inconvenience of living in one location and working in another.

The final “soft” cost that I will address is the public perception of moving jobs out of their current location and to another, as well as the potential exposure associated with future governmental regulations associated with this activity. Market movements associated with drives to “Buy Local” and legislation designed to increase the expense associated with off-shoring are gaining traction in multiple locations.

It is easy to see why low wage rates in other parts of the world may be attractive. As companies continue to become more virtual in their natures’ Virtual Office can mean an office anywhere on the globe. The initial success and savings generated by moving the simple and repetitive off-shore has given rise to the desire to move more and more complex and unique functions as well. This complexity and uniqueness affects the efficiency and effectiveness of the model.

While the relative wage differential will continue to be an important factor in the off-shoring equation, other factors will continue to increase in importance as the off-shoring drive continues to move up the business complexity curve.

The End of Maintenance

Service used to be a distinguishing characteristic for a company. You wanted to be known as a great service company. If you were good at it, service was also a pretty profitable way to augment both the top and bottom lines. But that was before customers figured out that they could make do with lower levels of service. Excellent service is now too expensive, and barely acceptable service has become good enough. There are many forces at work in the market, and I think they all point toward the end of maintenance as a viable service or business.

Almost all products come with some sort of maintenance agreement to start. It is normally referred to as the manufacturer’s warranty. This is the period of time after the purchase of the product that the manufacturer guarantees that the product will work. The length of this guarantee can vary and depends on several things.

The age of the technology involved, the stability of the market, the relative dominance of the consumer or the vendor in the market, and the speed with which new technologies or substitutable products are introduced, can all be factors effecting the length of the product guarantee.

Automobiles are a baseline technology that has been around for more than one hundred years. They may be becoming more complex, but their basic components still include engines, seats, wheels and the other basics. One manufacturer’s automobile is readily substitutable for another. Warranties on cars can now extend up to ten years. Manufacturers are now guaranteeing car operation for a decade. Research shows that few people actually own a specific car that long but the guarantee is there.

On the other end of the spectrum telephone companies used to require a twenty-year support guaranty from its suppliers for the products they purchased. It wasn’t initially expected that technology would change at the rate it has evolved to. High reliability and long product life cycles were the norm. Now the carriers can no longer pass along the cost of that type of product and its support to the consumers, so now much shorter product support guarantees are acceptable.

Apple has decided that the warranty on the iPhone will be one year. They have also decided that it is a limited warranty, meaning only certain service repairs will be covered, and that they may repair or replace a broken iPhone with potentially refurbished model or parts. They are Apple. If you want one of their iPhones this is what you get.

So, if the article is about maintenance, why am I spending so much time talking about warranty?

The answer is simple. Once your product comes off warranty you have basically two options for service: You can get a maintenance or extended warranty type contract, or you can hope that your product won’t break, and if it does break you can hope there will be someone out there that can fix it.

Or the third alternative will be that you can go out and buy another, or the next generation of product and then make use of the new product warranty.

I think it is safe to say that business used to be all about the best service possible. It then modified that perception and position by saying it was all about the best service at a reasonable price. It seems it is now more along the lines of the cheapest price for the lowest minimally acceptable service.

Products were engineered to the highest levels of reliability. They were not expected to break. When the product came off warranty customers were expected to purchase post warranty maintenance contracts, just in case something ever did go wrong, they would get the best support possible. Since the products were engineered so well, they didn’t break very often. Maintenance contracts were very profitable for most manufacturers.

It seems that something strange started to affect both ends of this arrangement. Manufacturers could not afford to make such reliable products in the new market. They didn’t have the time required to create them. And if they did, customers were not really interested in paying for them versus slightly less reliable, but much less expensive competitors.

There is a wireless carrier that has recognized this shift in preferences. They have a tag line that asks: “Our network reliability is within one percent of our competitor’s. Why would you pay them twice as much for only a one percent difference in reliability?”

On the other side of the relationship, customers decided that maybe reliability, while nice, wasn’t worth the premium they were paying for it. They started to examine their costs. One that obviously pops up is the high cost of maintenance. The drive started to reduce this cost.

Customers started looking a competitively provided maintenance solutions. Competitors realized that if products were reliable, they could sell maintenance cheaper than the manufacturer with relatively little risk, and still make money. In turn customers demanded that if the manufacturer was going to provide maintenance they would need to match or even better these competitive maintenance price levels.

The race to the bottom was now on.

The speed with which new products were introduced was increased. It would seem that the life cycle of products became ever shorter. Products were developed, introduced and then superseded by the next newer and improved version at an accelerated rate.

The reliability of new products diminished in accordance with the lower prices. As the life cycle, and more importantly the life expectancy of products reduced, they were no longer engineered to last a long time. It seems that they are now engineered to last only slightly longer than their warranty periods. After that, all bets are off.

Customers were more willing to accept reduced maintenance capabilities if they came at commensurately lower prices. It has often been said that we have evolved into a disposable society. What was once retained and repaired is now discarded and replaced. After all, with the new and improved version either already out, or on the cusp of availability, why would you want to repair the old one, when you can get the new one for close to, or possibly only slightly more than the repair price?

Why would you want to repair the old one, when you can get a new and improved one?

When a car comes off warranty it is six to ten years old. At this point in time it will be significantly depreciated in value. Chances are if it needs a repair it will be a significant investment verses the actual residual value of the older car. Probably better to get a new one.

When you buy your iPhone you get a year maintenance. Hopefully it will last just a little longer than that, but it doesn’t matter. The iPhone was released in 2007. There has been a new iteration of the iPhone released every year since then. And people line up every year in advance of the release to get some of the first new ones. Why would you want to fix your old iPhone when the cost of the repair represents a significant portion of the cost of just getting the next generational model?

This same approach is now finding its way into business as well. The demand for reduced maintenance costs by customers and the shorter product life cycles driven by competition are combining to eventually squeeze maintenance out of existence as a viable business for manufacturers.

It will probably become what would be called a “break – fix” type of environment. Customers will look for a warranty on a new product that is commensurate with its expected life cycle. They will probably have an extra one or two around as spares. If one breaks they will implement a spare and then do the cost benefit analysis of either getting the broken one repaired, or just buying a new one from the next generation of products.

It may take time for this apocalyptic vision of maintenance to come to pass, but I do think it is coming. The economics on both the vendor and consumer sides of the value equation are pushing it in this direction. Vendors won’t be able to afford the multiple generations of maintenance staff required by rapid product development and introduction. And customers will not be will to pay the costs of even reduced maintenance contracts if newer and more capable replacement products are rapidly and relatively inexpensively available.

I think we are heading to the point where the warranty and the life expectancy of a product are going to be very close to the same length. Any incremental life that can be squeezed out of any product beyond the warranty period will be looked at as an incremental unexpected benefit. Once the warranty expires, the break-watch will begin. If and when the product should happen to break (remember products will no longer be over engineered to last significant periods) the fix – replace decision will be made.

If it makes sense to repair it, it will be repaired. If it doesn’t make sense to repair it, it will be replaced. I just don’t think that we will see products continue to be under maintenance contracts in the future. Business probably needs to start planning for that eventuality now.

Future Jobs

This is a tough topic to tackle without sounding too trite or stale. But I now have children entering the job market and I have been continuing to do some networking with several people who are in a job search mode so it is on my mind. As usual I got to thinking about where to go and how to position for the jobs of the future. With the continual drive for cost reductions and all the talk about bringing certain jobs back on shore (as others continue to go off-shore), is there truly a way to future proof what you do for a living? I don’t know for sure, but as usual I do have a few thoughts on the topic.

It must be acknowledged and accepted that the rules of the game are changing. We must adapt or it probably will not end well. There will be those who will stubbornly hold out the hope for a return to the days when this country could manufacture and build its own products, and people could earn a living doing it. This was an ideal and golden time, but as we have all seen, there may be scattered exceptions, but by and large that economic structure has gone.

I think this was only the start. Almost every role that can be defined within an organization, can be subject to the same risk of off-shoring, out-sourcing, or whatever description you may choose to use for being moved to a cheaper labor oriented area. Production was moved off-shore because the labor was cheaper. The quality may not have been as good initially, but that can be and for the most part has been rectified. We all wanted the cheapest products possible, because they were good for the bottom line.

We have already seen instances where financial and accounting functions are being out-sourced and off-shored in the name of reducing costs. These are largely looked at as internal functions. They are usually associated with the overhead costs and functions, and as we know, everyone wants to reduce overhead. There are many people across the globe who are trained in the financial and accounting disciplines that perform these functions cheaper than they can be performed here.

We have already seen many instances where Research and Development, what was once a cornerstone of our growth engine, have been moved off-shore to lower cost countries. It seems that there are also many places with smart people who can write code and create products, with many of them working for significantly lower costs than here.

We have also seen the relocation and / or reduction of some of the Human Resource functions to other locations. Many of the repetitive steps associated with the simple recruiting and support functions can be and have been moved to lower cost countries. There has also been an explosive growth in the utilization of self-help and web portals as replacements for actual people.

Service and support is also similarly questionable. It is possible that this trend specifically associated with service may be reversing, but it is still highly probable that when you call for help or support on many products, your call is directed to an off-shore, low cost call center somewhere else in the world. People who predominantly talk on the phone as a function of their job, can have a phone to talk on in just about any low-cost country.

So, against this type of cost cutting and low cost country focus, what do we do for a living going forward?

I think for starters focus on one word: Customers.

The majority of business functions and disciplines that are at risk in being moved to low cost countries do not interface with customers.

Yes, I know that call centers and service have moved off shore and they deal with customers. And again, by and large customers don’t like it. It has been surveyed and noted as a major customer dissatisfier when it comes to support from vendors. And if given a choice almost every customer would prefer to deal with someone in their own time zone and their own country when it comes to support.

As I said, companies are recognizing what their customers want and this trend may be slowing, if not reversing as some of these service related positions return on-shore.

One of the inviolate axioms of business to business commerce is that “People buy from People”. It used to be the same for business to consumer commerce, but the internet seems to be changing that for commodity type transactions. I’ll get to that part a little bit later.

Selling will always be a function that requires direct customer interface. It will also invariably require face to face exchanges between the seller and the customer. In short, it cannot be off-shored easily, if at all.

As we continue to evolve to a service oriented economy, and as products continue to become more and more complex as well as more commoditized and interchangeable, having people who have the ability communicate specific value propositions, and more importantly be able to sell those value propositions in the new economy will be at a premium.

On the reverse side of the selling to customers, will be the implementation of the complex products and services that have been sold. It doesn’t matter if it is a good or service that has been sold. This brings us to the operations team. The reality is that most customers will not accept a “Do It Yourself” approach to the implementation of the good or service that they have purchased. They are usually going to want the company that sells it, to also be the one that puts it in.

Again, the direct customer interface from the operations team on the implementation of the customer’s purchase will be a key to that customer’s satisfaction, and potential future purchases. It can’t be off-shored and it can’t be minimized in its importance. The best product in the world can be sold, but if it is not implemented well, the customer will not be satisfied. This will be the case with both product and service implementations. Having good customer interfacing operations teams will also be a non-negotiable requirement for the future.

I have looked at specific individual customer interfacing roles up to this point, but what about broader multiple customer roles, such as Marketing?

For the most part in the past I have considered marketing an overhead function with a two-drink minimum. This is said with just a little tongue in cheek. However, if we note that individual customer interfaces are important then it is not too far a leap to expect that individual markets are important as well. Even though there is much written about the “global” economy, I don’t think that goods and services can be positioned and marketed the same way in Canada as they are in Brazil.

No one in Brazil will know what a Tuque is, and I have met very few in Canada who understand the importance of a good Caipirinha. Expecting one marketing approach to work in both regions will probably not be a good recipe for success. I do not think there will be a good or reasonable substitute for local market knowledge, cultural awareness, presence and positioning.

I suppose that the same could be said about lawyers and the specific legal requirements of each market. However, the less said about lawyers, the happier I find myself to be.

So where does that leave the organizational and business jobs of the future?

I think that it will be those outward facing, and customer interfacing roles that will be the jobs of the future. I don’t believe that customers will stand for the out-sourcing and off-shoring of them. It is the personal relationships and the trust that is built by direct customer interface that is the basis of a successful business relationship. There may come a time where that changes, but that may be in the “next” generation of business.

That means that the internal facing business and organizational roles are at risk as a function the eternal drive for lower costs. Accounting, Finance, HR (some of the functions), Research and Development and Production / Manufacturing, all to one level of success or another can be and have been sent to lower cost countries.

What is also interesting to me is that historically a little more than forty percent of CEOs that are hired come out of the finance discipline. In good times this number percentage goes down as growth is a focus and in tougher times it goes up as the bottom line takes on even greater importance. Many others come from the accounting and engineering functions as well. My point is, as many of these internal accounting, finance and engineering functions get out-sourced, where will the future leaders come from?

If these entry level (and other) types of roles and positions are sent elsewhere, where will the future leaders get their starts. It is in these roles that we learn and gain experience. If the roles aren’t there to provide the experience and jumping off points, are companies also off-shoring the development structures that the future leaders have used to get started?

This could mean that in due time, future leaders would predominantly come from those countries that the jobs were off-shored to.

The Illusion of Choice

I find it rather interesting that I read a many different articles and books from many different sources, that become the genesis of many of my own articles. This fact isn’t really that interesting, unless you consider it interesting that I read things that consist of more than one hundred and forty characters, require a certain amount grammar and literacy capability, and don’t use emojis to convey how the author feels about the topic they are covering. What is probably a little more interesting is that I like to write about business, sales and leadership, and that I rarely find the inspiration for my articles in literary sources that are purporting to be specifically about business, sales and leadership. I seem to find my thought applications from other sources that resonate at a little more elemental and hopefully timeless level.

Such is the case today.

By and large I have found most business articles to be somewhat bland and derivative of other previously written sources. They are also somewhat ephemeral and short lived. There was “The One Minute Manager” and then “The Fifty-Nine Second Employee”. Really. They all seem to be related to the idea of “get rich” or “get successful” quick sort of scheme. After all, if someone actually wrote the definitive text for how to successfully run a business or organization and get rich and successful quick, what would all the other authors have to write about?

Some of my preferred sources can go back hundreds or even thousands of years. I think I have mentioned “The Art of War” by Sun Tzu, “The Prince” by Machiavelli, “The Book of Five Rings” by Musashi and the “The Art of Worldly Wisdom” by Gracion on multiple occasions. Fortunately, my inspiration today was not from these sources, although, come to think of it some of what Sun Tzu said could apply…. I’ll leave it to those that have read both sources to comment.

Today my ideas sprung from a few words by the man who was the coach of the team that lost, yes lost, the last national collegiate championship game for American football this year. For those of you that missed it, it was on TV. I bet you can find it on YouTube. Clemson scored on the last play of the game to defeat Alabama. (I make sure to define it as American football, as I do have friends in the rest of the world where “football” is something entirely different. It is what we in the states would call “soccer”. I don’t know why.)

You would think that there would be far more to learn from the Clemson coach, the winner of the championship, than from the Alabama coach, the man whose team lost it. After all, it was an upset. Alabama was favored and was supposed to win, and it fact, almost did. There may be much to learn from the Clemson coach, but those lessons may not apply to business, sales and leadership as well as what the leader of the Alabama team had to say. At least for me in this instance.

Coach Nick Saban, of the University of Alabama has enjoyed sustained success in his field, the likes of which has probably not been seen in decades. He is successful. He has already won a total of five national championships (across 2 different schools) and is annually expected to be a contender for the next championship playoff. He is the example and standard of what every other coach, school and leader wants to be and do.

But he still lost, last year.

When he was asked what he is going to change, and how much he was going to do different next year in order to win the championship, he responded with what can best be described as an old school response.

He said that he understood all the new offenses, defenses, systems and processes that are out there, but that he was not going to overhaul a system just because he had lost in this year’s championship game. He came in second out of three hundred and seventy-five schools, which when thought of in that way, wasn’t really too bad. Yes, the loss hurt, but there are literally hundreds of other schools and coaches that would have wanted to be there in his place. He understood what it took to get there, and he also understood what it would take to get back next year.

It was at this point that he made the comments that resonated so strongly with me. He discussed that having learned what it took to be successful, he learned that there are no short cuts. He referred to it as “the illusion of choice”. He said that so many people want to make the easy decision, or take the supposed easier road to success. A new process, or a new system were the quick cure. He said this was an illusion. If you wanted to be successful (in his profession) there really were no choices.

It required the recruiting of the best talent available. Alabama’s recruiting classes of new freshmen out of high school are routinely viewed as some of the best in the country. Think about the fact that every three to four years, he (like every other college football coach) has close to one hundred percent turnover of his team. But every year he contends for a championship.

It requires a work ethic that is second to none on his part, and it has to be transferred and translated to the rest of his staff and the players on the team. There can be no illusion that talent is enough. It takes hard work and dedication. There is a base line process and preparation that needs to be adhered to.

Many have heard me discuss my aversion to the perceived over-utilization of process that seems to be plaguing businesses today. Yet here I am praising it. Here process is used to prepare the team. They have practiced and been trained on how each individual need to prepare, perform and act as part of the greater team. A process is not used during the game or against the competition. If so the competition would quickly adapt and defeat it. There is a game-plan, but not a game process.

He assembled the best staff possible, that he vested with the authority to get things done and that he held accountable for those various aspects of the team (Offense, Defense, Special Teams, etc.) he had assigned. However he only held himself responsible for the outcome. He never blamed anyone else. It was his responsibility.

It was this litany of decidedly unglamorous basics that he pointed out were responsible for getting him and his teams (multiple, different teams) to arguably the acme of his profession. He pointed out and reiterated that there really was not choice if you wanted to be successful. It took talent, it took outworking the competition, it took everybody’s commitment and buy-in for the team succeed. There were no “get rich” or “get successful” quick schemes.

That didn’t mean that he wouldn’t change and adapt. He is also recognized as one of the best leaders at innovating and modifying his game plans when his team’s talent, or the competition called for it. He has noted that the basics of the game have not changed, but how you apply them can vary greatly in each situation.

As I noted, by design his team membership turns over every four years. He also turns over his leadership (coaching) staff with significant regularity. His assistant coaches are in high demand to become the leaders at competing college programs because of their success and what they have learned. No less than seventeen of his assistants have gone on to lead their own programs.

It looks like the players are not the only ones that are mentored, taught and become leaders.

Sun Tzu, from almost twenty-five hundred years ago, also talks about talent selection, training and preparation as immutable keys to an organization’s success. He is also quick to point out that flexibility and the ability to adapt to new and different situations, and to be able to take advantage of them while either in or on the field are also the keys to success.

It looks like the idea of putting well trained teams in the field and letting their leaders lead them is in fact an idea that has been around for over two millennia. It sounds to me like Nick Saban may be right when he says that if you want to be successful, and enjoy a sustained success, it really is an illusion of choice. While a new process or system may come into vogue, success is really built on the basics of talent, hard work, and planning, and then letting your leaders lead, and not relying on the illusion that some other process or system can be a substitute for one of those basic building blocks of success.

Organizational Chemotherapy

One of the most hackneyed, trite and stale topics to talk about in business is change. Of course that is all the more reason for me to talk about it. We all know we need to change. This is a given. I do not think there is one person out there that could not identify something associated with their occupation, or some aspect of what they do, that needs to be changed. If that is truly the case, I think the greater question associated with change is not what to change, but how and when to change it.

I recently read an article which featured a discussion with Mark Cuban, the owner of the Dallas Mavericks NBA basketball team and erstwhile member of the board on the television show “Shark Tank”. I am neither a particular fan of the Mavericks (I prefer the Dallas Stars hockey team), nor do I watch the Shark Tank, but I was intrigued by the article. Mark Cuban is known for speaking his mind quite often, or at least he appears to speak his mind quite often based on the media coverage he receives, and upon first blush this particular article didn’t seem to be any more important than any of the other myriad of times that he has chosen to speak up.

I guess I speak up quite often too, but since I neither own a professional sports franchise, or appear regularly on TV, there are not nearly as many media articles that cover what I have to say or write. Therefore, I seem to have to write my own.

I guess having a couple billion dollars can influence the media’s opinion of you. Go figure.

Mark Cuban, while appearing on CNN’s “New Day,” morning infotainment, talk show and celebrity-fest referred to President Donald Trump as “political chemotherapy” for the system. He then went on to explain the genesis of the term was from one of his “smart friends” who said:

“Mark, I’ve voted for politicians my entire life. Do you know what the definition of insanity is? Doing the same thing over and over and expecting different results. So I voted for Donald Trump. Is he poisonous in a lot of respects? Yeah, this is out chemotherapy. We hope he’s going to change the political system. And if that’s the way you’re evaluating Donald Trump, he’s doing a phenomenal job.” (

I am in no way or form going to get into any discussions regarding politics or the relative values, or lack of values of any politician. I am merely interested in the term “political chemotherapy”.

Using this example, I would extend Cuban’s example to the professional environment in that when an organization or business continues to do the same thing and apply the same process over and over again, and does not seem capable of doing anything else, but continues on hoping for a different result, it would seem that it would also become time for what I would call organizational chemotherapy.

And indeed, we often see that this as the case when it is finally recognized that there is a need for a change of direction within the organizational system. This change usually comes in the form of a new business or business unit leader, usually from outside of the stricken organization, who is brought in. Since they are not beholden to, or vested in the existing processes or structures, it is their role and responsibility to be the change agent, much like chemotherapy, that changes the way the existing business system is operating.

I do not seek to minimize or reduce the hardship that people must go through when they are forced to endure chemotherapy. Everyone I have spoken to who has gone through it, and everything I have read about it indicates that it is as an unpleasant process to endure as can be imagined. Having to ingest a proscribed list of toxic and poisonous chemicals into one’s system on a regular basis for the purpose of eradicating items that if left unchecked will destroy the system, cannot be thought of in any sort of lighter terms.

I am however interested in the analogy that was drawn by Mark Cuban’s friend to the political process, and the similar analogy that can be drawn to the business process and organization.

It seems in both the political system, as well as in the business system, it sometimes takes the injection, or introduction of something that can best be described as a known toxin into the system to get the system to change. This usually occurs when it is recognized that if left unchecked the system can become, or may have already become somewhat compromised, and are unable to correct themselves. The inertia of the organizational and business process in these cases, once compromised are almost impossible to correct from inside the system.

Almost all business systems are risk averse. It doesn’t matter what the organization says. It doesn’t matter if the organization claims a culture that rewards risk. Almost all business processes are created to reduce risk. And one of the greatest perceived risks to business is change.

Change in business requires the system to do something it hasn’t done before. It can be small or it can be large. Regardless, it will be resisted. Over time the resistance to change will become ingrained into the system. The resistance to change can almost become a process unto itself. This point is usually achieved when the stakeholders in the status quo structures and processes have neither the authority or inclination to “buck the system”.

The perception in the organization evolves that the return for the risk of challenging the system is lower than the potential penalty for the continued less that optimal performance under the current methodologies.

This is the point in time for the organization, when it will probably take nothing less than business chemotherapy to force the system to change. There will probably be both good and bad effects associated with it. A stable if underperforming system will become at least temporarily unstable. There will be uncertainty and risk for the members of the organization as they must change what they do and adapt to the changes being imposed, or face exiting the system as part of the corrective solution.

One of the side effects of organizational chemotherapy is that like its sourcing namesake, it doesn’t specifically correct the system. It is actually designed to remove something that is detrimental to the system. While similar, they are in fact two distinctly different actions. It hopefully allows the treated system to return to its normal, more healthy performance level.

I think we have all seen high profile instances of organizational chemotherapy. I have actually lived through one, where a CEO was brought in specifically to change and remove a “good old boy” culture that was hampering the growth and evolution of the organization. It seemed he was successful beyond even the board of director’s expectations in that he seemed to alienate everyone including the board that hired him, and he genuinely seemed to enjoy those aspects of his role.

The issue was that once the culture had changed, there was not a new beneficial system and process available to put in place to replace the old one. The CEO knew how to remove what was unwanted, but did not know how to replace it with what was desired. The company began to falter and performance began to fail. The board then had to step in again and replace the chemotherapy agent with a new CEO who rapidly built back up a new culture based on merit and performance. The company then took off.

The progression was one of starting with an organizational system where performance was secondary to “who you knew” or were politically aligned with; to one where it was essentially toxic to be associated with the old system and regime, but again where performance was secondary; to one where performance and merit were moved to the forefront.

It took approximately three years from when the chemotherapy CEO was installed to when he was replaced. And this represented three distinct organizational systems and processes. It was also interesting that as the solution to the first cultural problem, he only knew how to remove the problem. He did not have the capability to implement the desired final solution for the organization. He focused on his strength which was to remove the undesirable aspects of the original organization. It took someone else with a different skill set to rebuild the new system.

Organizations have a tendency to want to drift into comfortable, known and reduced risk structures and processes. It takes careful stewardship and an eye on the future by the organizational leader to continue to drive a balance between acceptable risk, challenge and new directions, and the continued implementation of risk reducing processes and decisions.

Regardless of how hard an organization tries, it continues to be exceedingly difficult to violate or even change the Risk-Return economic equation. As an organization constrains itself with the drive to reduce risk, it also by necessity also reduces its related opportunity for gaining an acceptable return. Invariably the solution to this issue is for the organization to try and implement even more of the constraining systems and processes to address the new issues, which in turn creates even more organizational drag.

At some point it becomes apparent that a chemotherapy type solution will be required to change the self-defeating process constraints. As shown in the above example, organizational chemotherapy may solve the current problem, but it needs to be closely monitored, because correcting the current set of problems is in many instances not the same as creating the desired final solution and system.

The Review Process

I got to thinking about all of the reviews that I have had the pleasure of sitting through, or have been sentenced to, as the case may be. Both the ones that I conducted and the ones that I just got to attend. They are a sometimes interesting, and sometimes not so interesting mix of development, product, marketing, finance, sales, operations and ultimately business reviews where there was a little of each of the previously mentioned disciplines covered. They have ranged in length from the relatively short one hour to the interminably long multiple days in length. I have traveled internationally to attend, present or conduct them as well as done the same over the phone. Throughout all of these reviews, the most important thing that I learned is that it is up to the review leader, not the review process, to make the review useful.

I think it is reasonably apparent that no one likes to be the bearer of bad news in a review. We all like to feel that we can and should be able to march triumphantly into the review and present as well as receive only good news. Schedules are being met. Sales are up. Earnings are good. Enough said. Take a bow. Let’s get out of here.

Admittedly I have been in only a few reviews like that, very few.

However, most of the time I have found that a review usually contains some good news, some bad news and more than a significant amount of extraneous information. Extraneous information is the information that is presented about the activities conducted by the presenter, that are other than the assigned topics that they were given to present on. Extraneous information is what fills up the extra charts and time in almost every review. It has evolved to almost become and expected part of the review process.

I think this might be another opportunity for the coining of another one of the specifically not famous “Gobeli Laws of Business”:

“If allowed to go unchecked the amount of extraneous information that is included in each successive periodic review will grow to a point where it renders the review almost useless.”

Since everybody likes to present good news, and since not all news is good news, people will almost always try and compensate for any possibly perceived bad news in a review by presenting more and more other extraneous information. This information, while possibly interesting to the presenter, and is usually positioned to sound like highly functional activity levels and good news, while in reality it is likely of limited use to the person conducting the review.

This type of information distracts from and obfuscates the important information to be imparted at the review, while continuing to maintain the appearance, flow and process of the review. Unless it is specifically cited and prohibited, almost every presenter at a review will probably include some of this type of information “filler”. The result will be overall less time available to deal with any potentially germane or relevant review topics.

I think I have mentioned before that I matriculated through management within the General Management business model as opposed to the seemingly more in vogue Process Oriented business model of today. It seemed then that objectives were mandatory and processes were guidelines as opposed to the current structures where the reverse seems to be the rule. Ownership of an end to end deliverable objective made reviews that much easier. Progress against an objective is always easier to measure than progress on a process.

The purpose of objective oriented reviews is two-fold: the avoidance of surprises, and the identification of actions for the resolution of issues. They are not and should not become opportunities for everyone to tell everyone else what they are doing.

One of the first rules of business is that there should be no surprises when it comes to performance. Everyone should have an objective, know how they are doing against that objective and be able to succinctly report that information. This approach should be applicable to every business discipline. There can be no excuse for “surprise” misses to sales targets, or budget overruns, headcount and staffing levels, profitability, etc. Providing this type of information is the responsibility of the review presenter.

Once a potential issue or objective miss is identified in the review, a plan of action to bring the objective miss back under control should be the next function of the review. A specific set of activities, and activity owners need to be identified and assigned. Performing this type of function is the responsibility of the review owner. Notice that I didn’t say solving the problem is the review owner’s responsibility. I’ll get back to this point later.

I think this also might be another opportunity for the coining of another one of the specifically not famous “Gobeli Laws of Business”:

“The best type of issue to have in business is one that you prepared for, and avoided.”

This is the focus of reviews. To enable the team to foresee, and take action to avoid issues associated with objectives. It should be with these review objectives in mind that reviews are conducted. If the material covered does not directly apply to these objectives, it should not be included.

There may also be a secondary focus on understanding the cause of the identified issue so that steps can be taken to avoid similar issues in the future, but I have found that these types of root cause analyses should probably be taken outside the review. This has the benefit of keeping the review to a shorter more manageable length, as well as minimizing the impression among all attendees of creating a negative environment for reporting issues.

Everyone has issues at one time or another in obtaining their objectives. A public examination of why they missed as opposed to a public plan on how they can recover will usually generate a more conducive environment where issues are identified and discussed as opposed to being glossed over.

If a review is allowed to become a matter of process, where the purpose of the review is lost in the extraneous information that each presenting group imparts to the other presenting groups detailing all the activities they are doing, but precious few of the issues they are encountering, then its value is lost. They should be times to challenge both management and each other. They are opportunities to do better.

I always looked at reviews as opportunities for the team to suggest solutions to issues. Issues are to be expected. Field Marshall Helmuth Karl Bernhard Graf von Moltke, who was Chief of Staff of the Prussian General Staff in the mid nineteenth century is credited as saying:

“No plan of operations extends with any certainty beyond the first contact with the main hostile force.”

This has also been simplified and paraphrased down to:

“No battle plan ever survives contact with the enemy.”

What this means is that once you start the implementation of anything, stuff happens that requires you to adjust both your plan and the way you implement it. In short, issues occur. And how you deal with them will directly affect the success of the endeavor and the achievement of the objective.

The sooner the issue can be identified, and the more information that can be supplied about it, the better the resulting response can be.

This again, should be one of the driving goals of the review. Everyone wants to avoid issues. The best way I know how to do this is to get them identified as early as possible and then take the requisite steps to mitigate, and hopefully avoid them.

I think the hidden key to the review is that each reported or identified issue needs to be accompanied by an associated solution. It should not be the review leader’s responsibility to solve all the issues. This is a situation that seems to have evolved in a process driven organization, in that it is usually only the leader that has purview over the entire system. Hence any issue associated with any step falls to them to resolve.

In an objective oriented review, it should be the responsibility of each individual that identifies an issue to also provide a suggested course of resolution. They are the ones who identified the issue. They should be the ones closest to it and in the best position to affect its resolution.

It will be the leader’s responsibility to accept, reject or modify the recommendation. It should not be the leader’s responsibility to generate the recommendation.

It seems more and more common that reviews are becoming just another step in a process. A box to be checked off. They seem to have lost some of their true purpose. That is a shame.

I have been in plenty of reviews where the time was spent and the motions gone through, and not much else was accomplished. But I can also remember many of the reviews where issues of substance were identified and dealt with. Where team members got to display their leadership capabilities when it came to solving their own and others issues. And where things got done.

They were challenging reviews where performance against the objectives was reviewed, hard questions were asked, and answered, and where the results were what drove the process.


I read an article the other day by Stephanie Vozza in “Fast Times”. ( ) It was one of their “4 Minute / Work Smart” articles. I normally am not too inclined to read these types of articles, but for some reason I did read this one. While it was ostensibly about why employees at Apple and Google are more productive, there was a passage in it that both resonated with me, as well as rang significant alarms. It captured what I have been feeling, and writing about regarding business and leadership in such a succinct way that I felt I had to address it. In her discussion regarding Organizational Drag, and the associated costs and losses to business due to processes, Vozza said:

“This often happens as a company grows, as the tendency is to put processes in place to replace judgment.”

Wow. I think she hit the nail on the head. Process is implemented to replace judgement. I do think there ought to be a qualifier in ahead of that last statement such as “Most processes, when over implemented…”. Many processes when implemented as guidelines do provide a needed and efficient methodology for accomplishing repetitive tasks. It is when they are over-expanded, applied and relied on for all facets of an organization that they cause drag and sap judgement.

A quick Googling of the word “judgement” provides the following definition:

“the ability to make considered decisions or come to sensible conclusions.”

Let’s tap the brakes here for a minute. Are we really saying that we want to replace people’s ability to make considered decisions, or to come to sensible conclusions with some sort of follow by rote process? Isn’t judgement one of the key attributes of business leadership and business stewardship? And not just judgement, but good judgement.

There are a lot of people who have said something along the lines of:

“Good judgment comes from experience, and a lot of that comes from bad judgment.”

Will Rogers, the American humorist said it in the 1930s. Simon Bolivar, one of the great heroes of the South American Hispanic independence movements of the early 19th century, said it in the early 1800s. I think you get my point. A lot of people have talked about the need for, and how you get good judgement. We would all like to think we were just born with it, but that is usually not the case.

The primary method of gaining good judgement is to learn it through experience.

So, again let me get this straight. It seems that by implementing so many processes to avoid the potential costs associated with errors and bad judgement, businesses are both creating the incremental expense of organizational drag that Vozzie noted, as well as removing the opportunity for team members to practice and gain good judgement through the experience of learning.

I don’t know about you, but I came up through business hearing the mantra surrounding management’s desire that we take (reasonable) risks in our efforts to improve the business. This is in line with the risk and return economic model. This model would require the use of judgement to ascertain what the contributing factors to the risk were, and did the expected return justify the business decision in question. The process oriented model would remove these opportunities.

Process, when used as a guideline and milestone marker can be a powerful tool. It seems that whenever it goes beyond this and starts generating ever finer detailed steps, is when it starts to generate issues both in terms of organizational drag, and what I think is potentially the greater long term risk, the stunting of leadership growth.

The Fast Times article mentions the total cost lost to organizational drag associated with process at approximately three trillion dollars. That’s a three with twelve (count ‘em, twelve) zeroes behind it. This seems like a relatively expensive price to pay to avoid whatever the number of errors associated with bad judgement (the learning process) and the costs that they would generate. One would suspect that by just flipping a coin one would hope to be correct on average at least half the time.

By removing judgement in favor of process future leaders are no longer able to get the experience (and judgement) that they will need as they move into leadership positions. The process experience that individuals gain in its place may be useful in a more predictable or production line type organization (secondary type economy sector – producing finished goods, e.g. factories making toys, cars, food, and clothes), but as the economy continues its evolution further into a tertiary sector (offering intangible goods and services to customers) I would think that judgement, and in particular good judgement would not only be preferred, but a necessity.

I think one of the ways to deal with the “Process versus Leadership” issue may be to dial back the drive for process just a little bit. I think we have all heard the adage that if a little bit of something is good then a whole lot more of it should be better. I think we are all aware of the fallacy behind that type of thinking as well. But, it appears to be the creeping mind set of many companies as they grow in size and expand across different geographical and technological markets.

It is all too seductive to aspire to manage all sorts of diverse markets and technologies via standardized processes. If it worked once in one place it becomes a goal to make it work every time in every place. Once that process starts it appears to be a slippery slope of incrementing just one more step in each process to take into account each new business or market variation that must be dealt with. The desire for repetitive and interchangeable processes leads to both product and market biases that can result in multiple missed opportunities as well as the organizational drag that has already been noted.

I think leaders may need to start thinking of the drive for processes as points on a scale. On one end of the spectrum there is a fully structured, process oriented organization. This would be an organization where very little judgement is required, the function or market are stable and little variation is required.

Accounting comes to mind, but that might just be me.

On the other end of the spectrum would be a completely judgement based organization where each new opportunity is unique and would require its own new set of potential processes for implementation. I am sure there are other examples, but organizations that conduct search and rescue operations along the lines of the freeing of the trapped Chilean miners in 2010 might be a good example of such a unique organization.

Obviously, in reality most businesses lie somewhere between these endpoints. There will most likely be multiple organizations within the business that are distributed along the process – judgement scale. What concerns me is that as process continues to be implemented in greater detail and into new areas, business run the risk of both alienating their current leaders in that their judgement will no longer be desired, and hampering the development of their future leaders as the opportunities to gain judgment are replaced with the continually more complex process.

Businesses need to begin learning to resist the desire to replace judgement with process, and understand that there needs to be a balance between the two. Just as many organizations seem to have a built-in resistance to change, they also seem to have a built-in desire for predictability which process seems to satisfy.

However, nothing comes without a cost. The implementation of process can create a stable, repeatable, predictable organization, but its costs can be seen in the organization’s inability to quickly respond to changing conditions, the resulting costs associated with organizational drag, and reduction in the use and availability of good judgement.

The Short Horizon

As the pace of business continues to accelerate, there seems to be one aspect of the business process model that is struggling to keep up: The Business Case. There was a time where capital expenditures were looked upon as long term investments by the business. The life-cycle and pay-back processes, as well as the accounting amortization of these investments, were expected to last years, and in some instances, even decades. The average business case became attuned to these norms.

But those days are long gone. As the speed with which technology has changed has continued, by necessity the business case used to justify the new or incremental investment has needed to become shorter. If Moore’s law of eighteen-month capability doubling (it was actually Intel executive David House, who predicted that chip performance would double every 18 months. Gordon Moore, for whom the law is named, was the co-founder of Fairchild Semiconductor and Intel, and whose 1965 paper described a doubling every two years in the number of transistors per integrated circuit was the basis for the coining of the “law”) is to be believed, then the asymptote for the length of an acceptable business case should approach that eighteen month to two year limit as well.

That doesn’t mean that a product’s useful life is only limited to eighteen months. I think quite the contrary. There are aspects of the Public Switched Telephone Network (PSTN) that have been in place for more than fifty years, and are still providing beneficial service to the communications carriers and their subscribers alike.

On the other hand, people are known to line up and over-night camp out every eighteen to twenty-four months in order to be the first to get the next generation of the Apple iPhone.

It appears that customers who are being asked for either capital or operational expenditures associated with technology oriented products, are driving their partners and their vendors to ever more rigorous and aggressive value propositions and rates of return. This is the genesis of the short horizon business case.

The simplest definition of value is how much money is made or saved over what period of time. The more you make, or the more you save over a given period, the better the value. In the past it was acceptable for a business case to extend out over a long enough time period as to show an acceptable return. If the initial business case for the sale didn’t make sense for one period of time, it was easy just to lengthen out the time frame until it did.

What appears to be happening is that as the rate of technological based product change has continued at the speed of Moore’s Law, the period that a customer is willing to measure value has shrunk. Business cases still need to show the customer value, they now must do it in far less time. The tried and true form of extending the business case period to make the value and pay back equations work is now gone. Customers will no longer accept it, and are driving for shorter and shorter review periods.

I think there are several factors in addition to technical obsolescence that are helping to drive a short horizon on the business case:

As each new generation of technology arrives it almost exponentially drives down the (residual) value of previous generations. I think it is no secret that one generation old technology is viewed as old and disadvantaged, and that two-generation old technology is probably approaching the zero value state. We have all seen this in our consumer based technology purchases as well. Products get old so quickly that we have developed a disposable attitude toward them. With Personal computers now going for a few hundred dollars, what is the value of a two-generation old computer? What was once repaired and retained is now simply expected to be replaced.

How would consumers (and manufacturers) react if the same logic was applied to say, automobiles and two to three model year old car was considered almost valueless?

We also see (comparatively) decreasing operational returns as each new technology generation is introduced. This means that as each new product gets smaller and more efficient the value of generating operational savings associated with the previous generation of product also tends to get devalued.

The idea of saving something with what you have is not as attractive as the possibility of saving more with something new. I guess this is what they call “Marketing”.

I think one of the final evolution’s of the short horizon business case is the “Cloud”. I am sure everyone has heard of this thing. It’s in all the magazines.

One of the many ways that manufacturers and vendors have adapted to the evolving business case rules is to try and remove both the obsolescence associated with technology and to more closely align the delivered solution with the customer’s need. The idea being that if a customer only needs a four-unit solution but the technology only comes in six or eight unit increments, there is a delivered solution miss-match.

By delivering a function from the cloud as opposed to a product based solution, the vendor has effectively removed technology obsolescence from the customer’s decision process, as well as matched the required amount of solution with the required amount of need.

The net result is a much shorter period needed to achieve the required business case. Customer purchases can be made in smaller increments, which in turn only require smaller pay-backs. Future product purchases and existing product obsolescence are removed from the customer’s decision criteria as the customer is now only purchasing the product’s function, not the product itself. The obsolescence issue, and all the other costs associated with operation of the product are now retained by the vendor (and should be built into their business case).

The continued drive for more value has driven customers and business cases to the short horizon. Capital for technology can no longer be viewed as a long-term investment. It must be judged and justified by how quickly it can pay back on its cost and the relative business value it generates. It is this drive for better business returns that continues to reduce the time scale associated with the business case.

This trend would appear to potentially be a seed cause for future changes to the way business is conducted. On one hand it will continue to make the sale of capital based technology products more difficult. By demanding shorter pay-back and business case periods, customers are in essence expecting lower prices for products, and higher value delivered. That is a demanding and difficult environment for any supplier.

It should also continue to drive product virtualization and the Cloud as ways for suppliers to retain costs and risks, and hence remove them from the customer’s business case. This will continue to be an interesting market, but not all technologies and products may be potential candidates for the cloud.

It could also be argued that a potentially unexpected result of the drive to align business cases with product life cycles could be the reversal of Moore’s Law. It has long been expected that there is some sort of limit to the capacity doubling process. It has been going on for over fifty years. There are recent articles in no less than the MIT Technology Review, Ars Technica, and The Economist (to name just a few) that are now stating that Moore’s Law have in fact run its course.

And this may also be of benefit to business. If customers want to align their capital business case length with the product’s life cycle, and the current eighteen to twenty-four month life cycle of the product makes this increasingly difficult, then one of the solutions may be to lengthen the product life cycle to more than twenty-four months. If there truly is a link between business case length and product life cycle, then this could be a possible solution.

This will be an interesting cause and effect discussion. Is the potential slowing of Moore’s Law going to cause the reversing of the short horizon trend associated with customer’s business cases, or is the demand for short horizon business cases going to accelerate the slowing of Moore’s Law due to business necessities? Either way, customers are requiring businesses to change the way they put together the business case for capital technology sales, and that is having a significant effect on how business can successfully get done.