A project manager working on a large project in another country notices that only a few team members are handling all releases. What should the project manager do to prevent this in the future?

The correct answer is to review user roles and update the team charter. This directly addresses the problem of an uneven distribution of work by clarifying responsibilities and expectations within the team. The team charter is a key document that defines team norms, roles, and responsibilities, making it the appropriate place to formalize changes that promote balanced workload distribution. Speaking to the customer and adding the issue to the issue log is reactive and doesn't solve the underlying problem of role definition. Documenting the risk register in the project charter is incorrect; the risk register is a separate document, and while uneven workload could be a risk, simply documenting it there doesn't resolve the immediate issue of role clarity. Involving the product owner to rewrite user stories is irrelevant to the problem of team members handling all releases; user stories define product features, not team member responsibilities.