Explore our AI courses, practical training for non-technical teamsExplore courses →Explore AI courses →
Human-AI CollaborationAI SkillsPractical Guide

15 Human-AI Collaboration Skills (and How to Practise Each One)

Fifteen small habits, four families, and a ten-minute way to practise each one on work you already have.

TLDR: Working well with AI is fifteen small habits in four families: set it up, judge what comes back, work with the people around it, and own the outcome. Each can be practised in ten minutes on work you already have. Run the self-check, pick three skills for your role and keep a weekly log. The list is our judgment, not a validated model. Sources read October 26, 2026.
15skills, grouped into four families.
10minutes per drill, on work you already have.
3skills to pick first, by role.

Share this article

The Short Version

Fifteen human-AI collaboration skills in four families, each with a definition, a daily-work example and a ten-minute drill. Score yourself on what you did in the last two weeks, pick three skills by role, and log one drill a week. Use, persistence and impact come from scoring again a month later.

Working well with AI comes down to small habits you can practise on Monday

People who work well with AI usually aren’t using a better tool. They’ve picked up a handful of small habits that nobody ever named, so it gets called “being good with AI” and can’t be taught.

Two analysts ask the same assistant for a summary of a competitor’s pricing changes. The first reads it, finds it sensible and sends it to the team. The second opens two of the pages the summary refers to, sees that one says something narrower than the summary claims, and fixes the sentence before it goes anywhere. The tool was identical. The difference was a habit: check one claim against its source before forwarding.

This guide names fifteen habits like that and sorts them into four families: setting the work up, judging what comes back, working with the people around it, and owning the outcome. Each skill has a one-line definition, what it looks like on an ordinary day, and a way to practise it in about ten minutes. My view is that these skills are learned by doing small, real reps, not by reading a list, so each drill uses work you already have.

This list comes from how we teach non-technical teams. It’s our judgment, not a validated competency model or a research finding, and other lists will slice it differently. For the narrower argument about which human skills gain value as AI gets cheaper, see our piece on human skills in the AI era. This one is the checklist.

  • Set it up (skills 1 to 4): choosing the task, briefing, giving context, working in steps.
  • Judge what comes back (5 to 8): checking, calibrating trust, challenging, holding your standard.
  • Work with the people around it (9 to 11): saying how you used it, reviewing others’ AI-assisted work, sharing what works.
  • Own the outcome (12 to 15): naming the owner, protecting information, knowing when to stop, adjusting how you work.
The Ten-Minute Rule

Practise one skill at a time, for ten minutes, on work you already have.

Setting it up: four skills that happen before you type

Most of the effort that decides how a session goes happens before the first prompt. A marketer who types “write a launch email” gets a competent, generic email and concludes the tool is average. The sentence didn’t say who the email was for, what the launch was or what the reader should do next.

  1. Choosing the task. Deciding which work is worth handing over and which isn’t. In practice: you start with repetitive, text-heavy work that’s quick to check, such as a first draft or a reformat, and keep the judgment calls. Ten minutes: list the last five things you did at work and mark each one “hand over”, “share” or “keep”. Look at where you hesitated.
  2. Briefing. Saying what you want, for whom, and what good looks like. In practice: the request names the audience, the purpose, the length and one thing to avoid. Ten minutes: rewrite a request from this week with those four parts, run both and compare.
  3. Giving context. Supplying the situation, not just the task. In practice: you paste in the background, the previous version or the constraints the assistant couldn’t know, and say what’s settled and what’s open. Ten minutes: do one task twice, bare and with two paragraphs of real context, and note what changed.
  4. Working in steps. Treating the first output as a draft you direct, not a verdict. In practice: you ask for an outline before the text, or a revision of one section, rather than starting over. Ten minutes: give one output three rounds of specific feedback (“shorter opening, drop the second example”). Stop when it’s usable.

Briefing is the skill people point to when they say “prompting”, and it’s one of fifteen. Here is a filled-in brief for a recruiter, with the parts that usually get left out.

A brief you can paste and adapt

I’m a recruiter writing to candidates who reached the final interview and weren’t selected. Audience: people who gave us several hours of their time, so the tone is warm and direct, not corporate. Purpose: tell them the decision, thank them specifically, and invite them to apply for future roles. Length: under 130 words. Constraints: no reasons for the decision, no promises about future openings, no phrases like “unfortunately we regret”. Context: the role was a customer success lead and the team chose someone with more experience in our sector. Before you draft, ask me up to three questions if anything is missing.

A Future Factors example. Swap in your own role, audience and constraints. The last sentence asks the assistant to ask you, which is the quickest way to find what you left out.

Have a look at the last line of that brief. Asking the assistant to question you first is a small move that tends to surface the context you forgot to give.

Judging what comes back: four skills that catch the polished mistake

