Useful operating visibility starts with the same objects teams use to do the work. Project health, goal progress, workload, and milestones should not require a separate reporting process.
A portfolio view should make it possible to move from an executive signal to the projects and dependencies behind it. The detail matters because risk rarely belongs to a single status field.
Good reporting reduces reconstruction. It should answer what changed, what is blocked, who owns the next step, and which decision or dependency is responsible.
Use one source of work truth.
Planning, execution, context, and reporting are easier to reason about when they point to the same underlying objects.