How you use AI shapes how you work. Pick the level that fits you.
---
## Level 1 – Exploring
Single questions, single outputs. You try AI when it's obvious, accept first drafts, don't yet own what you produce.
**What it looks like:** You ask Claude to summarise a paper and send it. You copy code that looks right. You draft once and hit send.
**You're here if:** You reach for AI when stuck, not by default.
---
## Level 2 – Applying
AI is your default first step. You iterate until it's right, catch errors, know when to push back, verify before sharing, transparent about AI's role.
**What it looks like:** Draft → iterate → spot the gap the AI missed → fix it → send. You test code. You edit drafts meaningfully.
**You're here if:** AI is how you start most work. You iterate. You know when something's wrong.
**August 2026 target for everyone at Mews.**
---
## Level 3 – Embedding
AI has changed how you work, not just speed. You design workflows and tools others use. You spot opportunities, help teammates think it through, share what works, set team standards.
**What it looks like:** You've built templates your team uses. You coach others on what prompts work. You've designed a workflow that's half the work with AI. You know the gotchas and you share them.
**You're here if:** You're thinking about how AI changes the work itself. You build things others use. You have opinions about responsible use.
---
## Level 4 – Shaping
You change how your team or function operates. You build systems and standards that reshape how people work with AI. You define when to use it, when not to, how to do it well. Others look to you as the model.
**What it looks like:** You've designed a suite of AI tools your function relies on. You've set the standards for iteration, context, when AI is right. New people learn from you. You make human oversight non-negotiable and visible.
**You're here if:** You're changing how a whole team thinks about AI. You own the craft and the standards. People look to you.
---
## Context
Different roles need different levels. Some roles need L2 by August 2026 – confident, regular use. Others are building toward L3 or L4.
Your manager will be clear about what your role needs. This is about building the right skill in the right place.
You can be different levels in different areas. An engineer might be L3 in prompt design but L1 in data analysis. An operator might be L4 in workflows but L2 in research. The skill is honest self-awareness.