C.42 - Reduce Avoidable Work While Preserving the Needed Result

Type: Method pattern Status: Stable Normativity: Normative unless explicitly marked informative.

C.42:1 - Problem frame

Use this when obtaining a needed result consumes work or time that might be avoided, but a local cut, faster operation or new tool could lose something the whole undertaking needs. A team repeatedly rebuilds reports after source changes. A service spends more time waiting for decisions than processing requests. A learner can obtain an answer instantly but still needs to acquire the ability to produce and challenge it.

The working reader is a practitioner responsible for improving a way of obtaining a result, with access to the people and knowledge needed to judge that result. The subject is the change to the whole way of obtaining it: what can cease, what must remain, what changes the troublesome condition, and how the change reaches subsequent work.

First useful move. Take one costly occurrence or proposed saving. Follow it to the result and receiving use it serves. Distinguish a contribution that is no longer needed from a needed contribution obtained with avoidable effort. This can already justify retaining an activity, removing an unnecessary duplicate, or identifying the particular condition a change must address.

Practical gain. The method helps the reader construct a worthwhile reduction instead of accelerating unwanted output, moving the burden to somebody else, or removing a condition of later success. Its result can also be a warranted decision to keep the present way.

Ordinary non-use. When an adequate known correction or domain Method already supplies the whole answer at acceptable burden, use it directly. If the only question is whether one proposed requirement contributes anything, A.11.OP supplies that test. If the main problem is a missing way to obtain the needed result, C.39 develops that construction. Return here when the live question is which avoidable work to remove and how to make that reduction hold in the receiving work.

An immediate protective action follows the applicable safety and authority rules. A broad improvement inquiry is not a prerequisite for protection whose grounds are already sufficient.

C.42:2 - Problem

A proposed saving can name a change at one place: fewer fields, fewer checks, fewer people involved, a quicker response or less time at a machine. The receiving result can depend on something outside that view. Removing a comparison can create rework; shortening a local queue can enlarge another; outsourcing can reduce the requester’s work while increasing verification and support.

The reverse mistake is to preserve every familiar action because it might have value. An obsolete output continues, a recurring error is corrected forever, and a capable person keeps performing an operation that could be removed or supplied more simply. Merely listing possible losses does not identify a change worth making.

The needed answer joins diagnosis and construction. It explains which work is avoidable under the actual purpose and conditions, how a proposed intervention changes those conditions, what the complete alternative costs and preserves, and what subsequent performance establishes.

C.42:3 - Forces

C.42:4 - Solution

Use a result-preserving comparison of whole obtaining ways. Recover what the work is for, locate a consequential avoidable demand, construct changes that address it, and compare those changes with continuing the present way. Introduce the selected change under adequate conditions and judge what happens in later work. Retain the present way or stop the improvement effort when a proposed reduction is not worthwhile.

A recall cue is:

Keep the needed result; remove unneeded work; prevent avoidable rework; distinguish waiting from processing; change a cause worth changing; carry the change into the next performance.

This is an order of explanation, not six compulsory gates. Enter at the question whose answer is missing. A new technology can remove rework, waiting and processing together. An independently supported change can proceed while another cause remains unknown. The dependency is between the grounds and the decision that uses them, not between positions in the mnemonic.

C.42:4.1 - Establish what the lighter way must still obtain

Name the result in its receiving use: who or what will use it, for which action or judgement, under which conditions and over what relevant horizon. Include a later use when the proposed saving can affect it. A result can be usable equipment, a decision, knowledge, an explanation, a capability or a maintained condition. These are not interchangeable successes.

Recover the conditions the recipient relies on. For a dataset, values alone may be insufficient without units and source identity. For a maintained service, ordinary output may be insufficient without recovery from a foreseeable failure. For learning, a correct answer from a helper may be insufficient when future independent performance is the purpose. Obtain the professional judgement that establishes those conditions; cost reduction does not establish them.

