B.5.PI - Initiate Inquiry from Ongoing Work

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

B.5.PI:1 - Problem frame

Use this pattern to make room for a useful question in work that people or agents currently treat as ordinary. Reports arrive, calculations run, repairs succeed, and nobody asks whether the way of obtaining or using those results needs examination. Use it also when someone says that an explanation misses something but cannot yet say what. A known error, an anomaly label and a request for help are not prerequisites.

Start at a small occasion already connected with the work: preparing a handover, demonstrating a result, explaining a consequential choice, or resuming work after a change. Recover what the result is supposed to enable and examine one available episode of obtaining and using it, including the adjustments that made it succeed. A performer can do this while preparing their own work; a colleague or team can arrange the occasion. It takes access and attention, even if only briefly.

The useful result is a question with an attainable next move, an early cue retained for further consideration, or a reasoned continuation without change. Here, inquiry includes a short question to a colleague or consultation of an existing explanation; it need not become a research project. The method helps bring an unexamined part of work into consideration. It does not promise that every hidden difficulty will be found.

Use an adequate existing answer directly. When the question is already clear, use its subject method. When a known useful method merely goes unnoticed at the right moment, A.15.11 helps arrange that encounter. Continuous monitoring, statistical anomaly detection and a full audit have their own methods; they are not mandatory implementations of this one.

B.5.PI:2 - Problem

A worker receives enormous values from a familiar calculation and says, “It sometimes does that.” A team meets every deadline through repeated manual repair. An assistant answers a colleague’s objection with a familiar recommendation, then treats the colleague’s inability to name a better answer as closure. The work continues without a question about the unexplained part.

More searchable advice cannot help until something makes that advice worth seeking. “Ask for help when there is a problem” assumes the recognition that is missing. “Look for anomalies” leaves both the occasion for looking and the relevant comparison unspecified. Even a passed checklist establishes only the conditions it actually checked.

The difficulty is to let ordinary work generate a question without requiring a prior diagnosis, a permanent observer or an expert who already knows the answer. The opposite error is to manufacture a defect whenever something differs from expectation, or to turn every small uncertainty into an expensive investigation.

B.5.PI:3 - Forces

B.5.PI:4 - Solution

At an ordinary work occasion, recover the use and what it takes; compare; keep what the account misses; form a question or retain the cue; obtain a worthwhile next contribution; return to the whole work. These moves form one connected method. Enter where a contribution is missing, return when a comparison changes the question, and stop when the receiving use is settled. The links below supply particular operations, not an obligatory chain of pattern applications.

B.5.PI:4.1 - Give the work an occasion to become a question

Select a bounded occasion that does not depend on someone first reporting trouble. At an ordinary handover, for example, ask the producer to show one result and how its recipient will use it. Recover what the producer actually had to do, including work that the official account omits. In preparing your own work, follow one result through its intended use instead of merely checking that you have produced it.

Choose an occasion with some prospect of a useful comparison: a consequential decision, a result passed to another person, a recurrent activity whose effort is poorly understood, or an available contrasting case. A small agreed sample can expose something that reviewing only failures would miss. Do not require every occurrence to undergo this examination. Keep the immediate work and its constraints in view.

A performer may adopt this as a habit; a teacher, team or tool maintainer may make it available through A.15.11. For example, an existing handover conversation can include “Show what the recipient can do with this, and what you had to add to make that possible.” This question does not anticipate a specific error. A publication alone does not establish the habit or supply the conversation. If access to the result, its use or an attentive participant is unavailable, identify that missing contribution rather than claim that inquiry has begun.

B.5.PI:4.2 - Compare before deciding what is wrong

Connect the intended use with an accessible episode. Try using the result, ask its recipient to demonstrate the use, compare an available prediction with what occurred, or work through a nearby case whose consequence can be established. Include the adjustments that made a successful outcome possible. Keep observations, memories and constructed cases distinct.

