Your teams have ChatGPT, Claude or Copilot. They ask a question, get an average piece of text, rewrite it by hand and conclude that AI doesn’t save them much time. In most cases the tool is not to blame: the request was too vague.

Prompt engineering is the skill of wording that request. At AI Sisters, an AI consultancy, we teach it to business teams: more than 900 companies supported, 60,000 employees trained. Here is what people actually learn, before-and-after examples by role, a standard one-day programme, how long it lasts and how to fund it.

In brief

  • Prompt engineering applied to work comes down to one method: tell the AI who it should be, what you know, what you want, and in what form.
  • Five techniques make most of the difference: context, role, examples, output format and iteration.
  • One day is enough to change habits, as long as you work on the team’s real files.
  • To make the new habits stick, a 6 to 12 week programme with a 90-day follow-up goes further.
  • Training delivered by a Qualiopi certified provider can be funded by your OPCO.
  • Progress can be measured: the same task before and after, time spent, number of back-and-forths, quality of the output.

Read also: how to fund AI training through your OPCO or your skills development plan.

Prompt engineering, applied to work

In research labs, prompt engineering means studying how models respond to instructions. In a business, the question is simpler: how do you get a usable deliverable on the first attempt, a memo, an email, a table, a summary, instead of a draft you have to rework?

The answer is a structure. Our method has six blocks, always in the same order: Role, Context, Task, Goal, Constraints and format, Tone. Each block is a few sentences long. The prompt stays readable at a glance and can be passed from one colleague to another.

The AI Sisters method: a prompt in 6 blocks. 1, Role: the expert you call in, with their experience. 2, Context: your job, your company, the material attached. 3, Task: exactly what the AI must produce. 4, Goal: what the result will be used for, and for whom. 5, Constraints and format: length, outline, table, things to avoid. 6, Tone: the expected register, in a few words.
The six blocks of a prompt, always in the same order.

The most misunderstood block is the first one. The Role is the expert you call in, not you. “You are HR manager at Martin Industrie” gives the AI no particular expertise. “You are an employment law expert with more than 15 years of experience, specialising in sensitive HR letters” changes the level of the answer. Your job, your company and your situation go into the Context.

To put it simply. A prompt works like a brief for a contractor you are meeting for the first time. If they don’t know who they are working for, what the document is for or what it should look like, they will hand back something correct and generic. The model has the same problem.

The five techniques that work

The guides published by Anthropic and OpenAI recommend the same habits we work on in our sessions. They come down to five techniques.

1. Give the context

Who you are, which company you work for, what material you have. “I am a management controller in a retail group, and I am sending you the budget and actuals export for the third quarter.” Without those two lines, the AI makes up an average situation.

2. Call in an expert role

Name the specialism, the experience and the level expected. The model then draws on the vocabulary and standards of that profession.

3. Show an example

Attaching minutes that have already been approved, a template email or a model table works better than three paragraphs of description. Ask it to keep the structure and change only the content.

4. Set the output format

Length, outline, table and its columns, number of bullet points, what not to do. This is the block that makes the result usable without edits. Add a safety rule: “if a piece of information is missing, write to be confirmed”.

5. Iterate instead of starting again

You correct the first result in the same conversation: “shorten part 2”, “add a deadline column”, “rephrase for a non-finance reader”. When a version works, you save the final prompt in the team’s library.

The five techniques and the mistake each one fixes
TechniqueCommon mistakeWhat to write instead
ContextA question with no situationJob, company, attached material, what is at stake
Role“You are an assistant” or your own jobA specific expert, with their experience
ExamplesDescribing the deliverable in detailAttaching a model to reproduce
Output formatLetting the AI choose the formOutline, length, table, columns
IterationAsking the question again from scratchCorrecting in the conversation, then saving
To put it simply. Iterating with AI is like going over a colleague’s work with a red pen. You don’t ask them to redo everything, you show them the three places to fix.

Train your teams in prompt engineering