AI output arrives in the same polished voice whether it’s right or wrong, so the checking comes from you. A draft that reads well is not evidence that it’s correct.

  1. Checking against a source. Confirming that claims, figures and quotes exist where the output says they do. In practice: you open the original for the two or three claims that carry the most weight, not for every sentence. Ten minutes: pick the three claims in a recent output that would embarrass you if wrong, and trace each to a source.
  2. Calibrating trust by task. Knowing that reliability changes from one kind of work to another. In practice: you trust it more on reformatting and first drafts, and less on anything needing judgment about your specific situation. Ten minutes: give the assistant one task you know the answer to and one you don’t. Note which one you were tempted to believe faster.
  3. Challenging the answer. Asking what could be wrong with it. In practice: you request the sharpest objection, the assumption it’s resting on, or what it couldn’t support from the material you gave it. Ten minutes: run the challenge prompt below on a recommendation you were about to accept.
  4. Holding your standard. Editing until the work meets your bar for voice, accuracy and fit, whoever drafted it. In practice: you can say what you changed and why, and the finished piece sounds like you, not like a default. Ten minutes: edit one AI draft to a version you’d put your name on, then list the changes you made most. That list is your standard.

Skill 6 has the clearest research behind it. In a preregistered experiment with 758 knowledge workers, those using AI on tasks inside its capability finished 12.2% more tasks and 25.1% faster, and on one complex task outside it they were 19% less likely to produce a correct solution.[1] It’s one study on a specific set of tasks, so don’t read it as a number for your own work. The useful part is the shape: the boundary between “good at this” and “confidently wrong” isn’t visible in the output, so you learn it task by task.

A challenge prompt for skill 7

Here is the recommendation I was about to accept: [paste it]. Give me the three strongest objections to it. For each one, say what would have to be true for the objection to be right. Then list any claim in the recommendation that you can’t support from the material I gave you, and mark it “unsupported”.

A Future Factors prompt. Use it after the answer looks finished, not before. The “unsupported” label gives you a short list of things to check by hand.

Our guide to critical thinking for AI has a longer set of questions.

Working with the people around it: three skills teams skip

Much of AI skill is invisible because it happens in a private chat window. These three skills make the work visible enough for colleagues to trust it and learn from it.

  1. Saying how AI was used. Telling the people who rely on your work what the assistant did and what you checked. In practice: a one-line note such as “first draft by AI, figures checked against the finance export” sits at the top. Ten minutes: write that note for the last thing you sent, and ask whether the reader would have wanted it.
  2. Reviewing a colleague’s AI-assisted work. Asking about the process without accusing anyone. In practice: you ask “what did you check?” and “which parts did the assistant write?” as ordinary review questions, the way you’d ask about a data source. Ten minutes: write the two questions you’d ask the author of a deliverable you’re about to approve.
  3. Sharing what works. Passing on a prompt, a brief or a check so someone else doesn’t start from nothing. In practice: you keep a short shared note of two or three briefs that worked, with what each is for. Ten minutes: strip the private details from your best brief this month and write one line on when to use it.

A manager who receives a report sees a clean document and can’t tell whether it was typed, drafted or pasted. That’s not a reason for suspicion. It’s a reason for a shared habit of saying so, so the manager’s attention goes to the parts that need it. An L&D designer who finds a brief that reliably produces a decent first draft of a quiz has made something the whole team could use, and it stays in her chat history unless she shares it.

Owning the outcome: four skills that stay with you

The last family holds up as the tools improve. Someone still answers for the work, decides what information is safe to share, and decides whether AI belongs in the task at all.

  1. Naming the owner. Deciding who answers for the output before the assistant drafts it. In practice: every piece of AI-assisted work has a named person who would explain it if challenged. Ten minutes: pick three tasks where you use AI and write the owner’s name next to each. If the answer is “nobody”, that’s the finding.
  2. Judging what goes in. Deciding which information is safe to paste, and in which tool. In practice: you check your organisation’s policy, strip names and figures you don’t need to share, and use the approved tool for anything sensitive. Ten minutes: take a recent prompt and rewrite it with the identifying details removed. Check whether the answer was any worse.
  3. Knowing when to stop. Recognising work that shouldn’t go to AI, or that has stopped benefiting from it. In practice: sensitive conversations, decisions about individuals and anything you can’t check are kept by the person. Ten minutes: write a “not for AI” list of five tasks in your role, with one reason each.
  4. Adjusting how you work. Reviewing what worked and changing the habit, not just the prompt. In practice: once a week you look back at one task and note what you’d do differently. Ten minutes: at the end of this week, write down one thing you’ll keep, one you’ll change and one you’ll stop.
The Ownership Rule

Name the person who answers for the output before the assistant starts drafting.

Here is what that looks like across four roles. The pattern is the same in each row: the assistant prepares, the person decides, and there’s a specific check with a specific person doing it.

