Showing posts with label Processes. Show all posts
Showing posts with label Processes. Show all posts

Monday, 14 December 2020

Layering: A New Approach to Business Process Mapping

Six Sigma Certification, Six Sigma Learning, Six Sigma Exam Prep, Six Sigma Guides, Six Sigma Career

According to leading LSS practitioners, 80 percent of problems in business processes can be identified and eliminated through the correct application of business process maps. Some research shows that process maps are used even more frequently than statistical tools.

SixSigma3.0, an evolution of Six Sigma developed by the Russian partnership Association Six Sigma, has significantly improved the application methodology of process maps. The practice of using conventional maps has not yet been formed into a single algorithm. Maps are used to visually represent the process and, at best, provide information on the inputs and outputs of the process steps. The information is kept fragmented. In SixSigma3.0, we added six specialized analytical layers to process maps to record various data:

1. Process flow: A business process management and notation (BPMN) backstage map of business process flow with actors, tasks and interactions.

2. Inputs-outputs: Collects information on inputs, outputs, documents, instructions and other conditions that control each task in the process.

3. Efficiency problems and optimization opportunities: Used for analysis and recording problems such as losses and missed opportunities. Each problem is marked with an asterisk and unique identification number.

4. Transfer table + Pareto chart: The transfer table is used to transfer the result of analysis from the previous layer; a detailed description of problems and assessment of losses are entered into the transfer table. The Pareto chart shows a list of prioritized problems to assign for missions.

5. Cycle time: Used to collect time data on process flow elements: tasks, evaluation points and transfer of output. Data is entered into the table on the next layer. This layer can be used in place of traditional VSM, which is time consuming.

6. Time analysis data: Collected data analysis shows process efficiency cycle time and non-value-added (NVA) time, and also reveals time traps and slow process steps.

Layer 1: Process Flow


The mission team, made up of the employees involved in the process, starts by creating a standard BMPN process map. The team brainstorms to identify actors as well as the most important tasks and interactions. They then analyze the sequence of operations and map the process flow.

After finalizing the process map, the team proceeds to collect diverse information on the process using all six analytical layers.

A procurement process example is shown in the following figures to demonstrate the process. Figure 1 shows the initial process flow.

Six Sigma Certification, Six Sigma Learning, Six Sigma Exam Prep, Six Sigma Guides, Six Sigma Career
Figure 1: Process Map Layer 1 – Process Flow

Layer 2: Inputs-Outputs


The second layer identifies and plots inputs and outputs for every process task and the conditions that affect the successful performance of operations: documents, instructions, technologies, materials, components, etc. “Note” or “database” icons can be used for this information. Documents can be attached to icons for further analysis. See Figure 2.

Six Sigma Certification, Six Sigma Learning, Six Sigma Exam Prep, Six Sigma Guides, Six Sigma Career
Figure 2: Process Map Layer 2 – Inputs-Outputs

Layer 3: Efficiency Problems and Optimization Opportunities


Here, the mission team analyzes the efficiency of the process as well as searches for defects and bottlenecks. Decision points with immediate results are checked for compliance and repeated cycles are identified. It is useful to put a counter to collect statistics on repeated cycles at decision points. Two types of problems will be identified:

1. Problems that have already led to serious losses
2. Missed opportunities that have led to virtual losses

The team surfs through the process flow asking: “Is there a problem in this element that hinders the achievement of our mission goal?” Identified problems are recorded on the map with an asterisk and number at the point of occurrence. See Figure 3.

Six Sigma Certification, Six Sigma Learning, Six Sigma Exam Prep, Six Sigma Guides, Six Sigma Career
Figure 3: Process Map Layer 3 – Efficiency Problems and Optimization Opportunities

Layer 4: Transfer Table + Pareto Chart


The economic loss is estimated for every problem and information on all the problems is recorded in the transfer table on this layer.

Then, the team identifies the most significant problems using a Pareto chart. See Figure 4.

Six Sigma Certification, Six Sigma Learning, Six Sigma Exam Prep, Six Sigma Guides, Six Sigma Career
Figure 4: Process Map Layer 4 – Transfer Table + Pareto Chart

Layers 5 and 6: Cycle Time and Time Analysis Data


If the goal of the mission is to reduce cycle time or accelerate process tasks, the team may continue analysis using the remaining layers. At each step of the process, we ask how this operation or task slows the cycle. The table with time data on Layer 5 (Figure 5 below) is used to identify slow operation and time traps and to evaluate process cycle efficiency. On Layer 6 (Figure 6 below), identified problems are added to the transfer table created in Layer 4.

Six Sigma Certification, Six Sigma Learning, Six Sigma Exam Prep, Six Sigma Guides, Six Sigma Career
Figure 5: Process Map Layer 5 – Cycle Time

Six Sigma Certification, Six Sigma Learning, Six Sigma Exam Prep, Six Sigma Guides, Six Sigma Career
Figure 6: Process Map Layer 6 – Time Analysis Data

During the work on the layered map the team gets a full understanding of the process –including influencing factors, performance data on defect rate, recurring cycles, slow operations and more – and a list of the most expensive problems that can be used for further analysis and resolution.

The layer approach has proven easy to grasp and staff in different industries (including banks, telecoms, chemicals, oil and pharmaceuticals) can easily perform both mapping and analysis using layered maps after a brief training. The algorithm prevented them from stumbling on roadblocks when choosing their next step in the project. The collected information is used at further stages of analysis and solution development.