One day on your real files, with ChatGPT, Claude or Copilot. Qualiopi certified, training rated 9.5/10.

See our tailored AI trainingBook a call

Before and after: three roles, three prompts

Here are three requests that come up in almost all our sessions, first as participants write them in the morning, then rewritten with the method.

The same need, two prompts. Before: “Give me some questions for an annual review.” Result: a generic list that fits any job, to be reworked by hand. After: Role, HR development expert, 15 years of experience. Context, HR manager, industry, job description attached. Task, a review guide in four parts. Goal, a structured and fair conversation. Format, five questions per part, a prompt for each question. Tone, supportive and direct. Result: a guide tailored to the job, ready to print.
A one-line request against a prompt in six blocks.

HR: preparing an annual review

Before

“Give me some questions for an annual review.”

After, with the method

Role. You are an HR development expert with more than 15 years of experience, recognised as one of the best specialists in annual reviews.

Context. I am the HR manager in a 300-person industrial company. I am preparing the annual review of a maintenance technician. I am sending you his job description and our team objectives, with no personal data.

Task. Write a review guide in four parts: review of the year, skills, objectives, career wishes.

Goal. Help the manager lead a structured and fair conversation, then write up the report.

Constraints and format. Five open questions at most per part, with one line of guidance for the manager under each question. No HR jargon.

Tone. Supportive and direct.

The result goes from a list of generic questions to a review guide tailored to the job, ready to print. A rule to set beforehand: no personal data about an employee in a tool the company has not approved. At Samsung Electronics France, the HR teams worked on their prompts using real cases, with that habit in place from the start.

Finance: commenting on a budget variance

Before

“Explain the budget variances.”

After, with the method

Role. You are a management controller with more than 15 years of experience, recognised as one of the best specialists in reporting to executive committees.

Context. I am a management controller in a retail group. I am sending you the third-quarter budget and actuals export, line by line. I am presenting to the executive committee on Thursday.

Task. Identify the five largest variances, in value and in percentage, and for each one suggest the questions to ask the operational teams.

Goal. Prepare a note the committee can read in two minutes.

Constraints and format. A table (line, budget, actual, variance, questions), then a five-line summary. Do not make up any cause: if you don’t know, write to be checked.

Tone. Factual and sober.

The controller gets a structured note to complete with what they know from the ground. The AI does not know the real causes of the variances: every explanation needs checking. At Albioma, 30 employees from the finance teams practised on real finance and accounting cases, with ChatGPT Enterprise.

Sales: following up after a meeting

Before

“Write a follow-up email for a client.”

After, with the method

Role. You are a B2B sales expert with more than 15 years of experience, recognised as one of the best specialists in long sales cycles.

Context. I am a sales engineer at a software publisher for industry. Here are my notes from yesterday’s meeting with a prospect’s operations director: her three priorities, her objections and the timeline she mentioned.

Task. Write the follow-up email.

Goal. Get a second meeting with her technical team.

Constraints and format. 120 words maximum. Reuse her words about her priorities and suggest a single next step, with two time slots. No stock sales phrases.

Tone. Professional and warm.

The follow-up email reuses the client’s words and suggests a concrete next step. Once the prompt is approved, it goes into the sales team’s library, or into a shared GPT, Claude project or Copilot agent.

The standard programme for a one-day prompt engineering course

A one-day prompt engineering course is built from the team’s tasks, gathered before the session through a questionnaire. The schedule below is an example: it adapts to the company’s tool, ChatGPT, Claude, Copilot or Gemini, and to the participants’ roles.

