Introduction
You face a recurring operational dilemma when strategic decisions made in the boardroom fail to translate into successful deliverables on the shop floor. Executives historically treated project management as a worker-level scheduling tool that generated unnecessary overhead and conflict. You experience this execution gap as missed deadlines, ballooning budgets, and resource allocation battles across departments. Organizations spent decades struggling to coordinate complex initiatives because they lacked a standardized framework.
Harold Kerzner solves this structural failure in Project Management by introducing the Project Management Maturity Model. The central idea is that achieving organizational excellence requires a structured five-level maturity model that transforms project management from a tactical tool into a sustainable strategic advantage. You learn to bridge the chasm between high-level business strategy and operational delivery by institutionalizing repeatable processes, singular methodologies, continuous benchmarking, and blame-free learning cultures.
The book guides you through the architecture of organizational maturity, starting with the historical need for structured management and progressing through the five distinct levels of the model. You discover how to customize assessment tools for your specific operating environment, extract valuable industry best practices, and conduct comprehensive organizational evaluations. The following questions guide your journey through this text:
- How do you transition an organization from informal project management to a standardized enterprise methodology?
- What metrics and assessment instruments accurately measure your current maturity level?
- How do you overcome internal corporate resistance and secure active executive sponsorship?
- What steps allow you to convert project management maturity into a sustainable competitive advantage?
1. The Strategic Need for Project Management
Organizations spent over forty years viewing project management merely as a worker-level scheduling tool that generated overhead and conflict, rather than recognizing it as a fundamental corporate competency.
For more than 40 years of using project management principles, organizations resisted recognizing project management as a core competency. Executives feared that treating project management as a strategic competency would require delegating decision-making authority to project managers. This transfer of authority threatened to diminish executive power and control bases.
Past misconceptions viewed project management as a driver of overhead costs, conflicts, and scope creep. Organizations previously believed project management increased administrative burdens and power struggles through multiple-boss reporting. Modern views demonstrate that structured project management lowers operational costs, improves customer relations, and delivers business solutions rather than just products.
Historical Resistance to Project Management
Executive reluctance manifested in specific operational views that dismissed formal project structures as unnecessary bureaucracy.
- Viewing project management merely as a scheduling tool.
- Dismissing formal methodologies as eyewash.
- Fearing suboptimization of departmental resources.
- Rejecting multiple-boss reporting structures.
Bridging the Strategy and Implementation Gap
Strategic planning often fails because consultants provide high-level advice on what to do without detailing how to do it. When executives hire consultants for business strategy, they frequently receive direction on market positioning but lack execution guidance. Project management bridges this gap by converting high-level strategic objectives into actionable operational steps.
A Fortune 500 company hired consultants to analyze product lines and strategy. After 1 week of meetings between executives and consultants, executives realized the consultants told them what to do but not how to do it. This realization prompted them to mandate project management training through Human Resources to ensure successful strategy implementation.
2. Defining Project Management Maturity
Project management maturity is an ongoing, continuous improvement process supported by structured assessment instruments and key intangible performance indicators.
With more than 30 project management maturity models in the marketplace, you must choose a model that aligns with your specific industry and business needs. These frameworks help you assess delivery systems, uncover improvement opportunities, and measure both tangible and intangible assets. Periodic reassessments ensure that continuous improvements are executed and gaps identified in previous evaluations are successfully closed.
Maturity is not a static point in time but a continuous cycle supported by periodic reassessments. It enables you to improve your capability to meet strategic goals and objectives through structured benchmarking against industry and world-class standards. This approach requires maintaining a continuous improvement baseline across your enterprise. You must examine the project delivery system and supporting infrastructure together.
As organizations mature, performance measurement must expand beyond traditional time, cost, and scope metrics to incorporate key intangible performance indicators such as leadership, trust, and corporate culture. For more than five decades of organizational focus heavily on earned value measurement techniques, businesses relied exclusively on tangible constraints. Modern dynamic organizations utilize both key performance indicators and key intangible performance indicators to evaluate long-term organizational success.
3. Customizing the Maturity Model
Organizations must often customize standard Project Management Maturity Models to align with their specific operating environments and short-term progress expectations.
Standard maturity frameworks assume that continuous improvement is easy and universally agreed upon. If your organization operates differently, or if you coordinate outsourced work managed by independent contractors, generic assumptions will fail.
Customization driven by senior management vision prevents significant employee resistance. It allows you to track measurable progress at regular assessment intervals rather than waiting years for results.
Public-sector agencies face severe project management difficulties because they operate under unique constraints. Government bodies often outsource 90 percent or more of their projects to private-sector firms. Contracts frequently go to the lowest bidder regardless of technical expertise. This environment creates distinct operational realities:
- immense ambiguity driven by political pressures;
- extreme risk aversion due to the fear of project cancellation;
- lack of clear career paths for project managers;
- difficulties implementing matrix management across hierarchical structures.
Hosting the Olympic Games requires managing massive, highly complex infrastructure projects involving hundreds of independent contractors over a multi-year life cycle. Preparation for the Olympic Games spans more than a decade and involves hundreds of contractors, each utilizing its own project management approach. The host city government, in coordination with Olympic committees, must handle large-scale infrastructure projects including sports facilities, security, communications, and transport networks while capturing lessons learned to avoid repeating costly mistakes. During these events, you manage 13,000 athletes competing from 200 countries across 30 different sports and 400 events.
4. Foundations of the PMMM
Strategic planning for project management is driven primarily at the middle-management level with active executive sponsorship, resting on five progressive maturity levels.
Strategic planning for project management starts differently than traditional corporate planning. Executives rarely drive these initiatives from the top.
Middle management initiates strategic planning for project management to avoid repetitive mistakes. Executive management provides vital support:
- funding;
- employee release time;
- cultural backing.
Without ongoing top-down executive sponsorship, continuous improvement processes weaken and eventually stall.
An automotive supplier developed an outstanding project management methodology through middle management and senior sponsorship. Methodology improvements stalled when executive sponsorship diminished until an executive champion was reinstated.
The project management maturity model, or PMMM, consists of five progressive levels. These steps guide you from chaotic practices to optimized results:
- Common language;
- Common processes;
- Singular methodology;
- Benchmarking;
- Continuous improvement.
While completion must follow this conceptual order, certain adjacent maturity levels can overlap based on your organization's risk tolerance and strategic initiatives.
Navigating High-Risk Maturity Levels
Level 3 of the PMMM carries the highest risk and degree of difficulty. This phase requires a major shift in corporate culture toward an enterprise-wide singular methodology.
Transitioning to a singular methodology requires every part of the organization to adopt the same project management practices. This change impacts work habits, social groups, and reporting structures.
Implementing an enterprise project management methodology multinationally introduces additional complications regarding local laws, contracts, and language barriers.
5. Level 1: Common Language
Level 1 maturity addresses organizational resistance and informal project management by establishing a standardized knowledge base and common language derived from the PMBOK Guide.
Organizations at Level 1 exhibit sporadic project management usage and a lack of executive support. You face organizational resistance to change that must be overcome through foundational training.
Characteristics of Level 1
Level 1 organizations struggle with multiple-boss reporting and a management focused on self-interest. You will notice a distinct fear of power shifts and a general unwillingness to invest in training.
Overcoming these barriers requires basic education in project management principles. You should address knowledge gaps through targeted interventions:
- overview project management courses required for executives lasting 3 to 6 hours;
- foundational training in PMBOK Guide terminology;
- professional certification preparation to build internal capability.
Scoring and Assessment Instruments
Level 1 maturity measures common language via a knowledge exam based on the PMI PMBOK Guide. The assessment evaluates individuals on core knowledge areas like scope, schedule, cost, and risk.
An assessed organization at Level 1 achieved a composite score of 454.8. You evaluate the results against a clear numerical threshold:
- scores below 600 indicate isolated pockets of formal project management knowledge that require remediation;
- a score above 600 shows a very good understanding of the required concepts.
6. Level 2: Common Processes
Level 2 focuses on developing repeatable common processes, standard life-cycle phases, and horizontal accounting systems to track costs and schedules across projects.
Moving beyond a shared vocabulary requires building repeatable procedures. You must develop standard life-cycle phases and horizontal accounting systems to track costs and schedules.
Progressing through this stage typically requires 6 months to 2 years. Survival forces, executive understanding, and new product development demands drive the adoption.
Evolutionary Phases of Common Processes
Level 2 common processes maturity evaluates respondent perceptions across five life-cycle phases driven by organizational forces like customer expectations and competitiveness. The survey uses 4 questions per phase to measure progress. An assessed organization achieved an average score of 18.0 in a range from minus 60 to plus 60.
The transition advances through distinct steps:
- embryonic phase;
- executive management acceptance;
- line management acceptance;
- growth;
- maturity.
Acceptance and implementation are pushed by customer expectations, market competitiveness, executive understanding, new product development demands, efficiency, and business survival.
Implementing Horizontal Accounting
Adopting horizontal accounting allows you to capture true cross-functional project costs. Line managers and executives often resist this visibility because it exposes estimating inaccuracies and budget variances.
7. Level 3: Singular Methodology
Level 3 achieves enterprise-wide efficiency by condensing disparate departmental approaches into a singular methodology supported by the Hexagon of Excellence.
Achieving a Singular Methodology
Organizations often start with multiple disparate approaches for different domains like IT and new product development. Maturity involves condensing these frameworks to the minimum necessary number of methodologies.
As maturity progresses, this singular approach becomes flexible. You can incorporate frameworks like agile and Scrum without breaking the core structure.
The Hexagon of Excellence
The Hexagon of Excellence comprises six key characteristics that differentiate project management-driven companies from average ones. These integrated areas form the core foundation of Level 3 maturity.
- Integrated processes
- Cultural support
- Management support
- Informal project management
- Training and education
- Behavioral excellence
Overcoming Cultural Fears
Cultural transformation toward a cooperative project management environment encounters four primary organizational fears that must be strategically addressed. Recognizing these barriers helps you ease the transition for your teams.
- The embedded fear of change
- The fear of creating a new social group
- The fear of shifting work habits or comfort zones
- The uncertain impact on wage and salary programs
8. Level 4: Benchmarking
Level 4 institutionalizes quantitative and qualitative benchmarking against similar and nonsimilar industries through dedicated project management offices.
Reaching Level 4 maturity requires continuous benchmarking to compare your internal project management practices against world-class leaders. You must maintain a competitive advantage by constantly measuring your performance against external standards.
Benchmarking for Competitive Advantage
Project management benchmarking involves analyzing critical success factors and key business processes. You must pair this data collection with a willingness to make structured changes.
Process benchmarking requires you to adhere to a strict code of conduct. You evaluate your methods against the best companies to identify operational gaps.
PMOs and Centers of Excellence
Organizations at Level 4 establish a project management office or a center of excellence to centralize knowledge. These entities direct benchmarking efforts and lead continuous improvement across departments.
- A project office typically focuses internally on methodology implementation.
- A center of excellence emphasizes external benchmarking and identifying new tools.
An aerospace company spent over 10 years benchmarking only against other aerospace companies before turning to non-aerospace firms in the mid-1990s and discovering superior methodologies.
Nonsimilar Industry Comparisons
Benchmarking against nonsimilar industries provides vital opportunities to discover innovative methodologies and practices outside traditional sector boundaries. Companies frequently benchmark exclusively within their own industry.
Expanding your search to nonsimilar industries uncovers advanced capabilities and creative applications that surpass internal standards. You break through conventional industry limitations by looking at how entirely different fields solve complex scheduling and execution problems.
9. Level 5: Continuous Improvement
9. Level 5: Continuous Improvement
Level 5 of the Project Management Maturity Model represents continuous improvement, recognizing that project management excellence is a never-ending journey. You evaluate benchmarking data and implement changes once your organization reaches this pinnacle.
Level 5 embeds a blame-free learning culture, comprehensive lessons-learned files, competency models, and portfolio management to sustain continuous improvement.
Characteristics of Continuous Improvement
Key characteristics of Level 5 include creating lessons-learned files from debriefings. You must transfer knowledge through forums and training to prevent repeating past mistakes. Establishing mentorship programs via a project management office or center of excellence ensures continuity. You also view strategic planning as an ongoing corporate-wide process rather than an isolated annual event.
Competency Models and Capacity Planning
Competency models replace traditional job descriptions by focusing on specific skills needed to achieve deliverables. These models allow training departments to build customized curricula rather than generic courses to address specific skill requirements.
Eli Lilly utilizes a competency model expecting project managers to have competencies in scientific and technical skills, leadership skills, and process skills.
Portfolio Selection and Multiple Projects
Projects must be strategically selected and prioritized using a portfolio classification matrix based on benefits and resource quality. You can classify projects to protect positions, build selectively, or assign team leaders, ensuring optimal resource allocation. Using a nine-square grid based on potential benefits and the quality of resources needed, you protect your organization from overcommitment.
10. Sustainable Competitive Advantage
Project management methodologies should be designed with the intent of converting them into a sustainable competitive advantage. A sustainable competitive advantage places pressure on competitors and requires continuous improvement. You must manage risk and align four strategic thrusts.
Integrating core values, strategic thrusts, and delivery systems allows organizations to convert their project management maturity into a sustainable competitive advantage focused on business solutions.
Strategic Thrusts and Competitive Advantage
Alignment requires focusing on specific elements. You must balance internal strengths against market realities.
The four strategic thrusts include:
- core values and core purpose;
- strategic focus;
- competitive focus;
- synergy.
Shifting from Products to Solutions
Strategic planning for project management has evolved to focus on delivering complete business solutions rather than isolated products. Selling solutions requires providing the delivery system alongside the product.
You use the project management methodology as part of the offering to handle the installation, testing, and operation for the client. Enterprise project management and engagement project management ensure that the client receives a complete operational capability rather than a simple hardware drop.
11. Advanced Maturity Assessments
Advancing to PM 2.0 and PM 3.0 incorporates agile collaboration, value management, and the measurement of intangible assets while avoiding metric mania.
From PM 1.0 to PM 3.0
Traditional management methods often fall short on complex assignments. You must update your practices to handle modern operational demands.
PM 2.0 combines traditional management with open communication. It relies on:
- distributed collaboration;
- agile principles;
- decentralized planning;
- dashboard reporting;
- committee governance.
PM 3.0 elevates project management into a strategic business process. You shift away from tracking only tangible execution metrics. Instead, you use structured business cases and value measurement methodologies.
Measuring Intangible Assets and Agile Integration
Benefits realization and value-management practices align your investments directly with strategic business objectives. You can evaluate non-monetary elements that impact your long-term bottom line and human performance.
PM 4.0 focuses specifically on intangible project management assets. These key factors reflect corporate health:
- governance quality;
- leadership;
- teamwork;
- trust;
- knowledge management.
Socialized project management connects distributed teams effectively. You utilize agile or Scrum approaches derived largely from software development. This environment allows you to monitor continuous performance improvements across complex organizational structures.
12. Conducting Maturity Assessments
Organizations act like biological organisms that reject unfamiliar changes. People naturally fear leaving their comfort zones or being judged by new metrics.
Conducting successful maturity assessments requires bypassing the corporate immune system, utilizing online tools, and engaging a broad cross-section of participants.
Bypassing the Corporate Immune System
You must overcome cultural resistance during a project management maturity assessment. Leaders should acknowledge these fears directly and start small with enthusiastic volunteers. Project-driven departments like IT and R&D provide welcoming entry points for early testing. You must also clearly communicate the ultimate purpose of the assessment to reduce anxiety.
Online Tools and Executive Dashboards
Web-based delivery methods allow for efficient distribution and automated scoring. The Kerzner Project Management Maturity Online Assessment Tool contains more than 180 questions. This software features an intuitive interface and auto-sorting of results by key departments, job functions, or hierarchy.
An Executive Dashboard enables top management to continuously monitor scores and export raw data into spreadsheet applications.
Strategic Participation Guidelines
An accurate maturity assessment requires broad representation across all hierarchical levels and departments. Assessing only experienced project managers yields a biased view of reality. Companies should involve cross-functional teams, key customers, stakeholders, and all layers of the corporate hierarchy.
Statistical validity requires you to follow specific sampling guidelines:
- invite 30 or more individuals from each operating unit;
- target at least 10 percent of the population in large companies.
You establish a PMMM assessment action team to coordinate these strategic participation efforts across the enterprise.
13. Extracting Best Practices
Capturing best practices has become essential for corporate survival as customers increasingly demand proof of formal methodologies and credentialed staff in proposals.
Treating best practices as intellectual property driven by proposal pressures requires a rigorous nine-step management process and periodic reevaluation.
Proposal Pressures and Survival
In response to customer requests for proposals, contractors must demonstrate certified staff, enterprise project management methodologies, maturity levels, and a willingness to share lessons learned. Treating best practices as intellectual property drives higher performance and business value. You must showcase PMP credential holders and an enterprise project management methodology to win competitive contracts. Customers expect clear evidence of continuous improvement and mature processes before awarding complex work.
The Nine-Step Best Practices Process
Implementing best practices effectively requires a structured, multi-step process for defining, validating, storing, communicating, and monitoring them. Companies must follow a structured process that answers nine critical questions ranging from defining what a best practice is to ensuring employees use them properly. This involves establishing ownership, determining validation criteria, setting up libraries, and performing regular reevaluations.
Maintaining Best Practice Libraries
Best practices require active management by designated owners and periodic reevaluation because they age and change alongside corporate definitions of success. Management involves three players: the best practice owner who maintains integrity, the PMO which holds final authority, and the library administrator who acts as caretaker. Because best practices age, companies must periodically review their libraries, deciding to keep, update, or retire practices.
One company started a best practices library and amassed hundreds of entries, but a later reevaluation revealed that fewer than one-third were still valid. You must guard against best practices overload by purging outdated methods that no longer reflect your current operational environment.
10 Key Ideas
- Harold Kerzner bridges the execution gap between boardroom strategy and operational delivery by introducing the Project Management Maturity Model to transform tactical tools into sustainable strategic advantages.
- Organizations spent over forty years viewing project management merely as a worker-level scheduling tool that generated overhead and conflict, rather than recognizing it as a fundamental corporate competency.
- Project management maturity is an ongoing, continuous improvement process supported by structured assessment instruments and key intangible performance indicators.
- Organizations must often customize standard Project Management Maturity Models to align with their specific operating environments and short-term progress expectations.
- Strategic planning for project management is driven primarily at the middle-management level with active executive sponsorship, resting on five progressive maturity levels.
- Level 1 maturity addresses organizational resistance and informal project management by establishing a standardized knowledge base and common language derived from the PMBOK Guide.
- Level 4 institutionalizes quantitative and qualitative benchmarking against similar and nonsimilar industries through dedicated project management offices.
- Level 5 embeds a blame-free learning culture, comprehensive lessons-learned files, competency models, and portfolio management to sustain continuous improvement.
- Integrating core values, strategic thrusts, and delivery systems allows organizations to convert their project management maturity into a sustainable competitive advantage focused on business solutions.
- Conducting successful maturity assessments requires bypassing the corporate immune system, utilizing online tools, and engaging a broad cross-section of participants.