## Session II: The case for open and async

> [“The real risk isn’t openness; it’s opacity.”](https://open-and-async.com/q/risk-opacity/)

### Discuss

- When did two of us last solve the same problem separately because neither could see the other’s work? What did that duplication cost?
- If location stopped mattering, who could we hire — or keep — that we can’t today? And who have we already lost by pretending it does?
- Which of our decisions live only in someone’s memory or a closed meeting? What happens when that person is out, or leaves?

### Split the room

**For managers:** What’s one decision you made privately this quarter that would have been stronger with the reasoning in the open?

**For individual contributors:** Where would working louder — sharing progress and risks early — have caught a wrong turn three weeks sooner?

### Debate

“Working in the open just invites noise and second-guessing.” Make the case for keeping things private — then make the book’s case that opacity is the bigger risk.

### Try it

Take a recent decision and write the one-paragraph “why” behind it, as if a teammate in another time zone had to understand it cold. Optional: run `draft_decision_doc` from the [companion tools](https://open-and-async.com/#mcp).

---

From the [*Open & Async* book club guide](https://open-and-async.com/book-club-guide/#the-case).