Linear Full Cleanup — Discovery Report
Date: 2026-03-17
Purpose: One-time map of the whole Linear workspace for cleanup aligned to service line → subservice → offering model.
Scope: Cleanup is workspace-wide — all client teams and all internal teams, not just LMNT. Apply the same taxonomy, structure, and ticket→project discipline to every team; prioritize by order below.
1. Teams (client vs internal)
| Team | Type | Notes |
|---|---|---|
| LMNT | Client | Active delivery (Option B) |
| CTA | Client | |
| Eden | Client | |
| EdenOS | Client | |
| MinuteMD-Amble | Client | Amble |
| Magicspoon | Client | MagicSpoon |
| Hedra | Client | |
| Interlude Studio | Client | |
| ABC Home and Commercial | Client | |
| ABC Team | Client | |
| GlobalVetLink | Client | |
| Urban Stems | Client | |
| Lilo Social | Client | |
| Insomnia Cookies | Client | |
| Ellie Mental Health | Client | |
| Honey Stinger | Client | |
| Rimo | Client | |
| Hyp+Access | Client | |
| iCustomer | Client | |
| SME Playbooks/Testimonials | Client | |
| Platform | Internal | Product/engineering |
| Delivery | Internal | Delivery team |
| GTM | Internal | Go-to-market |
| Sales | Internal | |
| Marketing | Internal | |
| Operations | Internal | |
| Finance | Internal | |
| Legal | Internal | |
| Recruitment | Internal | |
| Onboarding & Offboarding | Internal | |
| Project Management | Internal | |
| Content | Internal | |
| Management | Internal | |
| Exec | Internal | |
| Sick/ OOO Request | Internal | |
| Default | Internal | Catch-all |
| TEST | Internal | Test team |
| TEST2 | Internal | Test team |
| ARCHIVE | Internal | Archived work |
Sub-team hierarchy (set in Linear: Settings → Teams → Team hierarchy): Operations → Sick/ OOO Request, Onboarding & Offboarding. Sales → GTM, Content. See linear-teams-client-internal.md.
Deleted teams (2026-03): SME Playbooks/Testimonials (SME), TEST (TES), TEST2 (TES2). Removed from vault list and from linear_team_type_seed (SME).
2. Initiatives (sample; 22 total)
| Initiative | Status | Maps to |
|---|---|---|
| Amble | Phase 0 | Active | Client workstream |
| Amble | Phase 1 | Active | Client workstream |
| LMNT | Supply Chain | Completed | Retired (use Data Modeling, etc.) |
| LMNT | Documentation | Active | Client workstream |
| LMNT | Adoption | Active | Client workstream |
| LMNT | VP Level Strategy | Active | Client workstream |
| LMNT | Reporting and Analytics | Active | Client workstream |
| LMNT | Data Modeling | Active | Client workstream |
| LMNT | Ingestion | Active | Client workstream |
| Q2 2026 Platform Planning | Active | Internal |
| Delivery & Finance Analytics | Active | Internal |
| Platform Initialization | Active | Internal |
| OpenWork Initialization | Active | Internal |
| Strategy Service | Active | Service line |
| A.I Service | Active | Service line |
| Data Service | Active | Service line |
| Test-initiative | Active | Test |
| MinuteMD - Deal 1 | Active | Client |
| Edge-to-Activation - Service | Active | Offering |
| Recruiting | Active | Internal |
| Website | Active | Internal |
| Campaigns | Active | Internal |
| Employee LinkedIn Posts | Active | Internal |
| Sales Assets | Active | Internal |
| Partnerships | Active | Internal |
| Promotions | Active | Internal |
| Productivity | Active | Internal |
Observation: Initiative naming is mixed: “Client | Workstream” (LMNT), “Data Service” / “A.I Service” / “Strategy Service” (service line), and ad-hoc (Website, Campaigns, etc.). Align to taxonomy: client = “Client | Workstream”; internal = service line or workstream name.
3. Projects (first 50; more exist)
- With initiative: Most LMNT projects linked to LMNT | Data Modeling, LMNT | Ingestion, LMNT | Reporting and Analytics, LMNT | Documentation, LMNT | VP Level Strategy. Amble Phase 0 linked to Amble | Phase 0. Many Data Service projects linked to “Data Service” initiative.
- Without initiative: e.g. “GOV Evidence Intelligence GTM (Human-in-Control)” (GTM), “GTM Campaign Briefs” (Sales), “Documentation:” (TEST2).
- Orphan / test: TEST and TEST2 have many projects under “Data Service” (duplicates of LMNT-style work). Consider archiving or merging TEST/TEST2 projects into LMNT where appropriate.
- Project naming: Mix of “LMNT | …”, “[Name] Data Mart”, “Ingest and Backfill”, offering names. Align to
[Client] {Offering}or{Line} — {Offering}per knowledge/sales/services/README.md.
4. Unassigned issues (no project)
| Team | Sample (first 100 issues) | Unassigned (no project) |
|---|---|---|
| LMNT | 100 | 13 |
| Platform | 100 | 31 |
| Delivery | 0 | 0 |
Note: Full counts require pagination per team. Run linear-tickets-to-projects (audit only) per team for complete list and proposed project assignment.
5. Issue labels (current)
- AI / agent: ai-Codex, ai-Cursor
- Phase (website): phase-1-foundation, phase-2-core-pages, phase-3-content-interactions, phase-4-seo, phase-5-cutover
- Ops: ops-Human Step, ops-No Updates, ops-Needs Revisions, ops-Deferred from Sprint, ops-Needs Documentation, ops-Internal, ops-SLA Risk, ops-External Dependency, ops-Mid-Sprint Add-On, ops-Needs Grooming
- Capability (parent: AI Workstream, Data Workstream, etc.): cap-Security, cap-Project Documentation, cap-Client Communication, cap-Dashboard Development, cap-Data Modeling, cap-Data Infrastructure, … (many)
- Other: Updated Estimate, UrbanStems/Asana/Jira related
Gap vs taxonomy: Standard service-line labels (data, ai, strategy-analytics), phase labels (phase-0, phase-1, phase-2), and offering labels (omni, edge-to-activation, client-dependency, internal) should be added or standardized for cleanup and filtering.
6. Recommended cleanup order (workspace-wide)
- Internal teams first: Platform, Delivery, GTM, Sales, Marketing, Operations — align initiatives/projects to service line structure; assign unassigned issues.
- Client teams (priority): LMNT (good initiative structure; fix orphans/unassigned first), then MinuteMD-Amble, CTA, Eden, EdenOS — same treatment: initiatives, projects, unassigned issues, SOW where available.
- Test/archive: TEST, TEST2, ARCHIVE — decide merge/archive; move client work to the right client team where appropriate.
- All remaining client teams — Magicspoon, Hedra, Interlude Studio, ABC, GlobalVetLink, Urban Stems, Lilo Social, Insomnia Cookies, Ellie Mental Health, Honey Stinger, Rimo, Hyp+Access, iCustomer, SME Playbooks — one-by-one with SOW/roadmap alignment where artifacts exist.
7. Cleanup applied
- 2026-03-17 — Phase 2: Taxonomy doc created: linear-cleanup-taxonomy.md. Team list: linear-teams-client-internal.md.
- 2026-03-17 — Phase 3 — Structure: Linked 2 orphan projects to initiative “Campaigns”: GOV Evidence Intelligence GTM (Human-in-Control), GTM Campaign Briefs.
- 2026-03-17 — Phase 4 — Tickets: LMNT 13 → “Reporting”; Platform 31 → “Platform Ideas” (29), “Brainforge Website Migration” (1), “Recruiting” (1).
- 2026-03-18 — Internal teams (item 2): Delivery 0 issues. GTM 6 unassigned issues assigned to project Outbound SDR/BDR (GTM-1, GTM-2, GTM-3, GTM-4, GTM-6, GTM-7). Sales, Marketing, Operations: no unassigned found.
- 2026-03-18 — TEST/TEST2/ARCHIVE (item 4): Audit and merge/archive plan: linear-test-archive-audit-2026-03-18.md. Decide: move real LMNT work to LMNT, then merge TEST2 → TEST or archive test teams.
- Not done: SOW alignment per client, bulk labels, duplicate report/merge, full board audit, linear-status-sync. Run per team using linear-sow-alignment and linear-tickets-to-projects.
8. References
- Service model: README.md
- Linear cleanup taxonomy: linear-cleanup-taxonomy.md (Phase 2 deliverable)
- Skills: linear-roadmap-to-structure, linear-tickets-to-projects, linear-sow-alignment, linear-status-sync