AI Fit Teams
Prepare the organization around the technology.
Understand AI readiness across teams, workflows, capabilities, governance and adoption.
Technology readiness and organisational readiness fail differently. A sound architecture still dies if nobody owns the workflow, the data access takes four months, or the people expected to run it were never asked.
AI Fit Teams scores four dimensions against the work your organisation does: what it can do today, what it is trying to achieve, whether the teams can support it, and the habits that will carry or kill the change.
What you get
What the product produces.
- Readiness scorecard
- Capability, intent, teams and habits, each scored with evidence rather than opinion.
- Shadow-AI inventory
- Which tools and agents are already running, who switched them on, and what they can reach.
- Classified backlog
- Ship now, fix the prerequisite first, or defer — with the prerequisite named.
- 30/60/90 roadmap
- Named owners and success measures, including the human-review gates.
Four dimensions
Technology readiness and organizational readiness fail differently.
A sound architecture still dies if nobody owns the workflow, the data access takes four months, or the people expected to run it were never asked.
- Capability
- What the organization can do today: the skills in the building, the systems people can reach, and the work that already runs without heroics.
- Intent
- What it is trying to achieve, stated as an outcome rather than a technology. If leadership and operators describe this differently, that is the finding.
- Teams
- Whether the people expected to run the result were asked, have the time, and own the workflow it changes.
- Habits
- How decisions get made and reversed here. Habits carry a change or quietly kill it, and they are the dimension nobody scores.
A plan nobody in the building can run is not a plan. It is a slide.
How it runs
Three to four weeks, against the work you do.
Your processes, access to your data, and the people who would have to run whatever gets built.
The output is deliberately boring: a scored snapshot, a backlog you can argue with, and a sequence with owners attached. If the answer is that you should not do this yet, the assessment says so and tells you what would have to change first.
Engagement shape
- 01
Week 1
Workflow interviews, system and data-access review, and a shadow-AI sweep for the tools already in use.
- 02
Week 2
Capability and team assessment, with the scorecard drafted against evidence rather than opinion.
- 03
Week 3
Opportunity map and a classified backlog: ship now, fix the prerequisite first, or defer — with the prerequisite named.
- 04
Week 4
30/60/90 roadmap with named owners and human-review gates, then an executive readout.
Limits
What this is not.
Stated on the page rather than discovered in month three.
- It is an assessment. Running the change afterwards is separate work.
- It will tell you to defer work when that is the answer.
Want to know whether your organization can carry this?
Thirty minutes is enough to tell you whether a team assessment is the right first step, and whether the answer might be to defer.
A person reads every inquiry, usually replying within two business days.