Design database views

Create a database view that shows active projects with owner, status, next milestone date, and outstanding tasks for the Friday portfolio review. Sort by next milestone ascending, filter to active status and any project with overdue tasks, and include a count of open tasks per project. Check that the view exports cleanly to CSV for the PMO.

Before I present the project view to the PMO, make it easy for them to pick what to act on. Bring overdue items to the top, highlight projects with no owner, surface the next three milestones and the single biggest blocker, and add a quick legend explaining status values so reviewers don't have to hunt definitions.

I built a project view for the weekly review and the PMO says it's either too cluttered or missing what they care about. The PMO lead, Angela, wants a sharper filter but won't say which fields matter most. I can ask her to pick fields, or I can propose a compact view. Which choice will get faster buy-in and what exact compact field list should I propose to Angela?

Every time there's a meeting someone makes a bespoke view and the canonical project dashboard never stabilizes, so people stop trusting it. I want a habit that forces a single source of truth and prevents ad-hoc forks. What naming convention, ownership rule, and quick governance step will stop proliferation and get the PMO to use one view consistently?