CB.14 - Develop and Maintain a Shared Repertoire of Practice

Type: Community-building method pattern Status: Stable

CB.14:1 - Problem frame

Use this pattern when practitioners repeatedly encounter a difficulty that their ordinary exchanges do not resolve, useful ways of working remain scattered among participants, or contrasting experience suggests a worthwhile improvement. Several repairers keep reconstructing the same diagnostic explanation. Volunteer organisers have different ways to welcome people with limited time. A profession needs a workable response to changed tools or conditions.

The governed object is the community’s joint undertaking to obtain, qualify and maintain a useful repertoire: ways of working and the explanations, cases and support needed to use them. Community Building organises that undertaking and its return to practitioners. Method Engineering supplies the construction and qualification of a reusable method; Research Method Practice supplies inquiry into an unresolved knowledge question when research is needed.

First useful result: a recurring problem has a specific next contribution, a willing and equipped provider, and an intended receiving use. That contribution may be a sufficient existing answer, a bounded comparison, a draft and trial, or a project whose returned result can be judged.

What changes in practice: people can obtain and improve reusable help instead of repeatedly discussing the same difficulty. Differences and failed attempts shape the result; later users can find its applicable conditions and request a correction.

Use ordinary help through CB.5 when a known answer resolves one person’s case. Use HCD when the method is sufficiently known and the current need is for someone to learn it. A missing permission or unavailable resource may require its owner rather than development of a new method. Continue here when there is useful joint work on the repertoire itself.

CB.14:2 - Problem

Shared experience is unevenly recoverable. A confident account may conceal the conditions that made it work. A useful local adaptation may be discarded because it differs from the usual practice, or copied into places where its support is absent. Repeated advice can leave the common difficulty intact.

A community can also agree to write a guide without providing anyone with time to write, resolve disagreements or try it. Conversely, a project team may complete a document that practitioners cannot use and report the delivery as successful practice development.

The task is to connect the practical question, people with relevant experience, qualified development work and the receiving practice. Agreement can settle what the community wants to support; the claims about a method still need evidence appropriate to their use.

CB.14:3 - Forces

CB.14:4 - Solution

Begin with the difficulty in practice. Recover the available answer and contrasting cases, choose the joint work that can improve it, obtain the necessary development and support, then return a qualified result to an actual use. Continue maintaining it only while that contribution remains wanted and supportable.

CB.14:4.1 - Turn repeated difficulty into a bounded development question

Ask practitioners to show the situation in which their present approach is insufficient. Recover what they were trying to achieve, what they did, the result, the difficulty and the conditions that may matter. Include a successful contrast or a failed attempt when it can distinguish an explanation. Obtain permission for sharing the material at the level the joint work needs.

State the question as a change someone could use. “Help a receiving repairer recognise which case needs specialist investigation” is more useful than “improve knowledge sharing”. Identify who needs that result and what they would do differently. A request from an organiser still needs comparison with the practitioners’ work.

First look for a sufficient existing answer. Ask the person with relevant experience, recover the applicable guidance and compare its conditions with the case. ME.2 and ME.4 help recover the repertoire and its source meanings when the needed material is scattered or unclear. If an existing answer suffices, return it through CB.5 and stop the development proposal.

Separate the remaining difficulty. The instruction may be incomplete; the method may fail under a changed condition; a person may need practice; or an organisational condition may prevent competent work. These can coexist, but their recipients differ. Return a learning need to HCD, an assignment or support problem to its owner through OCE, and a reusable method question to ME.

If an explanation or effect remains unknown, use RMP.1 with the exact question and current source answer. It first tests whether existing material is sufficient. Research follows only when the unresolved question, non-routine choice, inspectable criticism and communicable result conditions hold. An unfamiliar question or an intended data collection exercise alone does not establish that need.

CB.14:4.2 - Use differences to find a useful exchange

When participants want to learn from contrasting practice, agree which dimensions matter to their work. Select several that can reveal distinct strengths or limitations, such as recoverability of a case account, effort spent obtaining missing information and usefulness of the returned explanation. Explain what each observation means and use comparable cases where possible.

Invite participants to describe their own practice against those dimensions, with examples and relevant conditions. Keep unknown observations visible. A large gap is a reason to investigate what differs; it may arise from case mix, tools, access, experience or the way the observation was made.

Discuss a contrast with the practitioners who produced it. Ask how the apparent strength was achieved, which conditions it required, what it cost and where it failed. Look for reciprocal contributions: one group may have an effective intake conversation while another makes its later reasoning easier to recover.

Choose a specific exchange from that comparison. Name what one participant will show, what the other will try, and what result they will bring back. CB.15 supplies a connection with another practice when the needed experience is outside the current group. A learning programme for a particular person then uses HCD as needed.