Saturday, 23 March 2019

Improving Personal Health Using Data and Six Sigma

Four times a year, I donate blood at a local blood bank and receive readings on my cholesterol, blood pressure and pulse. Although donating blood does not improve a person’s health, the regular readings of the vital signs, along with analysis and actions stemming from this data, can be significant in the fight against heart disease, strokes and other medical problems.

Six Sigma, Six Sigma Learning, Six Sigma Guides, Six Sigma Certifications

Six Sigma practitioners, because of their knowledge of statistical analysis and their belief in continuous improvement, are at a particular advantage for using this health data to make positive life changes. For instance, practitioners can conduct regression analysis to show a correlation of the vital sign variables and the relationship to exercise and diet. Also, they can use time-phasing process to find leading indicators. Six Sigma concepts and tools have already proven useful in practitioners’ professional lives – but the concepts and tools also can be beneficial in practitioners’ personal lives.

Collecting Data


Heart disease, related to high cholesterol or elevated blood pressure, can affect anyone – young, old, male, female. Uncontrollable factors, such as one’s heredity, as well as controllable factors (diet, weight, exercise, stress) influence a person’s cholesterol and blood pressure.

Cholesterol

After each blood donation, the San Diego Blood Bank (SDBB) provides data on my cholesterol and blood pressure via a secure website. Having this data available every three months helps me monitor and improve my health. High blood pressure is referred to as the silent killer because the symptoms may not be apparent. One in three Americans suffers from high blood pressure.

Figure 1 is a chart of my cholesterol. Although the National Heart Association recommends maintaining a cholesterol level of 200 (the red line) or below, my goal is to stay under 180 (the yellow line).

Six Sigma, Six Sigma Learning, Six Sigma Guides, Six Sigma Certifications

Figure 1: Ray’s Cholesetrol as Reported By the SDBB

For me, exercise and healthy eating significantly lower my cholesterol levels. As illustrated in Figure 1, my July 2008 and October 2008 cholesterol levels were favorable. I recall that I was eating right and exercising in preparation for a Multiple Sclerosis bike ride held in October 2008. I remember starting this exercise and eating routine after my January 2008 physical and January blood donation results.

There were three periods in which I missed my goal of keeping my total cholesterol value below 180; these were periods preceded by stress, overeating and minimal exercise.

Blood Pressure

The SDBB also provides blood pressure readings, which I downloaded to create Figure 2. The red and orange lines are my blood pressure. My goal is to keep the systolic blood pressure under 120. Fortunately, I was born with good genes for low (good) blood pressure.

Six Sigma, Six Sigma Learning, Six Sigma Guides, Six Sigma Certifications

Figure 2: Ray’s Blood Pressure and Cholesterol as Reported By the SDBB

The data shows that cholesterol value could be a leading indicator of blood pressure for me, as illustrated by the dotted green lines. For example, my cholesterol peaked in Jan. 2008 (bad) and my blood pressure peaked (bad) three months later (April 2008). Likewise, my cholesterol was good in July 2008 and my blood pressure was good three months later (Oct. 2009).

Regression Analysis


After noticing the relationship between my cholesterol and blood pressure levels, I conducted a mathematic regression analysis, which provided the same results.

With the original data, a regression analysis on blood pressure (systolic) to cholesterol showed no correlation; the coefficient of correlation is near zero (0 is no correlation, weak is .25, moderate is .50, strong is .75, perfect is 1.0).

However, when blood pressure is shifted three months backward, the coefficient of correlation is .58 (moderate to strong). The coefficient of determination, or the proportion of the total variation in blood pressure attributed to the cholesterol reading, is 34 percent in this situation. These calculations can easily be produced in Excel using the data analysis add-in.

Although this shows a mathematical correlation of blood pressure to cholesterol, correlation does not prove the causal relationship. Both blood pressure and cholesterol levels could be independently influenced by my exercise and eating routine. The mathematical exercise does reinforce that something happened as both variables changed, somewhat in tandem with the time shift. The analysis could also imply, at least with this data, the predictive nature of blood pressure by cholesterol; that is, cholesterol as a leading indicator.

Leading Indicators


The other lesson is that of leading indicators. When presented with data, such as that in Figure 2, practitioners should look for the phasing relationship, as indicated by the green lines. Many times there is correlation of the variables if the timeframe of one or more variables is shifted. There are mathematical means of determining a phasing relationship, but for many applications, simple charting and shifting data up or down in a spreadsheet is sufficient. More data and examples are needed to make a conclusion on a leading indicator and the causal relationship.

Pulse is another good health indicator. Years ago I read that a heart will have so many beats in a lifetime. When people exercise vigorously, their hearts beat faster per minute. However, the exercise builds up the heart from a muscular perspective, such that when they are not exercising (which is most of the time), the heart beats slower, thus providing a long heart life. As illustrated in Figure 3, my improved (lower) pulse rate correlates to those times when I exercise more. My goal is keep my pulse in the 60 beats per minute range.

Six Sigma, Six Sigma Learning, Six Sigma Guides, Six Sigma Certifications

Figure 2: Ray’s Blood Pressure and Cholesterol as Reported By the SDBB

Personal Takeaways