Ask what makes an apparent difference acceptable or inevitable. “This always happens” states frequency; it does not establish adequacy. “The procedure was followed” supports conformance; it does not establish that the procedure answered the receiving question. Conversely, unfamiliarity does not make a result defective. A symbol that looks like a numerical answer may be an agreed status marker; an adjustment may preserve a necessary constraint.

Use subject knowledge to interpret the comparison. When that knowledge is missing, the question may concern what the result means or which conditions justify its use. Do not invent the missing observation or explanation. If the available account already explains the difference and supports the intended use, continue the work without creating a problem.

An anomaly is a difference relative to an account, expectation, comparison class or intended use that merits consideration. Make that reference clear when it affects the next move. Statistical rarity, a breached requirement, a felt mismatch and an unused possibility are different reasons to look. Problematization develops or questions what is taken for granted so that a consequential question becomes possible. It can change the comparison itself: something previously normal can become questionable under a better account. Anomaly detection therefore need not be completed before problematization starts.

B.5.PI:4.3 - Keep the part that the familiar account loses

Retain the episode, expression or contrast that cannot yet be explained. B.5.EA helps a participant develop a distinction when familiar words conceal it. The listener should try the proposed interpretation on the original case: if following the offered advice would leave the concern untouched, reconsider the interpretation. Use the conversation, document or work already available before asking the participant to collect more evidence. Ask for a missing fact when it is actually needed; do not require the participant to supply the diagnosis that the joint work is meant to develop.

For example, advice to make a help form clearer does not answer why someone who sees no problem would open it. Preserve that difference even when neither participant can yet state a complete alternative method. An objection warrants examination of the account; it does not make the objector’s causal explanation true.

An early cue is something already noticed as worth retaining before its meaning or continuation is settled. It is not yet a confirmed anomaly or a formulated question. Keep the passage, observation or rough expression that lets someone return to it. The existing conversation may suffice. A.16.1 supplies deliberate preservation when otherwise the cue would be lost; B.4.1 can make possible continuations explicit after stabilization when someone needs that contribution. Neither requires every exchange to acquire a new form or route record.

Stop here if only the cue is recoverable and further articulation is presently unproductive. Identify an attainable return occasion when one is available, without inventing a commitment or declaring the concern resolved.

B.5.PI:4.4 - Ask from the situation before naming a solution

State what the work should enable, what comparison or experience raised the question, under which conditions, and why the answer could matter. Ordinary words are enough: “How can this figure help price the next batch when it has no numerical value on some days?” is a usable question without the phrase “division by zero”. Search a library or ask a colleague using the situation and needed result. A PatternID is one way to obtain an answer after its relevance becomes intelligible, not a prerequisite to inquiry.

Let the first answer change the question. A calculation can be correct for the wrong quantity. An explanation can answer an easier question than the one the recipient needs. Return to the original use before accepting either as closure. B.5.QD develops a consequential question when the initial one needs reconstruction; B.5.QD.CF examines assumptions behind an apparent conflict. Use those contributions only while the question needs them.

An adequate known explanation, instruction or direct correction may finish this use. If the question needs a new construction, explanation or test, B.5 connects the reasoning contributions. Keep later investigation and problem formulation under their own conditions; a provisional question need not be promoted immediately to a fully specified Problem or research programme.

B.5.PI:4.5 - Obtain a continuation that can actually be used

Choose what is missing now: an existing answer, one discriminating comparison, accessible expertise, a capability to develop, or a larger inquiry. Judge the effort against what the answer could change in the encompassing work. C.11.DUA examines burdens imposed by advice; C.11.CRC compares an attainable change with continuing as now. They help choose an intervention, not decide whether a participant is allowed to voice an unresolved concern.

Carry an answer back to the receiving use. Does it let the recipient act, understand or ask a better question? If a small comparison can discriminate between plausible explanations, make that comparison before prescribing a larger change. If the performer understands the needed action but cannot execute it, obtain support or a suitable learning method; repeating the question does not develop the capability.

