A focused course, tailored for you
IT Services Data IC's Capability-Authorship Playbook
How a data individual contributor at an IT services firm anchors a capability when delivery restructures around AI augmentation.
When IT services firms restructure delivery around AI augmentation, data ICs without published capability-authorship narratives read as labour-category cost.
$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
IT services firms running AI-augmentation restructure reach data IC functions in the same operating-model cycle. Lead engineers above are protected by capability-area ownership; junior ICs below are protected by their direct delivery. The IC layer is the band the deck reviews most carefully.
The data ICs who survive own a documented capability narrative with measurable delivery outcomes, an architectural-decision record the capture team cites, and a quarterly capability-state artefact the practice principal forwards.
The course covers the three artefacts and the 90-day path to capability-authorship framing. Plus a hand-built implementation playbook against your real data IC scope.
The 12 modules
Module 1. Reading AI-augmentation restructure for data IC implications
AI-augmentation restructures at IT services firms reorganise data IC functions in three predictable phases: enterprise platform review, vertical practice review, and IC-portfolio review. The diagnostic decodes which signals (delivery-margin compression, AI-augmentation revenue targets, billable-utilisation drift, capability-area billings growth) indicate that the data IC layer is in the redraw set. Which ICs survive on task coverage and which survive on capability-authorship.
Module 2. Generic data IC vs capability-authorship owner
Two structurally different framings of the same data IC seat read very differently to the restructure review. Generic IC shows up as billable headcount on a labour-category line. Capability-authorship reads as the technical leadership the practice structurally depends on across recompete cycles: documented capability narrative, ADR the capture team cites, and quarterly state artefact the practice principal forwards. The three artefacts that mark the shift.
Module 3. Your documented capability narrative
Pick one data capability you currently anchor (data warehouse migration, real-time pipeline implementation, data-mesh adoption, ML-feature platform, governance-and-quality framework). Write the narrative as a Senior-IC-grade two-page document under your byline anchored to measurable delivery outcomes: throughput, latency, data-quality SLO, cost-per-record, and downstream business-KPI contributions. Three structural templates.
Module 4. Architectural-decision record for capture
An architectural-decision record (ADR) the capture team cites is the most defensible capability-authorship artefact in IT services data IC work. The ADR covers context (client constraint, regulatory overlay, cloud target), considered options, decision (warehouse pattern, pipeline pattern, governance pattern), consequences, and rollback path. The packaging that makes ADRs cited by capture in recompete proposals and the way to surface them as your authorship.
Module 5. Quarterly capability-state artefact for the practice principal
The quarterly artefact is a two-page state document covering capability-area momentum, client-account adoption, AI-augmented delivery outcomes, data-quality SLO performance, capture-team coordination, and emerging risks. Cadence is end-of-quarter delivery to practice principal with copies to capture, BD, and pricing leads. Three worked examples from real IT services data IC capability portfolios at different AI-augmentation stages.
Module 6. Working with capture, BD, and account leadership
Data IC work travels into capture (recompete-pursuit teams), BD (account expansion via modifications), and account leadership (named-account executives). The collaboration pattern that strengthens defensibility positioning: capability artefacts shared with capture, joint pursuit-team participation, account-leadership-relationship maintenance. Examples of capture narratives that elevated a data IC to Senior or Lead.
Module 7. Data-governance overlays: GDPR, CCPA, HIPAA, regulated industries
Data IC work intersects with GDPR, CCPA, HIPAA, financial-services data regulation (SOC 2, PCI DSS), and emerging frameworks (EU AI Act on training data, state privacy laws). The compliance overlays that strengthen the capability narrative as regulator-aware data IC work. How to position governance rigor as IC-grade IP the practice principal cites in regulated-industry recompetes.
Module 8. Cross-engagement leverage
Reusable data IC practices that scale across engagements: data-modelling templates, pipeline-pattern libraries, governance-framework patterns, observability instrumentation models, deployment-pipeline templates for regulated environments. The leverage pattern that signals capability-authorship IC work rather than single-engagement coverage. How to convert delivered work into published practice the practice principal cites in restructure defence.
Module 9. AI augmentation as accelerator
Use AI augmentation to strengthen capability rather than absorb it. The narrative documents how AI augmentation (delivery acceleration, automated data-quality monitoring, AI-assisted modelling, AI-driven anomaly detection) increased margin, accelerated delivery, and protected client outcomes. Three patterns and how to document each as capability-strengthening leadership the practice principal cites.
Module 10. Scope statement: IC vs Senior IC / Tech Lead
Two overlapping seats with different scopes. IC scope covers task delivery, ADR contribution, IP authorship at workload level. Senior IC scope adds multi-capability technical leadership and adjacent-engagement partnership. Tech Lead scope adds cross-capability technical strategy, ADR ownership, and recompete-pursuit participation. The scope statement that puts you in the Tech Lead track defensibly.
Module 11. Promotion mechanics inside IT services data IC
Internal path from IC to Senior IC to Tech Lead. The promotion artefact (capability narrative, ADR-adoption record, recompete-win contribution, governance-overlay leadership) and the cycle calendar (year-end performance review, capture-tied promotion review, practice-cabinet 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 capability-authorship framing
Day-by-day plan with daily artefacts. Days 1-7: capability narrative scaffold drafted with technical-metric inventory. Days 8-21: ADR v1 drafted with capture-team adoption confirmed. Days 22-45: quarterly artefact v1 delivered to practice principal. Days 46-60: multi-capability technical-leadership conversation. Days 61-90: Tech Lead conversation scheduled with practice-cabinet 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 capture cadence, governance overlays, leverage, and AI accelerator.
Modules 10 to 12 cover scope, promotion, and 90-day execution.
FAQ
Will capture actually cite my ADR in proposals?
Module 4 is built around the format capture cites.
What if my engagement spans multiple data capabilities?
Module 3 covers that case.
Why pay for this instead of reading free data-engineering content?
Free content covers technique.
Is Tech Lead actually open?
Module 11 covers that diagnostic.
What is in the implementation playbook for me specifically?
A draft capability narrative; a draft ADR; a 90-day plan with conversations against your practice principal.
