bookmark_borderHow I use Twitter

In his closing presentation at the recent Technical Communications Conference, RJ Jacquez outlined how he uses Twitter as a way to communicate with the users of his product, and as a way to share ideas with, and learn from, other technical communication professionals.

There were several people at TCUK09 that used Twitter throughout the conference, sharing quotes, thoughts and ideas about various presentations and I eded up having a few conversations about why I use Twitter so I thought I’d capture my thinking here.

I have two Twitter accounts, one for personal use and one for professional use. The personal account is used for keeping up with people I know in social terms, and most of the messages are chatty, with the occasional link or photo. I find it a good way to keep up with people but I don’t rely on it so if I don’t check it for a day or so then it’s not something I lose sleep about.

My professional account is used to share my thoughts about either my current work or on various aspects of our profession, responding to things posted by other people, or tracking through the myriad of useful links that people share.

And that to me is one of the key reasons for using Twitter. It’s a filter, a filter of trusted sources, that constantly points out things I wouldn’t have found myself and where I can have discussions with my peers about things that interest me.

Our profession covers such a wide area that keeping up with the latest trends and discussions on the fringes can be nigh on impossible. Twitter offers me a way to keep in touch, to be part of the conversation about these things, and whilst it can be seen to be frivolous, the value to be gained outweighs the downsides.

However, like most social networking or social media services, you get out what you put in and when it comes to Twitter, you really need to try it to find out if you can benefit for it.

You can follow me on Twitter.

bookmark_borderNotes from Technical Communications Conference

These are transcribed from my hastily written scrawls throughout the day.

Smart Authoring for a Smarter Planet
The keynote presentation by Peter Angelhides

Set the tone well for bigger thinking about our profession, broadening the scope to the world wide consumption of information and how it can be processed intelligently.

Information for your products is useful both for existing users and for future customers. Don’t lock it away, let Google find it and then follow the links back, find other sources, other places where conversations about your product are happening. Information allows this, product usage doesn’t.

Everybody’s (not) doing it: is it really OK to keep ignoring document users?
by David Farbey

“Documentation is an asynchronous conversation” – Ginny Redish (from her book)

Training are usually separate from Docs, suggest either moving Training (we have!) or requesting debriefs after training sessions.

“Developer Mirror” is all too common – aka The Curse of Knowledge (you forget how much you didn’t know, so presume everyone knows things you know).

“The conversation needs to be focussed on what both parties want to improve”.

If you can write an article, you can write anything
by Kim Schrantz-Berquist

Applying Journalism techniques to writing
Using “5Ws & 1H” (Who what when where why and how) forces specifics and may end up change the subject of what you are writing about.

Inverted Pyramid – get the 5Ws and 1H into the first paragraph, top loading the information.

Use the “Stop reading test” to determine if it is working. How far down the page can you stop and feel comfortable you know the 5Ws and 1H?

Google Earth help manual uses hourglass technique, toploads information, then has area for user to choose what to do next, then has more detail/facts.

Good way to present Support Notes?

www.how-to-write.org

Paths to success: Networking and Contributing
by Linda Urban

Build your network and Make a contribution – these are the strings and glue of being successful.

Connection with people, conversations are where it all happens.

Visual Attention: A psychologist’s perspective
by Dr Chris Atherton

Attentionomics. Gestalt.

Extraneous cognitive load so less is more (see Nurnberg Funnel on minimalism in documentation)

Magic number is 4 (recent studies show), not 7 plus/minus 2!

We have two parts to the brain, one deals with audio processing, one deals with visuals. Both work at the same time (which is why we enjoy videos/webcasts so much), but quickly max out when we are only processing one type of information (which is why reading is tiring).

Without Hot Air
by Niall Mansfield

Discussed how information was presented in the book (which outlines real solutions for combatting global warming).

Book is available through Creative Commons to download.
Drafts were posted to blog to drive discussion. Aim was to share the information as it was public spirited content.

The secrets of Telepathy
by Justin Collinge

A double session covering ways to to communicate better by understanding how other people process information.

Filtering in effect – aural vs visual – McGurk effect, video on YouTube.