What AI does, what the human owns, how it gets checked

RoleWhat AI doesWhat the human still ownsHow it gets checked
AnalystDrafts a summary of a data export and suggests possible explanations for a trendWhich explanation is credible, and what goes into the recommendationThe analyst traces headline figures to the export. A senior colleague asks how it was produced
RecruiterDrafts outreach and rejection messages from a briefThe decision about each candidate and the tone of the messageThe recruiter reads every message before it sends. The assistant never judges suitability
MarketerProduces variants of a campaign email from an approved messageWhich claims are true, and the final choice of messageThe marketer checks each claim against the product page. Legal reviews any number
L&D designerTurns source material into a draft outline and practice questionsWhat learners need, and whether the questions test the right thingA subject expert reviews the questions, after the designer tries them on a few learners

A Future Factors working split. Adjust it to your organisation’s policy and to what your tools can reach. For the full approach to review, see our guide to writing human-in-the-loop guidelines and the manager’s guide to managing the responsible use of AI.

Skill 14 is the one people resist, because it can feel like admitting the tool isn’t useful. Deciding a task isn’t for AI is a good outcome.

A ten-minute check on where you stand

The check below takes ten minutes and asks what you did in the last two weeks, not how confident you feel. That’s deliberate. In a survey of 319 knowledge workers, higher confidence in generative AI was associated with less critical thinking, while higher confidence in their own ability to do the task was associated with more.[2] The data was self-reported, so treat it as a pointer. It suggests “I feel comfortable with AI” is a weak test and “I did this thing” a better one.

The 15-skill self-check: score one point for each honest yes

#SkillIn the last two weeks…
1Choosing the taskI decided on purpose which tasks to hand over and which to keep.
2BriefingMy last request named the audience, purpose, length and one thing to avoid.
3Giving contextI pasted in the background the assistant couldn’t have known.
4Working in stepsI gave specific feedback on a draft instead of starting again.
5Checking against a sourceI opened the source for at least one claim that mattered.
6Calibrating trustI trusted the output less on a task where I knew it was weak.
7Challenging the answerI asked for the sharpest objection before accepting a recommendation.
8Holding my standardI changed a draft until I’d put my name on it, and could say what I changed.
9Saying how AI was usedI told a reader what the assistant did and what I checked.
10Reviewing others’ workI asked a colleague how an AI-assisted deliverable was made.
11Sharing what worksI passed on a brief or a check to someone else.
12Naming the ownerI could name who answers for each AI-assisted piece of work.
13Judging what goes inI removed sensitive details or used the approved tool.
14Knowing when to stopI kept at least one task away from AI, and knew why.
15Adjusting how I workI reviewed one task and changed something about how I do it.

Score one point per yes. 0 to 5: getting started, so pick three skills and run one drill each. 6 to 10: you have the basics, and the gaps are often in skills 9 to 15. 11 to 15: working well, so share it, because skill 11 is how a team catches up. A Future Factors working check, not a validated assessment.

Today’s score is use. Score again in a month for persistence, whether you’re still doing these things unprompted. Whether the work is better or faster for it is impact.

Pick three, by role

Nobody needs all fifteen at once. A recruiter and an analyst share the list but not the starting point, because a missed habit does different damage in each job. Pick the three that would hurt most to skip this month.

Pick your three, by role

RoleStart withWhy theseFirst ten minutes
Analyst5 Checking, 7 Challenging, 12 Naming the ownerNumbers travel further than the caveats attached to themTrace the three most important figures in your latest summary to the source
Manager10 Reviewing others’ work, 9 Saying how AI was used, 14 Knowing when to stopYour team copies what you ask about and what you acceptWrite the two review questions you’ll ask of the next AI-assisted deliverable
Recruiter13 Judging what goes in, 14 Knowing when to stop, 8 Holding your standardCandidate data is sensitive, and decisions about people stay with peopleRewrite one recent prompt with identifying details removed
Marketer2 Briefing, 8 Holding your standard, 5 CheckingVolume is cheap, and a wrong claim in a campaign is costlyRewrite last week’s brief with audience, purpose, length and one thing to avoid
L&D designer3 Giving context, 11 Sharing what works, 7 ChallengingA good brief for one course helps the whole team, if it’s sharedAdd two paragraphs of real learner context to a brief and compare the draft

A Future Factors suggestion by role, based on where a missed habit costs most. If your role isn’t listed, ask which of your outputs travel furthest without anyone checking them, and start with the skills that sit closest to those.

For the team-level view, see what AI skills employees should be trained in.

A weekly practice log, filled in

A drill done once is a nice afternoon. Done weekly, it becomes a habit. Here is a log a recruiter might keep over four weeks.

A weekly practice log, filled in