Standard programme for a one-day prompt engineering course
TimeContentWhat participants produce
Early morningWhat generative AI does, its limits, and which data can go into which toolThe team’s usage rules
MorningThe six-block method, demonstrated on one of the team’s casesA first structured prompt
Late morningWorkshop: rewrite three everyday promptsThree tested prompts, before and after
Early afternoonExamples, output format, iteration, attached documentsA complete deliverable on a real file
AfternoonRole-based workshop, then a team challenge in Promptathon styleThe best prompts, presented to the group
End of dayPrompt library, shared GPT or project, individual usage planA team library and the assessment of what was learnt
A one-day prompt engineering course. Morning: 1, the rules, which data in which tool. 2, the method, the six blocks on one of the team’s cases. 3, workshop, rewrite three everyday prompts. Afternoon: 4, techniques, examples, format, iteration. 5, challenge, role-based workshop in teams. 6, library, team prompts and usage plan.
The six stages of a day, from the usage rules to the team library.

The workshops use the participants’ own documents and processes, so they can reuse the prompts the very next day. The format is described on our ChatGPT training for businesses and Claude training for businesses pages, depending on the tool you have rolled out.

How long should prompt engineering training last

The right length depends on the goal: bringing a group on board, changing habits or building lasting practices.

Prompt engineering training formats and lengths
FormatLengthWhat it is for
PromptathonHalf a dayA team prompt competition on business challenges, to bring a group on board quickly
Intensive courseOne dayLearn the method and leave with prompts tested on your own files
Programme6 to 12 weeksSeveral sessions to make practices stick and go as far as agents, with a 90-day follow-up

The Promptathon suits an away day or a tool launch well: a one-hour introduction, then several rounds of challenges. At Albioma, the whole sequence took three hours, one hour of AI Show then two hours of Promptathon in six teams. For a group that needs to produce work with AI every day, one day remains the minimum. To go further, our tailored AI training combines these formats by role.

Funding: Qualiopi, OPCO and the skills development plan

A prompt engineering course is a training activity like any other. It can be included in the company’s skills development plan and funded by its OPCO, the skills operator for its sector. The condition: the provider delivering it must be Qualiopi certified, the national quality certification awarded after an audit.

AI Sisters is Qualiopi certified. For your application, we provide the quote, the course programme, the attendance sheets and the certificates. The process happens before the session: check your sector’s funding criteria with your OPCO, submit the request with the programme, then wait for approval before setting the date.

The schemes, the list of OPCOs and the questions HR directors ask are covered in detail in our article on funding AI training, and on our Qualiopi certified AI training page.

How to measure progress

A prompt engineering course is judged by what teams do afterwards. Four measures are enough, and none of them needs a special tool.

Measuring a team’s progress. Before: a questionnaire on each person’s usage, tools and questions, the starting point. During: the same task twice, at the start and at the end of the day, measuring time, back-and-forths and quality. End of session: the assessment of learning required by Qualiopi, along with satisfaction. 30 to 90 days: lasting practices, prompts reused, library kept up to date.
Four points of measurement, from the questionnaire to the 90-day follow-up.
  • Before the session, a questionnaire gathers each person’s usage, tools and questions. At Albioma, it showed that every participant still had questions about what they could share with an AI.
  • During the day, everyone handles the same task at the start and at the end: time spent, number of back-and-forths with the AI, quality of the output scored on a simple grid.
  • At the end, the assessment of learning required by Qualiopi and the satisfaction questionnaire. Participants rate our training 9.5/10.
  • Thirty to ninety days later, we look at what has stuck: prompts reused, the team library kept up to date, tasks the team now hands over to AI.

The last point matters most: a participant who has saved five prompts and uses them every week has really changed the way they work.

Key takeaways

  • Prompt engineering at work means briefing the AI like a contractor: role, context, task, goal, format, tone.
  • The Role calls in an expert; your job and your situation go into the Context.
  • An attached example and a precise output format avoid most edits.
  • One day on the team’s real files changes habits; a 6 to 12 week programme makes them stick.
  • With a Qualiopi certified provider, the training can be funded by your OPCO.
  • Measure on the same task, before and after, then at 90 days.

Let’s build your team’s training

30 minutes to talk about your roles, your tools and funding. More than 900 companies supported.

Book a meetingDiscover the Promptathon

Sources