Analytics header

Wednesday, February 11, 2009

Hope and Denial and why does it really matter?

In these testing times feelings and emotions run high as people deal with the implication of the financial crisis on both a personal and professional level. One of the many ways that I hear from people is to keep hoping for the best, to hold on, and hunker down so that we will hopefully survive the crisis. The question is: is it not the same as being in denial? Would it not be more effective in the long run to be to take a realistic approach and look the situation in the eye – if you will? I suspect that it may be fear that is driving this behavior. People tend not to show hesitation or lack of hope because it may be percieved as if they have admitted defeat - and that will surely lead to failure. Therefore they rely on a goal setting approach to help drive hope, hope for a bettering of the current circumstance.

However I believe that sometimes this hope may be based on goals that have been set with little regard to the current circumstances and may in fact be the driver for failure. The fundamental problem is denial of what is really happening. In any situation a healthy dose of realism is always needed. We need to both understand the circumstances that we are facing and use this knowledge to navigate towards realistic future goals. We have to be realistic in assessment of a situation in order to truly understand the risks. 

Hope is effectively used by leaders to motivate and inspire people. However this hope has to be based on something substantial. Hope with no grounding in realistic goals has achieved very little. Look no further than the current economy. “This could not happen to us” – they said. Well it did, because the only thing that they had was hope – hope that the bubble will not burst.

People will not follow blindly just on hope and if they do then it usually is detrimental. So what does all this have to do with product management leadership? I have over the last decade experienced time and time again, through multiple positions, this blind quest of companies to grow on false premises grounded in denial of the real market’s situation.  They operate companies based on hope of better times and more market share. While the notion of better times is mostly always true, if you look far enough in the future, it is subjective. The sizing of a market is another one of these elusive quantifications that like statistics can be crafted to support a certain viewpoint. In the new approaches to product management it is important to have a deep understanding of the market, the people that you are marketing to and obviously their needs. Once that understanding is achieved the quantification of the market size becomes much easier. However sizing a marked before gaining an understanding of it is not only dangerous but it is denial – a false assumption that is based on a hope that it is really there. As David Meerman Scott just recently reminded us in his blog post “people just want to do business with people”.

Some markets are well defined - like the diaper market. There is a finite number of screaming toddlers that require these paper based collection devices to keep them sanitized. Yet if we do not understand the market enough we may base strategic product decisions on a hope that the market will increase in size – maybe there is unexplained excremental yield amplification due to organic baby foods (that was a joke). This is of course a gross simplification and markets are rarely as static or as simple as that. Yet the lesson is that based on an understanding of a market one may and should come to a conclusion if there is (or not) a market size to base the growth of future business.  As product management leaders we always hope that our product will be successful – the next big thing. However we all know that in order for that to happen we need to base the product plan on real market needs – yes realistic market needs. Not needs that we assume the market has because we have developed unrealistic what-if scenarios.
 
The famous saying “Hope for the best and prepare for the worst” embodies this relationship between hope, realistic and adversely denial. Denial is when one only hopes with no preparation grounded in the reality of current and future circumstances. A healthy dose of realism is always good medicine. The test of true leadership is the ability to be realistic. Yes plain and simple, be realistic while at the same time being able to inspire and motivate towards a goal that we all hope will bring better times. Like my wife always tells me when pondering the question: “what will you do if you win a million”? If you are dreaming - why not go all the way, let’s buy an island in the Caribbean, and get a beaming device that can get us there in a matter of seconds. I can only say that I hope that it may be true, but it is just as unrealistic as winning the million in the first place.

Thursday, January 1, 2009

What to do with the politics in systems implementation projects

In the past few months I have been involved in software implementation projects for some big life science companies. It has been a while since I did this type of role so it has been somewhat of an experience getting back in the swing of things. The fact that I have returned to what was once familiar territory gave me a chance to reflect on some peculiarities and phenomena in these types of engagements, one of which as everybody surely knows is politics. In every such situation I really try to understand the pros and cons as well as the causes of these phenomena. 

Let me start with the good things. In a way politics forces the people involved to seek consensus. This process involves a lot of discussion in which the solution and the problems are reflected on with many people providing input. Ultimately this can lead to, in certain situations, to alternative and possibly better solutions. Another result of these “political” discussions are of course the fact that you get to dig into the detail and thus uncover certain aspects of the problems that would have been found later in the process, at a time where design decisions are more costly to undo.
When working in such environment I find that everybody is trying to get as much detail covered as possible. There is a feeling that we need to get all the details hashed out before we move on. Obviously this is result of our “systems theory” upbringing. By that I mean that the way most people, with technical backgrounds, learned to tackle complex problems is by a process of functional decomposition in which the problem is taken apart to an atomic level in the analysis process. 

