Take a Break! The Trip Report
Rest stays invisible until someone puts it on the record, and the leader goes first
Nobody believes the vacation policy. They believe what they see. When people leave quietly, answer email from the beach, and slip back in on Monday hoping no one noticed they were gone, the real policy is obvious: time off is something to apologize for.
Charles, Igor, and I have been talking about intentional downtime, taking a real break to recover physically, mentally, and relationally, especially in times of crisis, when rest is the first thing we cut and the last thing we can afford to lose. Out of that conversation came a practice worth stealing: the Trip Report.
The idea comes from Bill Campbell, by way of Trillion Dollar Coach. Campbell suggested the management team at Google share details of their travels with one another, and the point was never the travel. It was trust. People who know each other as humans instead of job titles work through hard problems faster and disagree without drawing blood. A few minutes of vacation stories turns a room full of functions into a team.
The mechanics are simple. When you come back from time off, write a short report and share it with your team. Where you went, even if "went" means your backyard. What you did. A photo or two. One story that made the break worth taking. What you deliberately ignored while you were gone. Five minutes at the start of a meeting or a few paragraphs in the team channel. That's the whole thing.
It sounds trivial. It isn't. On most teams, rest is invisible. You see the person before they leave and after they return, and the gap in between gets treated like a rounding error, or worse, a liability. Silence teaches people that downtime is vaguely shameful, so they take less of it and hide the rest. A Trip Report does the opposite. It puts recovery on the record. It says this person fully disconnected, came back sharper, and isn't embarrassed about any of it. Every report shared makes the next one easier to write, and you start learning things about your teammates that would never survive a standup agenda.
If you lead the team, you go first. Nobody takes the "please use your PTO" email seriously when it arrives timestamped 11:47 PM on a Saturday. Your calendar is the policy. Take the real break. No laptop. No quick check-ins. Then come back and give the report. Show the team what disconnecting actually looks like, and that the place survived without you. That last part is good for you, too.
Crisis makes this harder and more necessary at the same time. When everything is on fire, grinding feels virtuous and rest feels like theft. That math is backwards. Burned-out people make expensive mistakes, and teams with no trust reserves fall apart under exactly the pressure you were trying to outwork.
Take the break. Write the report. Share it. Then count how many days it takes before someone else on the team books their own.
What did you think of this essay?