Category: Work

It was only back in December that I pondered this but with the news that Google Reader is to shut down I find myself revisiting some of those choices.

I still use Google Reader heavily, I consume it mostly through the website itself and via Reeder on my iPad, so it’s annoying that they are pulling this service.

But, as the adage goes, you get what you pay for, so I find myself, once again, revisiting the ‘what am I willing to pay for’ line of thought.

There are a few alternatives to Google Reader out there, I’ve tried some myself in the past, and already the tech blogs are offering their ‘best alternatives to’ posts.

But for me, the new consideration has to be whether I have the option to pay for the service with the hope that it offers a level of protection against the service disappearing on me. It’s either that or roll my own, or perhaps a 3rd party option like Fever (I have a server, and it is an option I might look at when I have more time, i.e. probably never!).

So far, of the many suggestions, the one I’ll be trying is NewsBlur precisely because it has a ‘paid for’ option.

As well as the specific impact of Google closing Reader to those that use the service, the fact that a company as rich as Google is (rightly) shutting down services that it sees no value from is a trend that is likely to start to pick up momentum.

Instagram prompted my original post on the “Going Paid” trend, how long before FaceBook push that application behind a paid for subscription?

Time will tell how this trend will pan out, but one thing remains constant and that’s the ever shifting nature of social media applications and their usage models.

A new year, a fresh challenge.

I’ve been working in the Technical Communications field my entire career. From those first days, stumbling my way around FrameMaker 4 with only a vague idea of what I should be doing (and largely using the FrameMaker User Guide as a sample of both approach and layout) to my current incarnation as Product Information Manager which involves running a team of 6 technical writers, looking at what other services we could offer to other parts of the (now) global organisation I’m part of, not to mention running a developer community website and generally advocating a product view wherever possible.

Actually, make that my previous incarnation.

As of today I’m changing roles, with a new job title of Product Operations Manager.

I’ll be working within the Product Management Team dealing with operations issues, planning and so on, and generally helping the Product Managers, and Senior Architects do their day jobs (the phrase ‘herding cats’ has been used on more than one occasion so far).

It’s very exciting, a little bit scary (in a good way), and a big step out of my comfort zone of technical communications. Whilst the principles of managing a team with multiple deliverables and differing focus areas is something I’ve been doing for a while, it’s good to have a new challenge.

The new role will take me away from technical communications, and whilst I’ll still retain a passing interest I know myself well enough that it’s only a matter of time before I lose track of developments and trends altogether. I am a sucker for new things!

I’m not sure what that means for this blog, or my other interactions with the technical communications community, but I’ll figure that out in good time.

Meanwhile, I’ve got a job description, a new boss, new teammates and a whole new world to get my head into and it’s all kicking off this week. Hence why I’m sat in a hotel room in Sunnyvale writing this blog post.

Anyway, first things first.

Breakfast.

One of the challenges the team will face this year is how to coordinate the creation of product documentation with geographically dispersed teams, across different product lines.

At present we have engineering teams in Glasgow, Belfast, Limerick, Jakarta, Sunnyvale CA, and Bedford NH, building four products and maintaining five other legacy applications. Currently we have six technical writers in Glasgow and one in Belfast. Initial assessments suggest there is a bit of a resourcing gap (a separate issue I’m dealing with) but beyond that the main challenge will be figuring out how to best work with these disparate teams.

I have asked this question in a couple of places and had some excellent responses. Some cover things we had already considered but there were some gems borne of real life experience that I was lucky enough to have shared with me. Many thanks to Tom Marshall, David Farbey, Cheri Mullins, Larry Kunz, Alan Bowman, and Kay Winter and others for their suggestions.

First things first though, and it will be important to discuss and agree on responsibilities, tasks, and roles. Naturally there will be a level of autonomy, so it makes sense to have sensible agreements on what issues require escalation and so on. Part of these early discussions will also need to include tooling agreement, writing styles and output formats. Ideally these can just be extend from what the team currently uses but that will have an impact on both sides.

