Engagement Leadership · Commercial wing
Resource Onboarding & KT Tracker
SIMULATEDVerified Jul 2, 2026A resource is a cost from day one and an asset from day forty. Access requests — not training — are the longest pole; compress them and the carrying cost falls. Then guard the other end: a departing senior's knowledge.
Same instrument · three industries — pick a use-case to reconfigure the run
Access + ramp
Access > 14 days
Cost before productive
Pre-provision access
30 / 60 / 90 ramp · access = the longest pole
ML Engineer
Offshore
access 18d + ramp 35d → productive day 46
Data Engineer
Onshore
access 8d + ramp 35d → productive day 36
Delivery PM
Onshore
access 4d + ramp 35d → productive day 35
QA / Eval
Offshore
access 21d + ramp 35d → productive day 49
MLOps
Onshore
access 12d + ramp 35d → productive day 40
Domain SME
Onshore
access 6d + ramp 35d → productive day 35
Access is the pole nobody manages
Steering-committee takeaway: A resource is a cost from day one and an asset from day forty. Onboarding compression is the cheapest margin lever nobody manages.
Resume echo — resource-lead reality of the 31-resource AMEX portfolio; onshore/offshore mobilization.
How this is built
Time-to-productive = ramp (35d) + access beyond a 7-day norm; blocked if access > 14 days. Carrying cost = time-to-productive × loaded day rate (onshore $1,100 · offshore $700). Pre-provisioning caps access at 5 days.
KT view scores each knowledge area by bus-factor; scheduling KT adds a backup (+1). Single point of failure = bus-factor < 2. Stack: Next.js (static) + shared design system; client-side.
Limitations: ramp and rates are illustrative; real onboarding varies by role and client security posture. It exposes the access bottleneck and the KT risk, not a full mobilization plan.