When we checked in with our TC Dojo Mastermind members, they asked us for a place where they could collaborate with each other outside the regular meetings. Until this point, we had a wiki where everyone could collaborate, but it just wasn’t meeting their needs. So, earlier this week we stood up a community forum site to make it easy for Mastermind members to share their knowledge and experience.
Continue reading New Forums available to Mastermind Members
We usually talk about Style in terms of content structure and layout, but this time I wanted to talk with you about our style. Specifically, our style of service.
I was recently on a mentoring team call with one of our newer customers and they said something that really struck me: “Boy, you guys [at Single-Sourcing Solutions] really are different than the others. This is great! This is what I have always wanted, someone to show me.”
For me, there could not have been a higher compliment! After over a decade in business, it’s only natural that I would take a nostalgic look back. When I first started Single-Sourcing Solutions, I knew one thing. I wanted to do things different. To buck the traditional consultancy and develop a service that focused on building a stronger community. Continue reading It’s a question of Style
In the TC Dojo last week we found out: Your company is at risk of debilitating lawsuits that, in the worst case, can put you out of business. Joe Devney, forensic linguist, editor, non-fiction writer, and previous STC chapter chair shared stories of companies who delivered insufficient, poorly-written documentation or who failed to provide any documentation at all.
First, he shared the foundation and statistics for potential risks of businesses who skimp on documentation. Then he told real-life stories.
Now, I’ve seen Joe speak before at a local STC chapter meeting. I always learn something new about how to produce good technical documentation. Usually that moment of enlightenment comes out of the shock of something I’ve just heard him say with regard to someone else’s content. (Something that usually triggered a major catastrophe for the company in question.)
Today was no different. Continue reading What happens when you skimp on documentation?