The timezone is an obvious issue which could have a dramatic impact on communications between the teams. Case in point, the teams in Bedford and Jakarta have a 12 hour difference! So one of the first things we will need to do is consider, as we won’t have the luxury of immediacy, is a ‘rules of engagement’ or contract between teams as to how we will correspond, talk, meet and share information. Nothing too formal, but setting out expectations will do no harm. For example, when sending out an email should you expect an acknowledgement? Or should everyone have ‘read receipts’ enabled?

Some of the challenges we may face we already have solutions for; we use Google Docs for collaboration, we have conference lines ready, our engineers use a common JIRA install.

Thankfully there are numerous technologies that can help us with communications:

• Everyday – Instant Messaging – for a quick question or two, and as a way to see who is available (and how you are working with), IM is a useful tool. Add in file sharing and it becomes a little more powerful.
• Information Sharing – WIKI and Google Docs – for collaboration we’ve had good success with Google Docs, but there is no reason a WIKI couldn’t fulfil the same role.
• Meetings – Skype or Google Hangouts – Skype nicely doubles as an instant messaging app, which also allows you to send files and of course you can host conference calls there. Recently I’ve seen some friends have success with Google Hangouts (part of Google+) which, as most laptops come equipped with a webcam these days, might be a good option too.

Not to forget the trusted old telephone! Ideal for a 5 minute catchup every day or so.

And, of course there will also need to be face-to-face meetings on a regular basis to make sure the technical writers feel part of the team, that includes organising social activities as well.

Other suggestions I heard, and which are worth heeding:

• Regular conference calls – Make sure these have an agenda and that everyone has prepped beforehand to maximise usefulness.
• Access to latest builds of the software – in our office we can checkout the latest build of the code any time we want, no reason remote technical writers can’t do the same.
• Be sensitive to cultures, both professional practices and social niceties.
• Adjust for time zones.

There are many pitfalls ahead and whilst I have great confidence we will figure them all out, obviously the more we can spot up front and negate, the better (and cheaper) the end solution will be. As ever, I have the advantage of working with smart people so I’m confident it will work, once we figure out exactly how.

The festive season is upon us, cards have been posted, presents have been bought, and in a couple of hours I’ll head home, leaving work behind until early January.

2012 has been an interesting year.

We started the year with a challenge, one of making the information we produce ‘findable’. Cutting across more than 20,000 topics of information, it was always going to be a big project, particularly as we still needed to keep up with product development. As the year draws to a close the final pieces of this mammoth project are falling into place and should, fingers crossed, be launched in the first couple of weeks in January.

From my viewpoint, it’s been an excellent example of giving people the space to do great things. I’ve not interferred much with this project, gently pushed it when it was needed, made decisions when required but by and large left the team to get on with it. The results are looking good.

Of course plans were impacted when the company I work for was merged with KANA software. Thankfully it was, for us, a mostly seamless experience. The day to day activities of the team haven’t changed (yet), but there has certainly been a lot more for me to pick up as the requests for documentation resource started to come in from other parts of the organisation. We are still figuring out how best to provide a service but it’s already looking like we will need to hire to backfill some gaps in other geographies.

Elsewhere I finally managed to get the new ISTC website launched, and have since enhanced it in a few places, adding in new Area Group pages, and generally beefing up the functionality in the background. Plans are coming together for the next set of changes so keep an eye out for those.

So, plenty to keep me busy in 2013, and that’s without covering off the building of a new community website at work …

One highlight for me has been getting back into the blogging habit here and generally feeling a bit more excited about my profession, hopefully I will continue to get a lot of value from sharing my thoughts here in the future!

That said, I’m off on holiday now but will be back in the first week of January. If you celebrate it, have a very Merry Christmas, and all the best to you all for 2013, thanks for reading!!