Eventually, I learned that the project board had rejected this proposed project before. I discovered that a stakeholder who had pushed to start the project several times -- despite the fact that the board discarded it -- approached my team member, who happened to be a junior member and new graduate.
As a new member to our team, I had to explain the project selection process of our organization. The board selects projects from a business-oriented approach. Under this direction, projects produce business benefits that will contribute to achieve organization's strategic objectives. The proposed project did not fit this mindset, but as a new project team member, how could he have known?
I explained further to this project team member that in this mindset, project professionals must wear a business and technical hat. Depending on the situation, project managers must ensure that their project teams deliver projects that will produce the benefits and results that the organization is looking for.
This is just one example of how project professionals will need to be able to coach "multi" teams, especially those made up of new and young project members. You can't assume that everyone on the team shares your same knowledge.
Eventually, the junior team member understood why only projects that will help the organization fulfill its intended purpose should be selected. A few days later, we met with the stakeholder to ask for specifics about the project with regard to the organizational benefits.
How do you coach junior project team members when they are less knowledgeable?