Follow a proposed deletion through its actual uses. Ask what would become unavailable, unreliable or more burdensome if this contribution ceased. Reuse a supplied contribution where it remains sufficient. When a local action belongs to several larger undertakings, B.1.5.EW helps recover those encompassing uses; B.1.5.RS evaluates a replacement against what each affected whole relies on. Follow indirect uses only while they can change the decision. Unknown use prevents an unrestricted deletion, not every bounded change.

Separate three conclusions:

• The result or contribution is no longer needed: ending its production may be the useful change.
• The contribution is needed, but this particular action does not supply anything further: remove or replace the redundant action while preserving the contribution.
• The contribution is needed and this action currently supplies it: construct another adequate way before withdrawing it.

A.11.OP supplies the contribution test for one proposed mandatory requirement. A positive contribution does not establish that its burden is worthwhile; C.11.DUA helps resolve that further question. An existing obligation remains binding until changed by its competent authority or agreement. A practitioner may propose its removal without being entitled to stop complying.

C.42:4.2 - Recover where the effort and elapsed time arise

Use a recent representative occurrence, an already available account, or another source sufficient for the decision. Follow the work from its initiating need to the recipient’s usable result. Recover consequential actions, handoffs, corrections and support. Include unsuccessful or exceptional occurrences when excluding them would make the proposed change look better than its actual use.

Distinguish active work from elapsed time. A request can spend two hours in processing and three days awaiting an input or decision. Do not add those days to labour hours or treat elapsed-time reduction as a reduction in labour without a further argument. Also distinguish resource occupancy from attention: a device can remain occupied while its operator does other work.

Locate the condition that makes an occurrence wait. It might lack usable input, permission, a decision, an available resource or the result of another operation. Trace a consequential dependency until there is a condition someone can change or a justified limit. If the condition is shared, examine the combined demands: a proposed earlier slot is not available merely because each request separately fits it.

Collect only the detail needed to distinguish the live changes. An existing timestamp and a conversation with the responsible participant may settle the question. If measurement or inquiry would itself be substantial work, C.11.DUA compares its attainable decision contribution with its whole burden.

C.42:4.3 - Diagnose the avoidable demand without calling every difficulty waste

Use the distinction that changes the proposed intervention. The following cases are common entries, not an exhaustive partition:

Treat configuration-related rework concretely. If an accepted instruction requires one edition while the performer uses another, recover which edition was required, how the performer obtained the used one, and where the mismatch could have been prevented. “Be more careful” gives no new obtaining condition. An authoritative source, usable retrieval, recognition of the required edition and a proportionate check can form a preventive change. Its added effort belongs in the comparison.

A failed hypothesis is not automatically failed work. If the intended research result was a distinction between explanations, a well-grounded negative answer can supply it. Likewise, repeated practice can produce a capability even when it produces many similar outputs. Recover the intended result and the actual contribution before classifying that effort as avoidable. Repeating an invalid measurement may be wasteful; learning why it was invalid may supply valuable knowledge.

For waiting, distinguish an unavailable prerequisite from an ordering problem among already feasible actions. Making an earlier decision, preparing an input in advance, changing batching or allocating an available resource can shorten the path. Each candidate still needs its receiving conditions. Starting more items can increase contention; moving a compulsory decision to the end can create extensive unusable work. A shorter first completion and greater sustained throughput are different improvements.

For processing, construct a different obtaining operation rather than merely naming a tool. Explain what the tool or performer receives, what it does, how the recipient obtains an adequate result and what happens outside its supported cases. Reuse, delegation and automation are possible means. None wins by its category alone.

C.42:4.4 - Construct an intervention through the condition it changes

Work backwards from the desired difference: what would have to be different for this effort to cease or decrease without losing the required contribution? Then work forwards from a feasible action: what changes, how does that affect the operation or dependency, and why does the needed result remain obtainable? Reconcile the two explanations.

