Our Take
The space versus time distinction makes sense, but the golf analogy obscures that most organizations still lack basic AI deployment frameworks before they can even think about employee development space.
Why it matters
With only 20% of workers using AI daily and 17% believing it will help their jobs, the skills gap represents a coordination problem between AI tooling rollouts and workforce readiness.
Do this week
HR leaders: audit whether your AI training happens during protected development time or squeezed between existing tasks, then block dedicated weekly AI experimentation hours for Q2.
Survey reveals skills-readiness gap in AI adoption
ADP's survey of 39,000 global workers found only 26% strongly agree they have skills needed for career advancement over the next three years (per company research). Less than 20% of workers strongly agree their employer invests in skills development.
The research, titled "Today at Work 2026," shows only 20% of workers use AI nearly daily, while just 17% strongly agree AI will positively impact their job within a year (company-reported figures).
ADP's Chief Talent Officer Jay Caldwell argues the core issue isn't time allocation but "space" for development. He defines space as "mental, physical and cultural availability to truly dig into something for long-term impact, unshackled from competing priorities and pressure to deliver short-term ROI."
Low daily usage signals adoption barriers
The 20% daily AI usage rate suggests most organizations haven't moved past pilot phases into systematic deployment. When combined with the 17% who expect positive job impact, this indicates a disconnect between AI availability and practical integration into workflows.
The skills development gap compounds this problem. If workers lack structured time to experiment with AI tools, adoption rates will likely remain low regardless of tool availability or executive mandates.
Caldwell's "space versus time" framework addresses a common failure mode: cramming AI training into existing schedules rather than treating it as core skill development requiring dedicated focus and iteration cycles.
Create structured AI experimentation windows
The key insight is distinguishing between calendar time and development space. A 30-minute AI training module between meetings lacks the context-switching room needed for genuine skill building.
Organizations should treat AI skills development like any other core competency requiring sustained practice. This means blocking dedicated weekly hours for workers to test AI tools on actual work tasks, not theoretical exercises.
Manager involvement becomes critical for creating this space. Without clear expectations that AI experimentation is part of the job, not an add-on, workers will default to existing workflows under delivery pressure.
The survey data suggests most organizations are still in early AI adoption phases, making this an opportune moment to establish structured development practices before bad habits solidify around tool usage.