While reviewing a deliverable on a large IT project, a stakeholder raises a concern about the final product. What should the project manager do first?

The project manager should first discuss the concern with the team and review the project requirements documentation. This allows the team to understand the stakeholder's perspective and compare it against the agreed-upon requirements. This step helps determine if the concern represents a deviation from requirements, a misunderstanding, or a potential change request. Discussing with the team and reviewing documentation before escalating or involving other stakeholders ensures a fact-based understanding of the issue. Simply recording it in an issue log without initial investigation is premature. Involving the sponsor or product owner immediately without understanding the root cause or impact can be inefficient and unnecessary.