For example, repeated copying between incompatible records may cause mismatches. Removing one copy, using a common interpreted source, checking correspondence, or redesigning the receiving operation are different interventions. Compare how each would preserve the required contribution and what support it would need. If the proposed action merely moves the copying to the recipient, it has transferred work rather than removed it.

Where a causal claim matters, use C.28.CM to state the intervention and outcome, develop the relevant causal explanation, challenge plausible rivals and preserve its limits. Several causes can coexist or interact. A useful intervention can affect several at once; a single root-cause label is not a required result.

Keep causal explanation and protection distinct. Suppose a wrong edition could arise either from a stale local copy or from an incorrect retrieval index. A supported comparison with the authoritative edition may protect the next use under both explanations. Use that protection when its conditions and burden warrant it. Decide separately whether distinguishing the causes would change a worthwhile preventive action. The protection’s success alone would not prove which explanation was true.

Construct a complete candidate only as far as the decision requires. Include an unchanged adequate way when it remains a live option, a direct small correction when available, and removal or replacement when those could win. C.39 develops a missing operation or join; C.38 constructs comparable whole ways when the proposed alternatives are still disconnected ingredients. An existing adequate alternative needs no new construction.

A changed purpose requires a new comparison basis. Ending an unwanted report and producing the same report faster do not obtain the same result. First establish the remaining needed use and the authority to change the commitment; then compare ways that serve that use. Do not claim preservation by quietly weakening the result.

C.42:4.5 - Compare complete alternatives over the relevant horizon

Carry each live candidate through construction, transition and subsequent use. Include what makes it obtainable: competent performance, data, access, equipment, permissions and support. Explain how exceptions are detected and handled, how the new means are maintained, and what happens if they are unavailable. Use existing adequate arrangements rather than inventing a new process for each concern.

Compare the whole burdens that can change the choice. They can include preparation and integration, learning and verification, ordinary execution, correction, support, maintenance, recovery and withdrawal. Determine who bears each burden and when. Separate a transfer accepted by its bearer from an unprovided condition. A recipient’s capacity limit can make a locally cheap alternative infeasible.

Use compatible quantities where a calculation is useful. For a fixed number of repeated uses, a simple account can compare initial effort plus recurring effort, with separately stated exceptions and uncertainty. Do not add labour time, elapsed delay, money, failure severity and future capability into an unexplained total. C.11.CRC develops a comparison when several contributions and shared constraints make those interactions consequential.

Compare the joint intervention, not the sum of imagined independent gains. If a common source both removes copying and prevents the resulting correction, distinguish the effort categories so the same minutes are not saved twice. Include remaining failures; complete elimination is a claim needing grounds, not a consequence of installing the change.

Check the horizon and the cost of reversal. An expensive preparation may be justified by many future uses and unjustified by a single remaining occurrence. A simpler manual way can win when volume is low, conditions change rapidly or exception handling dominates. When the demand or horizon is uncertain, show which plausible change would reverse the choice. Obtain more information only when it can change a worthwhile decision.

At a later decision, compare what each feasible continuation would still require from the current situation. Already incurred effort is not charged again and does not by itself justify continuing. It remains in any account of the undertaking’s total effect. Include new costs of withdrawal, restoration and lost capability; an available tool and one still needing construction are different starting conditions.

Preserve required margins and later ability. Unused capacity can support recovery or demand variation. Human practice can preserve a needed capability. Deleting either may reduce present activity while increasing future vulnerability. Establish the needed reserve or capability from its own use; do not preserve every idle resource or repetition merely by naming possible future value.

When one candidate preserves the same needed conditions and is no more burdensome on any relevant coordinate, with at least one strict reduction, it is preferable for this comparison. When gains conflict, make the actual trade-off explicit, such as accepting more setup effort for earlier availability, or retain alternatives until the person responsible for that choice can settle it. A binding safeguard is not converted into an optional cost by this comparison.

Choose a supported change, a bounded trial, a narrower use, continued operation, or no further improvement work. A new safeguard can be part of the lighter whole. Worth is not equivalent to the fewest operations.

