Admin Dashboards and ETS
•Current ETS numbers questioned; admins already build dashboards via Apps Script/vibe coding
•Need to extract/visualize, act/bulk update, add context, improve Find Time, measure
Cleanup and Automation
•Cleanup should be continuous (daily/ongoing), not quarterly manual cleanup; overlaps series mgmt + bulk actions
•Fits the automation roadmap (meeting reaper/analyzer: stale/skip/resched/cancel + focus blocks)
Priority and Attribution
•Current ETS numbers conflicting with “P1” priority; needs recalibration or deprioritization
•Risk of over-investing in interim tools: help now vs “solution coming” line-in-sand
•Audit value spans engine + surface, making impact attribution hard (time saved vs Find Time/personalization gains)
Upcoming Tasks and Milestones
•Maya to brief leadership and reframe impact metrics (include downstream gains: bulk actions, learning signals)
•Team to align with partners (Chris/Alex) on why audit is P1 despite current metrics; confirm priority after numbers update
•Jordan to pause deeper build 1–2 days pending P1 confirmation; then start “overview/audit” page
•Plan recurring research office hour/focus group (fortnightly) to review launches + test new designs
•Near-term candidate for panel review: proactive drafts workflow automation sync (requested by Sam)