VYRCOWhat you will learn
- An observation describes a fact; a hypothesis offers an explanation that still needs evidence.
- Every sample, photograph and file needs enough context to identify it later.
- Completing an action does not establish a cause or prove that a problem will not return.
Who it is for: Technicians, supervisors and engineers sharing investigations.
Start with a question that can be checked
Before searching for a cause, write down what needs to be understood: the affected part or function, when the issue began and its known extent. “The mold fails” does not organize a useful investigation. “Ejection stopped during order OP-DEMO on the afternoon shift” defines an event without inventing its origin. Include what remains unknown.
Give the event a stable identifier. Use it in the failure log, evidence folder and later repair record. This prevents a separately shared photograph from losing its connection to the case.
Build a timeline, not a persuasive story
Order facts by time and source. If a machine clock differs from a phone clock, retain both references and record any known offset. Do not rewrite the original value to make the sequence fit. A timeline may contain gaps: these are investigation tasks, not spaces to fill with assumptions.
Distinguish when something happened, when it was observed and when it was recorded. An 11:00 message may describe a 10:30 event. The distinction helps compare alarms, samples and shift changes.
| Field | Fictional example | Purpose |
|---|---|---|
| Fact | Ejection stopped at 10:30 | Defines the event |
| Source | Alarm saved in file A17 | Allows checking |
| Hypothesis | Possible interference, unconfirmed | Keeps an idea separate from a conclusion |
Make evidence possible to find
A reference such as “photo in a chat” is fragile. Record the file name or ID, date, author or custodian and authorized location. For a physical part, identify sample, cavity if known, order and storage condition. Retain the original and distinguish annotated or cropped copies.
Before sharing material, check for customer, personal or confidential design information. An external copy may need redaction; document what was hidden so readers understand the evidence limits. Missing access to an original should remain visible rather than being treated as a completed review.
Compare hypotheses with results
Use five whys to organize questions or an 8D report to collect work, but do not confuse completed fields with a demonstrated cause. For each hypothesis, write what would support it, what would weaken it and which authorized check remains open. The technical owner must define the method before an intervention.
Keep results that contradict the initial explanation. If several changes were made together, preserve that limitation: later improvement cannot identify the effect of one change alone. Link approved modifications to their change records and keep the previous configuration identifiable.
Close with scope, ownership and follow-up
Separate temporary containment, completed repair, verification and follow-up. The record should show what was functioning, under which restrictions and who made the decision. If another team owns an action, assign a person and a review date instead of writing only “pending”.
When reviewing a recurrence, return to the previous event and evidence. If the part, material or configuration changed, do not describe both cases as identical without checking. A limited conclusion can still help the next team decide what information to gather.
Fictional case: a mark beside a connection
The team finds a stain beside C2 and opens EVT-DEMO. A photograph records location and date but does not show an active leak. A leak hypothesis is logged and an authorized check requested. The later inspection remains linked to the same event. Until a result is available, the report states “cause pending”; the repair record will contain only work actually performed.
Mistakes to avoid
- Replacing “possible” with “confirmed” without recording the evidence behind the change.
- Deleting a reading or photograph because it contradicts the preferred explanation.
- Closing the case when only temporary containment has been completed.
Checklist before continuing
- The event has an ID, scope, times and identified sources.
- Facts, hypotheses, checks and conclusions remain separate.
- References lead to the original evidence.
- Every action has an owner, verification criterion and status.
- The next shift receives restrictions and specific next steps.
Sources and review
- BASF · Injection Molding Troubleshooter
Defect terminology and initial guidance; consult grade- and application-specific information.
Accessed: 2026-10-09 - NASA · Configuration Management
Principles for identifying, reviewing and verifying changes. VYRCO formats are original, not NASA forms.
Accessed: 2026-10-10
Original general guidance by VYRCO based on the listed references. Examples are fictional. Editorial review does not validate your process. To correct an item, identify the article, date and source at info@vyrco.com.