C.42:4.6 - Introduce the change without substituting a document for practice

Make the selected change usable where the next affected work occurs. Identify the actual performers and support providers; obtain the necessary permission or agreement, access and available resources. Resolve simultaneous demands rather than assigning the same scarce support twice. If the work remains beyond current capability, obtain an adequate performer or develop the missing capability. If capability is already sufficient, an additional course is not required.

Use A.3.1.MI to distinguish the proposed way, introduction strategy, preparation, actual introduction and later work. Keep an adequate existing instruction where it suffices. Where an error recurs, change the conditions that allow it at the point of use: withdrawing an obsolete copy, supplying the correct source, making an exception route usable or providing the missing decision can matter more than another announcement.

Select a trial when its attainable result can alter adoption or scope. Choose cases that expose the disputed condition, including consequential exceptions, and preserve the necessary result during the attempt. Establish when to continue, restrict, revise or stop. A known adequate correction may be introduced directly under the applicable rules; the word “improvement” does not require an experiment.

Plan recovery appropriate to the subject. A previous software configuration may be restorable; lost trust, interrupted service or a person’s acquired experience cannot be undone by replacing a file. Use limited exposure, retained alternatives, parallel provision or another suitable protection where reversibility is limited. Include these costs in the choice.

C.42:4.7 - Judge later performance and return to the consequential question

Compare the intended difference with what occurs in the receiving work. Was the needed result obtained, with its safeguards and support? Did whole effort or relevant delay decrease, for whom, and under which conditions? Include transition work and exceptional cases at the scope of the claim. This account of the total effect and a new decision about future work use different cost bases, as explained in §4.5. A successful demonstration or completed instruction is not yet evidence of sustained ordinary performance.

Distinguish a useful result from its explanation. Observed improvement can support keeping a local arrangement while leaving causal attribution uncertain. If the claimed advantage depends on attributing the effect to one intervention, C.28.CM supplies the further causal question. A.3.1.MI keeps introduction, contextual support and the later performance claim separate.

Return to the part whose grounds changed. A newly required output reopens the purpose comparison. Recurrent mismatch reopens the preventive construction. A longer support queue reopens the whole-burden comparison. An unhandled input reopens the permitted scope or fallback. Preserve earlier answers that still hold; one exception does not require rebuilding every unchanged part.

Keep the change when the supported gain remains worthwhile. Restrict or replace it when only some uses remain adequate. Restore a suitable earlier way when the new one loses a needed condition. End this improvement undertaking when its useful result has been obtained or further work is not worthwhile. Review again on an action-changing event, such as changed demand, lost support, a new receiving use or evidence that the preserved condition no longer holds.

C.42:4.8 - Continue development without turning economy into its only purpose

A worthwhile reduction can release attention, capacity or resources. Establish what has actually become available before promising it elsewhere. Then ask whether that changed position makes another useful problem, investigation or capability attainable. C.40.NP develops this continuation from an obtained result.

The next undertaking may change the problem, create knowledge, expand a capability or improve the way future changes are obtained. It can require more current work. Judge that contribution in its own right. Preserving the means for later development does not require perpetual activity, and ending an obsolete undertaking can be a successful reduction. This method governs economy of obtaining a result; it does not define all development as obtaining the same result more cheaply.

C.42:5 - Archetypal Grounding

These are constructed cases. Their numbers and observations are premises for inspecting the reasoning, not evidence that the method has produced a measured benefit in practice.

C.42:5.1 - A repeated research packet: removal, prevention and automation

A research group must supply a weekly packet of ten matched observations for a comparison. The recipient requires correct source identity and units, a usable comparison, and an explicit hold for unresolved rows. A separate presentation duplicates the accepted table. The recipient confirms that the table is sufficient for this use; no other current use of the presentation is found. The authorized work owner agrees to stop that duplicate output.

