Project Impacts Promotion Levels: Use this setting to determine the visibility and reporting of project impacts across different contexts. The promotion levels control how prominently a project impact is surfaced in dashboards, reports, and workspaces:
To Program: Promote the project impact to program and portfolio-level dashboards. This visibility ensures that significant impacts, including risks, issues, changes, dependencies, etc., are tracked and managed appropriately to support decision-making and effective oversight and accessible for executive review. Stakeholders are provided with a comprehensive overview, supporting high-level decision-making across multiple projects.
To Parent Project: Promote the project impact to the top parent project. This ensures the parent project manager has oversight over the various impacts that relate to the larger, integrated project. The promoted impact will also appear in the parent project workspace, ensuring the parent project manager can effectively oversee potential challenges, risks, and dependencies that may affect the overall project delivery.
To Dashboard: Promote the project impact only within the specific project it belongs to. The impact will be visible in the project’s dashboard and project workspace for focused tracking and management by project-specific stakeholders. This level keeps the impact within the immediate project without escalating it to program or parent levels.
Not Promoted: The project impact will be visible only within the project workspace and will not appear in any dashboards or reports. This is useful for tracking impacts internally, where visibility is limited to the project team. Unlike promoted impacts, these impacts are not included in broader reports, but they are still visible in the project workspace to ensure the team is aware of all potential issues and can manage them effectively.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article