EN
Language · same page NLNederlands/ai-en-automatisatie/ai-empathy-map-coach-skill-voor-claude/ ENEnglish (UK)/en/ai-and-automation/ai-empathy-map-coach-skill-voor-claude/ ESEspañol/es/ia-y-automatizacion/habilidad-de-entrenador-de-mapa-de-empatia-de-ia-para-claude/ We do not remember your choice and never redirect you automatically.
~/skills/ai-empathy-map-coach[ok] loaded
INS.SKILL · FREE FOR CLAUDE, ALSO FOR CODEX AND CURSOR

The AI Empathy Map Coach skill for Claude

You describe your customer in two sentences, and Claude builds an empathy map with you using Dave Gray's canvas: a starting block with who and goal, six quadrants, and a source label on every point telling you whether it is a fact or an assumption. It never fills the map in blindly: it asks follow-up questions, looks for the gap between what your customer says and what they do, and always ends with core insights and three concrete actions. What you do not know is not smoothed over but flagged. Those open spots are your research agenda.

Download the skill View all 100 skills NL 3.1 KB · zip containing SKILL.md · MIT licence · no account needed
$ installation, line by lineFIG.00
~/.claude/skills
theseo ~ %
  inflating: ai-empathy-map-coach/SKILL.md
theseo ~ %
  ---
  name: ai-empathy-map-coach
  description: AI Empathy Map Coach skill voor Claude. Helpt ondernemers,…
theseo ~ %
[ok] skill active · 995 words of instruction loaded

the lines above come from the zip on this page · SKILL.md is 6,289 bytes

~/skills/ai-empathy-map-coach/01-demonstratie[run]
Section 01 · The demonstration

Vague target group in, sharp map out

reg. E.001

This is the first example given in the SKILL.md itself: Mark, 42, a self-employed painter in Tilburg with three staff, who wants new private customers through his website. Watch what happens to the labels. The claim about competitors is an assumption and is marked as such; the gap between what Mark says and what he does comes from observation and is worth its weight in gold.

