Achieving the Dream released their AI for All Task Force report last month, Creating the AI-Enabled Community College and if you work in community college leadership, or high school CTE, and haven’t read it yet, you should. It’s thorough, well-researched, and strategically sound. McKinsey numbers. WEF forecasts. ATD’s own ICAT framework. It’s built on solid ground.
I’ve spent the last several years designing IT education systems — the infrastructure that actually delivers training, assesses competency, and produces job-ready graduates. So I read this report with a specific lens: Does this help a college build something?
The honest answer: yes and no.
—
What the report nails
The urgency case is airtight. Microsoft’s Work Trend Index found 66% of leaders won’t hire someone without AI skills. 71% would take a less experienced candidate with AI skills over a more experienced one without them. The gap between what students are using and what institutions are ready for isn’t narrowing — it’s accelerating.
The report’s eight action areas — strategic leadership, ethical governance, assessment, staff capabilities, professional learning, curriculum redesign, workforce alignment, and student success — give college leaders a coherent framework. If you’re a president wondering where to start, this gives you a map.
And the report includes this line in Action Area 7, which I want to quote directly because it matters:
> “Create simulated workplace scenarios using generative AI that develop practical, job-relevant skills through authentic problem-solving.”
That sentence is more important than the report probably realizes. It points at the exact mechanism that makes competency-based IT education work.
—
What the report doesn’t address
Here’s the problem: the report tells you what to do across all eight action areas, but it assumes the infrastructure to do it already exists or will materialize on its own. It won’t.
Simulated workplace scenarios sound great in a strategic plan. Building them — hosting them, assessing them, connecting them to an LMS, linking them to certification pathways, tracking student performance across them, and producing portfolio evidence that employers trust — is a completely different problem. That’s a systems architecture problem, not a policy problem.
The same applies to adaptive learning platforms, AI assistants, predictive analytics, and early alert systems. These are all tools that need to be wired together into a coherent data fabric. Running Canvas, a GNS3 lab, an AI chatbot, and a separate analytics dashboard doesn’t create an ecosystem. It creates seven point solutions that don’t share data and don’t produce coherent outcomes.
The report’s strongest contribution is validating the direction. But direction without infrastructure is just intention.
—
Where the architecture lives
The gap between the ATD report’s vision and what a college can actually implement is not small. But it’s buildable. The technology stack is mature enough now — LTI 1.3 for LMS integration, open-source hypervisors for lab environments, AI APIs for assessment and feedback, badge and portfolio standards for competency tracking. The pieces exist. What’s missing is the integration architecture that connects them into a training pipeline that actually produces graduates with stackable certifications and employers waiting to hire them.
That architecture is what I build. Not another tool — the layer that makes existing tools work together as a system.
If you’re a community college leader who read the ATD report and thought “great, now what?” — you’re not alone. But the answer isn’t to buy another point solution. The answer is to design the system first, then choose the tools that fit it.
The report tells you why. The infrastructure tells you how. One without the other is incomplete.