CB.5:4 - Solution

Start with the receiving result. Distinguish the work it needs, obtain a suitable contributor under feasible terms, support its performance, and close the return between the contributor and the recipient. Keep domain correctness, authority and the limits of available evidence attached to the actual work.

Working reminder: name the receiving result; agree a feasible contribution; prepare the work; obtain a usable return; explain acceptance or the remaining gap.

CB.5:4.1 - Turn a general request into a receiving use

Ask who will use the contribution, for what next action, and under which conditions. Replace “we need more content” with the question a reader cannot yet answer or the action they cannot perform. Replace “we need ideas” with the use difficulty and the kind of proposal the receiving team can consider.

Choose the result before recruiting contributors. For a case, establish the subject and relevant configuration, what has been tried, the uncertainty, permitted material and useful response window. For a shared resource, establish its intended users, applicable content and the person who can maintain it. For a recommendation, establish what the recipient needs to decide and what the recommender actually knows.

Agree how the recipient will recognise a useful contribution. A case owner may need a justified next step; a design team may need a testable use account; a service owner may need evidence that a permissible intervention restored the required function. The criteria come from the receiving work and its domain, not from the number of responses or the contributor’s popularity.

Distinguish accepted, usable and applied. A recipient can accept a technically sound explanation but be unable to act because access is missing. A product team can find a suggestion informative while declining its implementation. Preserve the actual outcome so that the contribution can be improved without claiming work that did not occur.

CB.5:4.2 - Obtain the contributor and the conditions

Find people whose competence, experience or access matches the needed contribution. Ask for a bounded piece of work, explain its recipient and criteria, and disclose the relevant interests of the organiser or sponsor. Confirm willingness, available effort, preparation and a useful return window.

Make the scope negotiable. A person can provide an observation without writing the whole guide, review one claim without maintaining the product, or answer a question without accepting a permanent service obligation. If the receiving promise requires more than anyone can commit, narrow it, obtain funded provision or use an accountable supplier.

Obtain the material, tools, access and permissions needed for the chosen work. OCE.6 supplies the fuller method when actual organisational assignments or enabling relations are current. Its central distinction matters here: selecting a capable person, agreeing a contribution and establishing permission are different achievements.

Provide preparation for the actual gap. A peer can help formulate a case or inspect an example. A qualified HCD contribution can develop missing capability. If the underlying professional method is unavailable, return that development or inquiry question to Method Engineering or Research Method Practice. More reminders cannot replace it.

Identify the receiving person before the contribution is made. Agree when and how they will inspect it and give a useful response. An open suggestion box without a receiving decision can invite effort the organisation is not prepared to use.

CB.5:4.3 - Choose the work and its acceptance conditions

The following branches illustrate different contributions. Select the branch that matches the receiving result and combine branches only with an explicit connection.

Answer a question or provide peer support. Prepare the question, connect it with a competent willing respondent and compare the response with the case’s conditions. Ask for the basis and applicability of the answer when these change its use. The case owner returns what became possible, what was tried or which condition still prevents action. Use the relevant service route when a response or escalation must be dependable.

Enable self-service. Give the user an applicable instruction, necessary access and a recognisable result or stopping point. Try the route under the user’s conditions and provide a route for exceptions. A public reference may serve many people who never join the discussion. OPS.6 supplies the action and return discipline when this is an operational case; the applicable domain method supplies the action itself. A confusing or obsolete instruction returns to its owner for correction.

Help someone enter useful work. A participant can recommend a possible colleague, introduce a newcomer or help them prepare. Obtain the person’s agreement to the relevant introduction and give the recipient a factual account of the contribution offered. The employer or activity owner judges suitability and agrees the work. For onboarding, name the task the newcomer must be able to perform and supply the corresponding material, help and learning where needed. A recommendation is not a hiring decision, and an introduction is not completed preparation.

Recommend an offer to a potential user. Connect a real receiving need with an accurately described offer. State the experience or evidence behind the recommendation, its limits and the recommender’s relationship to the provider. Let the recipient inspect the terms and decide whether to continue. CB.1 supplies the honest-offer discipline; the provider remains responsible for product claims. A community relationship supplies no obligation to promote a sponsor, and a purchase alone does not demonstrate that the recommendation served the person.

Co-design a result or product. Choose what contribution is wanted: a use account, requirement, concept, design alternative or tested part. Give contributors the relevant problem, constraints, available material and acceptance question. SYSE.2 helps connect the use situation to a candidate concept and compare changes on either side of the system boundary. The receiving product specialist must examine the contribution and return an adoption, revision, rejection or unresolved question with a reason. A popular proposal still needs the applicable engineering judgement.

Produce or improve material. Establish the reader’s intended action, the subject method and correctness basis, and the person who can review and maintain the result. Ask participants for useful cases, explanations, corrections or a bounded authored contribution. Inspect the result through a representative use before presenting it as a reusable answer. For a teaching publication, obtain the relevant HCD learning design and use Learning Product LPF for the publication; the subject expert, author, learning designer and provider can be different people. If a necessary contribution cannot be obtained, preserve the gap instead of treating submitted material as a complete learning product.

Maintain an object or a shared resource. Name what must remain usable and who can authorise the actual work. For technical maintenance, MNT.1 establishes the unit, configuration, required functioning and the question being decided. Obtain the applicable professional method and permissions before an intervention; return functioning evidence and the separate decision to resume use where required. For a knowledge resource, obtain a capable maintainer, correction criteria and a route for obsolete or disputed content.

When a contribution spans institutions, obtain the actual contribution and authority from each. A university, supplier or association may provide useful people, material or access; its category alone specifies none of those commitments.

