Skip to content
Interface language: English
Imperium / Signal

A community of practice needs something people can do together

Give practitioners time to examine real cases, share their reasoning and make clear what has been confirmed.

Article language: English

A woman holds a card with a leaf beside ornate red drawers.
In this article

A company channel called “Sharing experience” has a name, an icon and dozens of members. Training announcements, article links and reminders of the next meeting appear there. When an employee asks how to handle an unusual case, however, she gets an answer later in a private conversation with someone she knows. The channel exists. The shared practice may be happening somewhere else entirely.

Imagine a group of companies where different people maintain product catalogues. Their tasks are similar: receive material, distinguish variants, clarify uncertain names and prepare descriptions. They are not on one project team and do not share a list of assignments. They do share a question: what should they do when a supplier's material is not enough to represent a product reliably? That may be a reason to form a community of practice.

A community is useful when participants learn something relevant through working together on their own cases. Membership in a channel, a course or a presentation series does not by itself establish that relationship. Before announcing another knowledge-sharing programme, find out what people want to understand and do better together. The name of the group will not supply that purpose, even with a carefully chosen icon.

A shared domain also needs shared activity

Etienne and Beverly Wenger-Trayner's 2015 introduction describes three elements of a community of practice: a shared domain, relationships among people and a practice they develop. A job title or website alone does not create such a group. Participants need real contact and a shared body of experiences, ways of acting and approaches to recurring problems.

In our example, the shared domain is initially “product catalogues”. That is very broad. One participant publishes prices, another manages images and a third clarifies specifications with suppliers. To keep the conversation from becoming a series of unrelated presentations, the group can begin with a narrower question: how do we tell whether two documents concern the same variant? Each person brings a case where the comparison was not obvious.

The shared activity is then to reconstruct the reasoning. Which information matched? What raised a doubt? Who was asked, and what did the answer resolve? The group need not immediately establish one instruction for every company. A useful result may be a better question for the supplier and recognition of a situation where comparing the documents is not enough.

This differs from a company announcement about a new system. “We use this application from Monday” may be necessary information, but it does not itself require a community of practice. If most meetings transmit management decisions, participants become an audience for announcements. It is difficult at the same time to expect them to treat those meetings as a place to discuss uncertainty and unfinished attempts freely.

Knowledge architecture in a company (in Polish) has another purpose too. A repository helps people find material and understand its status. A community may help clarify a situation for which no material exists yet. The two can support each other. Filling a directory with files does not mean people have learned to handle difficult cases together.

A case worth bringing to others

Suppose one person receives two product descriptions with different names and similar photographs. Instead of showing the group only the corrected entry, she presents the point of uncertainty. She does not disclose material she is not allowed to share or data unnecessary to the question. She can prepare a suitably limited example showing the relationship between the documents. The aim is to understand the choice, not to put someone else's mistake on display.

The others do not have to know the right answer immediately. Someone may notice that trade names were compared instead of variant identifiers. Another may ask whether the photograph actually shows the item described. Someone else may recall a similar situation where a supplier used one set of material for several versions. Each contribution adds part of the picture, but no analogy replaces checking the current case.

Brown and Duguid's 1991 paper discusses, among other things, an ethnographic study of service technicians' work. It shows the importance of interpreting cases and exchanging experience beyond the formal job description. This is an analysis of a particular practice, not proof that opening a discussion channel will improve any company's results.

For the fictional catalogue group, a useful outcome may be deciding what question to send back to the supplier. After receiving an answer, the person who brought the case shows what was clarified and what remains unknown. That return matters: without it, the community collects interesting guesses but does not know which helped. Not every discussion has to end with a universal instruction.

Participation also requires the ability to ask for help without pretending to have a finished solution (in Polish). If every example becomes a public examination of its author, people may bring only matters long since resolved successfully. The group will see polished presentations rather than the moments when shared knowledge is actually needed. The person leading the discussion should keep questions connected to the task instead of looking for a winner.

Voluntary contributions take time too

An invitation to a community does not remove daily responsibilities. Someone must prepare a case, limit the material, return with the outcome and help new people. If the company wants to benefit from this work, it should know when it can happen. Expecting regular contributions while leaving the same list of urgent assignments is a real organisational choice, even if it looks like an innocent calendar invitation.

