Skip to main content

Staying valuable

How to Stay Valuable at Work as AI Gets Better

The advice to "be creative and keep learning" is true and useless. This is what staying valuable looks like as specific, observable behaviour.

The short answer

Staying valuable at work as AI improves is not about learning AI. It is about becoming the person who uses it to produce better outcomes, and who can show that they did. That breaks into three capabilities: AI Fluency (working effectively with the tools, including checking them), AI Leverage (redesigning real work around them rather than just chatting), and Proof (evidence of measurable improvement that travels with you).

The evidence explains why the order matters. Basic fluency is fast becoming a baseline: in a 2026 survey of over 1,000 United States employers, 74 percent called AI skills a strong advantage or a requirement, and 57 percent had already raised their productivity expectations because of AI.17 A baseline does not make you valuable; it stops you being excluded. What the labour market rewards, and what protects experienced workers where younger ones are losing ground, is judgment about where and how the tools should be used.7

This guide turns each capability into behaviours you can observe in yourself, with the research behind each one and a plan for the next 30 days.

Why "learn AI" is the wrong goal

Every list of advice for the age of AI says to learn AI. It is true, and it is not enough, for three reasons the evidence makes plain.

First, basic fluency is becoming table stakes rather than an edge. Employers say AI skills matter: 74 percent of United States employers in ZipRecruiter's 2026 survey saw them as a strong advantage or requirement, and half expected candidates to be practical or advanced users already.17 Microsoft's 2024 survey of 31,000 knowledge workers found 66 percent of leaders saying they would not hire someone without AI skills, and 71 percent preferring a less experienced candidate with AI skills over a more experienced one without.3 Those are company surveys, but the direction is consistent, and employers surveyed by the World Economic Forum expect 39 percent of workers' existing skills to be transformed or become outdated by 2030.1 When everyone is expected to have a skill, having it stops distinguishing you.

Second, "AI skills" mostly does not mean technical skills. The OECD's 2026 review of the evidence found that fewer than 1 percent of workers need advanced AI skills, while most need digital skills and the ability to use, analyse and interpret data, alongside managerial and human skills such as problem-solving and creativity.15 Lightcast's analysis of 1.3 billion job postings found 51 percent of postings requiring AI skills were outside IT and computer science.2 For most people, fluency means using and checking, not building.

Third, claimed fluency is nearly as good as certified fluency, which means neither is a durable advantage. In a 2026 experiment where 1,725 recruiters in the United Kingdom, United States and Germany rated synthetic CVs, listing AI skills raised the chance of an interview invitation by around 8 to 15 percentage points, but formal certificates added only a moderate amount over simply declaring the skill.16 If employers cannot yet tell real fluency from claimed fluency, the person who can demonstrate results has an advantage that a course completion does not provide.

What the evidence says about who benefits and who does not

The research on AI and individual workers contains a paradox that most career advice ignores. AI helps the least experienced people most, and it is hurting the least experienced people most.

AI narrows skill gaps on tasks

  • When around 5,000 customer support agents were given an AI assistant, productivity rose 14 percent on average, but 34 percent for the newest and least skilled agents and hardly at all for the most experienced. The tool spread the practices of the best agents to the rest.6
  • In a randomised trial with 776 professionals at Procter and Gamble working on real product problems, individuals working with AI matched the performance of two-person teams working without it, and the usual gap between technical and commercial staff disappeared.5
  • In the Boston Consulting Group experiment with 758 consultants, those given GPT-4 on tasks inside its competence produced work rated around 40 percent higher in quality, and the bottom-half performers gained most.4

And yet the youngest workers in exposed jobs are losing ground

Using payroll data on millions of United States workers through June 2026, Stanford researchers found that employment of 22 to 25 year olds in the most AI-exposed occupations was 19 percent below where it would have been had it kept pace with less exposed peers, while experienced workers in the same occupations showed no gap. The gap is relative to less exposed peers, it came through reduced hiring rather than dismissals, and it concentrated in occupations where AI substitutes for tasks rather than complementing workers.7 Our guide on whether AI will replace your job covers what that study does and does not show.

