Wednesday, July 2, 2008

On-line collaboration experiment

Last week I posted a question on LinkedIn and received a significant amount of responses. My reason for posting the question was threefold:




  1. I was curious about the answers I would receive


  2. I wanted to see the quantity and quality of responses it would generate; and


  3. I wanted to test the medium to see if it was a useful online collaboration platform for brainstorming


Well, I received a large amount of replies to my question (17 in two days). The questions are open for a week so I expect they will continue to trickle in from this point on. I asked the respondents to each provide their top three points so that means I generated a rather lengthy list of 51 points in very little time and effort. Many of the points were the same or similar, so after removing duplicates, the list was narrowed down to 38, which can also be an indicator of the quality of the responses given that some themes are definitely recurring and there don't seem to be any out in left field. So far so good. But now what to do with this rather long list? The best thing would be to find a way to get participants to vote or rank the points in order to come up with an ordered or prioritized list (we often use multivoting techniques in projects, so if this could be done online, it could be a real project team timesaver...). So there is something missing in this regard. To compensate, I have posted the list in Google Docs. This will permit collaborators to vote on the issues from the brainstormed list and then a prioritized list can be generated. The trick is to get the collaborators to participate...



So here is the question : What are the Top 10 issues facing small and/or medium sized businesses today?


The brainstormed list and results of the voting can be found below or in an easier to read format at: http://spreadsheets.google.com/pub?key=pcnLN5HtUKspp2c6Fq9Z2Zw






Lessons learned:

I had a bit of difficulty making the multivoting clear to all participants so it neccessitated a bit of email correspondence to clarify - my bad. Make sure the instructions don't leave any room for interpretation. Try to Poka Yoke with a couple of people before publishing the questionnaire at large.

The Google Docs method neccessitated I go into the document every time someone voted so that I could hide their results from view of the others. You don't want to influence votes by leaving it visible. This was a bit of a pain and would probably cause problems if several people try to access the document at the same time. There are probably better technologies out that that you don't have to pay for.

I made the multi-voting simple by asking for a ranking their top 10 rather than going for points. It is more intuitive for the voters this way. However, in order to come up with a final list, I had to turn those rankings into points to avoid misrepresenting the value of those criteria that didn't make the Top 10 chosen by the voters. Consequently, I could have but in a formula to automatically do this but I chose to do it directly in Excel instead - it was just easier that way. Anyway, the point is that there was another intervention required on the "facilitator"s part to do this. To be truly lean, this would have to be done automatically as the rankings are entered by the voters.

Conclusions:

I think this is a promising alternative for disparate teams to move projects ahead. I am sure there are simpler methods out there but this one worked and with a honed effort, it could become quite effective. If you have any suggestions on other ways to collaborate online, I look forward to hearing about them.


Cheers,


Patrick


Saturday, January 26, 2008

Communication

I'd like to spend a bit of time writing about communication. Lately I have facilitated several sessions and observed a very common occurence- it seems we humans have difficulty understanding each other....

Working in Quebec, we often have to deal with language issues and it is easy to chalk this phenomenon up to that but I believe that this is not really the root of the problem.

We are taught as facilitators to paraphrase; to ensure we understand what has been said and also to close the communication loop by demonstrating to the person we are paraphrasing (and others) that we understood. However, all too often, I have witnessed people saying the same things but in different ways. While they are in essence paraphrasing each other, they are not using the same words or structuring their thoughts in the same way and to each other, they are not at all the same. I have seen this situation derail meetings into heated discussions to the surprise of other participants who don't understand at all what the disagreement is about. So why is it that some people can easily process information that is presented in different ways and other people can only process it in one way - the way it is structured in their minds?

I believe it has more to do with how we are wired internally to receive and process information than it does with language or culture. The reason I say this is because I have been dealing with very structured professionals over the years and I find that this phenomenon seems to occur the most when the interaction is between two professionals (engineers, architects, lawyers, doctors, etc.) while those that witness the occurence and who don't understand what all the fuss is about are more often than not generalists of some sort (purchasing professionals, management, etc.).

What are your thoughts?

Tuesday, October 30, 2007

Change Plan


Here is a 5 Step change process that can be used for any project. It is an ongoing project of mine to develop this tool, any comments are most welcome.

The Formula E=DxA refers to the premise that effective change is a function of both the desire to change and the ability to undergo the change. This is synonymous to the adage that you can lead a horse to water but you can't make him drink....You therefore need both elements to make it work, and we often neglect one or the other in change efforts.

