2 ms·
I started an internal blog - using Confluence, because it was already a tool used by the company so I didn't have to convince anyone to install anything new. M
by simonw 7y ago
I started an internal blog - using Confluence, because it was already a tool used by the company so I didn't have to convince anyone to install anything new.
My goal was to introduce a culture of internal blogging at the company. I didn't really succeed on that front - I used my blog a bunch and a few people made a post or two - but I like to hope that if I'd kept at it for longer (I left the company) it would have started to catch on.
The reason I like internal blogs is that they release you from a lot of the pressure of writing more formal documentation. If there's a technique that I think is a good idea but that has not been established as an agreed best practice, writing it up in official documentation doesn't feel like the right thing to do. Writing it up on a personal internal blog as "as-of date X my opinion is that we should do Y" is always OK.
Likewise: writing documentation that later goes out of date can cause harm. Writing a blog entry that says "as of February 2020 this particular system worked in this particular way" seems much safer to me.
- Geeflow 7y agoI also think internal blogs are a great tool. But I also share your experience of how few people are actually using them. At my current company, it is the same thing: I wrote the majority of posts and a handful of people contributed a handful of other posts. I guess the 1% rule [1] applies to internal systems as well... [1]: https://en.wikipedia.org/wiki/1%25_rule_(Internet_culture) https://en.wikipedia.org/wiki/1%25_rule_(Internet_culture)