A focused course, tailored for you
Enterprise Consulting IC's Capability-Authorship Playbook
How an individual contributor at an enterprise consulting firm anchors a capability when delivery restructures around AI delivery.
When enterprise consulting arms restructure around AI delivery, 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
Enterprise consulting arms restructuring around AI delivery reorganise IC functions in the same operating-model cycle. Senior ICs above are protected by capability-area ownership; junior ICs below are protected by their direct contribution. The IC layer is the band the deck reviews most carefully.
The ICs who survive own a documented capability narrative with measurable client-engagement 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 IC scope.
The 12 modules
Module 1. Reading AI-delivery restructure for IC implications
AI-delivery restructures at enterprise consulting arms reorganise IC functions in three phases: enterprise platform review, vertical practice review, and IC-portfolio review. The diagnostic decodes which signals (delivery-margin compression, AI-platform-revenue contribution targets, billable-utilisation drift, capability-area billings growth) indicate that the IC layer is in the redraw set. Which ICs survive on task coverage and which survive on capability-authorship.
Module 2. Generic IC vs capability-authorship owner
Two structurally different framings of the same enterprise consulting 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: 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 capability you currently anchor (cloud-modernisation pattern, AI-platform integration, data-platform implementation, ML-operations framework, application-modernisation playbook). Write the narrative as a Senior-IC-grade two-page document under your byline anchored to measurable client-engagement outcomes: throughput, latency, defect-escape rate, system-availability SLO, AI-augmented delivery contribution. 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 enterprise consulting. The ADR covers context (client constraint, regulatory overlay, AI-target architecture), considered options, decision (cloud pattern, AI-platform pattern, integration pattern), consequences, and rollback path. The packaging that makes ADRs cited by capture in recompete and large-deal proposals.
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, regulatory-overlay positioning, 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 enterprise consulting IC capability portfolios at different AI-delivery stages.
Module 6. Working with capture, BD, and partner channel
IC work overlaps capture (large-deal pursuit), BD (account expansion via modifications), and partner channel (technology partners, hyperscaler partnerships, ISV partners). The collaboration pattern that strengthens defensibility positioning: capability ADRs shared with capture, joint pursuit-team participation, partner-channel co-engineering. Examples of joint-team narratives that elevated an IC to Senior or Lead.
Module 7. Industry-specific overlays for enterprise consulting clients
Enterprise consulting work spans regulated industries: financial-services (SOX, PCI DSS, FFIEC), healthcare (HIPAA, FDA, payer regulation), public sector (FedRAMP, ATO), telecommunications (CPNI, telco-regulator data rules). The compliance overlays that strengthen the capability narrative as regulator-aware engineering. How to position regulatory rigor as IC-grade IP the practice principal cites in regulated-industry recompetes.
Module 8. Cross-engagement leverage and reusable consulting IP
Reusable consulting IP across engagements creates a moat: methodology variants (cloud-modernisation, AI-platform implementation, data-platform implementation), benchmark data, transformation roadmap templates, reference architectures. The IP-authorship pattern that gets cited in proposals and recompetes. How to convert one delivered engagement into a published methodology under your byline.
Module 9. AI delivery as accelerator
Use AI delivery to strengthen capability rather than absorb it. The narrative documents how AI-augmented delivery (automated code generation, AI-assisted testing, AI-driven operations, AI-augmented architecture review) increased margin, accelerated delivery, and protected client outcomes. Three patterns (cloud-modernisation accelerator, AI-platform accelerator, data-platform accelerator) and how to document each.
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-engineering 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 enterprise consulting
Internal path from IC to Senior IC to Tech Lead. The promotion artefact (capability narrative, ADR-adoption record, recompete-win contribution, AI-delivery outcomes) 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, industry overlays, IP, 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 capability spans cloud, AI, and data?
Module 3 covers that case.
Why pay for this instead of reading free 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.
