Why PMBOK® v8 Fails Without the
Right Starting Approach
ADVISORY
By Kenneth Bainey, MBA, BSc, BETI, PMP
Edmonton, Alberta, Canada
Abstract
Over the years, I have seen organizations blame PMBOK® standard when project management rollout fails. In many cases, the problem is not the standard. After decades of working with projects, I have seen organizations invest heavily in governance, templates and methodology while overlooking how their people think about project decisions. PMBOK® v8 gives us an opportunity to correct that sequence. This article explains why I believe mindset must come before method. It also argues that framework adoption begins with an operating approach, not paperwork, and shows what happens when that order gets reversed.
The Rollout That Looked Perfect on Paper
I sat in meetings where a new project management PMBOK® framework was launched with considerable enthusiasm. The steering committee was established. Governance roles were documented. Templates were approved. Risks, Assumptions, Issues, and Dependencies (RAID) logs templates were ready- the four categories most PMOs track using a log. Stage gates processes were mapped onto the organization’s delivery lifecycle. On paper, the framework looked excellent.
Six months later, the templates were still there. No one was using them how they were designed to be used. Status reports had become theater. Risk registers were populated the week before steering committee meeting and ignored after the next week. The framework hadn’t failed. It had never actually started. This is the pattern I want to mention, because I think most of the industry misdiagnoses it. Organizations don’t fail at PMBOK® because they lack process. They fail because they skip the mindset shift that must happen before process means anything.
Why More Process Doesn’t Fix an Operating Approach Problem
I have seen the same reaction many times. When delivery begins to slip, management reaches for more control and structure: another gate, another approval, another report, compliance check. I understood that reaction when I was sitting on the executive side of the table. The problem is that more control and structure does not necessarily produce better judgment. It is the solution that is closest to hand, and it produces something you can point to in a steering committee deck. But it almost never works, because the underlying problem isn’t structural. It’s behavioral.
A team that treats PMBOK® as a compliance obligation will find a way to comply with anything you build. A team that treats it as an operating system will find a way to make almost any process work.
Approach is the difference between a project manager who updates a risk register because the template requires a weekly entry, and one who updates it because they’ve internalized risk identification as part of how they think about the work in front of them. A fool with a tool is still a fool. Handing someone a template doesn’t change how they think, it just gives them a new place to put the same old habits. If you want a PM who actually thinks that way, you change how they see the job first. The tool comes after.
More…
To read entire article, click here
Editor’s note 1: This is Article 1 of 7 in a series drawn from the Author’s book, The PMBOK® v8 Application Playbook, published in June 2026. Mr. Bainey is also the author of two foundational textbooks: Integrated IT Project Management (2003), published by Artech House Engineering; and Integrated IT Performance Management (2016), published by Taylor and Francis.
Editor’s note 2: These articles are not a criticism of PMBOK8. The author is a strong supporter of PMBOK, PMI, and the v8 standard. He served as a practitioner reviewer for both PMBOK Guide v7 and v8, and the entire premise of the Playbook and this article series is built on top of the standard, not against it. The series exists to help practitioners apply PMBOK v8 more effectively in the field — it’s a companion to the standard, not a critique of it.
How to cite this article: Bainey, K. R. (2026). Mindset Before Method: Why PMBOK® v8 Fails Without the Right Starting Approach, PM World Journal, Vol. XV, Issue IX, September. Available online at https://pmworldjournal.com/wp-content/uploads/2026/09/pmwj168-Sep2026-Baney-Mindset-Before-Method-1.pdf
About the Author
Kenneth Bainey
Edmonton, Alberta, Canada
Kenneth Bainey is a retired Chief Information Technology Officer and project management professional with more than four decades of experience across public, private and academic sectors- technology modernization, consulting, teaching, and executive delivery leadership. He has led and advised on complex projects involving governance, digital modernization, stakeholder alignment, risk, performance management, and organizational change. He is a part-time lecturer in project management and has taught PMP® preparation and applied project management in Canada, the United States, Europe, and the Caribbean.
He holds an MBA from Edinburgh Business School (UK) and a BSc from the University of Alberta, along with graduate Civil Engineering studies at the University of Calgary. He also holds multiple professional designations, including PMP, P.Mgr., BETI, CMgr., CIM, and CCP.
He is the author of two foundational textbooks:
Integrated IT Project Management (2003), Artech House Engineering publisher
Integrated IT Performance Management (2016), Taylor and Francis publisher
Both books focus on moving organizations from rigid processes and reporting to genuine performance, value, and accountability. He was also one of the reviewers of PMBOK® Guide v8 and v7, contributing practitioner insights into how principles, performance domains, and value concepts can better support real delivery. In 2020, he received the PMI Global Eric Jenett Project Management Excellence Award, recognizing his sustained contributions to the profession. Ken can be contacted at ken.bainey@shaw.ca
