
Map your team's hidden AI use patterns
You'll have a written one-page map or diagram showing which AI tools your team is actually using, what tasks they're applied to, and where workflows overlap or conflict.
What you'll make
Team AI Usage Map
- Current State: who uses what AI tools for which specific tasks
- Workflow Conflicts: where team members solve identical problems with different AI approaches
- Integration Gaps: tasks that could benefit from AI but aren't using it yet
- Priority Actions: top 3 changes that would improve team productivity based on usage evidence
Write your map as structured sections with specific examples and person names (if comfortable sharing) or role descriptions
The 3 parts
Each part ends with a check you can see.
Document what each person actually does daily
Map each team member's daily tasks before looking for AI usage — capture the work reality first
Done when
You have a task-by-task breakdown for each team member showing what they spend time on, with at least 3 specific examples of work outputs you can examine
Challenge your team's stated AI approaches
Compare what people say they do with AI against evidence from their actual work outputs
Done when
You have tested at least 5 claimed AI use cases by examining actual work quality, speed, or consistency changes, with clear evidence for each
Create your team's usage reality map
Synthesize your workflow audit and testing results into a visual map that shows verified AI usage, conflicts, and prioritized next steps
Done when
You have a complete one-page map showing verified AI usage by person/task, documented workflow conflicts with impact assessment, and ranked next steps based on evidence rather than assumptions
Capstone: you put together your Team AI Usage Map.
Where this helps
An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.
About this lesson
What you'll be able to do
- Create a visual map showing actual AI tool use across your team with specific tasks documented
- Identify at least 3 workflow conflicts or gaps where team members are solving the same problem differently
- Have documented evidence of which AI applications deliver value vs which are productivity theater
- Know where to focus team AI adoption efforts based on real usage patterns rather than assumptions
Who it's for
- Team leads who suspect their people are using AI but don't know what or how effectively
- Managers trying to make smart decisions about AI tool budgets and training
- Anyone responsible for workflow optimization who needs to see the actual state before making changes
What it won't cover
- Individual AI skill training — this is about mapping, not teaching
- Comprehensive AI tool evaluation — you'll work with what people already use
- Privacy-invasive monitoring — this relies on voluntary disclosure and observable workflows
Skills you'll practise
- Workflow discovery through direct observation
- Usage pattern analysis from incomplete data
- Conflict identification between parallel processes
- Evidence-based prioritization for tool adoption