What is an AI Skills Log?
Forget simple checklists of who has used ChatGPT. An AI skills log, or competency framework, is a dynamic record of what employees can actually do with AI to solve business problems. It’s not about knowing AI in the abstract, but about applying it to real
work. Instead of a static list, think of it as a detailed map of your organisation's practical AI capabilities, from drafting marketing copy and summarising sales data to analysing market trends. The goal is to move beyond tracking course completions and measure an employee's ability to generate valuable, efficient, and accurate outputs using AI tools.
The Common Mistake: Starting with the Tool
Many managers begin by asking, "Who on my team knows how to use this AI tool?" This is a flawed starting point. It leads to a generic and often unreliable inventory based on self-reported skills, which correlate weakly with actual ability. This tool-first approach creates a log that is disconnected from business outcomes. You might discover that half your team has “used” an AI assistant, but you have no idea if they can use it to shorten project times, improve customer reply quality, or generate actionable insights. The result is a meaningless list that fails to drive performance or justify AI investments.
The Solution: Define the Task and Prompt First
The headline of this piece contains the core strategic advice. Before you even think about logging skills, you must first define the specific business tasks you want to improve with AI. Do you want to accelerate market research? Automate the first draft of compliance reports? Personalise customer outreach at scale? By defining the task, you provide a clear purpose for the skill. From there, you can consider the prompts required. Prompt engineering—the art of crafting instructions for an AI—is the fundamental mechanism for translating a business need into an AI-driven action. A well-defined task and an understanding of the prompts needed to achieve it are the building blocks of a meaningful skills log.
Structuring Your Log Around Business Outcomes
When you lead with the task, your skills log transforms. Instead of a vague entry like "Proficient in AI Assistants," you get specific, measurable capabilities. For example, for a marketing team, a skill might be: "Can use an AI assistant to generate three distinct ad copy variations for a new product, adhering to brand tone and a 200-character limit." For a finance team, it could be: "Can use AI to summarise quarterly earnings reports into a five-point executive brief, flagging key risks." This task-oriented approach makes the skills log an active tool for workforce planning, allowing you to identify specific gaps and target training where it’s most needed.
From Prompts to Proficiency Levels
The complexity of the prompts an employee can design and iterate on becomes a powerful indicator of their proficiency. You can create levels within your skills log based on this. A 'Functional' user might use a simple prompt to get a basic summary. An 'Advanced' user might employ techniques like chain-of-thought prompting, asking the AI to reason step-by-step to handle a complex, multi-stage problem. This allows you to differentiate between someone who can perform a simple, templated task and someone who can innovate and solve novel problems with AI. This detailed view of proficiency is essential for strategic talent development and placing the right people on the right projects.
How to Get Started
Building a task-oriented AI skills log doesn't have to be overly complex. Start small with a single team or workflow. First, collaborate with team leaders to identify 3-5 key business processes where AI could deliver significant value. Second, for each process, define what a successful outcome looks like. Third, work backwards to determine the steps an employee would take with an AI to achieve that outcome, paying close attention to the kinds of questions and instructions (prompts) they would use. Finally, use these task-and-prompt definitions as the foundation for your skills log. This focused, iterative approach is far more effective than trying to boil the ocean with a company-wide, tool-focused survey.
