Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:25:10 UTC

OPS.17:4.2.1 - Choose how service work develops usable knowledge

Repeated requests can consume expert time even when useful answers already exist. They can also expose an answer whose conditions are unclear, a missing professional solution, or a costly workaround worth removing. Start with a representative receiving case and distinguish these possibilities before commissioning more articles, training or a new knowledge platform. The first useful result is a choice of what to reuse or change, with the professional contribution and support it needs.

Knowledge-Centered Success (KCS, formerly Knowledge-Centered Service) is a candidate when the service needs to develop shared working knowledge through its use. The Consortium for Service Innovation’s complete practices guide explains the professional practice: knowledge is reused and improved during service work, while analysis across uses changes content, workflow or the underlying service. An adequate manual, direct source or competent provider remains a serious alternative. Use it directly when it supplies the required result; a single unfamiliar case need not justify a continuing knowledge programme.

For a selected KCS use, obtain the particular operation from the following treatments and bring its result back to the operating choice. A practitioner familiar with the operation can reuse it; a performer new to it needs access to the explanation and any support required to perform it competently.

  • Connect the request to a usable answer. Use Structured Workflow Integration and Track Reuse to retain the requester’s circumstances, find and judge existing knowledge, and associate the interaction with the knowledge actually used and what is known about its outcome. Professional diagnosis or investigation supplies an absent answer. Return the supported resolution, or the precise unresolved question and the qualified contribution needed next. A maintained external source can remain the answer rather than being copied into another authority.
  • Make the reusable contribution discriminating and correctable. When material needs development, use selective creation to distinguish useful contextual capture from another article. The simple template and article-structure treatment explain how the question, environment and resolution support later discrimination, while requester-specific details stay in the interaction record under its access and retention rules. Use Article State for the separate confidence, audience and governance decisions. Reuse is Review connects actual application to correction by a capable contributor; opening or citing an article alone supplies no such judgement.
  • Choose the receiving improvement. Use Knowledge Optimization when recurring uses can change which content, access, workflow or product problem deserves action. Preserve materially different conditions behind similar requests. Return the supported discrepancy and affected uses to the responsible practice; a recurring symptom motivates investigation without establishing its cause.

These returns determine which further contribution to obtain. For a sound answer that is hard to recover or maintain, use the relevant Knowledge-Corpus Access Engineering (KCAE) method: KCAE.MEMORY retains permitted episodes and conditional connections; KCAE.CHANGE maintains editions and affected derived results; KCAE.EVAL examines the usefulness of the access arrangement. A missing domain answer needs its professional supplier. Use OPS.22 when service observations need interpretation or an authorized response. Return a proposed reusable operating-method change to OPS.16. CB.14 is useful when a community actually wants to develop and maintain a joint repertoire.

Include the work that makes the chosen arrangement sustainable. Diagnosis, content correction and analysis across cases need suitable competence, time, permission and a receiving decision maker. The full KCS guide develops content standards, proficiency and coaching, and continuing organizational support; check which of those conditions are already available and what must still be provided. Use Roles and Proficiency for the rights model and its competency conditions. Content Health Indicators and Process Alignment Review distinguish article-standard checks from observations of case handling. Coaching for Success and Structuring Coaching Sessions explain how to arrange the coach’s contribution, the practitioner’s work and follow-up. Obtain missing support, revise the service promise or retain the simpler adequate arrangement. Compare the burden on contributors and recipients as well as the sponsor’s expected saving. New material can also be warranted before failure, when a forthcoming change and its professional evidence create a useful receiving question.

An agent can perform any of these contributions within its actual qualified capability and granted scope. If automation removes the capable observation that previously corrected an answer, arrange an adequate replacement for that contribution. It may be an agent check, suitable independent assessment, receiving-outcome evidence or qualified human work, according to the claim at issue. For tool integration and interrupted self-service, use the guide’s Technology Integration to preserve the context needed by the next performer. The changed division must still supply the service result and the knowledge correction on which future use relies.