3.6 Remote & Hybrid Work: Latency Controls

Manufacturing is a physical reality. We process heavy atoms, not just bits. While we embrace the capital efficiency of asynchronous remote work for digital tasks, the reality of the factory floor dictates our rhythm. This policy explicitly defines the operational protocols required to maintain perfect synchronization between distributed hybrid teams and the physical production line.

Remote work in our company is not an entitled “benefit”; it is an operational mode. It is actively granted only when the employee consistently demonstrates they can bridge the “Latency Gap” without slowing down the factory line.

Role-Based Eligibility Logic

We categorize roles based heavily on their proximity to physical, operational risk. Eligibility is dictated by the physics of the job, not by seniority.

Tier 1: On-Site Essential (100% Physical Presence)

Who: Production Operators, Line Maintenance, Factory Warehouse, IQC/OQC Inspectors, HR, Hardware Test Engineers (Bring-up).
Why: You cannot remotely solder a board, correctly inspect a micro-solder joint under a microscope, or effectively read the body language of a candidate via Zoom.
The Rule: 100% full physical attendance required. No exceptions.

Tier 2: The Bridge (Hybrid Mandatory)

Who: Product Owners (PO), Hardware Design Engineers, Key Engineering Managers, Strategic Supply Chain Leads.
Why: These crucial roles define exactly what the factory builds. You must “walk the Gemba” (actually see the real factory process) to make valid engineering decisions. A pristine CAD model is not reality; the warped prototype on the line is.
The Rule: A minimum of 3 days/week on-site. You must be fully present for all NPI (New Product Introduction) trial builds.

Tier 3: Remote Eligible (Digital Output)

Who: Software/Firmware Engineers, PCB Layout (Only when Schematic is Frozen), Pure Data Analysts.
Why: The total output of these roles is purely digital code or electronic files.
The Rule: Remote is allowed only when the “Factory Interface” protocols below are flawlessly met.

The “Factory Interface” Protocols

Remote employees must compensate for their physical absence by increasing their communication fidelity. The following protocols are mandatory to prevent “out of sight, out of mind” delays.

Protocol A: The Anchor Timezone

The factory line does not care about your local sunrise.

The Rule: Remote staff must overlap a minimum of 4 continuous hours with the Production Time Zone.
The Impact: When the factory is operating in GMT+7 and you are in London, you must alter your personal schedule to be actively available when the line is operating.
The Violation: Missing a synchronous “Red Button” meeting with the factory team due to “timezone differences” is a severe performance violation.

Protocol B: Remote Debugging (The “Avatar” System)

“It works fine on my machine at home” is an unacceptable excuse.

The Hardware Ban: Do not take expensive prototype hardware to your home. Home environments severely lack ESD protection and thermal testing chambers.
The Avatar: To debug remotely, you must pair seamlessly with a dedicated on-site “Avatar” (A Factory Technician or Jr. Engineer) who acts as your physical hands.
The Digital Twin: You must ensure your remote environment matches the factory test rig exactly (the exact same firmware version, the exact same test scripts).
Visual Fidelity: When debugging a physical hardware defect, you must use high-resolution, live video. Do not guess based on text descriptions.

Protocol C: Documentation as Corporate Presence

In a physical office, you can tap an engineer on the shoulder. Remote, you cannot.

The Availability Signal: You must constantly update your digital status (Slack/Teams) to accurately reflect your real availability.
The 15-Minute Rule: During the mandated 4-hour overlap window, your response time to direct operational pings must be < 15 minutes.
The Output: “Work out loud.” All architectural decisions must be committed to the System of Record (Wiki/Jira) immediately. When it is not written down, it is effectively not done.

Environment & IT Security Standards

To work remotely, your personal infrastructure must meet professional standards. This is entirely the employee’s responsibility.

Bandwidth: A hard minimum of 50 Mbps Down / 10 Mbps Up. Video calls must be artifact-free.
Acoustics: A dedicated, quiet, door-closable room. Loud background noise (barking dogs, traffic, cafes) during client presentations or strategy calls is highly unprofessional.
Security:
- VPN: Always On.
- Visual Privacy: No working on company IP in public cafes where proprietary code or unreleased schematics are visible to passersby.

Enforcement & Exceptions

Revocation of Privilege

Remote work is a revocable privilege. It will be rescinded immediately by management if:

Ghosting: The employee is functionally unreachable during the Core Overlap Hours.
Blocking: A critical production stop (Line Down) is prolonged because the remote employee was “offline.”
Quality Decay: Code or Design quality drops due to a lack of collaboration.

The Golden Handcuff (Exceptions)

Exceptions to the On-Site/Hybrid tiers (e.g., granting full-remote to a Hardware Architect) explicitly require CEO Approval. These are reserved only for niche experts whose specific skill set is unobtainable locally. These exceptions legally require a signed Service Level Agreement (SLA) defining specific travel frequency (e.g., must fly-in to the factory for 1 solid week per month).

Final Baseline Checklist

The Control Point	The Requirement	Why?
Overlap Window	4 Hours continuous overlap with Production Time Zone.	To resolve blockers before the factory shift ends.
Response Time	< 15 Minutes during the core Overlap Window.	To prevent expensive line stoppages.
Hardware at Home	Prohibited.	IP security and ESD safety protocols.
Hybrid Rhythm	3 Days On-Site minimum for Tier 2 roles.	To maintain physical product context (The Gemba).
Escalation SLA	Must answer Red Button executive calls 24/7 if critical.	A Line Down event fundamentally ignores your timezone.
Digital Status	Calendar/Slack status must be 100% accurate at all times.	To avoid “Ghosting.”