The group traces recurring correction to mismatched source editions. It can obtain the authoritative edition and check the row identities before preparing the comparison. This adds a small action but prevents the specified mismatch. The validity of the subject measurements remains a separate required condition.

Three complete alternatives fit these stipulated requirements. All figures are staff minutes, include the recipient’s changed work where any, and assume the stated weekly demand:

The present 100 minutes comprise 60 minutes of necessary preparation and verification, 20 of duplicate presentation work and 20 of correction of the specified mismatch. These categories do not overlap. The revised manual way keeps the 60, adds 10 for the identity check and 5 for support of the changed arrangement, and removes the duplicate and specified correction.

The tool uses the qualified source identifiers to prepare the comparison and hold unsupported rows. Its 45 minutes include 25 for preparation and verification, 10 for exceptions and 10 for maintenance. Its 300 initial minutes include configuration, checking, instruction and transition. The stipulated comparison grants neither candidate new authority to approve unsupported observations. The same substantive result, controls and access conditions remain.

For eight remaining weeks, the revised manual way uses less total effort than the tool, despite more effort in each ordinary week. At twelve weeks the totals become 1,200, 940 and 840: the tool then wins under the same assumptions. Its extra initial burden over the revised manual way is 260 minutes and its weekly saving is 30, so their order changes after 8⅔ weeks. Uncertain duration can therefore matter more than a small refinement of weekly estimates.

The tool was a legitimate candidate from the start: one integration can remove duplicate preparation and a mismatch mechanism together. It did not have to wait for a calendar sequence of earlier improvements. Conversely, the tool’s attractive weekly figure did not make it the eight-week choice.

The group chooses the manual change for the eight-week undertaking. The work owner makes the authoritative source accessible, replaces the old preparation instruction and provides a responsible contact for unresolved rows. In a constructed first-use variation, the source is temporarily unavailable. The agreed response is to hold the affected packet or use an independently adequate fallback, not silently reuse an unqualified copy. That exception’s actual burden would enter the subsequent comparison.

Suppose the next four packets meet the agreed conditions, including delivery within the permitted window after the temporary hold. Their recurring effort totals 300 minutes; the exceptional source recovery adds 30, and actual initial preparation took the stated 40. The resulting 370 minutes include the recovery instead of hiding it. The record supports four acceptable packets with that effort. A claim of 30 minutes saved additionally relies on the comparability of the 400-minute baseline; the record alone does not establish that counterfactual or the remaining weeks.

The group can keep the change within these supported conditions while continuing the ordinary comparison. If correction persists because some supposedly matching identifiers have different meanings, the original prevention premise fails for those rows. The group reopens that interpretation and retains the useful deletion of the duplicate presentation. If the recipient later needs an annotated presentation for a new audience, the deletion decision is reconsidered for that use; the source-identity improvement can remain.

In a separate constructed variation, the integrated tool has already been built, is available and preserves the same required conditions. Four weeks remain. Continuing with it requires 180 minutes; changing to the not-yet-introduced manual way requires 40 minutes of transition plus 300 minutes of recurring work, or 340 in total. The original 300 minutes of tool construction remain part of the undertaking’s historical effort, but the current choice is not 480 against 340. Any new withdrawal, recovery or capability loss would enter the future comparison separately. The initial eight-week comparison and this later choice differ because the available means and remaining work differ.

C.42:5.2 - A service delay is not its processing time

A translation service spends two hours preparing and checking a document, but completed requests wait three days for an authorized release decision. A proposed tool saves twenty minutes of preparation. For the request at issue, the next available authorized release slot is three days away. Twenty minutes less preparation does not create an earlier slot, so this change alone cannot provide next-day delivery.

The service follows the delay to its condition. A qualified release decision is required; only one authorized reviewer currently has a weekly slot. The live alternatives include keeping that arrangement, obtaining an earlier decision slot with the same reviewer, or qualifying and authorizing another reviewer. Simply omitting the decision does not preserve the result.

