Service Lead Cross-Client Linear Views
Purpose: How each Service Lead sees all execution issues across client teams where their line is in play. Uses saved views aligned to Operating roster; avoids label taxonomies unless necessary.
Also read: linear-day-1-guide.md (SL Day 1 checklist and how this fits with labels and global views).
Prerequisites: Operating allocation data showing which clients use which service lines.
Last updated: 2026-03-30
Principle: Views + Operating, Not Labels
Default approach: Saved views that filter by Team ∈ {roster of client teams} for your line.
Why: Operating already knows “who is staffed where.” Labels (line:data) duplicate that taxonomy and drift when staffing changes.
Fallback: Labels only if Linear plan limitations prevent multi-team saved views.
Step-by-Step: Build Your Cross-Client View
1. Export Roster from Operating
Get the list of active client teams where your service line has allocation:
| Service Line | Client Teams (from Operating) | Last Updated |
|---|---|---|
| Data | Eden, LMNT, CTA, ABC Home | 2026-03-30 |
| AI | Eden, Magic Spoon, Default | 2026-03-30 |
| Strategy & Analytics | UrbanStems, GlobalVetLink | 2026-03-30 |
DRI: Each SL maintains their roster accuracy during monthly Operating hygiene (see success-metrics).
2. Create Saved View in Linear
Option A: Workspace-level view (recommended)
If your Linear workspace supports multi-team filters:
- Go to Issues → New View
- Filter:
Team→ Select all client teams from your roster - Filter:
State→ Active (Backlog, Todo, In Progress, Blocked) - Optional: Add
Assigneefilters orDue Dateranges - Name:
{Line} Cross-Client View — Q2 2026 - Share: Make visible to your line’s stakeholders (HoD, CSOs)
Option B: User-level view
If workspace permissions are restricted:
- Same steps as above, but save to My Views
- Export link or screenshot for monthly service line review
3. Verify Coverage
Cross-check against Operating for completeness:
- Are all clients with Data allocation visible?
- Are there orphan issues on client teams not in your view?
- Red flag: Client exists in Operating but not in Linear view = roster drift
4. Refresh Cadence
| Trigger | Action | DRI |
|---|---|---|
| Monthly Operating hygiene | Rebuild view if client roster changed | SL |
| New SOW / client onboarding | Add new client team to view | SL |
| Offboarding / reallocation | Remove client team; archive or hand off | SL |
The “My + Subscribed” Safety Net
If multi-team views are not available in your Linear plan:
- Assign yourself or subscribe to issues you need to track
- Use built-in view: Assigned to me + Created by me + Subscribed
- Known gap: Passive visibility (you won’t see issues until assigned/subscribed)
- Mitigation: CSO tags SL on critical cross-service items; proactive subscription habit
Fallback: Labels (Requires HoD Approval)
If views prove insufficient, use this controlled label taxonomy:
| Label | Applied When | Owner | Audit |
|---|---|---|---|
line:ai | Issue involves AI service line | CSO or SL at creation | Monthly in service line review |
line:data | Issue involves Data service line | CSO or SL at creation | Monthly in service line review |
line:strategy | Issue involves Strategy & Analytics | CSO or SL at creation | Monthly in service line review |
Rules:
- Apply at issue creation (not retroactive batch labeling)
- One primary line per issue (if cross-service, use CSO escalation, not dual labels)
- Monthly audit: HoD checks label consistency vs Operating roster
Transition: If labels are approved, create saved view filtering by label:line:{X} AND Team ∈ roster for redundancy.
Integration with Service Line Review
Monthly agenda item:
- Roster accuracy — Operating vs Linear view match?
- Coverage gaps — Any client teams missing?
- Label drift (if using) — Consistency check
Input to quarterly narrative:
- Cross-client pattern detection (e.g., “3 Data clients hit same Snowflake issue”)
- Capacity balancing insights
Quick Reference
| Need | Solution | Owner |
|---|---|---|
| See all my line’s work across clients | Saved view: Team ∈ roster | SL |
| Roster changes | Operating hygiene → rebuild view | SL |
| Spot-check one issue | Linear search + assignee/subscription | SL |
| Monthly audit | Service line review checklist | SL + HoD |
| Emergency fallback | Labels (with HoD approval) | HoD |
Related
- success-metrics — monthly hygiene includes roster accuracy
- client-vs-service-line-systems-of-record — Operating as source of truth
- linear-hygiene-standards — issue quality bar
- expectations-by-cadence — monthly Operating review