If no worthwhile improvement is available, retain the current adaptation with its relevant conditions. If inquiry cannot be afforded or a needed observation is inaccessible, say what remains unknown and what that means for the current use. Inability to investigate does not certify adequacy. A retained cue and an available later occasion can be the bounded result. Where consequences require a decision now, obtain it through the applicable subject and authority rules rather than letting unresolved uncertainty silently authorize continuation.

B.5.PI:4.6 - Keep the opening usable while the whole work continues

After use, examine whether this occasion brought something consequential into consideration and whether the result justified its burden. Change an unhelpful question, move a disruptive occasion, obtain a missing response, or remove a ritual that produces only ticks. Passing an execution checklist can support selected claims; it does not close concerns outside those claims. A known-condition checklist is designed through A.15.11, while the present method keeps a way to question what that list leaves unexamined.

Make it possible to respond. A worker with no access to receiving outcomes cannot inspect them. A request that nobody can answer does not supply assistance. When raising a concern is punished, changing the conditions of joint work may be necessary; asking for greater personal vigilance does not repair those conditions. Use the smallest attainable support that answers the need, without assuming a permanent observer.

Producing a result, keeping it usable and learning from the attempt can be enacted together in the same action. B.1.5 and B.1.5.EW help recover the relevant Method composition and how those actions enact encompassing work, including the constituent capabilities and receiving use. In a time-critical or bodily action, a pause, later replay or another participant’s observation may preserve the whole better than an added question during execution. Human learning and changes to an AI system’s access, instructions or training require their respective methods. An answer obtained with supplied guidance is not evidence of later independent recognition.

B.5.PI:5 - Archetypal Grounding

These are constructed cases with stated conditions, not measurements of the method’s effectiveness.

B.5.PI:5.1 - An on-time handover hides recurring work

A team hands over a completed daily schedule. Nobody requests an audit: the recipient receives the schedule on time. While preparing an ordinary handover, the producer follows one entry from the incoming list to the recipient’s use. They show that they retype twelve equipment names from memory because the incoming abbreviations differ from the recipient’s names. The deadline is met because the producer knows both conventions.

The listener first says, “Make the deadline reminder clearer.” Applying that suggestion would leave all twelve retypings and the reliance on one person’s memory unchanged. The producer cannot name a better method, but can point to those transformations. Keeping that contribution changes the question from punctuality to whether the recipient can identify the equipment without repeated reconstruction. The producer’s skill remains a successful adaptation, not evidence of misconduct.

The next question is small: “Can we make the correspondence available without losing distinctions the recipient needs?” In this case an authoritative list already exists. The two participants compare twelve entries with it; ten have a unique correspondence, while two abbreviations denote different equipment in different buildings. A single global replacement would conceal that difference. They retain the building context, give the recipient the resolved names and leave the two unresolved entries for the person who can supply their locations. The receiving schedule is checked by identifying the intended equipment, not by counting replaced labels.

For repeated handovers, an available mapping keyed by name and building may remove some reconstruction. Whether to prepare and maintain it depends on actual use and effort. A one-off schedule with no further receiving difficulty can keep the manual translation. In either case the inquiry returns to the schedule: the recipient can use the supplied identities, or knows which entries still need a location. It need not create a new organization-wide programme.

If the recipient instead demonstrates that both naming conventions are already understood and the retyping merely changes typography, the proposed identity problem disappears. Ask whether the extra effort is worth removing; do not preserve the first diagnosis merely because it motivated the comparison. If neither receiving use nor the authoritative list is accessible, retain the dependency on memory as an early cue and obtain access when worthwhile. No claim of safe replacement follows from that cue alone.

B.5.PI:5.2 - A familiar calculation produces an unusable figure

A daily report divides total operating cost by completed units. On a day with zero completed units, the software displays an infinity marker. The preparer treats it as normal because it happens regularly. During a handover for pricing the next batch, the preparer tries to explain what price decision that entry supports. The gap becomes apparent through the use, before anyone names a division rule.