WeekSkillTask I used it onWhat I didKeep, change or drop
113 Judging what goes inOutreach message to a passive candidateRemoved the candidate’s current employer and salary from the promptKeep. The draft was just as good
214 Knowing when to stopFeedback after a final interviewWrote the feedback myself and used AI only to tighten itKeep, and add it to my “not for AI” list
38 Holding your standardJob advert for a customer success leadEdited the draft down and noted I often cut the opening lineChange. Add “no opening slogan” to my brief
413 Judging what goes inA second outreach messageDid it without being remindedKeep. This one has become routine

A Future Factors example. The last column turns a drill into a decision, and the week 4 entry is the persistence signal.

A Friday review prompt for skill 15

Here are my notes from this week: [paste what you used AI for, what you changed, what went wrong]. Group them into things to keep, change and stop. For each “change”, suggest one specific adjustment to my brief or my checking step. Don’t invent anything I didn’t write down.

A Future Factors prompt. Paste your own notes, since the assistant can’t remember your week for you.

You can build all of this on your own, and many people do. When a group of people are building the same habits at once, working with someone who has seen where these stall can shorten the learning curve, build a shared standard across a team rather than in one enthusiastic person, and help people apply the habits to their real work instead of generic examples. That is the work our corporate workshops are built around.

This week, run the self-check, pick your three skills and put three ten-minute slots in your diary.

Start with the first slot today.

Sana Mian
Sana Mian, Co-Founder of Future Factors AI

Sana is an AI educator and learning designer specialising in making complex ideas stick for non-technical professionals. She has trained 2,000+ learners across corporate teams, bootcamps, and keynote stages. Future Factors offers AI Bootcamps, Corporate Workshops, and Speaking & Consulting for businesses ready to adopt AI without the overwhelm.

More about Sana →

Frequently Asked Questions

Do I need all fifteen skills?

No. Most people already do a few without having named them. The self-check shows which, and the role table suggests three to start with. Treat the rest as a menu.

Is this just prompt engineering?

Skills 2 to 4 cover what people usually mean by prompting, and they’re a fifth of the list. The rest is about what happens before and after the prompt: choosing the task, checking the result, and deciding who is responsible.

How do I practise without risking real work?

Use work that is already finished or low-stakes, such as last month’s report, a draft that went out last week or an internal note. Drill 13 is the exception: do it first, because it tells you what’s safe to paste into the others.

Which skill do people skip most?

In our workshops, skills 9 and 14 tend to feel the most awkward: saying how you used AI, and deciding a task isn’t for it. Both can feel like admitting weakness, and both make colleagues more willing to trust AI-assisted work.

Can a manager use this to assess their team?

Use it as a conversation, not a scorecard. It asks about behavior in the last two weeks, which is fair to discuss in a one-to-one. Turned into a rating, it invites people to tick yes. For a team-level view, see our AI skills matrix guide.

About This Article

I read two research sources on October 26, 2026: the Harvard Business School working paper on the jagged technological frontier (Dell’Acqua and colleagues, 2023) and the Microsoft Research and CHI 2025 survey on generative AI and critical thinking (Lee and colleagues). The first is a field experiment on specific tasks, and the second is self-reported survey data, so neither says how much any of these habits will change your own results. The fifteen skills, the four families, the self-check, the role table and the log are Future Factors working methods, not research findings or a validated competency model. I did not test any tool hands-on for this article, and the scenes are illustrations, not client stories.

Sources

  1. Dell’Acqua, McFowland, Mollick, Lifshitz-Assaf, Kellogg, Rajendran, Krayer, Candelon and Lakhani, Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of AI on Knowledge Worker Productivity and Quality (Harvard Business School Working Paper 24-013, September 2023; forthcoming in Organization Science). Preregistered experiment with 758 knowledge workers: 18 tasks inside the AI frontier (12.2% more tasks completed, 25.1% faster, higher quality) and one complex task outside it, where AI users were 19% less likely to produce correct solutions. Read October 26, 2026. https://www.hbs.edu/faculty/Pages/item.aspx?num=64700
  2. Hao-Ping Lee, Advait Sarkar, Lev Tankelevitch, Ian Drosos, Sean Rintel, Richard Banks and Nicholas Wilson, The Impact of Generative AI on Critical Thinking: Self-Reported Reductions in Cognitive Effort and Confidence Effects From a Survey of Knowledge Workers (CHI ’25, ACM, 2025, Article 1121; Microsoft Research). Survey of 319 knowledge workers sharing 936 examples; self-reported data; higher confidence in GenAI associated with less critical thinking, higher self-confidence in the task with more. Read October 26, 2026. https://www.microsoft.com/en-us/research/?p=1135061

Psst, Hey You!

(Yeah, You!)

Want helpful AI tips flying Into your inbox?

Weekly tips. Real examples. Practical help for busy professionals.

We care about your data, check out our privacy policy.