Let me know what works or what doesn't work for you.











Wednesday, June 13, 2007

What is Six Sigma?

By: Patrick J. Pressoir, MSc and certified Six Sigma Master Black Belt

Adapted from: Wikipedia, the free encyclopedia: http://en.wikipedia.org/wiki/Six_Sigma

Where does it come from?

The term Six Sigma was first coined by Bill Smith and Mikel Harry at Motorola in 1986. Six Sigma was originally used as a term for a method to measure defects and improve quality with roots in Total Quality Management and Statistical Process Control. Some would argue that there is very little that is new within Six Sigma; however, it does use the old tools in concert for far greater effect. The telephone, the internal combustion engine, and the computer were all made from existing technology, used in a new way. The same is true of Six Sigma.
A few years after leaving Motorola, Dr. Harry co-founded the Six Sigma Academy offering the breakthrough business strategy and training to corporations around the world which started the Six Sigma revolution as a mainstream business practice.
Since that time, Six Sigma has evolved and means different things to different people, which is often a cause of confusion. Let’s look at some of these individually:

Six Sigma is about measures:

We can't effectively change something we can't measure, and we won’t know what to change until we measure. Without measures, we don’t know what we don’t know. Which also begs the question; if we value it, why aren’t we measuring it? Only by measuring the things a company values can we really understand how we are performing so that our measures, or "metrics" as we prefer to call them, carry relevance to every member, for every activity, of an organization. The foundation of Six Sigma uses metrics to calculate the success of everything an organization does in terms of what it values. Without measuring a company's processes, and its changes to these processes, it's impossible to know where you are or where you are going. Six Sigma is about understanding the root cause of a problem and addressing it at the source based on data, rather than going with gut feel solutions.

Six Sigma is about Statistics:

The symbol “sigma”, or σ, is a letter in the Greek alphabet. Sigma is used to represent standard deviation, a measure of variation. The term "six sigma" comes from the notion that if you have six standard deviations between the mean of a process and the nearest specification limit, you will have virtually no items that exceed that specification, and therefore, virtually no defects. When comparing all processes to customer expectations using this common metric, we can focus our efforts on the lagging processes.

Six Sigma as a Benchmark:

Six Sigma is recognized as a measure of world-class quality, only 3.4 defects per million opportunities (DPMO). Typical North American companies operate between three (66,807 DPMO) and four sigma (6,210 DPMO). Successful Six Sigma deployments have allowed companies to achieve these Best-in-Class levels of quality. In nature, all processes have variation. The benchmark of six sigma takes that natural variation into account to still deliver within the customer limits of what is acceptable quality.

Six Sigma as a Vision and Philosophy:

Initially, the early adopters of Six Sigma targeted manufacturing processes; however an increasing number of companies saw the promise that came with a Six Sigma level of quality through meeting customer expectations with an ability only few could match and improving faster than the competition. Thus, Six Sigma became a breakthrough philosophy for businesses to gain a competitive advantage. At the core, the Six Sigma philosophy is to satisfy customers’ requirements profitably, companies must therefore align what they do with what the customer needs. Today, Six Sigma is used in all forms of business whether products, services and transactional. Six Sigma practitioners believe that eliminating defects in products and processes is the best way to improve quality, costs, cycle time, and customer satisfaction. Quality is not viewed as a cost; on the contrary, the highest quality producer is the lowest cost producer. Through the Six Sigma philosophy, management can unify all improvement approaches and establish the highest quality at minimal cost for the company.

Six Sigma as a Program:

Six Sigma should not be a break from the past but an integration and continuum of existing quality initiatives and continuous improvement programs. It must seamlessly flow to and from existing initiatives, business strategy, and key performance measures. Ultimately, the Six Sigma methodology is a change management and problem solving approach that should be integrated into the corporate strategy as a means to achieve business objectives and consequently applied in all company functions and processes to maximize the benefit for customers, employees and shareholders alike.

Six Sigma as a Project methodology:

The Six Sigma method is a structured project approach for improvement based primarily on design, quality and statistical tools. It is a step-by-step team-based method for improvement taking into account customer requirements at the core that forces a team to fully comprehend a problem before implementing a solution. Typically, a six sigma project follows these five phases:

Define - formally define the problem, its impact and process improvement goals.

Measure – collect the necessary data on the current process’ key input variables.

Analyze - verify relationship and causality of factors with the outcome of the process. Determine the vital few factors from the trivial many.

Improve - optimize the process based upon the analysis, develop, validate and implement the solution.