An existing mathematical explanation establishes that the quotient has no real-valued result when the denominator is zero. That answer removes a false numerical reading; it does not choose a pricing method. The receiving question now concerns which costs, output and period can support the proposed price. Obtain the appropriate accounting and modeling contribution rather than replace the marker with an invented number.

If the receiver shows that the marker already means “no production”, is never used in pricing, and the pricing calculation uses appropriate separate inputs, the unfamiliar display need not be a defect. The relevant use is already explained. Altering the software solely to remove the unusual value would answer a different question.

B.5.PI:5.3 - An objection cannot yet become a named problem

A reader says, “This guide misses something,” and points to its instruction to ask for help when trouble occurs. The assistant proposes a more visible help button. The reader objects again but cannot name the missing method.

The assistant returns to the available exchange and tests its own advice. A person who regards the work as ordinary would still have no reason to use the button. This comparison preserves a difference between reaching help and finding a reason to seek it. The assistant can now examine ordinary work occasions instead of requiring the reader to prove a new diagnosis.

If the reader can only point to the phrase and must leave, keep that passage and the unresolved concern in the existing conversation. A usable question may come later. Neither a polished paraphrase nor the reader’s departure proves that the concern has been answered.

B.5.PI:6 - Bias-Annotation

An expert can mistake the absence of their preferred method for a defect. A familiar institution can instead normalize costly adaptations or silence a contribution because it has no accepted vocabulary. Test both interpretations against what the work enables. The person who notices a difference need not know its cause; the person who supplies an explanation still needs to show that it answers the original use.

B.5.PI:7 - Conformance Checklist

For guidance or an application claiming this method, examine the consequential conditions:

• The entry can occur without a recognized error, a diagnostic term or a request for an audit; its actual occasion, access and attentional demand are recoverable.
• The comparison retains the receiving use and what it took to obtain the result, including successful adaptations when they matter.
• A proposed interpretation is tested on the original case; the participant is not required to invent a diagnosis before their concern can be examined.
• An early cue can remain open without being mislabeled a confirmed anomaly, Problem or selected investigation.
• The continuation can obtain a usable contribution, identify missing means, or stop without change under stated conditions.
• Conformance, result achievement, adequacy for the receiving work and completeness of the description remain different claims.
• The result returns to the encompassing work, and any claim about later independent use has its own basis.

These checks cover the stated method, not every possible anomaly in the work under consideration.

B.5.PI:8 - Common Anti-Patterns and How to Avoid Them

Wait for the worker to complain. Use an ordinary demonstration or handover to connect a result with its use before a complaint exists.

Normalize by repetition. Compare the recurring feature with the use it serves; frequency alone settles neither harm nor benefit.

Solve the listener’s substitute question. Apply the proposed remedy to the originating episode and retain what it leaves untouched.

Require a named defect before listening. Work with a recoverable fragment or early cue. Interpretation and warrant can follow separately.

Turn every difference into a project. Use an adequate explanation directly, make a small useful comparison, or retain the present arrangement. An inquiry must earn its additional burden.

Treat a passed checklist as comprehensive adequacy. State what was checked and keep consequential concerns outside the list available for inquiry.

B.5.PI:9 - Consequences

An apparently routine task can yield a question that a search service, colleague or pattern library can help answer. Successful adaptations and inarticulate objections can contribute without already being recognized defects. The work gains a connection between doing, questioning and obtaining another method.

This consumes attention and sometimes exposes a need that cannot yet be met. False leads and imposed interpretations remain possible. The method supplies a way to begin and return, not a guarantee of discovery, learning or organizational improvement. Its use depends on accessible work, interpretation and an attainable response.

B.5.PI:10 - Rationale

Detection presupposes something to compare and attention to a difference. Ordinary work can supply both at an occasion where its result must mean something to another action. Recovering successful adjustments reveals dependencies that an output check alone omits. Asking what makes those dependencies necessary allows both criticism and justified retention.

