3.4 Meetings: Hygiene and Conduct

A meeting is a precision instrument. Used correctly, it cuts through operational complexity, aligns the cross-functional team, and accelerates decision-making. Incorrect utilization actively bleeds the organization of expensive engineering time and focus.

Operations are governed by a simple core principle: Meetings are solely for Interaction, not for Consumption.

A meeting must not be called merely to read a spreadsheet out loud (Consumption). A meeting should be called to debate the data, challenge the current status, and align on a specific narrative moving forward (Interaction).

The Gatekeepers: Core Prerequisites

Booking a “Working Meeting” is explicitly prohibited unless the Entry Criteria are satisfied.

Rule 1: No Agenda = Automatic Decline

• A calendar invite lazily titled “Sync” or “Touchbase” without a description is operational noise.
• The Baseline Standard: Every single invite must contain:
  1. The Objective: What is the specific goal? (Decide / Brainstorm / Align).
  2. The Agenda: The specific list of topics to cover.
  3. The Preparation: The direct link to the live Dashboard or Pre-Read document.
• The Rule: When a meeting invite lacks a clear agenda, all employees are officially authorized to decline it immediately.

Rule 2: The “Pre-Read” Requirement

• The Context: The first 20 minutes of an expensive meeting must not be spent watching a presenter read slides.
• The Standard: All data (Dashboards, Metrics, Proposals) must be sent asynchronously exactly 24 hours in advance.
• The Reality: It must be assumed that all attendees have already read the data. The clock starts immediately with Q&A, Debate, and Challenge. “The SMT yield dropped—why?” is a high-value meeting topic. “What is the SMT yield?” is a waste of corporate time.

In-Room Protocols: The Rules of Conduct

Once the door closes, strict rules of engagement apply.

Rule 3: No Tech (The Focus Law)

• The Context: Human multitasking degrades cognitive fidelity. Personnel are either contributing to the solution or reading email; doing both effectively is impossible.
• The Standard: In dedicated working meetings (Decisions/Brainstorms), laptops are closed, and phones are placed face down.
• The Exception: The designated Scribe (taking notes) and the active Presenter.

Rule 4: The Facilitator and The Scribe

Every working meeting must have two explicitly named roles before it begins.

• The Facilitator: This person owns the clock. They cut off circular debates. They ensure everyone, including the quietest technical expert, contributes.
• The Scribe: This person captures the formal “Decision Log.” They record exactly what the Outcome was and who owns the next action item.

The Status Update: Dashboard vs. Dialogue

There is a significant difference between passive “Reporting” (wasteful) and active “Aligning” (valuable). Status Updates are only valuable when they create an opportunity to challenge the data.

The “Dialogue” Rule:

• ❌ Bad Status Meeting: The Leader reads the dashboard out loud. The Team listens silently. (This should always be an email).
• ✅ Required Status Meeting: The Dashboard is visible. The Team actively debates the implications of the numbers.
  • The Manager: “The dashboard claims we are 90% done. I don’t believe it. Prove it.”
  • The Team: “Actually, we are hard-blocked on Component X. We need help right now.”
  • The Value: This interaction creates Direct Access to leadership and encourages intellectual honesty.

Meeting Archetypes (The Menu)

Only four specific types of meetings are permitted. Attendees must know exactly which archetype they are engaged in.

The Type	The Purpose	The Interaction Mode	The Required Output
The Decision	Select Option A or Option B.	Sharp Debate & Vote	The Decision Log (Option selected).
The Problem Solve	Generate engineering ideas / Unblock a system.	Brainstorm	Focused Idea List / Actionable Plan.
The Town Hall	Broad Status & Culture Alignment.	Broadcast + Deep Q&A	Shared Context / Clarified Direction.
The Retrospective	Analyze past failure or success.	Honest Feedback	Formal CAPA / Process Improvement.

Process Optimization

on Town Halls:__ Their ultimate goal is not merely top-down data transfer, but active Participation. Every Town Hall must reserve ≥25% of the total clock time for an open Q&A to allow the team to challenge leadership directly.

The Closure: Definition of Done

A meeting is only structurally “Done” when the required output is formally generated.

Rule 5: No Minutes = It Didn’t Happen

• The Standard: Tangible Action Items (Who does exactly What by exactly When) must be posted to the relevant Task Manager or Chat channel within 1 hour of the meeting ending.
• The Logic: When the verbal agreement is not written down in the system of record, it will be lost. The written log is the binding corporate contract.

---

Recap: Meeting Hygiene and Conduct

Parameter	Requirement	Value/Tolerance	Action
Agenda	Mandatory for meeting invitation	Contains: 1) Objective (Decide/Brainstorm/Align), 2) Topic list, 3) Link to Pre-Read	Decline invitation if absent
Pre-Read	Mandatory distribution of materials	Distributed 24 hours prior to meeting start	Meeting begins immediately with Q&A/debate
In-Room Focus	Technology restriction for working meetings	Laptops closed, phones face down	Exceptions: Designated Scribe & active Presenter only
Meeting Roles	Mandatory assignment	Facilitator (owns clock, ensures participation) & Scribe (captures Decision Log)	Required before meeting begins
Meeting Output	Formal recording of outcomes	Action Items (Who/What/When) logged in system of record	Within 1 hour of meeting end