An earlier slot is useful only if the document and necessary evidence are ready then and the reviewer can serve the combined requests. Moving a slot on one request’s plan supplies no extra capacity. If these conditions can be met, it can improve elapsed delivery time with little change in labour. If they cannot, the preparation tool may still be worthwhile for effort, but it does not solve the promised delivery-time problem. The receiving commitment needs another complete arrangement or a truthful revision.

The service can introduce a supported scheduling change while studying why the queue formed. It can also compare a combined scheduling and preparation change. The common question is what obtains the recipient’s adequate document; no universal order makes one intervention wait for the other.

C.42:5.3 - An answer, a capability and a useful negative result

A learner practices interpreting unfamiliar statistical results. A tool can produce a correct explanation of today’s example. If the needed result is only that explanation, suitable tool use and checking can be an adequate obtaining way. If the need is later independent interpretation, the supplied explanation does not establish the learner’s capability.

The practitioner separates practice that develops the missing operation from clerical copying that serves neither learning nor later use. A competent teacher can replace the copying with supplied material while retaining the learner’s interpretation, feedback and a consequential variation. Whether this changed practice develops the intended capability is a learning question requiring its own method and evidence. The elegance comparison keeps that result visible and includes the teacher’s preparation and feedback effort; it does not infer a learning mechanism from repetition alone.

Similarly, a research group may perform a careful test that rejects its preferred hypothesis. Removing the test because it produced no usable product would discard the knowledge it was meant to obtain. Repeating the same test without a new discriminating purpose can have a different value. The decision follows the receiving knowledge or capability, not the visible count of outputs or the emotional experience of success.

C.42:6 - Bias-Annotation

The Gov, Arch, Onto/Epist, Prag and Did lenses apply. Scope is transdisciplinary for the comparison and change construction, with subject-specific mechanisms, authority and evidence.

The method deliberately foregrounds avoidable burden. That can bias attention against reserves, inquiry and capability development whose contribution arrives later. Sections 4.1, 4.5 and 5.3 keep those results and their grounds in view. The opposite bias is speculative preservation of every activity; a merely imaginable future use does not establish its worth.

C.42:7 - Conformance Checklist

These checks inspect an explanation or application claiming this method; they do not require a new form for every improvement.

C.42:8 - Common Anti-Patterns and How to Avoid Them

Automate the unwanted output. A quicker duplicate still consumes work. Recover the receiving use through 4.1 before treating production as necessary.

Call all repetition waste. Similar practice attempts and negative tests can obtain capability or knowledge. Use the result distinction in 4.3 and the contrasting case in 5.3.

Turn the mnemonic into stage gates. Waiting for every earlier diagnosis can postpone a well-supported combined intervention. Follow the actual grounds and dependencies in 4.4.

Claim the local saving as the whole gain. A requester stops entering data while support staff reconstruct it. Follow the transferred contribution and its bearer through 4.5.

Install a rule and declare the work changed. A correct instruction cannot provide missing access, a performer or an available decision. Carry the change into practice through 4.6 and examine the receiving work through 4.7.

C.42:9 - Consequences

A practitioner can stop an unnecessary contribution, prevent recurring avoidable work, distinguish an elapsed-time opportunity from a labour saving, or select a worthwhile replacement without assuming automation is preferable. A warranted decision to keep a manual way is as legitimate as introducing a tool.

The price is attention to interactions and later use. An elaborate accounting exercise can exceed the attainable saving. Reuse sufficient existing knowledge and compare only distinctions that can change the decision. More difficult uncertainty can justify a limited trial or a narrower conclusion.

A retained protection or learning activity can make a candidate look less minimal while making the whole undertaking less burdensome or preserving a necessary later result. Savings remain conditional on demand, support and use; they can disappear when those conditions change.

C.42:10 - Architectural Rationale

The governing invariant is the needed contribution in its receiving use, not the visible activity that currently produces it. This makes removal and replacement comparable without treating all outputs as desirable or every familiar action as indispensable.