The whole method is longer than a reminder because its intermediate results differ. A selected occasion makes a comparison possible; the comparison may supply an early cue; articulation can develop a question; the question makes a relevant answer findable; use of that answer tests whether the original work was helped. None of these contributions can be replaced merely by naming the next pattern. The sequence can shorten, loop or stop as the available contribution changes.

B.5.PI:11 - SoTA-Echoing

The practice question is how ordinary work becomes open to useful inquiry before its performer recognizes a problem. The synthesis combines problem detection, questioning of assumptions and examination of successful work. It does not generalize a laboratory effect or one industrial practice into guaranteed autonomous discovery.

Interpretation, not only signal strength. Klein, Pliske, Crandall and Woods, Problem detection (2005), is a historical account of how context and interpretation affect recognition. It motivates comparing accounts and revisiting explanations in §§4.2–4.3. A technical detector is a serious alternative when a suitable representation and criterion already exist. Ruff et al., A Unifying Review of Deep and Shallow Anomaly Detection (2021), makes those technical choices explicit. Its detector families do not decide what an unexamined work practice should regard as worth questioning. Use such a detector for its stated object, rather than substitute statistical rarity for practical inadequacy.

Question the premise that makes a situation ordinary. Alvesson and Sandberg, Generating Research Questions Through Problematization (2011), supplies a historical method of articulating and challenging assumptions, including one’s own. Adapt that operation in §4.2 and §4.4. Their research-literature setting does not make novelty or academic audience interest sufficient practical value. A routine explanation remains preferable when it already settles the use.

Examine what successful work required. Marques et al., Learning from normal work in complex sociotechnical system—Case in midstream operation (2025), uses facilitated accounts of ordinary work, adaptations and constraints. This informs the non-incident entry in §4.1 and the handover case. The situated industrial study does not demonstrate spontaneous inquiry by an unsupported performer; neither its interview duration nor a permanent facilitator is prescribed here. Tucker, Edmondson and Spear, When Problem Solving Prevents Organizational Learning (2002), supplies a historical contrast: local workarounds can sustain output while leaving recurrent conditions unchanged. Retain the adaptation’s contribution before deciding whether to alter those conditions.

A noticed discrepancy is not yet learning. Bascandziev, Thought Experiments as an Error Detection and Correction Tool (2024), shows the importance of representation and reasoning in bounded force-and-motion tasks. Theobald et al., Do reflection prompts promote children’s conflict monitoring and revision of misconceptions? (2024), distinguishes effects on monitoring from later learning and transfer. These comparisons support separating encounter, interpretation and later capability in §4.6; they do not establish the same learning mechanism in humans and AI systems.

Reconsider the arrangement when a simpler ordinary interaction supplies the same contribution, repeated comparisons leave the original concern untouched, attention costs exceed the attainable benefit, or missing access makes the intended operation impossible. More prompts alone do not resolve these failures.

B.5.PI:12 - Relations

• A.15.11 arranges an encounter with a potentially useful method, including this inquiry method, and supports known-condition execution checklists. It does not supply the question developed here.
• B.5.EA develops a correctable expression; A.16.1 preserves an early cue; B.4.1 makes grounded continuations explicit when needed. Their results can remain provisional.
• B.5.QD, B.5.QD.CF and B.5 develop questions, examine conflicting assumptions and connect reasoning contributions after or during this entry.
• C.22.PFR, C.22.2 and E.18.1 govern problem-side distinctions, inspectable problem formulation and carrying an accepted formulation into work. They do not require every early cue to be such a formulation already.
• C.11.DUA/.CRC help choose a worthwhile continuation; A.15.7 selects a next action under current conditions. E.11.PUA returns a selected pattern’s result to its receiving use and can reopen inquiry here.
• B.1.5 and B.1.5.EW recover simultaneous constituent and encompassing methods; E.23.CDI frames capability development when the needed contribution cannot yet be performed.

B.5.PI:End