← Back to concept explainers

Concept Fable

User profile

Conclusion first:A Persona / User Persona is an abstract description of a typical user's goals, tasks, pain points, environment and behavioral patterns. For enterprise Agents, the persona cannot stop at "what users like"; it must also distinguish users, buyers, security reviewers, business owners, IT administrators and the frontline employees ultimately affected. A good Persona helps product, sales and delivery teams understand who gains value in daily operations, who is responsible for risk, who controls the budget, and who will veto the purchase during the security or compliance stage.

Persona, User Persona · Product / research

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

The accountant drew a face for every visitor, and only at the end saw the person who actually used the scale

The cloth shop's accountant liked to profile visitors. Wealthy ladies loved fine silk, scholars loved plain cloth, boatmen loved coarse hemp. He pasted these face profiles behind the counter, and the clerks made recommendations accordingly.

At first, the portraits were useful. When clerks saw someone in a long gown, they brought out plain cloth; when they saw a cart-pushing laborer, they looked for durable linen. Deals closed a bit faster, and the shopkeeper felt the shop understood customers.

Later, the newly arrived teahouse owner wore a long gown but wanted to buy tablecloths that could be washed frequently; a boatman preparing a dowry for his daughter wanted to see fine silk. The clerk recommended according to facial makeup stereotypes, which instead made the customer frown.

The bookkeeper's first fix was to paint the portrait in finer detail: age, clothing, accent, usual visiting hours. The wall was covered with paper, yet the assistants still made mistakes, because the same face could lie behind different tasks.

The old shopkeeper had the accountant sit in at the counter for half a month. She discovered that what truly influenced the purchase was not only who the person was, but also what he needed to accomplish at that moment, for whom he was buying, who approved the budget, and what trouble failure would cause.

So the profiles were rewritten: teahouse owners needed washability, batch production, and restockability; dowry customers needed respectability, color stability, and on-time delivery; travelers rushing for a boat needed cheapness, speed, and no fuss over patterns. Clerks recommended by task and constraint, not just by appearance.

The cloth shop did not throw away the portrait, but it no longer treated the face as the answer. A good portrait helps people remember a type of need, scenario, and decision pressure, helping the shop serve the people who will actually use the scale.

Later, when new apprentices joined, the old shopkeeper still had them look at the portrait on the wall, but required them to ask three more things: what is it bought for today, who will use it, and what happens if it is wrong. The portrait was used to begin, not to close the case. A truly good portrait helps the shop get closer to real needs faster, not stick the wrong label faster. Later, the cloth shop updated its portraits every quarter, not rushing to categorize a customer by what they wore, but correcting them through real purchases and failed service. If a portrait cannot help the apprentice judge better, it is just decoration on the wall; only when it connects tasks and pressure is it useful. Later, the apprentice observed the task first when meeting people, then used the portrait to speed up judgment, and misunderstandings decreased greatly. This sentence was later written into the newcomers' handbook, reminding everyone to look at the on-site cost first before talking about saving effort. And because of that reminder, when similar difficulties arose later, everyone did not rush to apply old methods. They learned to ask which step bears the risk first, then decide whether to loosen, tighten, or rearrange the process.

Reveal

This story is about: user personas

A Persona / User Persona is an abstract description of a typical user's goals, tasks, pain points, environment and behavioral patterns. For enterprise Agents, the persona cannot stop at "what users like"; it must also distinguish users, buyers, security reviewers, business owners, IT administrators and the frontline employees ultimately affected. A good Persona helps product, sales and delivery teams understand who gains value in daily operations, who is responsible for risk, who controls the budget, and who will veto the purchase during the security or compliance stage.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • The copper scale shop: product teams currently selling enterprise AI / Agent capabilities
  • Apothecaries, rice shops, cloth stores, pawnshops: different customer scenarios and role groups
  • The portrait behind the counter: Persona / User Persona document
  • The portrait is drawn ever more finely: the pitfall of mistaking surface features for the essence of the need
  • The people who pay, sign, use, and bear responsibility: the multi-role decision chain in enterprise procurement
  • Goals, tasks, concerns and constraints: the structured information a profile should really retain
  • Personas do not replace facts: Personas must come from research and deal feedback, not imagination

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

ICPuser researchjobs-to-be-donesegmentationworkflowusability

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号