Active work items represented across boards
Show the same work differently depending on who needs to act on it.
The Kanban view is now route-native in `apps/web`, showing how one work inventory can be translated for executives, IT staff, stakeholders, and service owners without creating disconnected systems.
Audience-specific board models
Items visible as waiting in at least one audience view
Expected reduction in status-chasing questions
Audience Boards
The boards should differ in language, not in underlying truth.
Executive Board
Executives should see decisions, risk, and outcomes rather than queue noise.
Approve dashboard automation sequence
Public data resilience plan
Program owner signoff
Service-status reporting refresh
IT Team Board
Operators need visible handoffs, blockers, and validation points.
REQ-2054 endpoint onboarding
INC-2041 remote access
REQ-2048 access change
Public data refresh fix
Stakeholder Board
Stakeholders need a plain-language view of progress and what is waiting on them.
New reporting enhancement
Website content update
Temporary staff access
Teams ownership cleanup
Service Owner Board
Owners need visibility into approvals, due dates, and dependency risk across their service.
Service definition gap
Runbook expansion
Vendor response lag
Notification rule refresh