Use a stable scale only when its meanings and progression fit a sufficiently stable practice. For a changing practice, describe the differences and test promising alternatives. Preserve dimensions separately unless a justified decision rule needs to combine them. The purpose here is to find useful work and partners; an overall league table would answer a different question and can make candid comparison harder.

CB.14:4.3 - Choose work that fits the size of the contribution

Select the smallest undertaking that can obtain the wanted result.

Writing can be shared, or one person can prepare drafts from practitioners’ accounts. Choose from the available time and skills. A commissioned writer can make progress while practitioners retain responsibility for checking whether the account describes their work and answers their question.

For a project, establish its purpose, scope, participants, resource provision, intermediate returns and completion condition through the community’s actual decision arrangement in CB.13. Include the people who will judge and use the result. A group may propose the work from below; the needed mandate and commitments still have to be obtained.

Obtain the time and access from their real owners. Use OCE.6 for assignments and enabling conditions, OCE.11 when this work overlaps with continuing commitments, and OPS.5 when a provider must decide whether to admit the work. An interested employee cannot commit an employer’s time merely by volunteering in the community.

Agree useful intermediate contact. A draft, unresolved case or trial observation should reach practitioners early enough to alter development. Choose contact frequency from that purpose and the project’s uncertainty. Regular reports of activity add little if the community cannot influence the result or obtain missing inputs.

CB.14:4.4 - Obtain a usable method contribution

Bring the cases, sources and disagreements to the people doing the method work. Preserve which claims are observations, participant interpretations, proposed explanations or established guidance. Recover the contribution and conditions of each serious option through ME.5 before presenting it as suitable for a new use.

For a guide, work through the intended user’s action: what makes the situation recognisable, what input is needed, what the person does with it, what result they inspect and when they continue or stop. ME.8 supplies that construction and a trial of the description. Invite practitioners to identify a missing operation or a place where the author has relied on private knowledge.

Keep disagreements attached to the claim they change. One participant may object to an instruction because it needs access unavailable at their site. Another may dispute the proposed explanation despite agreeing that the local workaround is useful. Obtain the missing condition, retain separate variants, narrow a claim or request the relevant investigation. A majority preference cannot resolve an empirical uncertainty.

When no available method supplies the needed result, give a capable method developer the gap, relevant cases, required result and conditions. Obtain a proposal explaining the actions, inputs, dependencies, alternatives and stopping conditions. ME.6 compares arrangements whose combined conditions matter; ME.7 develops the proposed whole while preserving what is established and what remains a candidate. Practitioners supply the work that tests those choices, and ME.8 makes the resulting explanation usable.

Obtain the qualification needed for the proposed use from ME and the relevant professional practice. A candidate can remain useful for further development while an unresolved condition prevents ordinary reliance. The community needs the developer’s result and limits before deciding whether to adopt it.

If the proposed improvement requires a change outside practitioners’ control, state the particular change and its owner. CB.16 can obtain and carry a collective request; OCE can develop a change to an organisation. The community’s guide should state the resulting condition that users actually have, including a still-unmet one.

CB.14:4.5 - Try the contribution in the uses that matter

Choose a first use that can answer a live question about the contribution. It may test whether a reader can recover the instruction, whether the approach fits the case, or whether its benefit justifies the burden. These are different questions; one successful reading does not answer all three.

Use ME.11 to arrange and observe actual trials when method evidence is needed. Select relevant conditions and, where it can change the decision, a contrasting situation that could defeat the claim. Obtain capable participants, permitted material, necessary support and the applicable stop before relying on the trial.

Observe the work as well as the verdict. Record what was tried, the result, effort, assistance, departures and unresolved difficulty. An expert’s intervention may reveal missing instruction or a needed capability condition. A participant’s approval may explain their preference while leaving effectiveness uncertain.

Return observations to the needed ME judgement: ME.12 checks coherence, ME.13 judges fit or transfer, and ME.14 compares practical worth against current alternatives. For causal explanations, keep the RMP question and evidence requirements in view. The community can coordinate these returns without turning every exchange into a research project.

Revise the affected explanation or conditions and try the changed use when its earlier result no longer applies. Preserve valid observations from unchanged uses. If the contribution remains unusable, return that result and the exact missing work; do not require the receiving practitioners to adopt it to complete the project.

CB.14:4.6 - Return the result to the repertoire and to practice

Have the intended recipients inspect the result against the agreed question. Return the useful guidance or product, its supported situations, evidence limits, remaining work and the means of obtaining help or reporting a problem. A project closes with an intelligible receiving result, including a justified stop when the proposed improvement failed.

Choose how later users will find it. Put a recurring answer beside the question people actually ask, link the fuller explanation and preserve its sources. Demonstrate the first use when explanation alone is insufficient. Keep access possible for someone who did not attend the development meetings.

