Plan the trial build as a team, then learn from it

This page helps teams agree what a trial build is meant to show and how observations reach the people who can review them. It is a coordination guide; it does not authorize work or replace the approved operating and safety instructions for your line.

Industrial machinery arranged along a bright factory production line

What a trial build should leave behind

When the build window ends, the team should have a shared scope that says what was built and why, the roles that took part, the design and material references in use, and a single place where observations were recorded.

Observations are descriptions of what was seen. Whether one is acceptable is decided in review by the roles who own that decision.

Coordinate the window in five steps

  1. 1

    Align scope and timing

    Agree the quantity, the configuration, the line and the shift or shifts, and what the team wants to learn.

  2. 2

    Check references and dependencies

    Confirm the design revisions in use and that the parts on the readiness register are expected before the start.

  3. 3

    Brief the participating roles

    Walk production, quality and engineering through the scope, the references and how to record an observation.

  4. 4

    Capture observations as they happen

    Record what was seen, on which unit or position, on which shift, and against which reference, in the shared log.

  5. 5

    Route follow-up

    Send each observation to the role that can review it and note it in the next coordination point.

Worked example: Atlas trial build 2, shift 2

Fictional example. The record routes an observation for review; it does not rule on it.

The observation

On the second shift, an operator noted that the connector needed an extra reposition before seating on 4 of 20 units built. All four were at the same fixture position.

  • Logged with unit positions, shift, and bracket B-214 Rev C as the reference.
  • Written as what was seen, with no assumed cause.

The routing

The shift lead sent the entry to the design engineer and the quality engineer, since the pattern could relate to the fixture, the bracket or the connector.

  • Both roles were named on the log line.
  • Status: assigned, with the review point set for the next build debrief.

What the team did not claim

The record does not say the build passed or failed on this point. Engineering and quality decide what the pattern means and whether more units should be checked.

  • The finding carries forward into the acceptance evidence index as an open review question.