The method joins questions whose answers constrain one another. Purpose determines which losses matter. The observed operation and its causal explanation constrain interventions. Whole-burden comparison determines whether an intervention is worth obtaining. Introduction and subsequent performance determine whether the proposed gain is available in practice. A change at any of these points can justify a bounded return without imposing a universal sequence.

A.11.OP tests one proposed requirement’s contribution. C.11.DUA judges the worth of advice and inquiry. B.1.5.RS determines which encompassing uses tolerate a replacement. Those results can be sufficient for a local question. The present method adds the connected construction from an avoidable demand to a worthwhile change and its continuation in work; it does not replace those narrower judgements.

The commonality across people, organizations and technical systems lies in this reasoning about obtaining ways. Their causal mechanisms, permissible interventions and means of recovery remain different. A shared comparison does not establish a shared mechanism.

C.42:11 - SoTA-Echoing

Practice question and selected line. How can a practitioner reduce avoidable work while preserving the actual result and conditions over the relevant horizon? The selected answer is the conditional synthesis in section 4: purpose and use, diagnosis, intervention construction, complete comparison, introduction and later reconsideration. It is a method proposal grounded in the comparisons below, not an empirical claim of universal superiority.

Toil reduction is a serious mature alternative. Google’s 2018 SRE treatment already compares elimination, simplification and automation, including maintenance and indirect costs. It is not an automation-first foil. Adapt its whole-burden and cause-removal reasoning in 4.3–4.6 to the broader receiving-use question. Use the domain practice directly when it already supplies that answer. For the broader question, sections 4.1 and 4.3 also compare changes when knowledge or capability is the needed result and purposeful repetitions contribute to it. The trade-off is extra diagnosis where those distinctions matter; this synthesis offers no established gain from repeating them when they are already settled. Eliminating Toil.

A competent improvement cycle can already suffice. IHI’s PDSA guidance connects prediction, a bounded test, observation, learning and adaptation; its implementation guidance distinguishes testing from changes in ordinary provision. Adopt that separation in 4.6–4.7. Adapt the earlier construction in 4.1–4.5 when the live uncertainty is which demand to remove or which complete alternative to test. PDSA can handle combined changes and unintended effects; the pattern does not claim those as missing inventions. If an existing improvement practice already carries the needed construction and comparison, use it without another pass. Reopen the selected synthesis if an equally usable simpler treatment preserves these distinctions at lower burden. Testing Changes, Implementing Changes.

Subtraction deserves consideration, not automatic preference. Adams and colleagues’ experiments support including subtractive possibilities explicitly when people generate changes; they do not show that removal generally outperforms addition. Later work reports task and population variation and further bounded replication. Adapt the candidate search in 4.4 to include ending or removing work; reject subtraction as the selection rule. An added preventive check can win, as 5.1 shows. Reopen the search cue if evidence for the actual reader and task makes it ineffective or unnecessarily burdensome. Adams et al., 2021, Juvrud et al., 2024, Fillon et al., 2025.

The worked cases establish inspectable consequences of their stipulated premises. They do not validate expected savings, a universal human or AI bias, or the comparative effectiveness of the whole method. A stronger practical claim needs evidence from its actual conditions.

C.42:12 - Relations

• A.3.1 supplies Method identity and the distinction from descriptions and performances.
• A.11.OP tests one proposed requirement’s contribution; C.11.DUA resolves consequential questions of advice or inquiry worth.
• B.1.5.EW recovers encompassing work; B.1.5.RS evaluates the compatibility of a constituent replacement with its affected uses.
• C.28.CM constructs and challenges a causal explanation when that explanation changes the intervention or attribution.
• C.39 develops a missing obtaining operation or connection; C.38 constructs whole alternatives when the available ingredients are not yet comparable.
• C.11.CRC compares contributions with shared constraints and consequential interactions.
• A.3.1.MI supplies introduction into practice and judgement of what to keep or change.
• C.40.NP develops a further worthwhile attainable problem from the position reached after a result.

C.42:End