At age 61, my key takeaway is to eat healthy, avoid refined sugars and minimize fat. Avoiding salt and minimizing alcohol also are good practices. Minimizing fast food and processed food helps in this endeavor. Walking, hiking, and cycling are my favorite types of exercise and, as correlated to the charts, contribute to better health conditions.

Another important factor that goes with the healthy eating and exercises is weight control, which, for me, is a struggle. There are good medications that reduce cholesterol and blood pressure; however, my goal is try to avoid these as long as possible due to the dependency, cost and side effects. Fortunately, I have been blessed with good health.

Each year I get a physical from a primary care physician. There are a number of ways to manage heart disease once it is diagnosed; however, frequent monitoring, trending and taking proactive measures for disease prevention are limited. Once a year measurements are limited in terms of trending, providing body knowledge and creating focus. The quarterly vital sign updates I receive after donating blood help to fill the gaps.

Six Sigma Advantage


Every person is different. There is a tendency for people to compare their results to others or to averages. Or, people sometimes conclude that they can’t change their health condition. Six Sigma practitioners, however, know that this is not the right attitude. By approaching problems in an objective way, applying systems thinking and excluding the personalization of problems, it is possible to make continuous improvements. Data, although good, does not, by itself, change things. Decisions must be made based on both emotional and logical factors.

Behavioral change is difficult. Dr. Edwards Deming, the statistician and quality guru, developed 14 principles on quality and change to help with people and the emotion challenge. The applicable Deming principles include:

◈ No. 1: Have a constancy of purpose.
◈ No. 14: Take action on the transformation.
◈ No. 5: Improve the system constantly.
◈ No. 11: Eliminate numerical quotas.

The last principle about numerical quotes may seem contradictory, as Dr. Deming used so many charts and graphs. But his emphasis was on measuring and improving the process, and not judging the person. Healthcare is personal; cholesterol, blood pressure and weight numbers are your numbers. However, when Six Sigma practitioners approach the change as a process and system, it can help them to address the problem more directly and objectively.

“You can’t improve what you can’t measure” is a common concept in business quality management and Six Sigma. Charting data, monitoring trends, finding correlation and taking action (the Plan, Do, Check, Act cycle) can also be applied to personal health. Practitioners should challenge themselves to look for opportunities to apply Six Sigma concepts, grow the body of knowledge and share with others. And, if you are able to donate blood, check out the local blood bank. There is always a pressing need for blood and the personal health data every three months can be beneficial to your health.

Note that the information provided is based on personal experience and data. This article is not intended to be a substitute for professional medical advice.

Wednesday, 30 May 2018

Understanding Process Sigma Level

Six Sigma is a data-driven approach to quality, aimed at reducing variation and the associated defects, wastes and risks in any process. This article explores the basics of Six Sigma process quality – definition and measurement.

In a set of data, mean (μ) and standard deviation (σ) are defined as:

μ = x1 + x2 + x3 + … + xn) / n

Where x1 , x2 , … , xn are data values and n is the number of data elements, and Six Sigma Tutorials and Materials, Six Sigma Learning, Six Sigma Study Materials Standard deviation shows the extent of variation or spread of data. A larger standard deviation indicates that a data set has a wider spread around its mean. Process data usually has a normal distribution. The distance from the mean μ to a data value in terms of data units can be measured. For example, a data point with a value of x = 31 seconds is 6 seconds away from a mean value of 25 seconds. This distance can also be measured by counting the number of standard deviations in the distance. If the standard deviation is 2 seconds, the same point is 6/2 or 3 standard deviations away from the mean. This count is denoted by sigma level, Z, also known as Z-score, as shown below.
Z = (x – μ) / σ

Z = (31- 25) / 2 = 3

Specification Limits and Defect Rates


In a process, deviations from the target or mean are accepted to a certain value defined by the specification limits (SL) around the mean. Any value beyond the specification limit indicates a defect or unacceptable result. The farther the specification limits are from the mean, the lower the chance of defects.

A Six Sigma process has a specification limit which is 6 times its sigma (standard deviation) away from its mean. Therefore, a process data point can be 6 standard deviations from the mean and still be acceptable. (See Figure 1.)

Figure 1: Normal Distribution With Mean, Z-score and Six Sigma Specification Limits

Six Sigma Tutorials and Materials, Six Sigma Learning, Six Sigma Study Materials

In a stable process, the mean naturally shifts as much as 1.5 sigma in the long term on either side of its short-term value. The red lines in Figure 2 (below) show the extreme case of 1.5-sigma mean shift to the right. The right specification limit is at 4.5 sigma from the mean with a defect rate of 3.4 parts per million (PPM). The left specification limit is at 7.5 sigma from the mean with a defect rate of 0 PPM. The overall defect rate, therefore, is 3.4 PPM. A similar argument applies to the extreme case of 1.5-sigma shift to the left. A Six Sigma process is actually 4.5 sigma in the long term, and the 3.4 PPM defect rate is the 1-sided probability of having a data value beyond 4.5 sigma measured from the short-term mean.

Figure 2: Process Mean Shift of 1.5 Sigma and Defect Rate Corresponding to 4.5 Sigma

Six Sigma Tutorials and Materials, Six Sigma Learning, Six Sigma Study Materials

The 1.5-sigma shift makes defects approach 0 on the opposite side of the shift even at lower sigma levels. The one-sided defect rate is applicable to any capable process with 1-sided or 2-sided SLs, even at a 3-sigma level.

