Have you ever faced the daunting task of evaluating an entire organizational program, knowing that billions of dollars and your company’s reputation are on the line? That’s exactly the situation I found myself in when the CEO of one of our nation’s science laboratories approached me with a critical challenge. The lab was under fire from the Federal Government for weaknesses in its procurement process, and a multi-billion-dollar contract hung in the balance. The CEO asked me to evaluate their procurement program from top to bottom – a task that seemed almost impossible given the complexity of their procurement program, the hundreds of identified issues, and the high stakes involved.
But as they say, necessity is the mother of invention. Faced with this challenge, I developed a new technique that I now call PXP, which stands for Pareto Analysis x Process Mapping. This innovative approach combines weighted Pareto analysis with process mapping to quickly identify and address critical issues in complex organizational processes. Let me walk you through how PXP works and how it revolutionized our approach to this complex and high-pressure situation.
Breaking Down the PXP Technique Using an Actual Case Study
The PXP technique consists of merging two tools and techniques that are traditionally conducted separately. Here are the main steps for the PXP technique as they were applied to a comprehensive assessment of a Procurement Program at one of our nation’s National Science Laboratories:
1. Weighted Pareto Analysis:
First, we conducted a comprehensive Pareto analysis of the lab’s large database of procurement problems. We sorted these issues not only by cause codes and responsible organizations, but also by the specific part of the procurement process where each issue occurred. We use weighting factors (a multiplier of x2 or x3) to account for the relative importance of certain information. The result is a frequency plot of where most of the problems were concentrated within the overall procurement process. These are valuable insights that we need to focus on the program’s weaknesses.
2. Process Mapping:
Next, we created a process map of the entire procurement process from start to finish. But here’s where we diverged from traditional mapping: instead of detailing every step, we created a framework or skeleton of the process. On the horizontal axis, we laid out the main phases of the procurement process. On the vertical axis, we listed all the organizations involved in the process.
3. Merging the Two Tools and Techniques:
We then plotted the results of our Pareto analysis on the process map outline. Suddenly, clear “hot spots” emerged – areas where the vast majority of issues were occurring. These hot spots jumped out visually, allowing us to quickly identify the most problematic areas in the procurement process, as well as which organization or job function owns that part of the process.
4. From Insights to Evidence-Based Questions:
Armed with these powerful insights, we were able to generate focused, evidence-based lines of inquiry questions about these hot spots. We generated over 120 very specific questions that allowed us to explore the many symptoms of programmatic weaknesses. Based on the questions and the process map, we determined the affected organizations that could answer these questions. We then established a plan to invite the appropriate subject matter experts from these organizations to participate in focus groups, where we could pose our questions and conduct and in-depth cause and effect analysis. Overlaying the results of our Pareto analysis on the process map and establishing our lines of inquiry questions were completed in the first week.
5. Focus Groups Yielded the Root Causes:
Once we established which organizations were responsible for the “hot spots,” we invited over 120 subject matter experts from 18 affected organizations to participate in 14 focus groups. In these focus groups we posed our questions and led the discussions straight into and in-depth cause and effect analysis. The 14 sessions with over 120 SMEs were completed in the second week.
Figure 1: The process map with an overlay of the Pareto Analysis (the “hot spots”)
The Power of PXP: Results and Benefits
The results were remarkable. At the end of two weeks, we had a clear understanding of the driving forces, the deep-seated organizational and programmatic weaknesses, that were causing the procurement program to underperform. The key that unlocked these insights was the PXP approach – overlaying the results of a weighted Pareto analysis on top of a process map framework of the procurement program.
The PXP technique proved to be a game-changer in several ways:
1. Rapid Identification:
We quickly pinpointed the exact areas where the procurement process was breaking down, rather than getting lost in the complexity of the entire system.
2. Precision:
By focusing on the concentration of problem areas (hot spots), we were able to drill down to the true root causes and contributing factors, rather than getting sidetracked by less impactful issues.
3. Engagement:
The visual nature of the PXP results made it easy to engage stakeholders and subject matter experts, facilitating more productive discussions and analyses that efficiently allowed us to get to the root causes.
4. Data-Driven Decision Making:
Every step of the process was grounded in data, from the initial Pareto analysis to the final recommendations.
5. Efficiency:
The entire analysis process took only two weeks – a fraction of the time it would have taken using traditional methods. Our client actually believed any assessment of their procurement program would take 3 to 6 months. And this process can be more efficient by using virtual white boards, rather than post-its on a wall.
Beyond Procurement: PXP Use Cases
While we developed PXP for an in-depth procurement program evaluation, its potential applications are vast. Any complex organizational process that generates data could benefit from this approach. Whether you’re dealing with manufacturing quality issues, customer service complaints, or IT system failures, PXP can help you quickly identify and address the most critical problem areas.
Here are just a few of the potential applications for this PXP technique:
1. Cybersecurity Threat Management:
a. Mapping types of cyber-attacks (e.g., phishing, malware, DDoS) to different network layers or system components.
b. Analyzing the effectiveness of various security controls across different stages of the cybersecurity lifecycle (prevention, detection, response, recovery).
c. Identifying which departments or user groups are most frequently targeted or involved in security breaches.
d. Analyzing the distribution of security vulnerabilities across different software applications, hardware components, or cloud services used by the organization.
2. Energy Sector:
a. Nuclear Power Plant Operations: Analyze safety incident reports across different operational phases to identify high-risk areas.
b. Oil & Gas Exploration: Map equipment failures to specific stages of the drilling and extraction process.
3. Aerospace & Defense:
a. Aircraft Manufacturing: Identify quality issues across various stages of the production line.
b. Defense Systems Development: Analyze cost overruns and delays in different phases of project lifecycles.
4. Healthcare:
a. Hospital Patient Flow: Map bottlenecks in patient admission, treatment, and discharge processes.
b. Pharmaceutical Supply Chain: Identify inefficiencies in drug development, production, and distribution processes.
5. Manufacturing:
a. Automotive Production: Analyze defects and quality issues across assembly line stages.
b. Electronics Manufacturing: Map component failures to specific production processes.
6. Cross-Industry Applications:
a. Supply Chain Optimization: Identify bottlenecks and inefficiencies across your supply chain.
b. Software Development: Identify which phases of your development lifecycle are producing the most bugs or delays.
c. Industrial Safety: Identify high-risk activities or areas across different operational processes.
d. Maintenance Management: Analyze equipment breakdowns and maintenance issues across various facility areas or production stages.
e. Security & Safeguards: Identify vulnerabilities or breaches across different security checkpoints or protocols.
f. Work Control Systems: Map delays or errors in work order processes from initiation to closure.
g. Engineering Change Management: Analyze bottlenecks or errors in the design modification process.
h. Environmental Health & Safety: Map incidents or non-compliances to specific operational areas or processes.
i. Quality Assurance: Analyze audit findings or non-conformances across different stages of the quality management system.
j. Quality Control: Pinpoint the stages in your production process where defects are most likely to occur.
k. Customer Service Improvement: Map customer complaints to specific parts of your service delivery process.
Conclusion: PXP is A Powerful Technique for Proactive Program Assessments
In today’s fast-paced business environment, we don’t have the luxury of spending months on program evaluations or process improvements. The PXP technique offers a way to quickly cut through the complexity of large-scale organizational processes and zero in on the areas that need the most attention.
By combining the power of data analysis (through weighted Pareto analysis) with the visual clarity of process mapping, BlueDragon’s PXP technique provides a unique and powerful tool for organizational problem-solving. It allows us to see the forest and the trees simultaneously – understanding both the overall process and the specific pain points within it.
As you face your next big organizational challenge, consider giving the PXP technique a try. You might be surprised at how quickly you can uncover insights that drive real, impactful change. After all, in the world of problem-solving, sometimes the best solutions come from looking at old problems in new ways.
For additional information on how to use PXP, schedule a free consultation with us.