The resolution of the paradox is uncomfortable but useful. AI makes a novice better at the tasks novices used to be hired to do, and it also makes those tasks cheaper to do without a novice. What it has not yet replaced is what experienced workers bring: knowing what the task is for, recognising when the output is wrong, and being accountable for the result. PwC's 2026 analysis of over a billion job advertisements found that junior roles exposed to AI were seven times more likely than other junior roles to demand traditionally senior capabilities such as leadership and strategic thinking.19 The bar for entry has moved up to where experience used to sit. The International Monetary Fund's 2026 analysis of job vacancies in advanced economies found the same tension: postings demanding AI skills offer higher wages, but the spread of those skills is linked to lower employment in occupations with high exposure and low complementarity to AI, a challenge it singles out for young people.20

Three ways fluent-looking AI use goes wrong

Before the framework, the failure modes, because each one is a way of using AI a great deal while becoming less valuable.

Unchecked output

In the 2025 KPMG and University of Melbourne study of over 48,000 people in 47 countries, 66 percent of employees said they had relied on AI output without evaluating its accuracy, and 56 percent had made mistakes in their work because of AI.10 A Microsoft Research and Carnegie Mellon survey of 319 knowledge workers found that higher confidence in the AI was associated with less critical thinking, while higher confidence in one's own ability was associated with more, and that the effort of knowledge work was shifting toward verifying and integrating output rather than producing it.11

Workslop

Research affiliated with BetterUp and the Stanford Social Media Lab surveyed United States desk workers in 2025 and found 40 percent had received AI-generated work in the previous month that looked polished but lacked the substance to move the task forward. Recipients spent nearly two hours dealing with each instance, and 42 percent saw the sender as less trustworthy.9 This is company-affiliated research, but its lesson is hard to argue with: passing along unreviewed output spends your reputation to save your time.

Deskilling

A multicentre observational study of 19 experienced endoscopists in Poland found that after routine use of an AI detection tool was introduced, their detection rate in colonoscopies performed without the tool fell from 28.4 percent to 22.4 percent. The authors note other factors may have contributed, and it is one study in one field, but it is the first field evidence of a skill declining after regular AI assistance.12 Anthropic's January 2026 analysis of its own usage data found that when the tasks its model could perform were removed from an occupation, the tasks left for the human often had lower educational requirements, a pattern it described as net deskilling.8 And a small, not yet peer-reviewed study of 54 students found those who wrote with a language model showed the weakest brain connectivity on EEG measures and struggled to quote their own essays.13 None of this means you should not use AI. It means using it in a way that keeps your own skill alive is part of the job.

The Stay Useful framework: Fluency, Leverage, Proof

This is Stay Useful's interpretation of the evidence above, organised so you can act on it. Each capability is defined by what an observer would see you doing, not by what you know.

Stay Useful framework

Fluency, Leverage, Proof

The order is deliberate. Leverage without fluency produces workslop at scale. Proof without leverage is a record of chatting. Fluency without either is what everyone will have by next year.

  1. AI Fluency: can you work effectively with modern AI tools?

    You brief the tool with the context a colleague would need. You iterate rather than accept the first answer. You know, for your own tasks, where the tool is reliable and where it is not. You verify against sources you open yourself. You know when not to delegate, and you keep your own skill in practice.

  2. AI Leverage: can you redesign real work, not just chat?

    You choose problems worth solving rather than tasks that are easy to hand over. You map a piece of work, decide which steps the tool does and which a person does, build in the checks, make it repeatable, and own it. Other people can run your workflow and get the same result.

  3. Proof: can you show measurable improvement?

    You have a baseline, a measurement and a written record: what the work took before, what it takes now, what quality changed, what you checked and what could go wrong. Someone who was not there could inspect it and believe it.

AI Fluency, as behaviour

Fluency is the capability most advice stops at, and the one the evidence says is necessary but not sufficient. Here is what it looks like when done well.

  • You brief, you do not prompt. Purpose, audience, inputs, output format, constraints, and what to do when uncertain. Our beginner's guide to using AI at work shows the anatomy of a good brief.
  • You iterate. Anthropic's usage data shows experienced users are more likely to work in patterns of iteration and validation, and have a higher success rate, than new users who delegate and accept.8
  • You know your own frontier. In the consulting experiment, the same tool lifted quality by around 40 percent on tasks inside its competence and left people performing 23 percent worse on a deliberately difficult one.4 Fluent users have tested the tool on their own tasks and know which side of the line each one is on.
  • You verify against a source you open. Not by asking the tool to check itself. Every figure, name, date and citation.
  • You know when not to delegate. Work where your own thinking is the product, or where you are building a skill you will need, you do first and use the tool second. The deskilling evidence is the reason.12
  • You do not confuse fluency with knowledge. The survey evidence says confidence in the tool lowers scrutiny.11 Fluent users treat their own domain knowledge as the check on the tool, not the other way around.