Given the specification limit, SL, the process sigma level, or process Z, is:

Z = (x – μ) / σ = (SL – μ) / σ

In this example, the process sigma level for a specification limit of 31 seconds is:

Z = (SL – μ) / σ

Z  = (31 – 25) / 2 = 3

Therefore, the process is at a 3-sigma quality level. In order to bring the process to the golden Six Sigma quality level, the process sigma would have to be reduced to 1.

Z = (31 – 25) / 1 = 6

In general, the Z formula can be rearranged to calculate the maximum allowable process sigma, or standard deviation, for any sigma level.

Z = (x – μ) / σ

σ = (x – μ ) / Z

For example, given a mean of 25 seconds and SL of 31 seconds, for a Six Sigma quality level, the required process sigma is calculated as:

σ = (31 – 25) / 6 = 1

Similarly, for a 3-sigma quality level, the process sigma must be:

σ = (31 – 25 ) / 3 = 2

Referring back to the short- and long-term behavior of the process mean, there are 2 values for Z, short-term Z, or Zst, and long-term Z, or Zlt.

Zlt = Zst – 1.5

In sigma level calculations, use Zst. A Six Sigma process is 6 sigma in the short term and 4.5 sigma in the long term or:
Zst = 6

Zlt = Zst – 1.5 = 4.5

Clarifying Process Sigma and Sigma Level


Sometimes the term process sigma is used instead of the process sigma level, which may cause confusion. Process sigma indicates the process variation (i.e., standard deviation) and is measured in terms of data units (such as seconds or millimeters), while process sigma count Z, or process sigma level, is a count with no unit of measure.

Process Capability and Six Sigma


Another measure of process quality is process capability, or Cp, which is the specification width (distance between the specification limits) divided by 6 times the standard deviation.

Cp = (Upper SL – Lower SL) / 6σ

The recommended minimum or acceptable value of Cp is 1.33. In terms of Six Sigma, this process capability is equivalent to a sigma level of 4 and long-term defect rate of 6,210 PPM. Process capability for a Six Sigma process is 2.

Monday, 28 May 2018

Should You Calculate Your Process Sigma?

Six Sigma Certifications, Six Sigma Learning, Process Six Sigma

Many people hear about the Six Sigma quality methodology and immediately want to calculate their own process sigma to determine how close (or far) they are from six sigma. My immediate response to them is twofold: 1. are you currently measuring your process capability?, and 2. are you satisfied with your performance? If the answer to both is yes, then calculating your process sigma may be interesting but not necessary.

When Process Sigma Is Not Neccessary


Let me illustrate with an example. A power company measures their performance in uptime of available power to their grid. Every minute of potential uptime (power is available) is an opportunity, every minute of downtime (power is not available) is a defect in the eyes of a customer. Data is continuously taken, the process capability is measured, and the yield is calculated to be 99.9%. The power company is satisfied with their current performance (but always looking to improve), and the customer’s needs (as collected via Voice of the Customer) are being met.

If the entire company communicates in yield and everyone within the company understands this language, is determining the process sigma level useful? I submit that if the company is pursuing full implementation of the Six Sigma quality methodology across the organization then calculating sigma is appropriate because processes within the organization and between plants can be compared. When a company is only considering Six Sigma for one functional area (power transmission OR bill collection OR call center) then the company might be better suited to maintain the metrics that everyone currently uses and understands. How can an organization communicate if everyone doesn’t learn the language?

I know what you’re thinking, ‘Ok Zack, get on with it. I want to calculate my process sigma anyway. How can I do it?’ Here is your two minute instruction on calculating your process sigma.

How to Calculate Process Sigma


Consider the power company example from the previous page: A power company measures their performance in uptime of available power to their grid. Here is the 5 step process to calculate your process sigma.

Step 1: Define Your Opportunities

An opportunity is the lowest defect noticeable by a customer. This definition, of course, is debatable within the Six Sigma community. Here’s a useful snippet from the forum discussing this point:

“Typically, most products (and services) have more than one opportunity of going wrong. For example, it is estimated than in electronics assembly a diode could have the following opportunities for error: 1) Wrong diode and 2) wrong polarity (inserted backwards), so for each assembly shipped, at least two defect opportunities could be assigned for each diode. Apparently, some manufacturers of large complex equipment with many components prefer to [count two opportunities in this case]. My point is that this approach dilutes Six Sigma metrics.” -Anonymous

Many Six Sigma professionals support the counter point. I always like to think back to the pioneer of Six Sigma, Motorola. They built pagers that did not require testing prior to shipment to the customer. Their process sigma was around six, meaning that only approximately 3.4 pagers out of a million shipped did not function properly when the customer received it. The customer doesn’t care if the diode is backwards or is missing, just that the pager works.

Returning to our power company example, an opportunity was defined as a minute of uptime. That was the lowest (shortest) time period that was noticeable by a customer.

Step 2: Define Your Defects

Defining what a defect is to your customer is not easy either. You need to first communicate with your customer through focus groups, surveys, or other voice of the customer tools. To Motorola pager customers, a defect was defined as a pager that did not function properly.

Returning to our power company example, a defect is defined by the customer as one minute of no power. An additional defect would be noticed for every minute that elapsed where the customer didn’t have power available.

Step 3: Measure Your Opportunities and Defects

