Vercel Projects Analytics Board

• Compressed multi-console governance into a single decision surface.
• Made allprojects mapping gaps visible and actionable in one table.

• Used a Collect -> Cross-check -> Filter -> Act workflow aligned with troubleshooting behavior.
• Separated capture, aggregation, and presentation layers for stable reruns.

• Public static snapshot: /projects/vercelboard/live.html.
• Includes KPI modules, cross-check table, and drift/web/speed filters.

• Owner / Product Engineer: defined governance goals, designed the data model, and shipped capture + synthesis + board UX.

• As project count grew, analytics and mapping states fragmented across multiple consoles and became expensive to audit.

• Control-plane data includes sensitive context, so public output must be sanitized.
• The board had to optimize for quick triage rather than become a full admin backend.

At scale, the question is no longer "do we have analytics?" but "which projects are enabled, missing data, or drifting from production mapping?"

• Audit Web Analytics and Speed Insights coverage.
• Cross-check public allprojects entries against Vercel project reality.
• Filter exceptions such as drift, web-off, and unmapped projects.

• KPI summary with total projects, analytics-enabled, data-available, and speed coverage.
• Cross-check table combining public URLs, Vercel projects, Web, Speed, and drift state.
• Search and filtering for rapid triage.

• Totals first, exceptions second.
• Governance actions are mapped directly into filter controls.
• The board keeps editorial readability instead of becoming a heavy admin console.

• Playwright capture pipeline for Vercel control-plane data.
• Static HTML renderer for KPI, mapping, and exception states.
• Capture, aggregation, and presentation layers stay decoupled for repeatability.

• The public site shows a safe static snapshot of the board.
• Sensitive control-plane details remain in local/private workflows.