AI Leverage: redesigning work rather than chatting

The gap between "40 percent faster on this task" in experiments and "2 to 3 percent of my week" in population surveys is the gap between using AI on tasks and redesigning work around it. Most people are on the wrong side of that gap, which is why being on the right side is valuable.

Leverage is also where the automation-or-augmentation distinction lives. The Stanford payroll study found employment declines concentrated in occupations where AI usage substitutes for human tasks, and flat or rising employment where it complements workers.7 The person who redesigns a workflow decides which of those it does. That is a position of influence over your own exposure that a user of prompts does not have. The economist David Autor argues that AI's distinctive opportunity is to extend the reach and value of human expertise, letting more people do higher-stakes work well; whether that happens in your workplace depends on who designs the work.14

What redesigning work involves

  1. Problem selection. Choose a piece of work that matters to someone: it is slow, error-prone, or nobody has time for it. Not the task that is easiest to automate.
  2. Mapping. Write down the steps as they actually happen, including the checks people do informally and the exceptions.
  3. Allocation. Decide which steps the tool does, which a person does, and where a person must confirm before anything proceeds. High-stakes actions stay behind a human.
  4. Safeguards. What information may enter the tool, and what may not. What gets verified and how. What happens when the tool is uncertain.
  5. Repeatability. Write the instruction and the checks so that a colleague could run the workflow and get the same result. If only you can run it, it is a habit, not a workflow.
  6. Ownership. You are accountable for its output, its failures and its improvement. Ownership is what makes it yours in a review conversation.

Leverage in practice: a weekly report

Before
A team lead spends two hours every Friday pulling numbers from three systems into a report that few people read carefully.
Chatting
The lead pastes the numbers into an assistant and asks it to write the report. It takes 90 minutes and reads better. Nothing else changed.
Redesign
The lead maps the report: what decisions it informs, which numbers matter, where they come from, what was checked by hand. They build a repeatable instruction that structures the numbers, flags anything outside a stated range, and drafts commentary on only those items. They add a check that every flagged figure is traced to its source before the report goes out, and a rule that no customer names enter the tool.
Result
The report now takes the lead a fraction of the time, and more importantly it reads differently: exceptions and decisions rather than a recitation of figures. The instruction and checklist are documented, so a colleague covered it during leave without the lead's involvement.
Why it is leverage
The work changed shape, the checks are explicit, another person can run it, and the lead owns it. This is the difference between using a tool and redesigning work.

Our guide to 25 ways to use AI to make your job easier gives each use case in the shape of task, AI role, human check and proof, so you can start from any one of them.

Proof: turning improvement into evidence

This is the part of the framework with the least direct research behind it, and we want to be honest about that. No credible study yet shows managers specifically rewarding documented AI impact. What the evidence does show is a labour market that cannot yet tell real fluency from claimed fluency,16 that is raising productivity expectations for everyone,17 that judges the quality of what you send harshly,9 and that rewards judgment and experience over tool use alone.719 In that market, a record of what you improved, how you measured it and what you checked is a rational hedge, and the only way to make your fluency and leverage visible to anyone who was not in the room.

What a piece of proof contains

The elements of a credible record of improvement

The problem
What the work was, who it was for, and why it mattered. One or two sentences.
The baseline
What it took before: time, error rate, turnaround, rework, whatever you can honestly measure. Estimates are fine if labelled as estimates.
The change
What you redesigned, which steps the tool does, which a person does, and what safeguards are in place.
The result
The same measures after. Where you cannot measure, say what changed qualitatively and who noticed.
The checks
What you verified, how, and what you found. An honest record includes the error the tool made and how you caught it.
The limits
What the workflow does not handle, and what could go wrong. This is what makes the record believable.

Keep these short, dated, and in one place. Three of them, built over three months, are a stronger answer to "how do you use AI?" than any list of tools, in a performance review or an interview.

The other things that matter, defined as behaviour

The generic advice is not wrong. It is unfinished. Here is what each piece means as something you could do this week.

