How to Surface and Map Team AI Workflows
You cannot manage what you cannot see. This playbook covers the practical steps for building and maintaining a clear picture of how every team member uses AI in their daily work. Start with a simple inventory, progress to pattern recognition, and eventually use visibility data to make informed standardization decisions.
This playbook covers the how. For the why and what, see the
skill definition
.
Developing Start here. Build the foundation.
- Create a shared Google Sheet with three columns: Team Member, AI Tools Used, Tasks Applied To. Send each person a 5-minute async form to fill out. Set a calendar reminder to refresh it every quarter.
- Pick the 2-3 deliverables your team produces most often (reports, emails, analyses). Ask each person to walk you through how they create one. Write down where approaches differ most. These are your highest-risk coordination points.
- Add one question to your next standup: 'Has AI changed how you do anything this week?' Cap responses at 60 seconds each. The goal is normalizing disclosure, not interrogation. Do this for 4 weeks straight before evaluating.
Proficient Build consistency and rhythm.
- Block 30 minutes every two weeks for a live show-and-tell. One team member shares their screen and walks through a real AI-assisted task from start to finish. Record it in a shared folder so absent teammates can watch later. Rotate presenters.
- Run a monthly 30-minute alignment check using three questions: What changed in how we work? Who else does it affect? Do we need to adjust anything? Document decisions in a running log so you can spot patterns quarter over quarter.
- Build a simple dashboard (even a spreadsheet tab) that tracks tool adoption by person over time. Flag tools that were adopted then abandoned. These often signal usability problems worth investigating. Review it before 1:1s to ask informed questions.
Mastered Operate at the highest level.
- Before any standardization decision, present the visibility data to the team: 'Here is what I see. Here is what I think we should standardize. Here is what I think we should leave alone.' Let them challenge your reasoning. Document the decision and the rationale.
- Set a benchmark for how fast proven practices spread: if one person discovers something valuable, it should reach the whole team within 2 weeks. Track this. If adoption is slower, diagnose whether the barrier is awareness, access, or relevance.
- Shift from manager-driven transparency to peer-driven sharing. Create a Slack channel or Teams thread where people post workflow changes as they happen. Seed it yourself for the first month, then step back and measure whether it sustains.
Unlock Skill Progression
Coaching Personalized to your current level
Progress Tracking Across every skill area
Mastery Validation Evidence-based, not guesswork