Metaphorical associative cards can support business work when they are used to generate hypotheses, not to deliver a supposedly correct answer. An image may reveal that people in the same meeting understand the product, customer, risk or strategic fork in very different ways. The useful part comes next: translate those reactions into statements that can be checked through interviews, analytics, a prototype or a small experiment. The cards do not replace market research, unit economics, legal review or managerial accountability.
I once joined a discussion about a difficult onboarding flow. Several people chose images with the same tension: a narrow bridge, a locked door and a staircase without a handrail. What mattered was not the visual similarity but the explanations. Product saw too many steps, sales saw an unclear reason to continue, and support saw fear of making an irreversible mistake. The session produced three testable ideas, not a hidden truth about customers.
Open a working situation in Reflecta
A hypothesis tool, not a substitute for a decision
A picture has no fixed business meaning. A boat does not automatically mean growth, relocation or instability. Meaning is created by the question, the person’s first response and the known facts. A careful statement sounds like: “This image makes me wonder whether customers lack a sense of control.” An unsafe statement sounds like: “The card proves that customers are afraid.”
That distinction prevents two common failures. The first is treating a personal association as market knowledge. The second is transferring responsibility to the tool. A card may expose a blind spot, but people still have to assess cost, priority and risk.
Prepare the question, facts and boundaries
Write the question before selecting an image. Keep it within a sphere the team can influence. “Which part of our value is difficult to understand?” is more useful than “Will this project succeed?” Then separate verified facts from assumptions and unknowns.
A short setup works well:
- one question for one session;
- facts and interpretations are recorded separately;
- each person explains only their own association;
- disagreement is allowed and no reading is declared correct;
- the outcome is a hypothesis plus a way to test it;
- cards are never used to assess an employee’s personality, loyalty or professional suitability.
Twelve exercises for product, customer, team and strategy
1. The product as it is today
Choose an image that resembles the product’s current state. Name three visible details before interpreting them. Ask which part of the association is already supported by user behaviour and which part remains a metaphor.
2. The product after an improvement
Select an image of the desired state three months from now. Avoid vague success language. Describe what users would do differently: complete the first flow faster, contact support less often or return without a reminder.
3. A day in the customer’s situation
Choose an image for the customer’s context before they meet the product, not for the customer’s personality. Form two hypotheses: what consumes time and what the person may be trying to avoid. Verify both through research.
4. The barrier before the first action
Use the picture to collect possible obstacles rather than answer “why do they not buy?” The barrier may be unclear pricing, fear of error, too much choice, low trust or an oversized first step. Keep no more than three hypotheses.
5. The language of value
Pick an image that expresses the benefit without naming a feature. Turn it into one sentence for a landing page. If the sentence is attractive but impossible to verify, add an observable result.
6. The team’s current working state
Each participant chooses a card about their own way of working, not about a colleague. Compare where people notice acceleration, overload, pause or lack of clarity. This can start a process conversation, but it is not a psychological test.
7. A conflict between partners
Each partner selects an image for what they are protecting in the disagreement. One may protect speed, another quality, another predictable spending. Naming the protected value is often more useful than deciding who is right.
8. The untested assumption
Ask: “What are we treating as obvious without evidence?” The card may prompt a hypothesis about price, channel, customer motivation or team capacity. Write the fact that would support or weaken it.
9. A strategic fork
Choose one image for each option and use the same criteria: potential benefit, risk, required contribution and unknowns. Do not compare an inspiring picture for one path with an alarming picture for the other without a common frame.
10. Risk and an early signal
Select a risk image, then ask which small sign would show that the risk is beginning to materialise. This turns a general concern into an observable signal such as increased drop-off, approval delays or fewer repeat visits.
11. An available resource
Look for a resource that can be used now, not an ideal future resource: data from previous launches, a colleague’s skill, a loyal user group, an unused communication channel or the option to narrow scope.
12. A small experiment
The final card describes a safe way to test, not the final outcome. Define an action for one or two weeks, one metric and a review date. If the experiment cannot be stopped or its cost is too high, it is not small enough.
Worked example: users leave before completing setup
A composite team was developing a subscription service for small businesses. Analytics showed that many people registered but did not finish setup. In the barrier exercise, someone chose a room with many identical doors. The first interpretation was straightforward: the interface offered too many choices. The second was less comfortable but more useful: users did not know which decision could be changed later, so they postponed every choice.
The team did not treat the image as evidence. They reviewed session recordings, support questions and five short interviews. Both hypotheses were partly supported, but the stronger issue was the absence of reassurance that settings could be changed.
The one-week experiment reduced the first screen to a recommended path and added a clear note about reversibility. The criterion was the proportion of users completing the first flow. The review date was fixed in advance so the team would not select a convenient day after seeing the results.
Save the hypothesis, action and review date in Reflecta
Ethics in group work
A team must know in advance that the cards are not a concealed assessment method. Do not ask for “the card of the weak employee”, decide who should control a budget from an image, or interpret another person’s reaction without consent.
| Appropriate use | Inappropriate use |
|---|---|
| describe your own response | explain what is supposedly in a colleague’s subconscious |
| form hypotheses about a process | diagnose the team |
| discuss observable behaviour | judge competence from a card |
| verify ideas with data | make staffing decisions from the exercise |
| allow a participant to decline | demand public disclosure of a personal association |
When formal power is present, the facilitator must protect the right not to answer. Silence is not resistance and does not require interpretation.
Common mistakes
Confusing a compelling metaphor with strategy. A strong phrase still needs a market test.
Speaking on behalf of customers. Even a vivid association remains a hypothesis until real people support it.
Mixing idea exploration with employee assessment. This makes the exercise unsafe and quickly destroys openness.
Drawing more cards until the answer feels pleasant. Keep two competing readings and decide which evidence would distinguish them.
Forgetting the review date. Without it, the metaphor becomes an inspiring note rather than part of a decision process.
The Reflecta protocol: from image to evidence
- Formulate one working question.
- Record facts and unknowns before selecting an image.
- Describe visible details without interpretation.
- Form at least two plausible readings.
- State your own conclusion without presenting it as objective truth.
- Choose a small reversible experiment.
- Set one main criterion and a review date.
- After that date, add the real event and note what was supported or disproved.
This sequence does not make the cards more accurate. It makes the reasoning more transparent and allows the team to learn from results rather than from the emotional impact of an image alone.
Questions to ask before closing the session
- Which conclusion rests on a fact and which rests only on an association?
- Whose perspective has not been heard?
- How might a customer, competitor or employee explain this differently?
- What is the cheapest test that can distinguish two interpretations?
- What result would make us abandon our preferred version?
- Who owns the next action, and when will the team return to the evidence?
Conclusion
Metaphorical cards are most useful in business when a conversation is trapped in familiar language. They can help people see the product differently, name a customer barrier, expose a conflict of interests or imagine a form for an experiment. Their value appears only when the discussion returns to reality: open data, interviews, user behaviour and a criterion chosen before the test.
Run a business reflection with metaphorical cards in Reflecta
— Sofia Rowan, Official Metaphorical Card Practitioner at Reflecta
This material is intended for learning and self-reflection. It does not promise to predict the future and does not replace professional help.