Looked at a variey of filters (aka meta-programming) including Direction (away from vs towards), Relationship (similarities vs difficulties) and Frame of Reference (internal vs external).

Audience of documentation will cover all types, yet we usually only write for one. Taking a set of instructions; it’s usually aimed at completing something successfully, but what of the people who like comparisons, or who want to make sure that something DOESN’T happen (troubleshooting info?)

Similarites – 70% of people start with these, emphasise these first then cover differences

Can write opening sentences which cover differences & similiarities, and ‘towards’ and ‘away from’ views – this matches the inverted pyramid writing style.

Future Vision of Technical Communicators
by RJ Jacquez

“Social media has redefined communication”

What makes an experience engaging? Accessible, Collaborative, Compelling, Easy to use, Personalised, Responsive.

Build experiences that engage your audience

Digital users are here (Grown Up Digital by Don Tapscott)

Socialnomics by Erik Qualman

Social networks have overtaken pron as the number 1 industry online.

SideWiki – comment on ANY website, no opt out. The conversation is happening now, whether you like it or not.

bookmark_borderThoughts on TCUK09*

Having had a few days to process my thoughts about the Technical Communications Conference I can confidently say that it is the best professional conference I have ever attended.

I’ll post up specific notes tomorrow, but I wanted to touch on some of the themes that seemed to be driven out of most of the presentations I attended. Now at this point I should make a confession, it’s about the presentation I gave on the Thursday morning (the second day) of the conference.

My presentation had a theme, a single word that I was focussing on, so throughout the first day, in all the sessions I attended, I was listening out for that word. That word didn’t appear in one session, and I had to push to get the word out of another of the speakers (the last of the first day).

I claimed that word appeared in all of the sessions I attended, it didn’t. Now, as far as confessions go, it’s not exactly earth shattering news but it’s important to me that I let you all know because, as I said in my presentation, if you are blogging you need to be honest.

The word I was looking for throughout the first day was “conversation”, and I was pleasantly surprised when I heard it crop up in the later sessions of the second day and I admit I was quite pleased when the closing speaker, RJ Jacquez from Adobe both mentioned my presentation and had a similar view to mine.

As for the sessions I attended, I don’t think there was one where I didn’t learn anything, even though there were a couple where I was asked to facilitate when I probably would’ve ducked out to chat to some vendors. It’s good that the speakers, whether well versed in public speaking or complete amateurs (like me), seemed comfortable and relaxed and really engaged with their audience.

And that for me is a good way to sum up the entire conference. I shudder to think just how much hard work went into organising the conference but from the smaller touches (the goodies in the hotel room), to the softer, informal approach that Paul and Rachel embody so well, really made a difference.

Given that our profession is both broad and deep, it was great to have other aspects around the fringes covered as well (cognitive psychology anyone?). All in all I think there was something for everyone, and the benefits of being exposed to other niche areas really made the conference worthwhile.

If you are in the UK next year, if you work in a profession either directly related to, or relatively related to, technical communications then I’d urge you to consider coming along next year. For me the best thing I’ll take away from the conference is the continuing conversation that is happening about our profession.

* #tcuk09 was the hashtag for the conference

bookmark_borderI am excited!

This evening I’m flying down to East Midlands airport and from there I’ll be making my way to Mickelover Hotel (near Derby) where I’m attending, and speaking at, the Technical Communications conference.

I’ve not done much public speaking with my last outing being a couple of years ago at a similar, smaller, conference and that seemed to go quite well so I’m fairly confident that I’ll be able to deliver a reasonably good presentation on my topic of choice which is, as it happens, about blogging.

I think I’ll be able to handle that, eh?

My slot is first thing on Thursday morning of the second day of the conference (graveyard slot much?) so I’ve time to run through it a couple of times yet but, overall, I think it’ll be alright. I’ll be posting it on my other blog on Thursday morning.

One added bonus to being in that part of the woods is that I’ll finally get to meet the Troubled Diva himself as well as SwissToni and Sarah, and to be honest I’m not sure which I’m more excited about, presenting at the conference or meeting Mike. Yay.

