A recent article in this journal by Nieto-Rodriguez 2026b has prompted me to return to a theme which I have written about many times in the past, but whose relevance appears to be as strong as ever – namely the ongoing need to specifically provide for users of project outputs to be part of the strategic and project processes – both in their development, and in their deployment.
The title of Nieto-Rodriguez’s article is The Success Illusion: Why “On Time and On Budget” Tells You Almost Nothing; Reimagining Project Management for a New Era, which describes his particular concerns rather well. I will be focusing on one of his case examples, which is practically a caricature of direct failure to determine the needs of key users of the project deliverables during development, and an associated failure to make any provision for helping users deploy the deliverables.
EXAMPLE OF NEGLECT OF USERS IN BOTH DEVELOPMENT AND DEPLOYMENT
A case example of both types of neglect from Nieto-Rodriguez 2026b
I reproduce most of Nieto-Rodriguez’s case example (under his heading The Project Everyone Applauded) mainly using his words, as follows.
A few years ago I worked with a European luxury goods group. They had built a new digital platform for their boutiques. One system to hold client history, preferences, purchases and follow-up, replacing a patchwork of local tools that had grown up market by market. …… The program finished two weeks ahead of schedule and slightly under budget. Every requirement was signed off. Every governance gate cleared at the first attempt……
Almost a year later, I was back with the same company on something unrelated, and asked what had become of the platform. The answer was uncomfortable. Sales advisors in the boutiques had quietly stopped using it. They had gone back to their own notebooks and their own phones.
The system worked exactly as designed. It had been designed around what headquarters wanted to see, not around what an advisor actually does in the ninety seconds before a client walks through the door. Nobody had asked the advisor. By every measure the organization used, that project was a triumph. By the measure that would have produced value, it never really began. The delivery was flawless. The investment was not.
We will first discuss failures to involve key operational users in developing this project.
DISUSSION OF NEGLECT OF USERS IN PROJECT DEVELOPMENT
Failure to consult key operational users in project development phases
The apparently inexcusable failure to consult with the key operational users in Nieto-Rodriguez’s example (in this case the sales advisors) in the development of the project might be seen as a somewhat exceptional oversight. However, as Nieto-Rodriguez also points out, this type of failure is evidently not uncommon.
The luxury group is not unusual. Systems are handed over, declared complete, and then compete for attention with the habits they were meant to replace.
Although he does not specifically mention failure to involve users in the development of this system, it is evidently implicit.
I personally find this type of failure nearly impossible to understand. I was the project manager for the introduction of a major new cost and financial system for Civil & Civic in the early 1960s, after it had completely outgrown its old systems. I don’t know of anyone who did not believe that it was absolutely necessary to consult with users at all levels to ascertain what they needed from a new system, and to check with them as the latter was being developed…
Life Fellow, AIPM (Australia)
Auckland, New Zealand
Alan Stretton is one of the pioneers of modern project management. In 2006 he retired from a position as Adjunct Professor of Project Management in the Faculty of Design, Architecture and Building at the University of Technology, Sydney (UTS), Australia, which he joined in 1988 to develop and deliver a Master of Project Management program. Prior to joining UTS, Mr. Stretton worked in the building and construction industries in Australia, New Zealand and the USA for some 38 years, which included the project management of construction, R&D, introduction of information and control systems, internal management education programs and organizational change projects. Alan has degrees in Civil Engineering (BE, Tasmania) and Mathematics (MA, Oxford), and an honorary PhD in strategy, programme and project management (ESC, Lille, France). Alan was Chairman of the Standards (PMBOK) Committee of the Project Management Institute (PMI®) from late 1989 to early 1992. He held a similar position with the Australian Institute of Project Management (AIPM) and was elected a Life Fellow of AIPM in 1996. He was a member of the Core Working Group in the development of the Australian National Competency Standards for Project Management. He has published 280+ professional articles and papers. Alan can be contacted at alanailene@bigpond.com .
Re-emphasising the need for users of project outputs
to be included in project development
and deployment processes
COMMENTARY
By Alan Stretton, PhD (Hon)
New Zealand
INTRODUCTION
A recent article in this journal by Nieto-Rodriguez 2026b has prompted me to return to a theme which I have written about many times in the past, but whose relevance appears to be as strong as ever – namely the ongoing need to specifically provide for users of project outputs to be part of the strategic and project processes – both in their development, and in their deployment.
The title of Nieto-Rodriguez’s article is The Success Illusion: Why “On Time and On Budget” Tells You Almost Nothing; Reimagining Project Management for a New Era, which describes his particular concerns rather well. I will be focusing on one of his case examples, which is practically a caricature of direct failure to determine the needs of key users of the project deliverables during development, and an associated failure to make any provision for helping users deploy the deliverables.
EXAMPLE OF NEGLECT OF USERS IN BOTH DEVELOPMENT AND DEPLOYMENT
A case example of both types of neglect from Nieto-Rodriguez 2026b
I reproduce most of Nieto-Rodriguez’s case example (under his heading The Project Everyone Applauded) mainly using his words, as follows.
A few years ago I worked with a European luxury goods group. They had built a new digital platform for their boutiques. One system to hold client history, preferences, purchases and follow-up, replacing a patchwork of local tools that had grown up market by market. …… The program finished two weeks ahead of schedule and slightly under budget. Every requirement was signed off. Every governance gate cleared at the first attempt……
Almost a year later, I was back with the same company on something unrelated, and asked what had become of the platform. The answer was uncomfortable. Sales advisors in the boutiques had quietly stopped using it. They had gone back to their own notebooks and their own phones.
The system worked exactly as designed. It had been designed around what headquarters wanted to see, not around what an advisor actually does in the ninety seconds before a client walks through the door. Nobody had asked the advisor. By every measure the organization used, that project was a triumph. By the measure that would have produced value, it never really began. The delivery was flawless. The investment was not.
We will first discuss failures to involve key operational users in developing this project.
DISUSSION OF NEGLECT OF USERS IN PROJECT DEVELOPMENT
Failure to consult key operational users in project development phases
The apparently inexcusable failure to consult with the key operational users in Nieto-Rodriguez’s example (in this case the sales advisors) in the development of the project might be seen as a somewhat exceptional oversight. However, as Nieto-Rodriguez also points out, this type of failure is evidently not uncommon.
The luxury group is not unusual. Systems are handed over, declared complete, and then compete for attention with the habits they were meant to replace.
Although he does not specifically mention failure to involve users in the development of this system, it is evidently implicit.
I personally find this type of failure nearly impossible to understand. I was the project manager for the introduction of a major new cost and financial system for Civil & Civic in the early 1960s, after it had completely outgrown its old systems. I don’t know of anyone who did not believe that it was absolutely necessary to consult with users at all levels to ascertain what they needed from a new system, and to check with them as the latter was being developed…
More…
To read entire paper, click here
How to cite this work: Stretton, A. (2026). Re-emphasising the need for users of project outputs to be included in project development and deployment processes, commentary, PM World Journal, Vol. XV, Issue X, October. Available online at https://pmworldjournal.com/wp-content/uploads/2026/10/pmwj169-Oct2026-Stretton-PMWJ-re-emphasizing-users-of-project-outputs.pdf
About the Author
Alan Stretton, PhD
Life Fellow, AIPM (Australia)
Auckland, New Zealand
Alan Stretton is one of the pioneers of modern project management. In 2006 he retired from a position as Adjunct Professor of Project Management in the Faculty of Design, Architecture and Building at the University of Technology, Sydney (UTS), Australia, which he joined in 1988 to develop and deliver a Master of Project Management program. Prior to joining UTS, Mr. Stretton worked in the building and construction industries in Australia, New Zealand and the USA for some 38 years, which included the project management of construction, R&D, introduction of information and control systems, internal management education programs and organizational change projects. Alan has degrees in Civil Engineering (BE, Tasmania) and Mathematics (MA, Oxford), and an honorary PhD in strategy, programme and project management (ESC, Lille, France). Alan was Chairman of the Standards (PMBOK) Committee of the Project Management Institute (PMI®) from late 1989 to early 1992. He held a similar position with the Australian Institute of Project Management (AIPM) and was elected a Life Fellow of AIPM in 1996. He was a member of the Core Working Group in the development of the Australian National Competency Standards for Project Management. He has published 280+ professional articles and papers. Alan can be contacted at alanailene@bigpond.com .
To see more works by Alan Stretton, visit his author showcase in the PM World Library at http://pmworldlibrary.net/authors/alan-stretton/.
Share this:
Like this:
Related