What an AI readiness assessment AWS search turns up
Your board asked for proof the company is AI-ready. You search "AI readiness assessment AWS," expecting a scorecard. What you find instead is a whitepaper: the Cloud Adoption Framework for AI (CAF-AI), published February 13, 2024, which AWS frames as a way to judge maturity and help direct near-term improvement, not a per-employee diagnostic.
That whitepaper doesn't name a single readiness score. Instead it organizes guidance across several organizational areas beyond people, built to help you judge maturity and prioritize near-term improvement rather than output one number. Alongside it sits the separate AWS Well-Architected Tool, which the earlier CAF People Perspective whitepaper describes as letting you review workloads against best practices by answering a set of questions.
Amazon's own CEO frames the scale of the opportunity broadly, in words that capture why organizations are paying this much attention to AI at all.
“Generative AI has captured people's imagination in a way few innovations have.”
— Andy Jassy, CEO, Amazon · Source: AWS Cloud Adoption Framework for Artificial Intelligence, Machine Learning, and Generative AI - AWS Whitepaper
Sources: AWS Cloud Adoption Framework for Artificial Intelligence, Machine Learning, and Generative AI - AWS Whitepaper, AWS Cloud Adoption Framework: People Perspective - AWS Whitepaper
The People Perspective asks about culture, not individuals
Inside CAF-AI, the People Perspective makes an explicit argument: adopting AI and creating value reliably isn't a purely technological challenge. AWS frames success as depending on the workforce embracing AI as a whole, which is a statement about organizational posture, not a measurement of any one team.
Its Workforce Transformation capability is defined as attracting, enabling and managing AI talent, from user to builder. That's a hiring and talent-management lens, built for an HR or transformation leader planning headcount, not a tool for finding out which of your current employees can already prompt well and which can't.
We'd be cautious about treating "attracting and managing AI talent" as evidence of readiness: it describes an HR ambition, not a measured capability in your current workforce.
Sources: People perspective: Culture and change towards AI-first
Who this documentation is written for
AWS is specific about its audience, at least for one piece of it. The Well-Architected Machine Learning Lens, published November 19, 2025, states it's intended for people in a technology role: CTOs, architects, developers, data scientists and ML engineers.
That's a deliberate scope decision: the AI readiness assessment AWS offers here asks architecture and workload questions, not "does our sales team trust AI outputs" questions, so a CIO handing it to a frontline manager is handing them the wrong document.
Sources: Machine Learning Lens - AWS Well-Architected Framework, Machine Learning Lens - AWS Well-Architected Framework - Machine Learning Lens
Why the guidance you're reading may already be stale
Both the CAF People Perspective whitepaper, dated January 10, 2023, and the broader CAF-AI whitepaper, dated February 13, 2024, carry AWS's own flag as historical reference material that might be outdated. Each is now more than two years past its publication date.
If your team pulled this whitepaper as an AI readiness assessment PDF for board materials, confirm you're citing AWS's latest CAF-AI revision before it goes into a board deck.
In our view, treating a one-time framework document as standing proof of readiness is a shortcut that erodes trust the moment a board member starts asking follow-up questions.
We'd run a short employee survey before leaning further on the framework: what your people actually do with AI day to day is the piece a document review can't tell you.
Sources: AWS Cloud Adoption Framework: People Perspective - AWS Whitepaper, AWS Cloud Adoption Framework for Artificial Intelligence, Machine Learning, and Generative AI - AWS Whitepaper
What AWS never asks your employees
Across everything reviewed here, no AWS document collects data from individual employees. There's no survey of who actually uses AI tools weekly, who's stopped after one bad result, or which team quietly built workarounds instead of adopting the sanctioned tool.
- As a starting point, consider asking: which teams use AI daily versus not at all?
- Consider asking: what do employees say stops them from using it more?
- Consider asking: do managers and frontline staff report the same level of AI skill?
- Consider asking: has training actually changed reported usage, or just awareness?
That's a real gap for a CIO trying to answer the board's actual question: not "does our framework look complete" but "are our people using this, and where is it stuck." A direct employee survey built for identifying AI adoption problems and selecting interventions before investing further does that job, and it's a separate job from scoring architecture.
A platform built around nine predefined survey types exists specifically to collect that employee-level evidence, covering usage, skills, perceived barriers, culture and change over time, the dimensions CAF-AI's People Perspective describes in principle but doesn't measure in practice.
Sources: People perspective: Culture and change towards AI-first
Running both assessments gets you closer to an answer
Running the AI readiness assessment AWS teams can complete with CAF-AI alone only covers half the picture: the organizational and technical half.
Use CAF-AI's framework review as a planning checklist for an executive conversation about AI readiness. Use the Well-Architected ML Lens with your architects and data scientists when a build decision is on the table. Neither replaces asking your workforce directly.
That's the pairing worth defending to your board: AWS's framework for the organizational and technical picture, and a direct employee survey for the human one. One without the other leaves half the readiness question unanswered.
Sources: People perspective: Culture and change towards AI-first, Machine Learning Lens - AWS Well-Architected Framework
Frequently asked questions
Does AWS provide a single AI readiness score or report?
No. AWS's CAF-AI whitepaper is framed to help you judge maturity and prioritize near-term improvements across several organizational areas, not to output one number or a final readiness score.
How long does it take to work through AWS's CAF-AI materials?
AWS's documentation doesn't state a fixed timeframe. Treat it as editorial judgment: a Business or Platform lead can skim the whitepaper in an afternoon, but applying it to real decisions takes longer.
Who should actually read the Well-Architected Machine Learning Lens?
Technical roles are AWS's stated audience: CTOs, architects, developers, data scientists and ML engineers. Even for those readers, the lens evaluates workload and architecture choices only, so it won't tell you whether that same technical team feels confident using AI day to day.
Is the CAF-AI people perspective guidance still current?
Not necessarily, and that's worth checking before you cite it. If AWS hasn't published a newer revision by the time you're reading this, treat the people-perspective detail as directional, and lean on your own employee data for anything time-sensitive.
What should I add if I only have AWS's framework review?
Start small: run a short survey with one team or department on usage and perceived barriers before expanding company-wide. That pilot tells you whether a fuller employee survey is worth commissioning, something a framework review alone won't show you.
Sources: AWS Cloud Adoption Framework for Artificial Intelligence, Machine Learning, and Generative AI - AWS Whitepaper, Machine Learning Lens - AWS Well-Architected Framework, AWS Cloud Adoption Framework: People Perspective - AWS Whitepaper
