An experience becomes a reference when somebody can use it to understand, decide, or act. That can happen between two people, inside a team, in a community group, or further afield. The bearing can be an explanation, a practice passed on, a tool, or a document.
The goal is not to reach a final builder rank. Someone starting out can share a reviewed example of what they have just learned. An experienced person can make a line of reasoning, or its limits, more reachable. No volume of publications measures that contribution on its own.
A team prepares a sheet for handling an incomplete file. It describes a case, the checks, the limits, and who to contact. A new colleague tries it and flags an ambiguity. The team fixes the sheet and agrees who maintains it. That internal resource is already a reference, even if nobody wants to publish it.
Public content can let other people find and examine an experience. Its reach is not guaranteed. A conversation, mentoring, or private work can also leave lasting capabilities, even when the effect is harder to count. Visibility does not replace usefulness, and its absence does not prove nothing was passed on.
The cards in this capability suggest pinning down the recipient, the context, the observations, and the conditions of use. A measure can help when it is explained. A qualitative example or an annotated decision can be enough. You do not need to invent something new: an adaptation or a reachable explanation can complete existing resources, while acknowledging them.
Sharing takes choices and means. Who contributed and wants to be named? Which information can circulate? How much preparation, review and upkeep is available? A doubt about the right to share calls for clarification with the people concerned; removing names does not automatically settle the question.
If you are growing a team, prepare a frame that leaves room for internal material, for conversations, and for choosing not to be exposed. If you back builders, a review, feedback from use, or an introduction both sides accept can help. The cards on the terms of sharing and on chosen visibility set out what needs a particular mandate.
A sign of progress: a recipient can explain what they understood or reused, and the limits they still have to examine. Direct feedback can show that. When no feedback comes, you can note the uncertainty without inventing an impact or concluding that the work serves nothing.
A resource can age, be corrected, replaced or withdrawn. Preparing for that is part of passing something on, without obliging its author to stay available for ever.
The cards in this capability
- 10.01 Put your name on it
- 10.02 Write after you build, not instead
- 10.03 An opinion is not an artifact
- 10.04 A trace is not necessarily code
- 10.05 Answer the question in public
- 10.06 Publish where people search
- 10.07 What publishing really costs
- 10.08 Nobody has written down what you know how to do
- 10.09 Leaving is not a betrayal
- 10.10 ⇄ The absence of a rule is a ban
- 10.11 ⇄ Your team works under your name