All categories
Prompting Patterns
Prompting

The AAA framework — prompting that works in everyday life

Good prompting is not a talent but a method. Explain clearly to the AI what you want and you get usable answers without asking three times. Stay vague and you get vague results — and give up after the third attempt. The gap is large: according to Bitkom 2025, 43 % of companies offer no AI training. That is exactly where this chapter starts. It makes prompting repeatable for a whole department.

43 %
without AI training
3
building blocks (AAA)
2–5
few-shot examples
1
prompt library

External figure: Bitkom 2025 · method from AI adoption work

The golden rule

Explain the task as if the AI were a new colleague. A new colleague does not know your industry, your tone or your target format. You give them context, a clear goal and an example. That is exactly what a good prompt does.

Explain the task as if the AI were a new colleague.

meinGPT · prompting fundamentals

AAA — three building blocks for every prompt

The AAA framework breaks every prompt into three parts. It works for text, analysis and support — for any request.

01
Assumptions
set the role & context
02
Assignment
state a precise goal
03
Appearance
format · length · style

A complete example shows how the three parts work together:

Assumption: You are an experienced business journalist with expertise in finance and technology. Assignment: Write an analysis of the opportunities AI offers small companies. Appearance: About 700 words, five paragraphs, professionally sound and easy to understand.

Before / after

The difference between a weak and a strong prompt is precision — not length. Three typical examples:

  • Clarity: ❌ "Write something about marketing" → ✅ "Write a 300-word introduction to content marketing for B2B".
  • Context: ❌ "Answer this email" → ✅ "Answer this customer complaint professionally and offer a solution".
  • Format: ❌ "List the benefits" → ✅ "List the 5 most important benefits as bullet points, one to two sentences each".

In our rollouts we see the same five mistakes over and over. Knowing them is how you avoid them:

The five recurring mistakes

Observed in our AI adoption work — these patterns cost the most time:

  • Too vague — "make it better" tells the AI nothing.
  • Missing context — the AI does not know your situation.
  • Unclear format — without a target format the AI guesses.
  • Too many tasks at once — one request, one goal.
  • No example for a complex format — with JSON or tables, a pattern is mandatory.

Few-shot as the company standard

If you want a consistent company format, give the AI examples. Two to five examples before the actual request enforce your format and your tone. Negative examples protect the brand voice — you show what is not wanted:

Right: "Dear Ms Schmidt," — wrong: "Hey Schmidt,"

That turns an arbitrary answer into one that sounds like your company. Few-shot is the simplest technique with the biggest leverage on consistency.

The prompt library as a team asset

A good prompt is work. That work should only happen once. Proven prompts become templates with placeholders{CUSTOMER}, {TOPIC}, {LENGTH} — and land in a central repository instead of 30 private note apps. A prompt journal with versioning records which variant works best.

Whoever maintains the library decides its value: the champion of a department curates the templates, collects successful prompts and shares them with the team. More on that in the chapter enablement & training.

The system prompt hierarchy

At platform level you do not have to maintain every prompt individually. meinGPT brings three levels together — from the general to the specific:

1
Workspace-wide
admin · tone of voice
2
Assistant
role & task
3
User
the concrete request

The global prompt sets company principles and tone once for everyone. The assistant defines its role. The user only formulates the request. Keep every level focused — duplication leads to blurred answers.

What this means for you

Prompting competence is the gap that 43 % of companies leave open. You do not close it with a tool but with a method (AAA), a standard (few-shot) and a shared asset (the library). That costs a few hours to set up and works in every department.

Where to read on

Who maintains the prompts and carries them into the team is covered in the chapter enablement & training. How assistants are built with system prompts, tools and knowledge is shown by the solution library. And what good prompts are worth in euros is calculated by measuring impact.

ISO Certified
GDPR Compliant
EU Hosting

Start with AI in your company

Together we find the right use cases, connect your systems, and bring AI into daily work in line with your business.