## Session IV: Working in the open

> [“Decisions without URLs get relitigated forever.”](https://open-and-async.com/q/relitigated/)

### Discuss

- Which of our decisions, processes, or docs don’t have a URL? How far are we from losing them to one departure or one retention policy?
- Who’s the person everyone DMs the same three questions? What would it take to write those answers down once, where people can actually find them?
- When did we last sit on a small problem — hoping it would sort itself out — until it got expensive? What made surfacing it feel costly at the time?

### Split the room

**For managers:** Do you reward the people who surface bad news early, or the ones who quietly fix things and never mention the risk? What does your team believe the answer is?

**For individual contributors:** What are you working on right now that no one would know about unless they asked? Where would you post a progress update so they wouldn’t have to?

### Debate

“If I share every rough draft and dead end, I’ll just look disorganized.” Argue it. Then argue why an ugly working URL beats a beautiful deck.

### Try it

Take the three questions people ask you most. Write each answer once, put it somewhere linkable, and send the link next time instead of retyping it.

---

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