bookmark_borderNew Manager: How soon is *not* too soon to start changing things?

I recently received an email which asked:

Since my career seems to be following a path broadly similar to yours … I’d love to know what your experience was and any lessons learned.

Specifically Mark, who sent the email, asked a few questions:

  1. How do you take over as manager for a group of technical writers?
  2. How do you get better management buy-in (promise cheaper or faster docs?)?
  3. What are the first activities you should do (content audit, benchmarking?)?
  4. How soon is *not* too soon to start changing things?

I’ll break each question out into a new post, so without further ado, onto question #4.

How soon is *not* too soon to start changing things?
The compulsion to change or fix things that, from your point of view seem wrong or broken is natural. You wouldn’t be in the position you were in if you didn’t have that kind of mindset. However you must resist these initial urges!

A common suggestion, that I’ve seen elsewhere, is to wait at least 3-4 weeks before making any changes. That sounds like a sensible timeframe to me, providing that you use that time appropriately (see the rest of my posts in this series).

The first few weeks in any new job sets out your stall for the coming years. It can be very hard to change initial reactions so use the time wisely, tread carefully and make sure you set a level of expectation that you can manage. Communicate your ideas and thoughts, making sure to state that you are still getting to grips with things, make sure everyone knows that you MAY change things but that you are taking a measured and professional approach.

And, to be honest, that’s all I have to offer. Hopefully some of the things I’ve suggested over this series of posts is of some use. Many of them can be embellished and taken further, others might only be applicable in my own circumstance, but my belief is that as the manager of a technical communications team you are responsible for letting them do what they do best, whilst managing everything else around them. Technical Communications is still a widely misunderstood field, so a lot of your initial work will be educational, making sure everyone else in the company knows what your team has to offer, whilst proving you understand the restrictions and limitations within which they must work.

So, thanks to Mark for emailing me with the initial set of questions. If anyone else wants to chip in, the comments are open.

bookmark_borderCherryleaf Survey

Cherryleaf will soon be publishing the results of their recent survey of Documentation Managers* and, having skimmed through a preview, the main thing that leaps out at me is that the field of Technical Communications in the UK remains as diverse as ever in many respects, yet completely the same in others, and none of that is a huge surprise.

Whilst we all may use different tools and approaches to our work, we all feel under the same constraints of time and resource. However the results do throw up a couple of issues and, as one of the participants of the survey, I thought I’d expand a little on one of those.

The survey hints at two issues:

  1. “The documentation teams generally continue to use authoring tools exclusive to the team … Content from 3rd parties, in most cases, needed to be … imported into the authoring system.”
  2. There was little evidence of any moves toward a company-wide approach to sharing and managing intellectual content.

I don’t think the first is a contentious statement but what interests me is the phrasing. The implication is that technical writing teams are seen as (or see themselves as?) content consumers, areas of the company into which content is lost to proprietary tooling. Obviously we publish a lot of content but perhaps we are a little too guarded of the information we collate?

I’ve never had an issue sharing information, regardless of state, as long as the appropriate caveats are in place. Information is meant to be shared, so the more of it we do, the better. In my opinion.

More interesting is the second point around the lack of evidence of company-wide information management. This is something I’ve been working on with key members of other areas of our company, and from previous experience it’s usually the technical writing team that takes a lead here as we gain the most benefit from having a good information management solution in place.

That may boil down to a document management system (from ad-hoc to access controlled repositories), or even a content management system, but ultimately the benefits are applicable across entire organisations. I’m lucky in that there are a couple of people who see the benefits and so it’s much easier to drive adoption and cooperation across the organisation, but even if that weren’t the case, and in the current climate, it may be something you should look into and start to drive forward yourself.

The survey results are, like any survey, a thin sample of our profession in the UK, but it’s great to have that information available. I’ve already spotted a few things that I can use in discussions within my own company, and there are plenty of common themes and ideas that can be carried forward to help improve our team.

So, well done Cherryleaf, I’m sure it wasn’t an easy process but I certainly think it was well worthwhile.

* A coverall title that encompasses anyone responsible for a team of technical writers.