WHY THIS EXISTS

Communication determines whether a team succeeds or stalls. Most operational failures come from unclear messaging, missing notes, or information not reaching the right person.
This manual defines the communication standards required for any functional team.

---

1. COMMUNICATION IS A TOOL

Communication is not casual conversation.
It is the transfer of information without distortion.

Poor communication leads to:
- Missed tasks
- Repeated mistakes
- Slipped deadlines
- Confusion
- Frustration

Strong communication creates:
- Predictable outcomes
- Faster solutions
- Shared understanding
- Real accountability

---

2. WRITE EVERYTHING DOWN

If it isn’t written down, it doesn’t exist.

Writing:
- Captures decisions
- Clarifies expectations
- Prevents misunderstandings
- Records who agreed to what
- Keeps projects on track

A meeting without notes is not a meeting. It is just talk.

---

3. USE W5 (WHO, WHAT, WHERE, WHEN, HOW)

Every message, task, and update must include:

Who is responsible
What needs to happen
Where it applies
When it should be done
How it will be handled

If a communication is missing one of these, it is incomplete.

Example:
Bob — repair the proximity system in the ordnance storage room. Estimated one day. Half-day buffer before project value is lost.

---

4. MEETINGS REQUIRE DOCUMENTATION

Meetings are only productive if they create a record.

Every meeting must include:
- Notes
- Action items
- Owners
- Deadlines
- A written summary sent afterward

If participants leave without documented tasks, the meeting accomplished nothing.

---

5. USE DIRECT COMMUNICATION PATHS

Information must go straight to the person who can act on it.

1. Speak to your lead.
2. If there is no response, escalate to their lead.
3. If that fails, escalate again.

Escalation is not disrespect.
It is required when the system stops working.

Do not:
- Gossip
- Hint
- Vent sideways
- Assume someone else will communicate for you

Say the needed information to the responsible person, clearly and in writing.

---

6. BE SPECIFIC

Do not communicate in vague or general terms.

Vague:
“Something is wrong.”

Clear:
“The proximity sensor in the storage room fails at a 2-foot distance. Happened twice today.”

Specificity prevents guesswork.

---

7. KEEP MESSAGES SHORT AND DIRECT

Every message should contain:
- The point
- The W5
- The expected action

Example:
Valve 4 is leaking 0.3 PSI/hour. Line closed. Logged at 10:35. Recommend replacement today.

Short. Clear. Actionable.

---

8. REDUCE EMOTIONAL NOISE

Urgency can be communicated without emotional escalation.

Bad:
“This is a disaster and I’m overwhelmed.”

Good:
“This stops production and requires immediate attention.”

Facts create action.
Emotion creates confusion.

---

9. ATTACH OWNERSHIP AND DEADLINES

Tasks must have:
- A designated owner
- A deadline

Without these, nothing gets done.

Bad:
“Someone handle this.”

Good:
“Alex is assigned. Deadline 4 PM.”

Ownership creates accountability.
Deadlines create movement.

---

10. PROVIDE SUPPORTING EVIDENCE

When reporting a problem, include:
- Photos
- Screenshots
- Error messages
- Logs
- Timestamps
- Observations

Evidence removes debate and speeds up solutions.

---

11. CLOSE THE LOOP

A task is not complete until it is formally closed.

A complete loop:
1. Assigned
2. Performed
3. Reported
4. Documented

Never assume people know you finished something.
State it clearly in writing.

---

12. STANDARD OPERATION PATTERN

Use this pattern for every task or issue:

1. Identify the problem
2. Write it down
3. Apply W5
4. Assign an owner
5. Set a deadline
6. Communicate with the correct person
7. Document progress
8. Close the loop

This structure removes confusion and creates predictable results.