OPS.17:5.6 - Repeated support changes the knowledge and then the service
Consider a constructed service helping project teams import records into a shared platform. A qualified specialist has established that, for platform version P4 with a particular permission setting, duplicated rows on screen are a display problem: the stored records remain unique, and the documented view refresh restores the display. The current manual calls this a stale view. Users search for duplicate imports and often miss it. A different P5 import format has produced a similar report, but its mechanism and remedy remain unresolved. The current routine sends requests to specialists and batches manual updates at month end; it leaves later responders repeating already completed distinctions.
The service lead compares four moves for the next month: retain the current manual and expert response; improve access to the known answer; use KCS to maintain answers through subsequent service work; or change the platform. Bulk article production would not distinguish the two configurations. Immediate platform replacement would assume a wider cause and benefit than the supplied evidence establishes.
For P4, the specialist first checks the requester’s environment against the supported conditions. The answer can remain in the maintained manual. A discoverable entry associates the user’s duplicate-row wording with that answer and its P4 permission condition. Its resolution states the applicable refresh and the expected result: one displayed row for each stored record. The service interaction retains which edition was used and whether that result occurred. The reusable entry need not include the team’s private project data. This small access correction is enough for a familiar matching case.
The P5 request changes the selection. Similar wording does not make the P4 answer applicable. Preserve the new environment and unresolved question, and obtain the appropriate platform investigation. The known P4 resolution stays usable. The service responders can apply the KCS workflow, and their case-handling allocation includes capturing relevant context and linking the answer used. The lead selects that workflow for continuing support so that developing answers and their conditions become available during service work, instead of waiting for the monthly manual revision. The full source techniques in :4.2.1 supply that work. The choice provides a way of handling the gap, not a newly established P5 remedy.
The service already has a small, allocated maintenance interval that can supply the P4 access correction. Proposed weekly analysis across cases needs additional qualified time, while current response commitments occupy the remaining specialist capacity. The lead keeps the useful local correction and obtains a separate contribution or changes the relevant commitment before promising recurring analysis. Expected future savings cannot supply that missing hour.
Suppose later observations show that matching P4 users obtain the right answer but still incur substantial effort repeating the workaround. The next comparison concerns removing that burden through a platform change, changing the service offer, or retaining the workaround at its actual cost. The product owner needs the affected conditions and receiving burden; the engineer must supply the causal explanation and proposed remedy. OPS.22 interprets the supported service result, and OPS.16 is used if the selected response changes a reusable operating method. Better article retrieval remains useful, but it no longer answers the whole improvement question.
Now change the performer. A corporate agent configuration is qualified to distinguish the supported P4 condition, use the current answer, perform the permitted refresh and check the resulting display. It can replace the corresponding human service performance. P5 remains outside that qualified use until a suitable answer and performer are available. The replacement also needs to preserve error detection: if the agent merely repeats the article while never noticing a failed result, the previous specialist’s corrective contribution has been lost. Obtain an adequate outcome check or other qualified assessment for that gap; human approval is needed only where the particular judgement or authority requires it. If a qualified agent obtains an answer without using an article, preserve the actual basis rather than inventing an article-use event.
After the change, assisted contacts fall from 40 to 12 per interval and the system records 30 agent interactions. The difference is 28 contacts; it does not establish 28 avoided issues or attribute the change to the agent. One issue may span several interactions, and a failed answer may never return as a ticket. The KCS self-service measurement treatment helps recover the relevant issue population, observed outcomes and unobserved part. Bring that bounded account to OPS.22 and compare the receiving effort and service mix as well as contact counts. KCAE.EVAL can examine the access contribution within that whole comparison.
A later policy change forbids the old refresh for one protected class of records. The responsible policy authority supplies the effective rule. The service revises the affected answer and uses KCAE.CHANGE to remove or mark stale dependent current advice. Historical correctness of the P4 diagnosis remains different from permission to act now. A recipient’s personal assistant must likewise obtain its own permitted access and action scope; the corporate agent’s grant does not travel with a copied answer.
When a person wants to learn the diagnosis, use HCD to arrange the needed learning. A claim that the person has acquired the capability needs evidence from their own performance. If independent practitioners instead want to establish a novel shared method, CB.14 can organize that joint undertaking and its professional contributors; the frequency of support questions cannot establish the new method. These changed purposes preserve the useful service-knowledge contribution while changing what else must be obtained.