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. Used incorrectly, it actively bleeds the company of expensive engineering time and focus.
In this company, we operate on a simple core principle: Meetings are solely for Interaction, not for Consumption.
Do not call a meeting merely to read a spreadsheet out loud (Consumption). Do call a meeting to debate the data, challenge the current status, and align on a specific narrative moving forward (Interaction).
The Gatekeepers: Core Prerequisites
Section titled “The Gatekeepers: Core Prerequisites”You are not permitted to book a “Working Meeting” unless you satisfy the Entry Criteria.
Rule 1: No Agenda = Automatic Decline
Section titled “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:
- The Objective: What is the specific goal? (Decide / Brainstorm / Align).
- The Agenda: The specific list of topics to cover.
- 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
Section titled “Rule 2: The “Pre-Read” Requirement”- The Context: We do not spend the first 20 minutes of an expensive meeting watching a presenter read slides.
- The Standard: All data (Dashboards, Metrics, Proposals) must be sent asynchronously exactly 24 hours in advance.
- The Reality: We assume everyone in the room has already read the data. We start the clock immediately with Q&A, Debate, and Challenge. “I see 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
Section titled “In-Room Protocols: The Rules of Conduct”Once the door closes, our rules of engagement apply.
Rule 3: No Tech (The Focus Law)
Section titled “Rule 3: No Tech (The Focus Law)”- The Context: Human multitasking is a myth. You are either contributing to the solution, or you are reading email. You cannot do both effectively.
- 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
Section titled “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
Section titled “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)
Section titled “Meeting Archetypes (The Menu)”Only four specific types of meetings are permitted. You must know exactly which one you are attending.
| 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. |
Note: 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
Section titled “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
Section titled “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.
Final Baseline Checklist
Section titled “Final Baseline Checklist”| The Requirement | The Standard | Action if Failed |
|---|---|---|
| The Agenda | A Clear, Stated Objective | Decline the invite. |
| The Pre-Read | Sent 24h in advance | Mandatory Silent Reading (First 10 mins). |
| Status Update | Active Interaction | When there is no Q&A/Debate, cancel and send an email. |
| Town Hall | Must Include Open Q&A | Direct access to leadership is mandatory. |
| The Output | Action Items Assigned | Meeting is invalid. A re-do is required. |