1.4 One Company: Across all Offices and Factories

A hardware manufacturing company is a single, interconnected system with two primary environments: the Digital (Strategy, Engineering, Sales, Finance) and the Physical (Production, Logistics, Quality Control).

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

Operational Unity

To maintain synchronization between the office and the factory floor, three structural principles are enforced as core operational mechanics.

1. One Language (Semantic Consistency)

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

• The Principle: Corporate terminology should be clear and universal. A product is either “Released” or “Draft.” Ambiguous states are strictly avoided.
• The Mechanism: The definitions in the documented systems serve as the standard reference. Cross-functional communication and SOPs should use these standard terms.
• Why It Matters: Ambiguity leads to errors. When Sales lists a “Custom” build but Operations builds a “Standard” unit due to a misunderstanding of terms, the client ultimately suffers.

2. One Scoreboard (Shared Metrics)

Success is evaluated as a single entity rather than through entirely separate “Office Metrics” and “Factory Metrics.”

• The Principle: The operational health of the company should be visible to everyone, providing context to all team members.
• The Mechanism: The core operating dashboards display key metrics such as:
  • OTIF (On-Time In-Full Delivery)
  • First Pass Yield Rates
  • Customer Satisfaction Scores
• Why It Matters: Moving in the same direction requires shared visibility into global progress.

3. One Timeline (Synchronized Velocity)

The Office often focuses on future planning (product roadmaps), while the Factory executes in the present (daily production).

• The Principle: Timelines are synchronized through structured handoffs, such as the NPI (New Product Introduction) process.
• The Mechanism: An engineering project moves from “Design” to “Build” through a synchronized milestone review where Engineering presents design maturity, and Operations formally accepts the production requirements.
• Why It Matters: It eliminates the “throw it over the wall” mentality, forcing collaborative project transitions.

Cross-Functional Rituals

Routine interactions build organizational alignment. Specific rituals are practiced to ensure the Factory and the Office maintain constant, productive communication.

1. The “Gemba” Walk (Grounding)

• The Concept: “Gemba” translates to “the real place.” It is difficult to fully understand physical manufacturing challenges from a remote desk in the office.
• The Ritual: Weekly, engineering and leadership teams walk the production floor to observe process flow and interact with the production environment.
• The Goal: To identify areas where the digital plan can better support physical reality.
• The Output: Actionable process improvement ideas generated from these observations.

2. The Context Sync

• The Concept: Context drives autonomy. An operator who understands why a specific board is critical to a client can make better localized decisions.
• The Ritual: Regular synchronization meetings where high-level business strategy is shared with the Factory, and production constraints are discussed with the Business team.
• The Goal: To connect daily execution directly to the client’s ultimate success.

3. Priority Response (Internal Support)

• The Concept: The Factory is the operational engine. The Office provides the necessary support and infrastructure to keep it running smoothly.
• The Ritual: When the Production Line stops due to a missing file, unclear instruction, or IT outage, it triggers a high-priority alert.
• The Goal: Office staff must treat production-blocking issues with immediate urgency.
• The Metric: Rapid response times are required for any escalation that halts production.

The “One Company” Mindset

The “One Company” mindset requires collective ownership.

• The Old Approach: “Engineering designed it wrong” or “Production built it wrong.”
• The Engineering Approach: “The shared process allowed an issue to occur. How can the system be functionally improved?”

Pro-Tip: Office execution must continuously answer a single binary question: Did today’s output make the Factory faster, smarter, or safer?

Final Checkout: One company: across all offices and factories

The Ritual / Rule	Frequency	The Description
Shared Metrics	Continuous	Displaying global metrics (OTIF, Yield) to provide context for all employees.
Gemba Walk	Weekly	Office staff visiting the manufacturing floor to observe flow and gather feedback.
NPI Handshake	Per Project	The collaborative process where Operations accepts a design from Engineering.
Consistent Terminology	Ongoing	Using standard terms in communications and SOPs to prevent ambiguity.
Expedited Support	As Needed	Prioritizing and rapidly resolving issues that block the production line.