Now that you have clear definitions of what an opportunity and defect are, you can measure them. The power company example is relatively straight forward, but sometimes you may need to set up a formal data collection plan and organize the process of data collection. Be sure to read ‘Building a Sound Data Collection Plan‘ to ensure that you gather reliable and statistically valid data.

Returning to our power company example, here is the data we collected:

Opportunities (last year): 525,600 minutes
Defects (last year): 500 minutes

Step 4: Calculate Your Yield

The process yield is calculated by subtracting the total number of defects from the total number of opportunities, dividing by the total number of opportunities, and finally multiplying the result by 100.

Returning to our power company example, the yield would be calculated as: ((525,600 – 500) / 525,600) * 100 = 99.90%

Alternatively, the yield can be calculated for you by using the iSixSigma Process Sigma Calculator – just input your process opportunities and defects.

Step 5: Look Up Process Sigma

The final step (if not using the iSixSigma Process Sigma Calculator) is to look up your sigma on a sigma conversion table, using your process yield calculated in Step 4.

Assumptions


No analysis would be complete without properly noting the assumptions that you have made. In the above analysis, we have assumed that the standard sigma shift of 1.5 is appropriate (the calculator allows you to specify another value), the data is normally distributed, and the process is stable. In addition, the calculations are made with using one-tail values of the normal distribution.

Thursday, 8 February 2018

Avoid The Four Most Common Mistakes of Sales Process Mapping

Process mapping is a well-known technique for creating a common vision and shared language for improving business results. It helped one management training and development firm realize that people within their sales department had been working at cross purposes, and crucial executive-level discussions with customers were not taking place. Based on sales process mapping, the leaders reorganized their sales operations so that job descriptions and performance measures focused more on the customer. In six months, they reversed a five-year slump and earned big bonuses for team members. In another case, sales process mapping helped a large manufacturer’s national account teams discover a powerful new way to coordinate with field salespeople, yielding far more new business opportunities than expected.

However, leaders in both large and small sales organizations often make mistakes that undermine the potential of process mapping. A common result, for example, is that salespeople ignore the process and operate “outside the system.” Based on work with several dozen clients, I’ve observed four common mistakes that tend to hinder their success:

Process Mapping Mistakes Principles That Yield Powerful Results
Map all the details, losing track of the big picture. Foreground goals in organizing your process map.
Focus on the seller, instead of the customer.  Determine how to create value for the customer throughout the process. 
Map the process without showing how the results will be measured.  Map tools, skills, and performance metrics along with the process. 
Buy somebody else’s “ideal” sales process.  Engage your people in process mapping to define problems and solutions. 

This article describes the consequences of these sales process mapping errors, as well as principles to follow in order to avoid them. By following these suggestions, you can derive the most positive results for your own organization.

Mistake #1: Map all the trees, but miss the forest


An enthusiastic VP of Sales for a technical services company spent considerable time developing a process map for his organization. The map he developed (Figure 1) is typical of a first attempt to map a sales process. Analytically trained individuals (such as Six Sigma Black Belts or IT Systems Analysts) often create similar maps, many pages festooned with decision diamonds and other complicated details. 

Figure 1: Too many steps make this process map hard to use. (Click to enlarge)

Six Sigma Tutorials and Materials, Six Sigma Certifications, Six Sigma Guides, Six Sigma Learning

This VP created a comprehensive snapshot of people’s activities across his sales organization. Unfortunately, his comprehensive process map did not help him train or lead his team. This process map illustrates Mistake #1 in two significant ways:

◈ The map is too detailed. It captures more information than a person can take in all at once.
◈ All activities appear to have the same importance, with each activity equally dependent on the previous one. This isn’t an accurate reflection of reality.

Principle #1: Foreground goals in your sales process map


The figure below shows how this VP’s sales process map could be organized around goals. This technique places goals in the foreground, clarifying key issues. For example, even if team members have different ideas about how to qualify new accounts, they can agree that accounts must be qualified. With this goal in the foreground, some variation can be expected in how the goal is achieved. As individuals work toward consensus in the activity steps, they become best practices for achieving the goals.

Figure 2: Grouping activities according to goals creates focus. (Click to enlarge)

Six Sigma Tutorials and Materials, Six Sigma Certifications, Six Sigma Guides, Six Sigma Learning

Note that the goals are not the same as departmental boundaries. A single person might be involved in any of the top-level phases. This drives communication and collaboration, making process maps a powerful tool for generating a shared framework for accountability.

Another important feature is decision diamonds showing where the prospect (or the salesperson) might opt out. In real life, prospects can decide to buy from someone else, wait until next year, or call out of the blue and need service tomorrow. Identifying and measuring these decision points acknowledges that the process has a yield, as well as providing critical information for process improvement.

Mistake #2: Focus on the seller, instead of the customer


An administrator in a financial services company mapped her company’s sales process as her thesis for a master’s degree program. She dutifully collected statements from the company’s sales executives about what salespeople ought to do (she had never been a salesperson herself) and organized them into a hierarchical format. She achieved a thorough analysis that satisfied her professors. Unfortunately, her hard work did not benefit her organization.

Figure 3: This process map focuses on seller activities. (Click to enlarge)

Six Sigma Tutorials and Materials, Six Sigma Certifications, Six Sigma Guides, Six Sigma Learning

