[The Path of a Project Manager] The Foundation for Making Decisions

Introduction

The role of a Project Manager (PM) is often compared to the captain of a ship navigating rough seas.
The route ahead is complex and tangled, sudden reefs (unexpected technical challenges) appear, and the crew (team members) cannot hide their fatigue.

The job of the PM, as captain, is truly nothing but a series of 'decisions'.

'Should I give up on this feature, or should I postpone the delivery date?'

'Should I accept all of the customer's requests, or should I prioritize maintaining quality?'

'How should I mediate between conflicting members?'

If one of these decisions goes wrong, it could cause the project to run aground and lead to a loss of business credibility.

The decisions a PM makes go beyond the scope of technical knowledge or management techniques, and are ultimately deeply rooted in the PM's own 'philosophy' and 'foundation' of values.
So, when the time comes, what exactly should this lonely captain believe in and rely on to set their course?

This question is the key to exploring 'the path of a project manager'.

1. Cases where a PM must make a decision

The moments of decision that a PM faces daily are diverse.
Here, I will delve into specific examples and the values that a PM should use as a foundation in those situations.

(1) Decisions regarding goals and strategy

[Example]
Toward the end of developing a new service, a powerful competitor began offering the same feature for free. The project is on the verge of a crisis where the original business model is collapsing.

[Foundation for decision-making]
'Maximizing the ultimate business value of the project'
Rather than just pushing forward because 'it was the decided goal,' the PM needs to make a decision to pivot (change direction).
In this case, rather than achieving the initial goal, it is required to return to the higher-level purpose of 'what we wanted to achieve with this project,' boldly change the scope, and find a new competitive advantage.

(2) Decisions regarding planning and execution

[Example]
The development team reported, 'Due to unexpected technical challenges, we cannot guarantee quality unless we postpone the delivery date of the most important feature by two weeks.'

[Foundation for decision-making]
'Ensuring system reliability and transparency to stakeholders'
The PM first prioritizes 'the quality that is the heart of the system' and makes the decision to allow for a delay in the delivery date.
What is important is the action that follows. Rather than hiding the fact of the delay, the PM accurately analyzes the scope of the impact based on data and reports it to the stakeholders early and with high transparency.
The PM chooses to maintain trust rather than fear temporary criticism.

(3) Decisions regarding risk and problem response

[Case Study]
Just before the system release, an external audit discovered a serious security vulnerability regarding personal information. It will take at least one week to fix, but the contractual release date is approaching.

[Basis for Decision-Making]
"Responsibility and Ethics toward Customers and Society"
This is the most agonizing decision. Rather than short-term pressures like contracts or penalties, prioritize the social ethics of "user data and safety."
The PM has the responsibility to make decisions that are painful in the short term but correct in the long term, such as delaying the release or temporarily suspending the service.

(4) Decisions regarding stakeholders and the team

[Case Study]
A technology-oriented engineer and a business-oriented planner clashed intensely over implementation policies, causing the meeting to reach a deadlock.

[Basis for Decision-Making]
"Team Health and Commitment to Common Goals"
The PM does not ignore the emotional walls lying between the conflicting parties and explores the "true intent" behind both opinions.
Perhaps the engineer is seeking "long-term maintainability," while the planner is seeking "early market entry."
The PM acts as a mediator, showing which intent contributes more to the success of the project, and makes a decision to reconcile their interests.

(5) Decisions regarding costs and contracts

[Case Study]
Due to unexpected work delays by an external vendor, a budget overrun has become certain. You are forced to choose between securing an additional budget or cutting lower-priority scope.

[Basis for Decision-Making]
"Sustainable Business Decisions"
This decision is the same as holding the "purse strings." The PM does not simply look at the amount of the budget, but weighs the long-term impact that reducing scope will have on customer satisfaction.
If accepting a short-term cost overrun allows you to avoid losing a major future revenue opportunity, you make the decision to secure the funds.
This requires business insight that goes beyond mere short-term contract compliance.

(6) Decisions regarding results and evaluation

[Case Study]
The project was completed within the deadline and budget, and all quantitative goals (such as processing speed) were achieved. However, the reputation from users is poor, with comments like "it's hard to use" and "the UI is complex."

