A focused course, tailored for you
Collaboration Platform IC's Workload-Authority Playbook
How an individual contributor at a collaboration platform vendor anchors a workload when the platform tightens around customer-tier expansion.
When collaboration platforms tighten around customer-tier expansion, ICs without documented workload authority read as fungible.
$199 one-time
Tailored to your situation. Access within 24 hours. 30-day money-back.
Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.
Why this course
Collaboration platform vendors running customer-tier expansion cycles reorganise IC functions in the same operating-model cycle. Senior ICs above are protected by their portfolio ownership; junior ICs below are protected by their direct delivery. The IC layer is the band the deck reviews most carefully.
The ICs who survive own a documented workload narrative under your byline, an architectural-decision record adjacent teams quote, and a quarterly workload-state artefact the engineering director adopts.
The course covers the three artefacts and the 90-day path to workload-authority framing. Plus a hand-built implementation playbook against your real workload.
The 12 modules
Module 1. Reading customer-tier expansion for IC implications
Customer-tier expansion at collaboration platforms reorganises IC functions in three predictable phases: enterprise platform review, product-line review, and IC-portfolio review. The diagnostic decodes which signals (customer-tier expansion targets, revenue-per-customer benchmarks, AI-augmented collaboration benchmarks, infrastructure-cost compression) indicate that the IC layer is in the redraw set.
Module 2. Generic IC vs workload-authority IC
Two structurally different framings of the same IC seat read very differently to the expansion review. Generic IC shows up as bench role with a feature-velocity number. Workload-authority IC shows up as the leadership the workload structurally depends on: documented narrative under your byline, ADR adjacent teams cite, and quarterly state artefact the engineering director adopts. The three artefacts that mark the shift.
Module 3. Your documented workload narrative
Pick one workload you currently anchor (collaboration core platform, integration platform, marketplace, enterprise admin, AI-collaboration surface). Write the narrative as a Senior-IC-grade two-page document under your byline anchored to measurable workload metrics: customer-tier adoption, time-to-value, reliability metrics, cost-per-action, and downstream customer-tier KPI contributions. Three structural templates.
Module 4. Architectural-decision record
An architectural-decision record (ADR) adjacent teams quote is the most defensible workload-authority artefact at collaboration platform scale. The ADR covers context (customer constraint, regulatory overlay, scale target), considered options, decision (architectural pattern, technology selection, migration path), consequences, and rollback path. The packaging that makes ADRs cited by adjacent teams and the way to surface them as your authorship.
Module 5. Quarterly workload-state artefact for the engineering director
The quarterly artefact is a two-page state document covering workload momentum, adoption trends, reliability outcomes, cost trajectory, downstream customer-tier KPI contributions, regulatory positioning, and emerging risks. Cadence is end-of-quarter delivery to engineering director with copies to product, SRE, and adjacent team leads. Three worked examples from real collaboration platform IC workload portfolios.
Module 6. Working with product, SRE, and adjacent IC teams
Workload authority overlaps product (PM partnership, customer-tier KPI ownership), SRE (reliability operations, on-call response), and adjacent IC teams (data, observability, deployment, customer-success engineering). The collaboration pattern that strengthens defensibility: shared ADR adoption, joint reliability reviews, cross-team workload reviews credited by IC name. Examples that elevated an IC to Senior or Staff.
Module 7. Reliability, cost-per-action, and customer-tier storytelling
Cost-per-action, reliability outcomes, and customer-tier expansion are what finance and senior leadership read first in expansion reviews. Format the cost-and-reliability story as a four-quarter trend with cost-per-action breakdown, reliability SLO performance, customer-tier KPI attribution, and forward optimisation pipeline. Three storytelling templates and the talking points each gives the engineering director.
Module 8. Cross-workload leverage
Reusable IC practices that scale across workloads: ADR templates, integration-pattern libraries, reliability-runbook frameworks, observability instrumentation models, deployment-pipeline patterns. The leverage pattern that signals workload-authority IC rather than vertical workload coverage. How to convert delivered work into published practice the engineering director cites in expansion defence.
Module 9. External presence: OSS, conferences, technical blog
External presence strengthens workload-authority positioning by establishing recognised authorship outside the firm. The publication and contribution cadence (OSS contributions to collaboration-related projects, conference talks at collaboration-and-platform conferences, technical blog posts on the company engineering blog) that protects IC seats through customer-tier expansion.
Module 10. Scope statement: IC vs Senior IC / Staff Engineer
Two overlapping seats with different scopes. IC scope covers workload delivery, ADR contribution, IP authorship at workload level. Senior IC scope adds multi-workload technical leadership and adjacent-team partnership. Staff Engineer scope adds cross-org technical strategy, architectural-decision ownership, and engineering-cabinet participation. The scope statement that puts you in the Staff track defensibly.
Module 11. Promotion mechanics inside collaboration platform vendors
Internal path from IC to Senior to Staff. The promotion artefact (workload narrative, ADR-adoption record, cross-team partnership outcomes, external presence) and the cycle calendar (mid-year review, year-end performance review, promo committee, announcement). What gets an IC shortlisted, what blocks an IC who is otherwise qualified, and how to time your move.
Module 12. Your 90-day move to workload-authority framing
Day-by-day plan with daily artefacts. Days 1-7: workload narrative scaffold drafted with metric inventory. Days 8-21: ADR v1 drafted with adjacent-team adoption confirmed. Days 22-45: quarterly artefact v1 delivered to engineering director. Days 46-60: multi-workload technical-leadership conversation. Days 61-90: Senior or Staff conversation scheduled with promo-committee sponsor identified in module 11.
How this addresses your situation
Specific modules that map to what you said you are dealing with.
Modules 1 and 2 cover the diagnostic.
Modules 3 to 5 produce the three artefacts.
Modules 6 to 9 cover cross-team cadence, customer-tier storytelling, leverage, and external presence.
Modules 10 to 12 cover scope, promotion, and 90-day execution.
FAQ
Will the engineering director actually quote my workload narrative?
Module 3 is built around the format directors quote.
What if my workload spans multiple product lines?
Module 3 covers that case.
Why pay for this instead of reading free engineering content?
Free content covers technique.
Is Senior IC actually open?
Module 11 covers that diagnostic.
What is in the implementation playbook for me specifically?
A draft workload narrative; a draft ADR; a 90-day plan with conversations against your engineering director.