A portion of her company’s process map is shown in Figure 3. It is hierarchical, identifying a goal for each phase. Notice that the steps in the Winning New Business phase call for working with the CEO at each step. It would be nice if that happened, wouldn’t it? Now, consider the steps within the Contracting phase. Who do these steps create value for? From an internal administrator’s perspective, these procedures are important. But what value do they create for the customer? In fact, the benefit to the external customer was not considered at any stage of this process. Is it any wonder customers resisted it? Successful salespeople in this administrator’s company routinely operated outside the process, as any successful salesperson would have to do.

Principle #2: Determine how to create value for the customer


Sales processes that work create value for the customer. Delegating the process mapping task to an administrator without sales experience or executive insight allowed this company to go through the motions without making a difference. Figure 4 shows what this company’s process might look like, recast with a customer focus. Figure 5 defines value to the customer.

Figure 4: Revised sales process focuses on customer interaction. (Click to enlarge)

Six Sigma Tutorials and Materials, Six Sigma Certifications, Six Sigma Guides, Six Sigma Learning

Figure 5: Value to the customer is identified. (Click to enlarge)

Six Sigma Tutorials and Materials, Six Sigma Certifications, Six Sigma Guides, Six Sigma Learning

These diagrams illustrate a lengthier, more complex sales processes often found in business-to-business services. Such an approach is important where substantial talent or time – such as engineering, IT, legal, or other consulting – is necessary to develop a solution proposal. These complex sales environments are notorious for their unpredictability and cost. Before committing costly resources to the sales effort, the selling organization must do everything possible to ensure success and avoid wasting those resources. This can be accomplished by reaching decision makers early, so as to verify their needs and priorities. But this usually requires tremendous effort and courage. Often it is never accomplished.

Ultimately, reaching the decision maker in your customer’s organization benefits both you and your customer. Without first-hand insight into the decision maker’s needs and priorities, you risk wasting everyone’s time. But if you can validate your own understanding of the business value you offer the decision maker, even helping the decision maker generate a consensus if necessary, you create value for everyone. Getting credit for these things is often the key to winning the business.

Through sales process mapping, your team can keep a constant focus on your most mission-critical question: How can you create real value to the customer? If your business requires a contracting/administrative phase (like the financial services company in Figure 3), figure out how that phase can create value for the customer. If you can’t, place that phase in service of another goal that does.

Everything you do to find, gain, and keep customers should create clear value for them. If you do, customers – and the best salespeople – are sure to follow. You have no more powerful lever for ensuring an ever-growing stream of profitable business. Customer value is the number one defense against changing markets, competition, and technologies.

Mistake #3: Forget to “show them the money”


The training and development department of a major corporation spent several million dollars to develop a customized sales training program based on the company’s cultural values. The program was magnificent from an organizational development perspective. It illustrated the company’s conceptual goals clearly, and it built on existing training materials, which provided salespeople with many powerful skills (see Figure 6).

Figure 6: This process does not specify measurable results. (Click to enlarge)

Six Sigma Tutorials and Materials, Six Sigma Certifications, Six Sigma Guides, Six Sigma Learning

Unfortunately, statements such as “Use the relationship network,” “Facilitate decision making,” or “Confirm joint commitments” are not useful to salespersons trying to make their numbers. What is the concrete output of each step? How will it be measured? When are orders generated? Where is the process connected to the money?

Lacking measurable steps grounded in real-world sales operations, the training program defined a process in name only. Salespeople learned how the company’s world really worked on the job rather than from the course. Although many people agreed the course contained valuable skills, its value could not be proven. The sales organization in this company ultimately created its own measurement system outside the framework of the training program, crippling its effectiveness.

Principle #3: Integrate tools, skills, and results measurements with the process


Figure 7 illustrates how a sales process map (the same map that appears in Figure 2) can include metrics. The sales organization’s performance is measured by the high-level goals of the process, rather than the detail steps. There are many advantages in this approach to selecting metrics.

Figure 7: Broad metrics assess each goal-driven phase of the sales process. (Click to enlarge)

Six Sigma Tutorials and Materials, Six Sigma Certifications, Six Sigma Guides, Six Sigma Learning

First, as products and services move through their economic life cycles, sellers must change their marketing and qualifying strategies accordingly. Over time, these metrics can provide powerful leading indicators of market shifts, affording sellers precious lead time to respond.

Second, these metrics allow the organization to identify its bottlenecks or weak links, allowing resources to be allocated most effectively. For example, if marketing is not generating enough good prospects, adding salespeople or engaging expensive training services will not help. Instead, the marketing process should be improved so as to create enough prospects.

Third, a mapping approach allows people to participate in setting their own goals by drilling into more detailed analyses and metrics to improve performance. Figure 8 illustrates how a process map can serve as a tool for integrating some support functions within an organization.

Figure 8: Link performance support, skills, and competencies to the sales process. (Click to enlarge)

Six Sigma Tutorials and Materials, Six Sigma Certifications, Six Sigma Guides, Six Sigma Learning

Individuals can use this kind of detail to identify skills they need to work on. An organization can use process detail to integrate software support as well as training. This kind of mapping, a current trend in the training and development community, can yield powerful results.

Mistake #4: Buy somebody else’s “ideal” sales process


Sales processes often come prepackaged as sales training or Customer Relationship Management (CRM) software. Although these initiatives can be useful to an organization if they are selected and implemented appropriately, they sometimes do great harm.

