1.4 One Company: Across all Offices and Factories

A hardware manufacturing company functions as a single, interconnected system. It operates within two primary environments: the Digital realm—which includes Strategy, Engineering, Sales, and Finance—and the Physical realm, encompassing Production, Logistics, and Quality Control.

The “One Company” concept is the operating protocol that synchronizes these two environments. Its purpose is to ensure the digital plan and the physical execution move in alignment. The company operates as a unified system where decisions made in the Office are explicitly designed to support the Factory, and signals from the Factory are used to immediately inform the Office.

Operational Unity

To maintain synchronization between the office and the factory floor, we rely on three core structural principles. Think of these as the fundamental operational mechanics that keep the entire system coherent.

1. One Language (Semantic Consistency)

Operational efficiency requires a shared vocabulary. A corporate term must mean the same thing to a Software Architect in the office as it does to an SMT Operator on the production line.

The Principle: Corporate terminology should be clear and universal. For example, a product is either “Released” or “Draft.” We actively avoid ambiguous, in-between states.
The Mechanism: The definitions documented in our central systems serve as the standard reference. All cross-functional communication and Standard Operating Procedures (SOPs) should use these standard terms.
Why It Matters: Ambiguity is a primary source of errors. If Sales lists a “Custom” build but Operations assembles a “Standard” unit due to a misunderstanding, it is ultimately the client who suffers the consequence.

2. One Scoreboard (Shared Metrics)

We evaluate success as a single entity. We do not rely on entirely separate “Office Metrics” and “Factory Metrics” that can pull the organization in different directions.

The Principle: The operational health of the company should be visible to everyone. This shared visibility provides essential context to all team members, from leadership to line operators.
The Mechanism: Our core operating dashboards display key global metrics, such as:
- OTIF (On-Time In-Full Delivery)
- First Pass Yield Rates
- Customer Satisfaction Scores
Why It Matters: To move in the same direction, everyone needs to see the same map and understand our shared progress toward common goals.

3. One Timeline (Synchronized Velocity)

The Office often focuses on future planning (like product roadmaps), while the Factory executes in the present (daily production). These timelines must be synchronized.

The Principle: We synchronize these timelines through structured handoffs. A key example is the NPI (New Product Introduction) process.
The Mechanism: An engineering project moves from the “Design” phase to the “Build” phase through a synchronized milestone review. In this review, Engineering presents the design’s maturity, and Operations formally accepts the production requirements and commits to the build plan.
Why It Matters: This process eliminates the inefficient “throw it over the wall” mentality. It forces a collaborative transition, ensuring both sides are prepared and aligned before work begins.

Cross-Functional Rituals

Routine, structured interactions are what build and maintain organizational alignment. We practice specific rituals to ensure the Factory and the Office maintain constant, productive communication.

1. The “Gemba” Walk (Grounding)

The Concept: “Gemba” is a Japanese term that translates to “the real place.” It is difficult to fully understand the physical challenges and nuances of manufacturing from a remote desk in the office.
The Ritual: On a weekly basis, engineering and leadership teams walk the production floor. The goal is to observe the process flow firsthand and interact directly with the production environment and the people working in it.
The Goal: To identify specific areas where the digital plan can be adjusted to better support the physical reality of production.
The Output: These walks generate actionable ideas for process improvement, grounded in direct observation.

2. The Context Sync

The Concept: Context drives effective autonomy. An operator who understands why a specific board is critical for a client can make better, more informed decisions at their workstation.
The Ritual: We hold regular synchronization meetings where high-level business strategy and client goals are shared with the Factory team. Conversely, production constraints and floor-level challenges are discussed with the Business team.
The Goal: To create a direct line of sight, connecting daily execution on the factory floor to the client’s ultimate success.

3. Priority Response (Internal Support)

The Concept: The Factory is the company’s operational engine. The role of the Office is to provide the necessary support, tools, and infrastructure to keep that engine running smoothly.
The Ritual: When the Production Line stops due to a missing file, an unclear instruction, or an IT outage, it triggers a high-priority alert or escalation.
The Goal: Office staff must treat any issue that blocks production with immediate urgency. Supporting production is a top priority.
The Metric: We measure and aim for rapid response and resolution times for any escalation that halts production.

The “One Company” Mindset

Ultimately, the “One Company” mindset requires collective ownership of both successes and failures.

The Old Approach: Pointing fingers—“Engineering designed it wrong” or “Production built it wrong.”
The Engineering Approach: Taking a systemic view—“The shared process we all use allowed an issue to occur. How can we improve the system itself to prevent this in the future?”

Recap: One Company Implementation Framework

Principle	Core Requirement	Key Metric / Mechanism	Mandatory Action / Ritual
One Language	Use unambiguous, universally defined corporate terms.	Terms defined in central systems (e.g., “Released”, “Draft”).	All communication and SOPs must adhere to system definitions.
One Scoreboard	Monitor company health via shared, global metrics.	OTIF, First Pass Yield, Customer Satisfaction Scores.	Use core operating dashboards for visibility and decision-making.
One Timeline	Synchronize Office planning with Factory execution.	Formal milestone reviews (e.g., NPI handoff from Design to Build).	Conduct collaborative transition reviews before work begins.
Gemba Walk	Ground Office plans in physical reality.	Direct observation of process flow and operator interaction.	Perform a weekly walk on the production floor.
Priority Response	Treat production-blocking issues with maximum urgency.	Rapid response and resolution time for line-stopping alerts.	Immediately escalate and resolve any incident halting production.