Not everyone needs to contribute in the same way. A beginner may mostly ask questions. Someone else brings difficult cases; another organises what came out of a discussion. Equal numbers of posts per person do not prove a group's value. More useful questions are whether people return to one another with problems and receive help that an announcements channel would not provide.

Aeneia conceptual photography

At the same time, voluntary contributions do not make jointly developed approaches automatically binding. Participants may find a new way to describe variants useful. A person responsible for the catalogue still has to check whether it fits the particular source and publication scope. The community does not acquire a mandate to change every company requirement by majority vote.

Notice whether the group is sustained by one person alone. If only that person brings cases and answers every question, the result may be valuable expert consultation, but not necessarily a shared practice among many people. That is not a criticism of consultation. The point is to name the arrangement honestly and check whether others have a reason and an opportunity to contribute experience of their own.

In our example, the company can give the team time for one focused conversation about a real problem rather than establish a year-long programme at once. Afterwards, participants can assess whether they learned something they will use soon. If the topic was too far from their work, narrow it. If the right person was missing, change who takes part. More invitations without that assessment only extend the calendar series.

Someone who does not know the group's history may join later. In our example, she hears “This is another case like the blue series” and does not know what the others mean. The shorthand works for existing members, but she cannot judge whether the analogy fits her problem. Access to a message archive may not help if she does not know which discussion to find or what it eventually confirmed.

The group can instead show a limited, understandable case: two documents, the point of contradiction and the answer that clarified it. The new participant can then identify the difference in her own case. Perhaps her identifier matches, while the photograph does not. Shared experience should not force every new difficulty into a familiar story. A useful question is which premises are the same here and which are missing.

This participation does not require the new person to give a finished presentation immediately. She can bring a fresh case and investigate it with others. For the group, it also tests their shared language: can they explain the reasoning to someone who missed the earlier conversations? If not, they need to add context before the advice reaches another team as a supposedly obvious rule.

Give material a status as it emerges from experience

A case discussion can produce different things: a confirmed explanation, a working suggestion and a question that remains unanswered. Preserve those distinctions. A statement from an experienced person should not become a rule for the whole company merely because it was copied into a knowledge base. Someone using the material needs to see the situation in which the advice arose and what was actually checked.

Suppose that after resolving the names, the group prepares an example comparing two documents. A good training example showing a solution preserves the question, the premises and the limits of the conclusion. The guide to training examples (in Polish) discusses how to prepare such material. If only a clean result remains, a reader may copy it into another case where the same premises do not apply. The most instructive part of the work will have disappeared during editing.

It also helps to separate one group's experience from other teams' conditions. Someone maintaining a manufacturer's catalogue may have access to data unavailable to a person working for a distributor. “Check the variant sheet” is incomplete advice for the latter if it does not explain how to recognise that the sheet is missing and whom to ask. A similar task does not mean the same resources are available.

When the group discusses a completed project, a retrospective that leads to a change in practice (in Polish) can help. The community can take one specific case from it and compare it with other people's experience. It need not repeat the entire project meeting. Its value appears when different teams recognise a shared problem and examine what can reasonably be carried from one experience to another.

When the shared subject is using AI

Return to the catalogues. A company starts using AI to prepare draft descriptions from supplied material. Participants can compare cases where an output mixed up variants, omitted uncertainty or sounded more certain than the source. Sharing such experiences helps them choose questions to check. It does not replace the person responsible for approving a description for publication.

Here the community can work with people responsible for rules and training the team to verify AI results (in Polish). Practitioners provide real examples of difficulties, while the training material shows what to check in a particular task. A new suggestion should be assessed before anyone presents it as a general rule for using the tool.

That starting point fits Aeneia Audit: one type of AI use, its sources, its output and responsibility for checking it. From there, the rules and materials the team needs can be organised. A conversation among practitioners provides the context of daily work that a demonstration of an application's ready-made features cannot replace.

Aeneia Audit: If practitioners bring similar difficulties with AI, select one real case to examine the sources, result and verification method, then prepare useful rules for the team. Explore the audit and organisation of AI use.

Before sending the next invitation, ask participants what problem they would like to revisit and what happened to the previous case. The answer may lead to another conversation, a specific piece of material or the end of the topic. If nobody sees a shared activity, the group needs another purpose or form. Keeping a channel active is not yet the same as working on a practice.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear