Skip to main content
GullyHR

Lab and line see each other as different worlds: a fix for electronics companies

The prototype-to-production handover is where faults slip into an electronics business and where blame starts. How the split shows, why it drives line exits, and a joint release routine.

Ganesh HS · · 6 min read

People working in a leafy Indian business neighbourhood with a bakery, studio and workshop

In brief

  • Design engineers run on sprints and prototype builds while SMT and assembly crews run on boards per shift, so each side reads the other's delays as carelessness.
  • Faults slip in at the handover: an unapproved alternate capacitor on the BOM, a silkscreen with no polarity mark, test limits copied from the previous revision.
  • When first-batch yield falls, the line usually carries the blame, and a run of scolded batches and lost incentive is a quiet driver of operator exits.
  • One release review with a named owner for every open item, the designer standing at the first build and yield shared back weekly remove most of the friction.

The first production batch of a new gateway board comes out of the reflow oven with tombstoned 0402 resistors and a header soldered the wrong way round. Design says the line rushed. The line leader says the assembly drawing had no orientation mark. Both are partly right. The batch heads for hot-air rework while the customer waits.

Among the pressures listed for board and device makers, this one is easy to misread as a technical problem. Designers and production crews keep different clocks, and the jump from prototype to volume is where mistakes get in. It is also where blame starts. Blame, in turn, is one of the quieter reasons SMT operators resign.

What the split looks like on a working day

  • A board is released with its notes buried in an email thread, not in a work instruction at the station.
  • Pilot boards are hand-placed in the lab, so nobody proves the stencil, the feeder set-up or the reflow profile until volume starts.
  • Line leaders learn of an engineering change when stores receives an unfamiliar reel.
  • Gerber files, the silkscreen and the centroid file feeding the placement machine come from three different revisions.
  • Functional test failures return to the line with a red tag and no explanation.
  • Designers never stand beside the pick-and-place machine, and operators never see a design review.

Rework, late shipments and resignations

Rework is the bill everyone sees. Boards pile up at the hot-air station, parts are scrapped when a pad lifts, and dispatch dates slide. Then the customer's incoming inspection starts finding faults. The bill nobody totals is in people. Operators told a batch failed because of them, with no cause given, lose incentive and confidence. Some stop flagging doubts. Others take a job with a competitor two lanes away where the line feels calmer.

Engineers pay too. They lose evenings tracing faults that a ten-minute talk with the line leader would have prevented. Over time they come to see production as the place where good designs get spoiled, and the gap widens.

Nobody owns the gap between release and first kit

Engineering's job ends at the release note. Production's job starts at the first kit. The space between belongs to no one. Each side also measures something different. Designers count features and milestone dates; the line counts boards per shift and first-pass yield. Yield and rework figures sit with quality and seldom reach the person who drew the footprint. Without a shared meeting and a named owner, every gap is argued about after the damage.

A joint release routine in six moves

  1. 1

    Audit three recent launches first

    List every fault in the first batch of each. Sort them into design, documentation, material and workmanship. The sort usually reveals how much blame the line absorbed for gaps upstream.

  2. 2

    Hold one release review before every first build

    Design, the line leader, test, stores and quality sit together for an hour with the BOM, assembly drawing, stencil, placement program and test limits on the table.

  3. 3

    A name and a deadline beside every gap

    A missing polarity mark belongs to the layout engineer. An unconfirmed alternate part belongs to purchasing. Kitting waits until the list is closed.

  4. 4

    Put the designer on the floor for the first build

    They watch the paste print, placement and the first boards out of reflow, and answer operator questions in person.

  5. 5

    Send yield and rework back every week

    A single page to design showing faults by board revision. Engineers see the effect of their choices, and the line sees faults traced fairly.

  6. 6

    Change how failures reach operators

    Explain the cause found, not just the tag. When the cause sits upstream, tell the operators who were first questioned.

Release review sheet, one per new board or revision
Board name and revision: ________.
Design owner releasing it: ________.
BOM checked against approved parts and alternates: confirmed or pending, owner ________.
Assembly drawing marks polarity and orientation for every part: confirmed or pending.
Stencil, feeder list and placement program ready and proven: confirmed or pending.
Reflow profile agreed for this board: confirmed or pending.
Test limits and fixture confirmed for this revision: confirmed or pending.
Work instruction updated with photographs: confirmed or pending.
Open items, each with owner and close date: ________.
First build date and design engineer attending: ________.

For the leadership side, see how contract manufacturers grow line leaders. For sharing yield targets fairly, see fair yield targets on assembly lines.

Habits that keep both sides talking

  • A monthly line walk for each design engineer, with the line leader explaining one recent fault at the machine.
  • Operators invited to the last ten minutes of design reviews for boards they will build.
  • A shared rework log that names the cause category and never the operator.
  • Recognition for engineers whose boards launch with a clean first batch, and for line crews who flag doubts early.

None of this calls for new software. What it calls for is one meeting, one name per gap and one page of shared numbers. For help setting up the routine, describe your situation.

Questions we are asked

Someone who owns neither side outright, for instance the quality manager or the plant head. Their job is to see that every open item carries a name and a deadline, and that kitting waits until the list is closed.

Read next

Let’s find your next step

Is your HR process ready to scale?

Identify payroll leaks, record gaps and hiring bottlenecks in a free first conversation, and leave knowing what to fix first.

Book a free consultation

Know what you need? Share your requirements in four short steps.

Want the full picture? See the paid HR Diagnostic.

Prefer a quick message? Chat on WhatsApp

Talk to an HR consultant

Tell us where to reach you. All fields are required unless marked optional.

10-digit Indian mobile, without +91.

Your details stay private. Privacy policy