Action needed
5
items to resolve
~15 min to clear
Sofia Park · 9 direct reports + 2 open reqs · Source: Workday roster + PPM resource summary
| Name | Project allocations | Total |
|---|
Finance view = Surface 4 (Budget Management)
Surface 1 is the resource manager's view — people-led, single-team scope. Finance partners support multiple managers across orgs and need a different shape: filterable cross-manager spend, budget benchmarks, and over-budget alerting. That JTBD lives on Surface 4, not here.
01
Per-manager × project spend
Filterable view of every manager's team allocation rolled up by project, with comparisons to forecast and budget targets. The view Kristin Willman generates manually for Eric today, productized.
02
Budget benchmarks per project
Each project's actual + forecast spend compared to its target budget at the C-code level. Replaces "intrinsically know or just assume what you should be targeting" with explicit benchmarks (Eric Platow 2026-05-01 email).
03
Over-budget alerting
Real-time push when a project crosses its target — distinct from the Type B weekly digest pattern used for resource changes. Budget exceptions need faster signal than weekly batch.
Coming in Surface 4 — pending Eric Platow session
Why Finance doesn't live on Surface 1
Surface 1's JTBD is "is my team set up right?" — answerable for one manager's team at a time. Finance's JTBD is "are my orgs on budget, and where do I need to ask questions?" — answerable across many managers' teams aggregated. Different JTBD, different surface. Same human (Matt) can use both, just for different questions. JTBD-by-hat separation locked in spec.md (Q6, 2026-05-11).