Environment Provisioning Time measures how long it takes to create a new, fully functional development or staging environment from scratch. Long provisioning times block onboarding, delay testing, and discourage experimentation with isolated environments. Fast, automated provisioning is a hallmark of mature platform engineering and directly enables developer self-service.
Time to create a functional environment. Elite level: minutes; Entry level: >1 week.
AMPLIFIED: Cloning a huge monorepo can take hours. Running all services locally may be impractical. Mitigations: sparse checkout, cloud dev environments, targeted local setup. Spotify's Backstage reduced time-to-10th-PR from 60 to <20 days.
Manual provisioning doesn't scale. The transition from manual to self-service becomes mandatory at department scale. Config drift multiplies with environment count.
Fighting config for days creates terrible first impressions.
Manual provisioning requires tangential infrastructure knowledge.
Self-service turns days into minutes.
More deps, services, storage needed.
Good docs: days → hours.
Cloning a multi-GB repo can take hours. First-day experience for new hires is terrible without sparse checkout.