[Basis for Decision-Making]
"What is True Success? (Defining User Value)"
Rather than being satisfied with merely achieving management metrics, the PM asks the essential question: "Did we provide value to the user?"
In this case, while acknowledging the achievement of goals, the PM redefines "true success" and makes the decision to incorporate user feedback as the highest priority item in the next improvement plan.

(7) Decisions regarding change and learning

[Case Study]
During development, a new AI technology was announced that would dramatically improve operational efficiency. Introducing this would make the current process obsolete, but the introduction itself carries risks and could potentially cause temporary delays.

[Basis for Decision-Making]
"Adaptation and Growth for the Future"
Instead of choosing the "peace of mind" of maintaining the status quo, the PM makes a decision based on the "long-term competitiveness of the project" to learn and transform by adopting new methods, even at the risk of delay.
This is a future-oriented decision that takes the growth of the entire organization into account.

2. What should a PM use as a "basis" for making decisions?

For a PM, a 'foundation' is not merely a manual or a checklist.
It is a universal set of values that guides a project in the right direction without being swayed by temporary emotions or external pressure.

This foundation is composed of three intricately intertwined layers.

(1) Higher-level Purpose

True business objectives and customer value that transcend the contract.

PMs continue to focus on the true purpose of the project—'what value it brings to the customer' and 'what business problem it solves'—rather than just the project contract or WBS (Work Breakdown Structure).
When torn between two options, the question 'which one brings us closer to the higher-level purpose?' always serves as the simplest decision-making criterion.

(2) Data and Facts

Numerical evidence such as objective data, facts, and risk analysis.

Emotional arguments and speculation are the most dangerous poisons for a PM.
The primary foundation for any decision must always be objective data.
A stance of calmly analyzing figures—such as progress rates, cost trends, risk occurrence probabilities, and technical measurements—creates a foundation that is not swayed by emotion.

(3) Experience and Humanity

Insight cultivated through past experience, intuition, and human relationships.

There are many problems in the world of a PM that cannot be solved by data and logic alone.
These involve human nuances, such as team morale, stakeholder dissatisfaction, and the 'unspoken requirements' of the customer.
Intuition cultivated through years of experience—such as 'this is dangerous' or 'this person doesn't really mean that'—provides deep insights that objective data often overlooks.
This is the PM's own asset, born from daily dialogue with the team and customers, as well as experiences of past successes and failures.

4. Conclusion

The path of a PM is one of constantly refining and integrating these 'foundations'.

It can be called a philosophical endeavor that continues to ask, 'What is right as a human being and as a leader?' even amidst the evolution of technology and drastic changes in the business environment.

The decisions a PM makes may seem like lonely tasks performed in plain meeting rooms or late-night offices.
However, each one of those decisions supports the architecture known as a system, becomes the foundation for a company's future, and ultimately shapes our society.

[Related Articles]

☆The Project Manager's Way of Life

☆The Ecosystem of IT Sites

☆The Path of Project Management

・Practical Project Management [Overview Edition] - Management Toolbox

[Book Introductions]

・Built to Last: Successful Habits of Visionary Companies (Kindle Edition)
by Jim Collins; Jerry Porras (Author), Yoichi Yamaoka (Translator)
Nikkei BP (1995/9/29)
A long-selling US book that uncovers the source of "visionary companies" that remain outstanding and endure through time. Through thorough research and comparisons with rival companies, it debunks various management myths one after another. It argues that the "core ideology" that withstands the test of time and remains unchanged is what is most necessary for a visionary company.
(* Book descriptions, etc., are generally based on the descriptions on the linked site (Amazon). Please refer to the link for detailed content.)

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

・Team Journey: Overcoming Adversity and Building Change-Resilient Teams (Kindle Edition)
by Toshihiro Ichitani (Author)
"Thinking together, creating together"—learn how to face the problems of development team management encountered in workplaces that have introduced Scrum and Agile, and the key points of team building through stories!
[Features of this book]
・Learn concepts and practices together from real-world stories
・Handles various team management issues, such as single teams and multiple teams
・Based on Japanese workplaces, making it easy to put into practice
・Ideal not only for those just starting with Agile, but also for those who want to practice it more effectively
(* Book descriptions, etc., are generally based on the descriptions on the linked site (Amazon). Please refer to the link for detailed content.)

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

