A couple of years ago, I asked a group of experienced developers if engineering blogs had ever made them want to join a company.
I received an interesting response from someone who worked at Incident.io, “We see so much ROI that we run monthly content days for the entire company, getting everyone to draft posts we publish gradually over the next month.”
I recently dug into this and found the CEO Stephen Whitworth had written a post about the team’s monthly content days. This takes place once every 20 days—effectively 5% of each person’s time. Stephen highlights some of the benefits:
- Greater awareness (every company writes their future one post a time, and Incident.io went viral a couple of months ago at Hacker News)
- Improved communication (including clarifying thinking—*ahem!*)
- Better syncing across different teams
While I’ve helped lead workshops to generate ideas, as well as office hours to help individuals work on ideas, I would definitely be interested in helping facilitate sessions more like this—something like a hackathon, but for writing.