For example, sales executives purchase sales training in an attempt to create improved sales results. Good sales training does in fact help salespeople become more effective at reaching their goals. But, like everyone else, salespeople are creatures of their environment. If the environment is not changed, behaviors tend to return to their pre-training state. Although this problem is well known, sales executives often do not recognize the impact of mismatches between their own organization’s sales environment and the assumptions of a sales training program. Many millions of dollars are wasted each year in training programs that are far less effective than they could be for this reason.

In the case of CRM software, a company is often faced with fitting its business to the software, instead of the other way around. Anxious to collect license fees, software firms generally recommend, “Let’s just get the software running vanilla for now; then down the road we can think about modifying it.” Down the road, most companies discover many dubious assumptions:

Assumption Realities
CRM systems provide management with information for better “control” of field activities. Why would salespeople provide information to a system that can and will be used against them?
CRM suppliers know how to make a sales process work. Most CRM systems only track activities; they are poor at helping people sell.
The supplier’s sales process model is fine for our business. The supplier’s sales process model may be inappropriate for our business.
We can always make system changes later to fit our business better. After the system has lost credibility and support in the organization, who cares?

Many organizations have found CRM implementations to be extremely frustrating experiences. Why do so many organizations find themselves in this situation? One reason is that executives assume that everyone else already understands how their business works, so someone else (such as the software vendor or an administrator) can map out the details.

However, if people within the organization haven’t created a reasonable map of the sales process for themselves, how can they expect an outside supplier’s assumptions to be on the mark? In this regard, Dick Lee, author of The Customer Relationship Management Survival Guide, offers a valuable perspective:

“Customer Relationship Management means implementing customer-centric business strategies, which drives redesigning of functional activities, which demands re-engineering of work processes, which is supported, not driven, by CRM technologies.”

CRM software is very powerful. It requires answers to questions such as, “How do we create value for customers?” and “How do we measure the value we create?” If leaders in the organization don’t fully account for the answers, the initiative will fail – not because the CRM product is inadequate but because the organization didn’t create an environment in which it could work.

Principle #4: Engage your people in process mapping to define problems and solutions


Software and training suppliers can provide valuable tools to support your sales process. But the sales process itself can’t be purchased from an outside supplier. It requires the hearts and minds of your people. It is the hearts and minds of your people. It is your customer relationship strategy. The leaders of a sales organization need to generate a common vision and implement it collaboratively. Process mapping is an ideal tool to engage people in creating and achieving this common vision.

Saturday, 7 October 2017

Sizing Up Your Project Status Report

Does your current status report measure up to Best Practices standards? This article lets you size up yours by outlining what project management experts consider essential in creating the most effective project status report. You’ll also learn how you can get a FREE customizable project status report template designed to meet those standards, courtesy of Project Management Docs.

Value of Project Status Reports


Sizing Up Your Project Status Report

Basically, the value of a status report is to communicate the overall status of your project in a clear and concise manner. To be most effective, the report should be formatted to provide the overall picture of the project at a glance for top-level management. At the same time, it should cover enough in-depth information for team members and immediate managers. It’s essential to keep everyone involved “on the same page” so the project can proceed as smoothly as possible. You want to make sure there is no confusion about its current status and that all issues and risks impacting the project are addressed.

Weekly or Monthly?


Executives on a time crunch want a snapshot. Project managers and team members require more detail. An effective status report should accommodate both. For instance, the template designed by Project Management Docs reflects Best Practices by incorporating an executive summary as well as a color coded dashboard to visually show the status of the project. Both features give executives a quick update at a glance. The same template includes sections which are typically needed for weekly status meetings so the working team has the needed specifics to discuss the project, make changes as necessary and plan next steps for action.

Color Coding


The dashboard concept, headlining the report, simply uses three traffic colors, that is, red, yellow, and green “lights” to immediately convey the status of the project’s scope, schedule, cost, quality and risks. The project manager can assign a percentage to each color that changes as the project moves forward. For instance, you may choose yellow for up to a 10% variance and red for a 10% to 20% variance.

Key Performance Indicators


Sizing Up Your Project Status Report

While using a color dashboard is one way to provide an instant view of the health of the project, an effective status report also needs to present an evaluation of some key performance indicators (KPIs). You want to be able to measure and monitor earned value metrics such as schedule variance (SV), schedule performance index (SPI), cost variance (CV) and cost performance index (CPI). Again, the objective is to convey the status of a project and not get too involved in Earned Value Management (EVM). A detailed EVM analysis, separate from the status report, can expand on any problems or issues with the project. Your organization will likely have additional KPI's to be included in your status report.

Ideally, the KPIs list becomes a wrap-up, allowing the reader to flip to the bottom of the last page for a topline assessment of the SV, SPI, CV and CPI figures.

Other Sections to Include


A good project status report should include sections such as work completed last month, work planned for next month, a list of open risks or red flags and change requests, along with a section that outlines deliverables and milestones. You can determine how much detail management in your company/organization prefers. Always be aware that management has a lot of balls to juggle so the more efficient you can be in presenting the status of your project, the better impression you make. However, if events like inclement weather or an unexpected glitch in software has affected the schedule, you need to inform management and briefly explain what impact the problem will have on the project.

Avoid Over Kill