Control – ensure the solution is sustainable by monitoring the key input variables and instituting control mechanisms to ensure that variances are corrected before they result in defects.

Six Sigma as a Tool:

Six Sigma is a virtual toolbox that assembles various management tools, statistical tools, and quality tools to aid employees and support staffs achieve systematic improvements. Some organizations also incorporate Lean tools into their Six Sigma toolbox for even greater effect as Lean focuses on eliminating waste and improving speed and effectiveness while Six Sigma focuses on reducing variation of the process. These are complementary and the debate of Lean versus Six Sigma really stems from a misunderstanding of the overall goal – to improve quality.

Six Sigma as a Goal:

The goal of Six Sigma is to achieve a 99.9997% defect free process the first time or 3.4 defects per million opportunities (DPMO); a goal of near perfect quality. Through Six Sigma, companies have found a way to increase quality and customer satisfaction, integrate the quality concept in everyday work as well as provide help and solutions to fix problems. Six Sigma is an up-front investment that will result in time saved downstream, and an opportunity for employees to make changes in their work place.

“What it is not”

Despite all its promise, Six Sigma is not a way to eliminate jobs or a “flavor of the month” that is here today and gone tomorrow. Six Sigma is not a separate initiative from regular work or another way for outsiders to tell us how to do our job or a way to slow us down so we can’t get our job done.

Many frameworks exist for implementing the Six Sigma methodology either on its own or as part of a Continuous Improvement, Operational Excellence, Quality System or Process Management program. Six Sigma consultants all over the world have developed proprietary methodologies for implementing Six Sigma quality, based on the similar change management philosophies and applications of tools.
So what does it all mean for us?
In essence, the six sigma method is about understanding what we do and how we do it, and then focusing on doing it better by addressing causes of waste and variation. That leads to action and sustainable breakthrough changes. Through six sigma, companies relentlessly question every process, every number, and every step along the way of how we do business. As six sigma takes hold across an organization, managers, employees, and customers ask different kinds of questions of each other than they've asked before because it creates a new way of thinking at all levels.
Enthusiastic speeches, colorful posters, and corporate mandates will not produce sustainable change. An integrated program using Six Sigma and Lean will teach new ideas and principles, some of which will run contrary to what people may have learned in school or professional practice. Once employees understand what Six Sigma is and how it works, they will begin to see that many well-accepted past practices and quality-control methods are less than optimal, or even misleading.
Understanding the customer needs, and having the right measurements to focus on, six sigma forces us to query what we have taken for granted, and that ultimately provides us with new direction. Six Sigma forces businesses to let go of bad habits; bureaucracy becomes de-layered, waste is eliminated, defects are reduced, and consequently, performance improves. Those employees closest to the actual work and to the customer are involved in the process and become empowered and motivated to meet or exceed consumer requirements. By thinking in terms of speed, cost, quality and health & safety, people begin to think firstly about what is not working properly from an objective perspective, secondly about the root causes, and finally about new or improved systems or processes that can be put into place to address those causes.

Thursday, June 7, 2007

Appreciative Inquiry

I co-organized an Operational Excellence seminar a couple of weeks ago for a Hospital in Montreal. One of the guest speakers covered the topic of Appreciative Inquiry (AI). While this term was new to me, there were many things he mentioned that were familiar and perhaps often overlooked (especially in large organizations). As managers, we strive to improve our departments and divisions to be the best that they can be. We often want to compare ourselves to Best-in-Class and benchmark other orgranizations that have our functions in similar and different industries. While this is good. It is not the only way to find Best Practices.

The basic premise of AI is that there are probably goods things being done within our own organizations that merit being explored, replicated, expanded, etc. In other words, maybe we should look internally before spending time and money looking outside.

I have been in numerous organizations over the years and have come to the conclusion that this is a richness that is rarely exploited. There is also a huge parallel to be drawn with Six Sigma deployment strategies that have proven that the breakthough gains are not achieved in the volume of projects but rather the ability of the organization to replicate the gains of key projects throughout the organization. Think of it in terms of effort versus payoff. Simply put, the first project requires much more effort to complete than the subsequent leveraged projects, but the payoff remains the same for each.

In addition, looking internally results in soft benefits:
-Recognition of work well done (what better recognition is there than saying this merits being copied by others...)
-Standardization of work (a Lean principle). Once again, this is a thorn in many a side of large organizations. Through leverage and replication, we are in essence removing waste by standardizing work.
-Familiarity. As best practices are adopted within the organization, employees become familiar with how things are done throughout the organization. This facilitates transfers, training, and reduces the reliance on tribal knowledge.