Generic advice translated into observable behaviour
The adviceWhat it means behaviourally
Domain knowledgeYou can tell when an output is wrong without checking, and then you check anyway. You know what the work is for, which the tool never will.
JudgmentYou decide which problems are worth solving, which outputs are good enough for which purpose, and when a task should not be delegated at all.
VerificationYou have a habit, not an intention: every specific claim traced to a source before it leaves your hands.
Workflow ownershipThere is at least one piece of work that runs the way it does because you designed it, and you are the person people ask when it breaks.
CommunicationYou can explain to a non-technical colleague what the tool did, what you checked, and what the limits are, in plain language.
ResponsibilityYou put your name on the output. You disclose AI use where it matters to the recipient. You do not hide errors the tool made.
Problem selectionYou spend your AI time on work that someone will notice improved, not on tasks that were already easy.
Learning speedYou test a new capability on a real task within a week of hearing about it, and you write down what you found.
Evidence of impactYou have dated records of specific improvements with baselines, results, checks and limits.

A note on New Zealand

New Zealand's position makes this framework more valuable, not less. In the KPMG and University of Melbourne study, New Zealanders reported among the lowest levels of AI training of the countries surveyed: 24 percent had undertaken any AI-related training against 39 percent globally, and only 36 percent believed they had the skills to use AI appropriately, against 60 percent globally.10 At the same time, a recruiter survey of 500 New Zealand office workers found 87 percent believed developing generative AI skills was necessary for career success.18 PwC's New Zealand analysis of job advertisements found postings asking for AI skills rose from about 3,900 in 2024 to about 9,600 in 2025, around 2.7 percent of all postings, with most of the growth in roles that use AI rather than build it, and wage premiums for AI skills that remain low across most sectors.19

Read together: demand is rising, the skills are scarce, and the market is not yet paying much extra for them. That is the situation in which someone who can demonstrate fluency, leverage and proof stands out most, because there are few of them and the evidence is easy to check.

A 30-day plan

  1. Days 1 to 7: fluency. Pick three tasks you do weekly. Brief the tool properly on each. Verify every specific. Write one line per task on where it helped and where it failed. This is your personal map of the frontier.
  2. Days 8 to 14: choose a problem. Find one piece of work that is slow or error-prone and matters to someone other than you. Map its steps as they actually happen, including the informal checks.
  3. Days 15 to 24: redesign. Allocate steps between the tool and a person. Write the safeguards. Build the instruction. Run it three times, fixing what broke. Have a colleague run it once from your instructions.
  4. Days 25 to 30: proof. Write the record: problem, baseline, change, result, checks, limits. Share it with your manager, not as a boast but as a proposal for what to do next. Then pick the next problem.

At the end of the month, check the behaviour rather than the calendar. Our AI skills checklist of seven things to check at work is the short version of the three ideas above, written as questions you answer about one real piece of work.

If you are early in your career, do the fluency week twice and put extra weight on the judgment column: do the task yourself first, then compare with the tool, and write down what you would have missed. The hiring data says the bottom rung is where the pressure is, and that judgment is what the rung above requires.719 Our guide on whether AI will replace your job explains why.

Related questions

What skills will AI not replace?

The honest answer is that nobody knows the long-run boundary. What the current evidence shows is that AI usage complements rather than substitutes in roles built on judgment, accountability, relationships and physical presence, and that employment in those roles has been flat or rising.7 The OECD finds employers value problem-solving, creativity and the ability to interpret data alongside basic digital skills far more than advanced technical AI skills.15 Treat any specific "AI-proof skills" list with suspicion, including this paragraph.

Is prompt engineering a real skill?

Briefing a tool well is a real skill, in the way writing a clear email is. Treating it as a specialist discipline is a mistake the market is already correcting: the recruiter experiment found certificates added little over simply claiming the skill.16 The durable skills are choosing the task, providing the context, and checking the result. Those do not go out of date when the interface changes.

Will learning AI help my career?

It will stop you being excluded, and the evidence says that matters: three-quarters of surveyed employers see AI skills as an advantage or requirement,17 and listing them raises interview chances.16 It will not, on its own, make you more valuable than everyone else who also learned it. Redesigning work and keeping evidence of the results is where the advantage sits.

How do I upskill for AI without a course?

Use the 30-day plan above on your own work. The research on who benefits from AI training finds that workers who receive it report better outcomes,15 but the most useful training is applying the tool to a task you already understand, because your domain knowledge is what lets you judge the output. A course can teach the interface. Only your work can teach you where the tool fails on your problems.

Should I tell my employer how I use AI?

Yes, in the form of proof rather than confession. A dated record of a problem, a redesign, a measured result and the checks you built is a proposal, not an admission. It also protects you: hiding AI use and presenting the output as your own is the behaviour that turns into a problem when the output is wrong. Our guide on whether you can use ChatGPT at work covers permission, disclosure and how common hiding it is.