FIG.01: From two sentences to a labelled map[#----] sheet 1/5
~/customer-research · claude + ai-empathy-map-coach
you > I don't understand why my site isn't generating any enquiries, build an empathy map for my typical customer
starting-block.txtthe skill asks first, fills in after WHO: Mark, 42, self-employed painter in Tilburg, 3 staff. GOAL: bring in new private customers through his website. DECISION MOMENT: when things are quiet and quote requests stop coming in.
claude · building the map using the fixed method...
[1/5]follow-up questions · concrete questions per quadrant, never filled in blindly: what does Mark see among competitors, who whispers advice in his ear
[2/5]real language · every point written the way Mark would say it himself, no marketing jargon and no abstraction
[3/5]evidence · every claim comes with a source: data, interview, observation or ASSUMPTION
[4/5]the gap · the difference between what Mark says and what he does explicitly flagged
[5/5]insights · three to five core insights plus three concrete actions for marketing, sales or product
empathy-map.mdshortened, the full structure is in the skill SEE: competitors with slick sites with before/after photos [ASSUMPTION, can be checked via SimilarWeb] SAY AND DO: says "I want more customers online" but spends 0 hours a week on his site [observation] GAP: the distance between those two lines is the sharpest insight in this map ACTION 1: test the assumption about competitors first before changing anything on the site
[#####] 5/5 done · every ASSUMPTION stays visible: those are your research questions
6E.01 · quadrants in the canvas
4E.02 · source labels per statement
5E.03 · things the skill refuses
0E.04 · euros, MIT licence, no account
E.01 to E.04 · properties of the skill file, not results or usage figures.
$ cat 01-wat-de-skill-is.md
DOC.01

What the AI Empathy Map Coach is

The AI Empathy Map Coach is a free skill from our own skill library. A skill is an instruction file, SKILL.md, that gives an AI assistant a fixed method for one task. No software to install, no subscription, no tool with a dashboard: a single 941-word text file that tells Claude how Dave Gray's Empathy Map Canvas is put together, in what order the blocks get filled in, what questions to ask per quadrant, and what must never happen under any circumstances: presenting an assumption as a fact. You download the zip at the top of this page, drop it into your Claude environment, and from that moment Claude builds empathy maps using this method.

The problem this skill solves is uncomfortably familiar. Ask any business owner who their customer is and you get an answer that sounds watertight and is based on nothing at all. The campaign gets built, the landing page goes live, and the message doesn't land. Not because the work is bad, but because it is aimed at a customer who mainly exists inside someone's own head.

The empathy map forces you to pull that picture apart: what does the customer really see around them, what do they hear from colleagues and friends, what do they think and feel, what do they say and do, where is their pain and what are they really looking for. And with every answer, the question that matters most: how do you know that?

It is written for business owners, marketers, product people and sales, as the file itself says. Anyone building a campaign, landing page, product or pitch who wants to sharpen their target group first. It is part of the skill library NL we make freely available through our AI and automation service, with no account and no sales email afterwards.

One thing you should know up front: the skill does not do customer research for you. It structures what you know, flags what you don't know, and tells you where to go and look. A map full of assumptions is an honest starting point, not a final destination, and the skill says so itself: gaps are valuable, they are your research questions.

$ cat 02-waarom-je-klantbeeld-gokwerk-is.md
DOC.02

Why most companies' customer insight is guesswork

The skill's frontmatter lists when Claude should pick it up, and the list reads like a surgery. Who is my customer. I don't understand my target group. What does my customer think, what does my customer feel, what does my customer hear. Building a customer profile, buyer persona, target group research. They are all variations on the same complaint: money is being spent on a target group nobody actually knows.

The first problem is that saying and knowing get mixed up. In almost every marketing meeting, assumptions get stated with the confidence of hard data. Our customer cares about sustainability. Our customer has no time. Ask where that comes from and you rarely get shown an interview or a dataset, usually just a feeling. The skill accepts a feeling like that, but it gets the label ASSUMPTION attached. That changes the discussion: it stops being about who is right and becomes about which assumption should be tested first.

The second problem is that customers themselves cannot be fully trusted either. Not out of bad faith, but because people report what they would like to do rather than what they actually do. That is why the Say and do quadrant in the canvas is a single box: the tension between those two is itself information. There is an explicit instruction for this: find the gap, flag it, because the difference between what customers say and what they do is gold.

The third problem is that the canvas is usually filled in as a box-ticking exercise. A team sits round the table for an afternoon, sticks sticky notes into six boxes and goes home satisfied. Everything on those sticky notes comes from the same heads that already misjudge the customer. That approach is explicitly refused: never fill in a template without questioning the user, the file states. It asks concrete questions per quadrant that let you discover for yourself where your own knowledge runs out.

Shown as a diff: the difference between how a target group is usually written up and how the skill does it, with lines taken from the example in the file.

~/skills/ai-empathy-map-coach/02-canvas[ok]
Section 02 · The canvas

One starting block, six quadrants

reg. E.002

The structure the skill enforces, with the kind of questions it asks per box. The order follows Dave Gray's revised 2017 version: first who and goal, then the quadrants, and pain and gain as the closing pair. Without the starting block the skill will not begin, because an empathy map without a goal is worthless, as the file states literally.

FIG.02: The anatomy of the canvas[##---] sheet 2/5
STEP 0 · WHOWho are we looking atname, role, situation
STEP 0 · GOALWhat do they need to dowhich decision, which job
STEP 0 · MOMENTThe decision momentwhen does the need arise
QUADRANT 1Seewhich providers, adverts, social postswhich competitors, trends, peer examples
QUADRANT 2Hearwhat do colleagues, friends, family saywhich podcasts, news sources, unwritten rules
QUADRANT 3Think and feelbeliefs, doubts, dreamswhat keeps them awake at night
QUADRANT 4Say and dowhat do they say out loud, what do they really dowhere is the gap between the two
QUADRANT 5 · CLOSINGPainobstacles, recurring frustrationswhich risks do they fear
QUADRANT 6 · CLOSINGGainwhich outcomes are they really looking forwhich wishes lie beneath the need
after the six quadrants the skill closes with 3 to 5 core insights and 3 concrete actions · for example a landing page hook, ad copy, a product improvement or a sales pitch
$ less ai-empathy-map-coach/SKILL.md # 941 words of instruction
DOC.03

What is actually in the SKILL.md

A skill is only as good as its instructions, so we simply describe them here. At the top is a frontmatter with the conditions under which Claude should pick up the skill: for questions like who is my customer, build an empathy map for X, build a customer profile and buyer persona, but also for the broader situation where someone is building a new campaign, landing page, product or pitch and wants to sharpen the target group first. The licence is MIT and the version is 1.0.0.

Then comes the structure. Step zero is the mandatory starting block: who are we looking at, what do they need to do, and what is the decision moment. The file is blunt about it: without this block the empathy map is worthless. Then come the six quadrants, each with concrete sub-questions. See covers providers, adverts, competitors and website experiences. Hear covers colleagues, podcasts, authorities and the unwritten rules of the industry. Think and feel covers beliefs, doubts, dreams and what keeps someone awake at night. Say and do covers observable behaviour and the gap between words and actions. And as the closing pair, Pain and Gain: the obstacles and risks on one side, the outcomes they are really looking for on the other.

The method has five rules. First ask follow-up questions, never fill it in blindly. Use real language, written the way the customer would say it themselves. Give evidence for every claim: where does this come from, data, interview, observation or assumption, and mark assumptions explicitly as ASSUMPTION. Look for the gap between saying and doing, because that is where the gold is. And finish with insights: three to five concrete insights plus three action steps, for example a landing page hook, ad copy, a product improvement or a sales pitch.

The output has a fixed structure you can copy straight away: the header with who, goal and moment, then per quadrant the points with their source in square brackets, a separate line for the gap between saying and doing, and to finish the core insights and concrete actions. Two worked starting examples come with it: Mark, the self-employed painter from Tilburg who wants to improve his site, and Lisa, 38, HR manager at an SME with eighty staff who has to choose a new HR tool at the moment management is asking for cost savings and the current tool costs €30,000 a year.

The file closes with five things the skill never does, more on that below, and with a proper source credit: the Empathy Map Canvas by Dave Gray at XPLANE, original version 2009, revised version July 2017, described in his book Gamestorming and his article Updated Empathy Map Canvas. The canvas is open source, and the file notes that it is used worldwide by, among others, IBM, IDEO and Salesforce.

~/skills/ai-empathy-map-coach/03-bronlabels[ok]
Section 03 · Source labels and the gap

Every claim a label

reg. E.003

The mechanism that sets this skill apart from a blank canvas: no statement goes into the map without a source. The four labels run from hard to soft, and the softest label is the most important, because every ASSUMPTION is a research question. The rows below come from the Mark example in the file, supplemented with one schematic data row.

FIG.03: source-labels.log[###--] sheet 3/5
source-labels.logfrom hard evidence to open question
SEE"competitors with slick sites with before/after photos"ASSUMPTIONcan be checked via SimilarWeb, the file says so itself: this is a suspicion still to be tested
SAY"I want more customers online"INTERVIEWMark's own literal words, so they go into the map exactly as spoken
DOspends 0 hours a week on his siteOBSERVATIONnot what he says but what he demonstrably does
MOMENTquote requests dry up in quiet periodsDATAschematic example: this label is for figures from your own records or statistics
GAPsays he wants more customers online, spends no time on it at all: this difference is the sharpest insight in the mapGOLD
DATA figures and measurementsINTERVIEW the customer's own wordsOBSERVATION behaviour actually seenASSUMPTION still to be tested
$ cat 04-herkomst-van-het-canvas.md # Dave Gray, XPLANE, 2009 and 2017
DOC.04

Where the canvas comes from

The Empathy Map Canvas is not an anonymous marketing template but a tool with an author and a history, and the SKILL.md credits it properly. Dave Gray developed the canvas in 2009 at XPLANE, the agency he founded, as a way to help teams see past their own assumptions. In July 2017 he published a revised version, and that is the version the skill follows. The main change in that revision is the order: the map now starts with the goal, who are we looking at and what does that person need to do, and ends with pain and gain. Exactly the order you see in FIG.02.

That order is not a detail. A team that jumps straight to sticking notes into the quadrants produces observations without direction: interesting material, no decision. By first fixing which decision or task is central, every quadrant becomes a filter. What the persona sees and hears only matters insofar as it touches that one decision. And by ending at pain and gain, the canvas forces a ranking: which frustration weighs heaviest, which outcome is really being sought. That is where the insights the skill closes with come from.

The canvas is open source and, according to the credit in the file, is used worldwide by, among others, IBM, IDEO and Salesforce. Anyone who wants to check the origin themselves: the skill points to Gray's book Gamestorming and his article Updated Empathy Map Canvas on Medium. We deliberately do not write more about the source here than the file itself does.

The empathy map rarely stands alone. In the design world it is the best-known tool of the empathise phase of design thinking, and anyone who wants to run through that whole process can turn to the Design Thinking Coach skill. Anyone who would rather reason from the job a customer wants done than from the person can take the Jobs to be Done Analyst skill: the same empathy, a different starting point. The two complement each other rather than replace each other.

~/skills/ai-empathy-map-coach/04-weigeringen[ok]
Section 04 · The limits

What the skill refuses

reg. E.004

The SKILL.md contains a list of five things the skill never does, and that list is exactly why the output is usable. An empathy map full of smoothed-over certainties is precisely the self-deception the canvas was meant to prevent. Each line below is a request you might make, with the response the skill gives according to its own instructions.

FIG.04: refusals.log[####-] sheet 4/5
refusals.log5 fixed rules from the SKILL.md
just fill in the map, I don't have time for all these questionsREFUSEDNever fill in a template without questioning the user. A map that rolls straight out of the AI comes entirely from training data, not from your customer knowledge. The skill asks concrete questions per quadrant that let you discover for yourself where your own knowledge runs out.
write it up a bit more professionally, this sounds so bluntREFUSEDNo vague marketing speak. Sentences like we understand our customer well are exactly what the file forbids. The map is written the way the customer would say it themselves, because that is the only language you can later echo back in your campaign.
just put that doubt in as a fact, I'm quite sure about itFLAGGEDNever present assumptions as fact. If you're sure, then supply the source: data, interview or observation. If you can't supply one, the label ASSUMPTION stays. Not to annoy you, but because a campaign built on the wrong assumption costs more than an afternoon of research.
I don't need the insights, I just wanted the canvasREFUSEDNo empathy map without concrete actions as the end result. A filled-in canvas that disappears into a drawer was not worth the time. The skill always closes with three to five core insights and three action steps for marketing, sales or product.
finish it off completely, I don't want to see any empty boxesREFUSEDNo perfectly filled-in map without gaps. Gaps are valuable, they are your research questions, as the file states literally. A map with no open spots does not mean you know your customer, it means you have stopped asking questions.
$ unzip ai-empathy-map-coach-skill-voor-claude.zip -d ~/.claude/skills/
DOC.05

Installing in Claude Code, Claude.ai or Codex

The zip contains a single folder with the SKILL.md inside it. Installing is a matter of putting the file in the right place, and that place differs per environment. SKILL.md has been an open standard since December 2025, so the same skill also works in Codex, Cursor and Gemini CLI. So you are not downloading a Claude file but a working instruction that any modern AI assistant can read.

CLAUDE CODE
  1. Unzip it into ~/.claude/skills/ (or .claude/skills/ in your project).
  2. Claude then recognises the skill automatically as soon as you start talking about your target group or customer.
  3. You can also call it directly, with /ai-empathy-map-coach.
CLAUDE.AI
  1. Go to Customize and then Skills.
  2. Upload the zip there as a skill.
  3. Or paste the contents of SKILL.md into the project instructions of a Project.
CODEX
  1. Open AGENTS.md in your repo.
  2. Paste the contents of SKILL.md into it, or place SKILL.md alongside it as a separate file and refer to it from AGENTS.md.
  3. Codex reads that along at every session.

After that, using it is simple: tell it who your customer is and what you are dealing with, and the skill starts with the starting block. New to skills? Read what Claude skills actually are NL first and the step-by-step installation guide NL. Want to write a skill yourself for your own way of working afterwards? The structure of a file like that is explained in writing a SKILL.md NL.

$ cat 06-wanneer-wel-en-niet.md
DOC.06

When to use it and when not to

It is at its strongest in the moments the file itself lists: you are building a buyer persona or customer profile, you are launching a new campaign, landing page, product or pitch, you feel your message is not landing, you are losing customers without knowing why, you want to align a team on one shared view of the customer, or you want to improve a product based on real customer need. In every one of those cases the gain is the same: the discussion shifts from opinions to labelled statements, and the next step becomes visible instead of just felt.

There are also situations where you are better off leaving it, or at least weighing it differently. If you have genuinely had zero customer contact, no conversation, no review, no data point, then almost every line of the map becomes an ASSUMPTION. It handles that correctly, and flags everything, but be aware of what you then have: not a picture of your customer, but a tidy list of research questions. That is worth something too, as long as you don't call it a customer picture. Valuable as a starting point, dangerous if you build a campaign on it directly. The honest advice then is: use the map to pick your three most important assumptions and test those first, for example with a few customer conversations.

The second limit is that an empathy map describes, it does not validate. A pain sitting in the quadrant does not mean someone will pay for the solution. Other tools from the same library exist for that question: the Value Proposition Canvas NL to hold your offer up against the customer's jobs, the Lean Canvas Strategist to test the whole business model on one sheet, and the Business Model Canvas Coach for the fully worked-out version of that. All three run on the customer knowledge the empathy map delivers.

And the last limit is the most important: the map is a snapshot. Customers change, markets shift, and last year's map describes last year's customer. Anyone who genuinely wants to steer by it repeats the exercise whenever something changes about the decision moment, and keeps the old versions to see which assumptions turned out to be wrong.

~/skills/ai-empathy-map-coach/05-upgrade-pad[ok]
Section 05 · From skill to employee

Run it yourself, or have it run

reg. E.005

This skill is the free do-it-yourself version of work we also deliver as a service. It stays complete and without a catch, but be clear about what a skill is: it teaches your AI how to do something, while every new session starts empty. It is neither the engine nor the memory. You prompt, you supply the context about your target group again every time, you check the result. Anyone who wants it differently has two follow-up steps: hand off the engine, or sort out the memory.

$ cat from-skill-to-employee.mdthree rungs, the same work
upgrade-path.shfree · employee · brain
RUNG 1 · FREE
where you are now
The skill: you are the engine You run the AI Empathy Map Coach yourself in Claude, Codex or Cursor. Costs nothing, works today, and you keep it fully in your own hands: no trial period, no locked-off parts. The limit is your own time: the map only gets built when you prompt, and you have to supply your target group knowledge again every session. $ claude --skill ai-empathy-map-coach · €0 · you prompt, you check
RUNG 2 · SERVICE
have it prepared
The AI employee: it is ready without you prompting Want this kind of thinking and writing work ready every day without sitting down with Claude yourself? There is the AI employee: a service where the work gets prepared and control stays with you, because output stays a draft until a person gives approval. We deliver this through Mansotti, the company TheSEO trades as, which builds three fixed employees: the Quote employee, the Sales employee for prospect research, and the Reporting employee for weekly and monthly reports. from €950 per month · a person approves, always
RUNG 3 · BRAIN
everything from one source
Jarvis: all your AIs know the same customer The skill teaches the AI; the brain is where the memory lives. Want all your AIs working from the same company knowledge? That is Jarvis, the organisation brain. It connects ChatGPT, Claude, Codex and your people to the same projects, core knowledge and decisions, so your next AI session does not start over. For this skill that means: your personas, validated insights and tested assumptions are still there next time. What that delivers in practice, from the plans to your first week, is at Jarvis itself. entry plan Brain Start: €9 per month incl. VAT · pay for your brain, not per AI question
# not a sales trick: rung 1 stays free and complete. The next rungs are there for anyone who wants to hand this work off.
~/skills/ai-empathy-map-coach/06-jarvis[ok]
Section 06 · The brain

What Jarvis delivers in practice

reg. E.006

Rung 3 deserves more than a paragraph, because when it comes to customer insight, memory is everything. An empathy map that evaporates after the session gets rebuilt from scratch next month. Jarvis is the organisation brain: it remembers what your AIs need to know, divides the work and keeps track of what happened. You notice it first at the start of a new session.

FIG.05: What a session gets back from the brain[#####] sheet 5/5
jarvis · organisation brain● sync
$jarvis recall "customer picture private clients" # schematic example
[core]persona recorded: decision moment is the quiet period with no quote requests · customer's own wording kept verbatim
[core]source rule: every statement carries a label, assumptions never go into a campaign as fact
[task]empathy map for spring campaign · draft ready · waiting for human approval
[decision]test the assumption about competitor sites first before any budget goes to the site: recorded, approved by a person
[log]previous session: claude built the map, the person removed one insight and approved two actions, result saved
[ok]context loaded · this session does not start empty
this is how every task moves through the brain: recordedcontext setdelegatedhuman approvalsaved · the full trail is at jarvis/how it works NL
context.kept Your next session does not start over Today you explain who your customer is, and tomorrow a separate chat knows none of it. With Jarvis every session starts with the same personas, core knowledge and earlier decisions, as in FIG.05: recall first, work second.
ai.connected ChatGPT, Claude and Codex, one source Every connected AI works from the same core knowledge and agreements. The customer picture you record and approve in one tool is used by the others too. You explain nothing three times and no three separate versions of the truth appear.
tasks.tracked Tasks scheduled, tracked, reported done An assignment is recorded with a goal and a deadline, picked up by the right agent and reported done with the result attached. You can see at any moment what is running, what is waiting and what is finished.
everything.logged Everything logged and open to inspection Every step leaves an auditable trail: who asked what, which sources were used, which agent worked on it and who approved it. Not because it has to, but because otherwise you cannot check what happened in your name.
human.approval Nothing goes out without approval AI prepares, a person decides. Output stays a draft until someone approves it, and only approved knowledge goes back into the brain. That line holds everywhere in the system, including work an agent has prepared entirely on its own.
brain.isolated Client brains stay separate If you work for several clients, the knowledge stays strictly separated per client. The empathy maps for one do not leak into the work for another.
# THE HONEST EVIDENCE · NOT A DEMO

We have been running on this system ourselves for months. Every agent session, every task and every decision is logged in it and can be read back. A new session therefore does not start blank: it first pulls up the decisions on record, the projects in progress and the latest changes, and carries on from where the last one stopped. So we are not describing a promise but the way of working we sit in ourselves every day.

$ cat prijzen.mdpay for your brain, not per AI question
Brain Start €9 /month incl. VAT 1 organisation brain · 1 user · 1 AI employee
Brain Solo €29 /month incl. VAT 1 organisation brain · 1 user · 3 AI employees
Brain Team €99 /month incl. VAT 1 organisation brain · 5 users · 10 AI employees
Brain Business €249 /month incl. VAT 3 organisation brains · 20 users · 50 AI employees

See the four plans at jarvis/prijzen NL. Through the waiting list NL you only pass on your preferred plan, without obligation. That does not yet create an account, an order or a payment obligation. We discuss business custom work first.

~/skills/ai-empathy-map-coach/07-verwante-skills[ok]
Section 07 · Related skills

The skills around it

reg. E.007

Customer insight sits at the start of a chain: first understand, then validate, then build. These skills from the same library of 100 free skills each take on a different part of that chain.

$ claude --interactief # seven questions, seven answers
DOC.07 · FAQ

Frequently asked questions

What does the AI Empathy Map Coach skill cost?

Nothing. The skill is free, falls under the MIT licence, and you don't have to create an account or leave an email address. You download a 3.1 KB zip containing a folder and a single file, SKILL.md, and that is the complete skill. There is no paid version and no sales email follows afterwards.

Does this skill also work in Codex, Cursor or Gemini CLI?

Yes. SKILL.md has been an open standard since December 2025, so the same file also works in Codex, Cursor, Gemini CLI and other tools that follow the standard. In Codex you unzip it into .agents/skills/ in your project, or into ~/.agents/skills/ for all your projects; Codex has supported SKILL.md directly since the December 2025 open standard. Putting the contents of SKILL.md into your AGENTS.md still works too. The instructions are readable text, so any AI assistant that accepts instruction files can work with it.

What is the difference from a buyer persona?

A buyer persona is a profile; an empathy map is the research underneath it. The map maps out what a customer sees, hears, thinks, feels, says and does, and records where each point comes from. Anyone who wants a persona can distil one from a finished map. It doesn't work the other way round: a persona without that grounding stays a made-up character with a name and an age.

Does the skill invent customer insights if I have no research?

No. Every statement in the map gets a source label: data, interview, observation or assumption. If you have no research, the map mostly consists of points labelled ASSUMPTION, and that is exactly the point: the skill never presents an assumption as fact and deliberately does not deliver a map without gaps. The open spots are your research questions.

What information does the skill need to get started?

Three things, and without those three it will not start on the quadrants: who the persona is, which decision or job is at stake, and at what moment the need arises. That starting block is mandatory, because an empathy map without a goal turns into a collection of loose observations. After that, the skill asks targeted questions per quadrant and you fill in the map together.

Can I use the skill for a campaign or landing page?

Yes, that is even one of the standard starting points in the file. The skill activates when someone is building a new campaign, landing page, product or pitch and wants to sharpen the target group first. The concrete actions every map ends with are built on that: think of a hook for your landing page, ad copy or a tweak to your sales pitch.

What does a finished empathy map deliver in practice?

A filled-in canvas with source labels is half of the output. The skill always closes with three to five core insights and three concrete action steps for marketing, sales or product. It also flags the gap between what your customer says and what they do, and that is usually where the sharpest insights sit.

$ cat 08-en-nu.md
DOC.08

Know your customer first, then get found

A sharp empathy map tells you what your customer is searching for and in which words. The next question is whether that customer finds you the moment they search. The free SEO scan shows in a few seconds where your site stands. And if you want to talk through what AI can do for your business beyond this, from individual skills to full automation, we are happy to just have that conversation.

Section 08 · Next stepreachable 24/7
Book a call NL
$ whoami
Gianluca, founder
Written by GianlucaFounder. Building visibility for Dutch companies since 2017, in Google and in AI answers. More about the institute.