CB.5:4.4 - Develop useful case work and comparison

Choose a construction that fits the question, available experience and time. The following adaptations from the Communities of Practice Guidebook retain different results.

Case clinic: obtain a reasoned continuation. Ask the case owner for a real challenge, a focused question and just enough permitted context. Begin with clarification; let contributors ask about conditions before offering solutions. Then draw out relevant experiences and compare proposed actions with the case. Keep observations, experience-based suggestions and qualified technical conclusions distinguishable. The owner explains what they will take away, what they will not use and what remains undecided. Arrange a later response when actual use can be observed.

For a complex case, the work may require substantial clarification and more time than a short round permits. Divide the question or obtain separate preparation when needed. With a large group, CB.4 can provide a speaking circle or smaller groups with a return. A facilitator protects the question and turn-taking; domain contributors supply technical judgement. If advice conflicts, recover the differing conditions or the missing evidence rather than choosing the most popular answer.

Design clinic: widen the possible next moves. Use this when time is short or participants’ contexts are too different for a deep case judgement. Give the owner a short opportunity to state the challenge. Follow with concise clarification, relevant experiences, suggestions and the owner’s account of what changed their thinking. Keep a record of possibilities useful to the owner. The result is a broader set of options, with further examination still needed; do not present the speed of the exchange as evidence that a solution has been selected or tested.

Story of practice: make experience available. Ask the teller to recover what happened, the conditions, actions, difficulty and outcome. Let listeners ask for details that change their interpretation and explain what may be relevant to their own situation. An interviewer can help expose a choice or failure that the teller treats as obvious. Keep a story’s context available when drawing a lesson. If someone needs a validated method or general causal explanation, obtain that further work; one compelling account does not provide it.

Project review: obtain an informed view of a larger body of work. Agree the question the project owner wants answered and give reviewers access and time to inspect the relevant work. Alternate examination with reflection so that claims can be challenged against the project, rather than against a short presentation alone. A rehearsal can help the owner prepare for an actual review. The project owner’s applicable acceptance and release decisions remain separate.

Demonstration or joint work: expose an action and its reasons. Choose a representative situation, let a competent practitioner perform or explain the difficult action, and give participants a chance to ask about a consequential choice. When they try the action, supply the relevant practice and feedback through HCD. Their experience can also expose a question for method description or development. Keep the observed action and the result it actually establishes recoverable.

These forms can be combined. A story can clarify a case, a demonstration can test an interpretation, and a project review can expose a smaller question. Explain the change of receiving result when the activity changes, so that participants know which contribution is now wanted.

CB.5:4.5 - Prepare an external contribution without losing the question

Invite an external expert or neighbouring practitioner when the group lacks a needed perspective or competence. Give the guest the actual question, relevant material, participant preparation and expected result. Check that the guest can address it and agrees to an interaction that lets participants clarify and examine the contribution.

A prepared presentation can be useful, but leave enough time for the community’s questions and their application. The guest may need to observe the work first, respond to selected cases, or join a small group after a general explanation. Choose the arrangement with the guest rather than presuming that a familiar lecture supplies it.

Connect preparation, shared work and continuation. Participants can submit questions in advance; the guest can identify missing context; afterwards, the recipient can return what was used or still needs clarification. Obtain agreement on retained material and attribution. A recording serves later use only when it contains the relevant question and can be accessed under the agreed conditions.

If the desired result is a continuing course, service or research project, obtain its provider and resource arrangement. The community can contribute domain expertise and cases, but a single guest visit does not supply the whole undertaking.

CB.5:4.6 - Return, accept, revise or stop

Give the recipient the contribution together with what determines its use: the question, applicable conditions, evidence or domain basis where needed, and unresolved limits. Use the existing discussion or work record when it can carry these facts.

Ask the recipient to return a meaningful disposition. Examples include: used as supplied; accepted for a stated later use; useful after a specified change; declined because a condition or requirement differs; or not yet assessable because a needed basis is missing. Explain the reason that can improve the contribution or prevent inappropriate reuse.

Agree further work rather than silently extending the original commitment. A small correction within the accepted task can proceed with the contributor’s available effort. A materially different request, repeated revisions or a new maintenance obligation needs a revised arrangement.

Close a failed contribution honestly. When no suitable helper is available, return the unanswered question and a possible source or service route. When the user cannot act, distinguish missing access from an unusable answer. When the product team will not inspect suggestions, stop inviting that kind of work until a receiving arrangement exists.

For an operational case, OPS.6 separates selection, performance and the resulting state. Use that distinction whenever a message or record update could be mistaken for a completed intervention. A technical answer, performed work and restored functioning have different evidence.

CB.5:4.7 - Make useful material reusable and support continuation

Retain a contribution when another receiving use warrants it and the relevant permissions allow it. Preserve the situation, method or explanation, applicability conditions and limits. Give later users a way to find it and report a changed condition or error.

Choose a capable owner for correction and maintenance. For professional method content, use the relevant Method Engineering contribution; for a resource containing existing qualified advice, use its established subject review and publication route. If no one can maintain a changing answer, limit its stated use and avoid making an indefinite currency promise.

Observe how the arrangement works for both recipients and contributors. Are useful questions reaching suitable people? Are answers used or returned with reasons? Does preparation and follow-up exceed the available effort? Repeated reliance on one generous contributor is a provision question even when the contribution is voluntary.

Change the specific failed connection: improve the request, recruit another qualified helper, make a reusable answer accessible, change a response promise or stop an unsupported activity. Return to CB.1 when a service, resource or another contribution better serves the purpose. Keep enough information for the next participant to continue without requiring everyone to repeat the whole exchange.