Agree who can correct the material and what maintenance they can sustain. ME.15 supplies the distinction between a changed method, a changed description, a local departure and a support change. Preserve the relevant applicability and evidence instead of treating every new file edition as a newly validated method.

For adoption, obtain the receiving practice’s decision and conditions. Learning a new way may require HCD; a changed assignment, tool or permission needs its owner. The returned repertoire offers a qualified option. Actual adoption and successful use remain observable later results.

The same resource can serve independent carriers who never join the community. Provide a usable explanation and conditions through an accessible publication or provider, and a feasible correction route where one can be maintained. Their use need not include a meeting, chat or public account of participation.

CB.14:4.7 - Maintain the contribution from later use

Invite reports that can change the advice: an unlike case, missing input, successful adaptation, failed result or excessive burden. Ask for enough context to decide which claim is affected. Credit useful corrections through CB.6 without rewarding only favourable outcomes.

Revisit the affected entry when evidence, tools, practice conditions or available support change. Preserve an older variant if another use still needs it. Retire or qualify misleading guidance and inform the people known to rely on the affected claim.

If no one can maintain a resource that requires continued support, reduce its promise, obtain a successor or withdraw that use through CB.11. A small resource with a clear limit may remain useful; an unsupported promise of ongoing advice will not.

CB.14:5 - Archetypal Grounding

CB.14:5.1 - From repeated case repair to a usable shared guide

In a constructed network of repair workshops, technicians repeatedly ask which information should accompany a request for a second opinion. CB.5 resolves several cases, but the same missing context recurs. The members select a bounded question: help a competent recipient decide what to inspect next without repeatedly requesting basic information.

They recover existing instructions and compare permitted, anonymised examples. One workshop obtains clear accounts of the symptom; another supplies a concise record of what has already been tried. Faster replies at the second workshop also reflect its easier case mix. The group treats that difference as a question, not proof that its approach is superior.

None of the existing instructions explains how to request help when the original configuration is partly unknown. Two practitioners, a method developer and a writer accept a four-week project to supply that procedure and its usable explanation. Their employers provide the agreed time; the community supplies an editor and intended trial recipients. The completion condition is a procedure that lets a recipient identify a useful next inquiry or state the information that prevents advice.

With the practitioners, the developer compares two arrangements: have a specialist reconstruct every configuration before a request, or let a competent recipient first inspect the known account and decide which missing fact is needed. The first is feasible through a paid service but would consume specialist effort even when the unknown detail does not affect the question. They select the second for a bounded trial, accepting that some cases will need an additional exchange. Using ME.7/8, the developer prepares the proposed procedure and explanation: state the question, distinguish known from unknown configuration, report prior actions, and obtain the recipient’s next inquiry or stop.

The first reading exposes wording that could lead the sender to guess an absent configuration; the team corrects it before the trial. In the complete-information case, the recipient chooses a next inquiry directly. In the incomplete case, the recipient identifies the missing detail, the sender obtains it, and the recipient can then continue. A third case lacks retrievable information and receives an explicit stop. The developer and receiving practitioners check these results against the procedure’s stated conditions and return its bounded fit, the additional-exchange burden and the retained limit.

The community accepts the developed procedure and guide for those communication uses, with the trial observations and limitation. It has not established a better diagnostic method or a general reduction in repair time. An editor maintains the guide; receiving workshops decide how to introduce it. A workshop outside the network can use the published instruction without joining its meetings.

CB.14:5.2 - Reciprocal comparison without a single winner

Volunteer garden groups compare welcoming a new helper and handing over an unfinished task. One group provides a useful first explanation but loses task context when the host changes. Another keeps that context well but expects newcomers to infer where help is needed.

They agree two dimensions with observable examples, inspect a recent arrival and handover in each group, and exchange the relevant practices. The first group tries a brief end-of-session handover; the second asks a newcomer to recover the first task from its invitation and welcome.

At the first garden, the departing host leaves a short account of the bed still to weed, the unlabelled seedlings to leave alone and the location of the tools. At the next session, a replacement continues the named bed without contacting the absent host and stops at the uncertain seedlings. Preparing and checking the account takes five minutes at the end of the session. The group keeps that effort for work that will pass to another host; the uncertain seedlings still need an experienced gardener’s decision.

At the second garden, the newcomer initially cannot identify a first task from the general invitation. The host adds the meeting place, the person to meet and a starter task, then demonstrates potting one tray. The newcomer finds the work and completes the next tray with help available. Preparing the materials and giving a ten-minute welcome are now explicit host work. The group arranges a willing host for the next arrival and retains supervision for tasks that need plant judgement; the clearer invitation alone would not supply that support.

Each group returns the changed practice, observed use and burden to its counterpart. One keeps a handover for unfinished work; the other provides a prepared first task and host. They remain independent and can adapt or stop either arrangement. If the accounts concern different work, they first revise the comparison rather than treating the apparent gap as a competence deficit.

CB.14:5.3 - A method project cannot promise an unknown cause

A group observes repeated equipment failures and wants to publish a preventive rule. The available cases do not distinguish a maintenance effect from differences in equipment and use. A qualified existing source can answer one configuration’s question, so that answer is returned immediately.

The wider causal question remains. RMP.1 is used to state who needs the answer, the competing explanation and the evidence that could change the rule. If a research contribution is justified and can be provided, the community arranges that work and receives its result. If the needed records cannot be obtained, the guide retains the uncertainty and omits the unsupported preventive claim. Useful case-sharing continues within that limit.

CB.14:5.4 - Known practice and absent provision

A volunteer already has a usable, appropriate instruction but cannot access the tool it requires. The organiser obtains the access decision from the owner or helps choose a feasible alternative. No new guide or practice-development team is needed. If the tool is available and the difficulty is learning to use it, the next contribution is HCD support.

CB.14:6 - Bias-Annotation

Frequent speakers, well-resourced sites and successful cases are easier to collect than quiet corrections, failed attempts or work under scarce provision. Invite relevant contrasts and let contributors restrict sensitive material. Explain how comparisons will be used before requesting them; a learning exchange coupled to undisclosed personnel ranking will distort both trust and evidence.

CB.14:7 - Conformance Checklist

For reliance on the joint development result, establish:

• The recurring difficulty and receiving use are specific enough to select a contribution.
• Existing answers have been considered; learning, support, method and research questions have appropriate recipients.
• Comparisons retain consequential conditions and separate dimensions; a difference is investigated before becoming a superiority claim.
• Sustained work has willing participants, effective time and access, intermediate returns and a completion condition.
• The method contribution has the description, qualification and evidence needed for its intended use.
• The receiving practitioners obtain a usable result with limits and an available correction or maintenance arrangement.
• Changed conditions can reopen the affected advice, and independent use does not silently require community membership.

These questions justify reliance on the result. A few recurring difficulties are sufficient to recognise the opportunity and begin the bounded inquiry.

CB.14:8 - Common Anti-Patterns and How to Avoid Them

CB.14:9 - Consequences

The community gains a way to turn distributed experience into resources people can use and improve. A temporary project can obtain sustained work without making all participation project work. Differences remain visible enough to support adaptation and reciprocal help.

The method consumes time for recovery, disagreement, testing and maintenance. That effort is justified by the recurring use it serves. A sufficient existing answer or a small support repair can be the better result.

CB.14:10 - Rationale

Repeated practical trouble is a useful entry because it links development to a receiving task. Comparing contexts then helps distinguish a missing explanation, a transferable contribution and a condition that belongs to another owner. This avoids asking one document to solve every difficulty.

Community judgement and method evidence have different jobs. Participants can establish priorities and sponsor a contribution. Qualified development and observation establish what users may reasonably expect from the resulting way of working. Connecting those returns preserves both practitioner influence and warranted claims.

CB.14:11 - SoTA-Echoing

The practice question is how a community can improve a reusable repertoire without losing its practical context or claiming more than its evidence supports. The selected line combines practitioner-led documentation and reciprocal comparison with explicit development, trial and maintenance contributions. Informal help remains the lower-burden alternative when it already resolves the use.

The Guidebook contribution above is an analytical adaptation with attribution to its authors, under its CC BY-NC 4.0 licence. The source text supplies the practical forms; this pattern adds the constructed cases and supplier connections.

Reopen this selection when the recurring use changes, new evidence defeats a method claim, comparisons cannot retain relevant conditions, or the work and maintenance burden exceed the value people obtain.

CB.14:12 - Relations

• CB.5 supplies immediate peer help and cases that may expose a recurring gap; CB.7 prepares organisers who support the development work.
• CB.13 supplies its collective mandate. CB.15 connects relevant practices; CB.16 carries a needed collective request to an external decision.
• ME.2 and ME.4 recover source contributions; ME.5 qualifies each contribution for its use.
• ME.6 compares arrangements; ME.7 develops the proposed method whole; ME.8 makes its account usable.
• ME.11 supplies trials. ME.12, ME.13 and ME.14 supply coherence, fit or transfer, and practical-worth judgements respectively; ME.15 maintains the repertoire.
• RMP.1 distinguishes a sufficient answer from a research contribution and returns the remaining question.
• OCE.11 supplies workable overlap with continuing commitments; OPS.5 supplies admission when an operating provider must accept the work.
• HCD supplies the particular learning contribution needed to use a known method; CB.10/11 connects observed value with continuation, transfer or ending.

CB.14:End