・How to Win Friends and Influence People (Revised Paperback Edition) (Kindle Edition)
by Dale Carnegie (Author), Hiroshi Yamaguchi (Translator)
Sogensha (2023/9/6)
The only official Japanese version of "How to Win Friends and Influence People" has undergone a major revision for the first time in about 40 years, following the 1936 first edition and the 1981 revised edition.
It persuasively explains the "30 Principles of Human Relations" that people should acquire in life, incorporating true stories collected over many years and practical examples polished in the field of adult education. A moving book that promotes actions and self-transformation to move people's hearts, based on deep human insight and humanism. An immortal masterpiece and historical bestseller that became the origin of all self-help books.
(* Book descriptions, etc., are generally based on the descriptions on the linked site (Amazon). Please refer to the link for detailed content.)

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

・A Book to Thoroughly Master the Basics of Project Management in One Volume (Kindle Edition)
by Kazuya Maeda (Author)
Gijutsu-Hyohron Co., Ltd. (2022/06)
This book is an introductory guide that allows you to learn about project management from the basics. After explaining the fundamental knowledge of project management, it divides projects into five stages: "Initiating," "Planning," "Executing," "Monitoring and Controlling," and "Closing," and carefully explains what should be done and points to be aware of at each stage.
(* Book descriptions, etc., are generally based on the descriptions on the linked site (Amazon). Please refer to the link for detailed content.)

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

・Practical Course on "Project Management" You Want to Know When You Become in Charge (Kindle Edition)
by Daisuke Ito (Author)
Nihon Jitsugyo Publishing (2017/2/1)
This book explains concrete knowledge and tools for project management, focusing on three perspectives: "Goal Setting," "Planning," and "Execution." It uses abundant diagrams to explain along the progress of a project. It is no exaggeration to say that many jobs and activities are projects. A must-read book for businessmen and everyone who wants to make their projects successful!
(* Book descriptions, etc., are generally based on the descriptions on the linked site (Amazon). Please refer to the link for detailed content.)

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

・A Guide to the Project Management Body of Knowledge (PMBOK Guide) 7th Edition (Kindle Edition)
+ The Standard for Project Management: Translated and supervised by PMI Japan Chapter
Project Management Institute (PMI) (Author)
PMI Japan Chapter (2023/1/6)
(* Book descriptions, etc., are generally based on the descriptions on the linked site (Amazon). Please refer to the link for detailed content.)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

・Illustrated Immediate Success: A Textbook to Thoroughly Understand the Knowledge and Methods of PMBOK 7th Edition in One Volume (Kindle Edition)
by Kazuya Maeda (Author)
Gijutsu-Hyohron Co., Ltd. (2024/9/20)
This is an explanatory book for the PMBOK Guide 7th Edition, known as the global standard for project management. In addition to the fundamental knowledge of project management such as "Project Basics," "Value Delivery System," and "12 Principles," it explains in detail the key points of the "8 Performance Domains," which can be said to be the main theme of PMBOK 7th Edition. It is a book recommended not only for studying project management but also as a first step for PMP exam preparation.
(* Book descriptions, etc., are generally based on the descriptions on the linked site (Amazon). Please refer to the link for detailed content.)

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

・Illustrated Introduction: Easy-to-Understand Basics of the Latest PMBOK 6th Edition (Kindle Edition)
by Yasuji Suzuki (Author)
Shuwa System (2018/3/23)
The PMBOK Guide is translated and published in 11 languages worldwide, including Japanese, by the Project Management Institute in the United States. Even when translated, it is difficult to understand due to many technical terms and katakana terms. This book is explained by the author, who is also the leader of the translation and supervision team for the "PMBOK Guide 6th Edition," breaking down the original meanings as much as possible. It uses plenty of diagrams to make it easy to visualize, making it easy to understand for everyone from beginners to veterans.
(* Book descriptions, etc., are generally based on the descriptions on the linked site (Amazon). Please refer to the link for detailed content.)

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-