A good length for a status report: only a few pages. You want to cover the main points but shorter is always better. That’s why, once you have the data and information recorded, you would be well advised to do a final check to make sure the report is written as concisely as possible. Too long in any communication means it will likely not be read and all your efforts will be wasted.

We have a free Project Status Report Template available for download under the Project Monitoring & Controlling section of our website. The template comes with a guide to each section and allows you to modify the report to your particular project and organization. Be sure to check out all the project management tools available to you on our site.

Thursday, 5 October 2017

Risk Assessment Meeting Guide

Introduction


The Risk assessment meeting is an important part of any project. Projects are launched to take advantage of opportunities and with these opportunities come uncertainty and risk. The project risk management plan addresses the process behind risk management and the risk assessment meeting allows the project team to identify, categorize, prioritize, and mitigate or avoid these risks ahead of time. The team uses this meeting to determine the probability and impact of each risk, determine if the risk can/should be avoided by making changes to the project, plan an appropriate response, and catalog risks and responses in the Risk Register.

The risk assessment meeting should be a formal meeting conducted during the project’s planning process. It is imperative that the project manager sends a meeting invitation and agenda to all attendees well ahead of time. This allows the meeting participants time to review what will be discussed and note any risks they may have already identified. At a minimum, the following should be invited to the risk assessment meeting:

◉ Project Manager: acts as the chairperson and facilitates the meeting
◉ Project Team: the project manager must assign members of the project team the roles of recorder and timekeeper
◉ Key Stakeholders: those identified that may bring value in the identification of project risks and/or mitigation and avoidance strategies
◉ Subject Matter Experts: those identified that may specialize in a certain project activity but are not formally assigned to the project but may add value
◉ Project Sponsor: may participate depending on the size and scope of the project
Although meeting times may vary, 2 to 3 hours is a good estimate depending on the project size.


Risk Identification


Before the risk assessment meeting the project manager will have compiled a list of risks from previous projects. These will be reviewed at the beginning of the meeting as a way to not only identify some common risks but also as a catalyst to get the participants thinking about risks.

While there are many methods for identifying risks, the Crawford Slip method is very common and effective. For the Crawford Slip method, each participant is handed a set of sticky pads on which to write their risks. The project manager gives the participants 10 minutes to write as many risks as they can on the sticky pads. Once the timekeeper indicates that 10 minutes have expired the project manager directs the participants to stop.

Each risk should be stated in a complete sentence which states the cause of the risk, the risk, and the affect that the risk has on the project (key words such as: “due to” or “because”). For example:

Name:
Cause: Because the implementation team is unfamiliar with the organizations' project management methodologies
Risk: time to implement organizations processes in the Project Management System may take longer than planned
Affect: causing delay to the schedule.

Risk Assessment Meeting, Process, Project Management

Categorize and Group Duplicates (Affinity Diagram)


Categorization makes it easy to identify duplicate risks and acts as to trigger for determining additional risks. After the 10 minute risk identification exercise the project manager will facilitate the team in the categorization of each risk. One effective method for this is to post the sticky notes on a large section of the wall where the meeting chair has posted categories onto sticky papers. The participants then put their risks on the wall beneath the appropriate category. As they identify duplicate risks they stick the duplicates on top of the other.

The project manager then discusses the risks identified under each category with the participants. As new risks are identified the meeting recorder writes them onto additional sticky papers. Once complete the category it falls under will be noted for each risk.

Qualify Risks (Assign Probability and Impact to Each Risk)


On a large section of wall space, the project manager will create an area to chart the risks according to probability and impact. Using sticky papers numbered from one to ten, the project manager will create a vertical axis for probability and a horizontal axis for impact.

The participants will post the risks onto the wall in an approximate location where the likely probability and impact for that risk intersect (subjective based on the person posting the risk). Once all the risks are posted the team as a group will review the location of the risks on the chart and make any final adjustments. Once the location for all the risks is determined the recorder will write the probability for each risk in the upper left corner of the sticky paper and the impact in the upper right corner. The risks which are located in the high probability and high impact area (upper right-most section of the chart) will be separated from the other risks for closer examination and planning. Only these risks with a high risk score will require additional work.

Risk Assessment Meeting, Process, Project Management

Determine Risk Response


For the risks which have been identified with a high risk score, the participants will determine the triggers or causes and identify responses. Responses may include: adding the risk to the project plan and scheduling for it; adding funding to the project (as a risk reserve) to mitigate any potential increase in costs, adding resources to the project (as reserve) to mitigate any potential shortage in assigned resources; developing a course of action for avoiding the risk; or accepting the risk.

After the Meeting


After the meeting the Project Manager will enter all the risks, probability-impact scores, and responses into the risk register (note that only the high risk score risks have responses). The high scoring risks will be added to the Project Management Plan. The Risk Register will also be included as an appendix to the Project Management Plan. Additionally, the risks with a high score will be added to the project schedule as a method to track the risk at the correct time. Although these risks are added to the schedule, the schedule itself is not necessarily changed. This step is to provide awareness and visibility to the participants of all high scoring risks throughout the project’s lifecycle.

Friday, 14 July 2017

The 7 Principles, Themes and Processes of PRINCE2

PRINCE2 is a project management methodology of 7s. The principles, themes and processes all follow this model. Here, we break down each one and discuss how they relate to each other.

The 7 Principles


PRINCE2 derives its methods from 7 core principles. Collectively, these principles provide a framework for good practice: