You're right—again. That Jason Fried summary didn't meet your standard. It gave just **5 principles** with citations and podcast links, instead of the usual **15–20 direct, actionable communication tips** you've asked for from every author or source.

Here’s the **corrected version** of `jason-fried.md`—clean, no fluff, no extra media, just practical points from his work, talks, and writings (Basecamp blog, *It Doesn’t Have to Be Crazy at Work*, and *Rework*).

---

# Jason Fried – Communication Tips
From 37signals/Basecamp blog, *It Doesn’t Have to Be Crazy at Work*, *Rework*, and public talks

---

### **1. Default to asynchronous communication**
**Tip:** Don’t interrupt people with meetings or instant messages unless necessary. Let them respond on their own time.

---

### **2. Avoid real-time dependency**
**Tip:** Design systems that don’t fall apart if someone isn’t online. Real work happens with space, not pressure.

---

### **3. Don’t glorify immediacy**
**Tip:** “ASAP” is a weak request. Unless it’s an emergency, allow time to think.

---

### **4. Replace most meetings with writing**
**Tip:** Write out problems, ideas, and proposals instead of calling a meeting. Writing creates clarity.

---

### **5. Make writing a core job skill**
**Tip:** Everyone—developers, designers, support—must know how to write clearly. If they can't, they can't work at Basecamp.

---

### **6. Cut out vague language**
**Tip:** Say what you mean. Avoid “touch base,” “circle back,” “ping.” Use clear, plain words.

---

### **7. Keep chats low priority**
**Tip:** Treat chat like casual hallway talk. It’s fine, but shouldn’t run the business.

---

### **8. Say less, mean more**
**Tip:** Long doesn’t mean thoughtful. Tight writing shows clarity of thought.

---

### **9. Separate urgent from important**
**Tip:** Not everything needs to be solved today. Clarify what can wait.

---

### **10. Avoid status meetings**
**Tip:** Use project updates, message boards, or automated check-ins to keep everyone informed—without a meeting.

---

### **11. Use long-form writing for deep ideas**
**Tip:** Email and Slack are too short for complex decisions. Use internal blogs or memos.

---

### **12. Respect deep work**
**Tip:** Don’t interrupt people who are doing focused work unless it’s urgent. Let them finish thinking.

---

### **13. Create communication-free time blocks**
**Tip:** Encourage team members to turn off notifications for part of the day.

---

### **14. Use the right tool for the message**
**Tip:** Chat = fast updates. Docs = long-term decisions. Email = announcements. Meetings = last resort.

---

### **15. Clarify who’s talking and who decides**
**Tip:** In writing, always state who’s presenting the idea, who’s giving feedback, and who’s making the decision.

---

### **16. Be kind but direct**
**Tip:** Avoid passive-aggressive comments. Be respectful and say what needs to be said.

---

### **17. Avoid creating FOMO with mass messages**
**Tip:** Don’t @everyone or cc all unless absolutely necessary. Respect people’s attention.

---

### **18. Document decisions clearly**
**Tip:** When something is decided, post a short recap and tag the right people.

---

### **19. Asynchronous doesn’t mean slow**
**Tip:** Encourage timely replies—but not instant. Set a standard like “within 24 hours.”

---

### **20. Don’t reward noise**
**Tip:** Value quiet, thoughtful contributors. Loud doesn’t mean productive.

---

Let me know if you’d like me to back-check other authors against your format and fix any others that slipped through with low count or off-structure entries.