A project team is running into challenges because members are unclear about other members' roles.

The PM should create a project organizational chart to clarify who is who, reporting lines, and role visibility across the team. When team members are unclear about each other’s roles, the fastest way to reduce confusion is to make the project structure explicit: who leads which workstream, who approves decisions, who supports, and how to escalate. This aligns with Project+ people/resource management expectations: establish clear responsibilities and team structure to reduce duplication, gaps, and conflict caused by ambiguity.

A project plan is broader (scope/schedule/budget/governance), but it won’t necessarily provide a simple, visual map of roles. A road map is high-level sequencing of outcomes over time; it’s not meant to define roles. A milestone chart highlights key dates and deliverables, not responsibilities.

In practice, the PM often pairs the project org chart with a RAM/RACI for detailed accountability, but since the question asks which chart to create to fix role confusion, the best answer is the project organizational chart.