The underlying assumption for this approach is that everything is known and that from the time the decomposition is performed the “system” will never change again. Both of these assumptions are of course false. We will never be able to uncover all the required detail and once we have most probably the details are irrelevant because the circumstances have changed.

The approach that I usually take is grounded in some of my earlier work understanding complex adaptive systems and Holonic systems or in other words systems that are in chaos. I will leave the detail out at this point and you can read more in some of the other posts on this topic. The bottom line is that in order to be most efficient one has to strive to identify recognizable patterns that may indicate possible problems and solutions. This of course takes a lot of experience and becomes kind of an art to know exactly when enough detail has been gathered to move on. However it is not "rocket science" nor does it require any special natural abilities. All that is required is the ability to embrace a radically different approach at problem analysis. In a way one has to learn learn new tricks -  which of course may be hard for old dogs.

So back to politics…. Obviously the bad part of a politicized process is that it is inefficient, and much time is spent dancing around making sure that everybody is ok with the compromise that regardless of what people tell you will always be part of the solution. Also a lot of time is spent in typical CYA maneuvers, which is also something that will never be admitted to, yet it is human nature. I guess some can draw a parallel to survival instincts. 

The art in of all of this is achieving a balance that like most things in life is important. The approach has to be holistic in that the project has to be embraced with not only the technical detail but an understanding of the social aspects of the project. Looking at implementation projects in this way is no different than a study in social interaction. A balance has to be achieved between autonomy of the individuals, manifested by their personal motivation and goals (political or otherwise) and the goals of the project to effectively provide a system solution. By the way this is exactly the definition of a Holonic system, which leads me back to art of identifying patterns and using them for problem definition and solution design, rather than the traditional functional decomposition approach. On an end note, politics will always be part of any project, it is inherently how we interact in a social system, and it is not necessarily all bad if you understand the causes and use these to your advantage.

Wednesday, October 22, 2008

Death to the Performance Review!

I came across a blog post on the Lean Blog about “Professor Channels W. Edwards Deming and Writes "Get Rid of the Annual Review” that comments an article in the Wall Street Journal by Dr. Samual Culbert, a Professor at UCLA Anderson School of Management. The premise of the article is that 

“It [Performance Reviews] destroys morale, kills teamwork and hurts the bottom line. And that's just for starters.”

Amazing, finally somebody has successful articulated exactly how I feel and what I want to say after every performance review that I have ever experienced. I am sure many of us have experienced this inexplicable sense of anguish, desperation and “I am not good enough” that follow the days after a performance review. It doesn’t matter how many positive and how many “great”, “excels in”, and “could not do without you” comments you get. We always focus on that one “needs improvement” or “could do better” comment that is probably in there, as Prof. Culbert points out, to justify the pay increase (or not) that has nothing to do with your performance.

“It isn't, "How are we going to work together as a team?" It's, "How are you performing for me?" It's not our joint performance that's at issue. It's the employee's performance that's a problem.”

I believe that the practice of performance reviews is in fact a symptom of lacking leadership skills. In this modern age we love the new shiny tools, and the diet pill. There is no substitute to the social interaction and personal sacrifice that a leader needs to exert in order to create a winning team. Dr. Culbert points out, which is so much in line with my experiences - it brings a chill to my spine:

“Instead of energizing individuals, they are dispiriting and create cynicism. Instead of stimulating corporate effectiveness, they lead to just-in-case and cover-your-behind activities that reduce the amount of time that could be put to productive use. Instead of promoting directness, honesty and candor, they stimulate inauthentic conversations in which people cast self-interested pursuits as essential company activities.”

When lacking skill we naturally look for tools as a substitute. If you don’t know how to fix a car, then it certainly will not help to use the expensive wrench. The scary part here is that there are even software tools for this! You need to acquire these skills and expertise, which in the case of leadership requires both years of experience and some fundamental personal traits that not everybody has. 

As Dr. Culbert also points out we love to measure, yet measuring requires some kind of baseline.
 
“In almost every instance what's being "measured" has less to do with what an individual was focusing on in attempting to perform competently and more to do with a checklist expert's assumptions about what competent people do. This is why pleasing the boss so often becomes more important than doing a good job.”

We love quantifying for many reasons, but it does not work for everything, especially when it comes to leadership and team work. It is another example of “Quantifying the Unquantifiable”.The end results are much more destructive than they are helpful or performance enhancing. Mark Graban points out in his blog post that this is very much in line with the teachings of Dr. Demmings. Demming in fact pointed out: 

"Running a company on visible figures alone is one of the seven deadly diseases of management. "

I have had this blog post bottled up so long that just finally writing it feels good. Thank you for the inspiration Dr. Culbert, I am now officially a fan!