The reflex
You would like to pass on a practice, but the examples of libraries or public code feel a long way from your craft or your experience.
The builder’s reflex
Start from the person to help and from what they have to understand or do. Choose a form that suits that need, technical or not.
Why
A trace can be a sheet, an explanation, an annotated decision, a diagram, a recorded demonstration made with agreement, or an example of work. It can serve inside a team, a community group, or beyond. A private repository can be useful to its recipients, just as a public page can answer no real need at all.
Someone in operations prepares a sheet for welcoming a visiting speaker. It explains the information to check, a case that calls for help, and who to alert. A peer tries it, then flags an ambiguity. The sheet becomes more useful without containing any code, original number, or new discovery.
Crafts have their own ways of passing things on. In finance, a worked calculation with its assumptions; in support, an annotated case; in design, a flow with its reasons; in volunteer work, a preparation list. Qualitative observations count too. The value depends on the help given and on getting the context right, not on an obligation to quantify.
You do not have to be the first person to explain a method. An adaptation, a translation, or a reachable example can help a new recipient, while acknowledging what comes from elsewhere. Someone starting out can keep what helped them and have their explanations checked. An experienced person can spell out the exceptions and the limits, rather than hunting for forced originality.
Try this
Choose a question someone actually meets. Offer a small resource that answers it, with an example and what falls outside its scope.
Use authorised information, or a constructed case clearly announced as one. Do not copy a real file just to make the material concrete. Agree the preparation time and the place the person will be able to find it.
Have the material tried or reviewed. Note what was understood, what is missing, and who can fix it if the practice changes. You can keep an internal or accompanied form if that answers the need better.
From where you sit
- Operations: explain a flow with its watch points and its handovers.
- Finance: prepare an example whose assumptions are understandable.
- Support: keep a useful case with its context and the limits on sharing it.
- Design: make a choice legible without requiring a number for every observation.
To discuss
Which form would help the next recipient of what we know, even with no code and no original measure?