If you are interested in learning more about AI see the link at the end of this post. I look forward to your comments.

http://appreciativeinquiry.case.edu/intro/whatisai.cfm

Monday, May 28, 2007

Setting stretch goals

We've often heard that by setting stretch goals we have a better chance of achieving the desired outcomes. This is true, but you also need to establish a strategy and plan to get there.

About twelve months ago I attended a running seminar given by the founder of the Running Room, John Stanton. By the end of the seminar, I was motivated to take my casual running to the next level and set a goal to complete my first marathon before I turned forty. I wanted to do something for me for a change.

I started a running regimen over the next eighteen weeks and registered for the Montreal marathon. I did not have a heart rate monitor nor was I able to accurately gage my running pace. I simply used a pedometer to estimate distances of my runs over the course of those weeks and logged the miles per the plan. Having registered for the marathon kept me motivated to keep training. September came and the big day arrived. The weather was perfect. I had visualized the course over the previous few days and had planned all the hydration stations in my run strategy. I figured I would complete the distance in the 4:30 pace group. For the first 21km, I felt strong and completed the half in 2 hours flat. Then I started to slow at about km 30. My legs felt heavy and the people who had been running around me started to pull ahead. By km 34, I was literally on autopilot and was shuffling along. It took everything I had just to keep going. I had to break it down into short objectives ; "just to the top of the hill; "just to the next corner; "just to the next km marker..." It was the most brutal experience of my life. I finally completed the second half in 2:45. I had achieved my goal but my execution was not the greatest.

In January, I registered for the Ottawa marathon. This time, I had a heart rate monitor and also was able to measure my pace and speed. I set a goal to complete the marathon in 4 hours and planned my training distances and speeds to support that objective. My training was more structured and my progress was measurable. Come my last training run, I was confident I would meet my stretch goal. I completed the marathon in 3:52!

The morale of the story here is that when you set stretch goals, you have to make sure they are agressive enough to be a challenge but not so agressive that they are impossible to achieve. The other part is that by setting stretch goals, we often achieve more than we thought possible provided that we set ourselves up for success by ensuring we have the proper elements to execute the plan to meet those goals.

Thank-you, John, for the motivation!

Friday, May 25, 2007

Project failure survey

I have seen alot of statistics on project failures (up to 70%!). I have also seen alot of reasons given for project failures, but I have not come across any statistical data on the distribution of those reasons. So, in an attempt to try and be a bit more data driven on this subject, I would ask that you provide me with your feedback and we'll see what it gives.

Here is the question:

In your experience, please rate the percentage of project failures that can be attributed to the reasons below (the total does not have to add up to 100%, of course) :



  • Ineffective or lack of change management (people side of change)

  • Poor scope control

  • Schedule overruns

  • Cost overruns

  • Deliverable did not meet expectations

  • Other (please specify)


Sample answer: Suppose I have been involved directly or indirectly in 8 projects that I woul classify as failures. 4 had ineffective change (50%), 1 had poor scope control (13%), 6 had schedule overruns (75%), 4 had cost overruns (50%), 2 did not meet expectations (25%), and 1 was abandoned (13%).

____________________________


Here are the survey results....

of 15 respondents :

a. 73.3% cited Ineffective or lack of change management (people side of change) as a cause of project failures.

b. 80% cited Poor scope control

c. 80% cited Schedule overruns

d. 53.5% cited Cost overruns

e. 73.3% cited Deliverable did not meet expectations

f. 86.7% cited Other causes as well

Interesting to note that most feel that cost overruns are not really a cause but rather a consequence of some other cause.

Also interesting is that the Other causes can be grouped into two main categories; poor project management (or manager), and sponsorship (or lack thereof).

The affinity for each of these causes is as follows:

Poor PM includes unrealistic planning, poor manager, lack of participation, lack of acceptance of roles and responsibilities, poor business knowledge, bad communications, poor documentation, lack of discipline, bad PM approach.

Poor sponsorship includes unclear requirements, unrealistic expectations, project abandoned, change of heart or direction of project, management change, lack of support.

As for the distribution of results, it gives something like this:

Percentage of project failures attributed to:

51% - Poor PM

41% - Poor change management (people side)

32% - Schedule overruns

30% - Cost overruns

28% - Poor scope control

20% - Poor sponsorship

17% - Deliverable not meeting expectations

Thanks again to all those who participated. Hope this in informative for you.