New devices, alien worlds

I wrote earlier about the way in which new devices with curved, round or irregular shaped displays would need new standards and vocabulary in order to describe the interactions with those screens and surfaces, partly because those surfaces are likely to be touch sensitive. It’s not an insurmountable problem, and the biggest issue may well be the politics involved in getting professionals from a variety of manufacturers and background’s to agree. That being said, there are authors who’ve developed a lot of time and thought to the description of novel geometries and I’d like to think that when standards committees meet, they’re going to channel some of the greats of science fiction.

Disc shaped, or round screens

An “always up”, round screen would make a lot of sense for tablets of the future (if Apple are reading this, I’d quite like royalties). We’d have to get used to seeing web-pages cut or scaled in interesting ways, but for many other applications including games and creative apps, there would be many advantages (not least because our eyes are “round” and much of our visual field is wasted with traditional screens). For movements around the screen or involving rotating, we have clockwise and anti-clockwise to fall back on, but what about moving to and from the centre of the screen. Perhaps the best known vocabulary for describing a surface of this type is found in the work of Terry Pratchett who coined four cardinal directions of “Hubward”, “Rimward”, “Turnwise” and “Widershins” to describe navigation on his Discworld. Turnwise and Widershins only really work for a disc already in motion, but hubward and rimward are the words we’re going to need the day we get an iDisc.

Rings, bracelets and wearable tech

As we start to see devices like the Smarty Ring, become more popular we’re going to be looking at non-visual interfaces that work with touch, motion or other forms of manipulation (the link here is to an excellent paper from the University of Glasgow... it’s well worth a look as it gives a good summary of what can be done and isn’t trying to sell anything). Describing the control of such a devices is going to be tricky, in part because the device can rotate around the arm, as well as being touched or manipulated by the voice. I couldn’t really find anything that worked for touch sensitive bands in professional or academic literature but an answer comes, yet again, from a fictional world. This time we turn to Greg Bear and his writing set in the fictional Halo universe. He uses turnwise and crosswise to describe movements around and across a band respectively and this could work when coupled with “left”, “right”, “clockwise” and “anticlockwise”. I initially toyed with the idea of using the geometry and layout of the human body to help with the descriptions, but realised that these devices may be worn on either arm by left or right handed.

Projected space

By projected space, I mean 3D environments created by devices such as Kinect, Google Glass, and the very Minority Report-esque Leap Motion controller. I feel that many of these systems will be dictated by the intent and application of the software and hardware being used, but it’s quite obvious that any directions being given will need a reference point. An example of this being done well can be found in the work of John G Hemry who tells tales of wars in space together with a spatial reference system he’s thought out that allows for ships to quickly orientate themselves in the 3D environment of a new solar system. Documenting a system that relies on the body for imput would not just need a way to describe the like this may well not look forward at all, as what we’re really talking about is whole body movement. The language and presentation of the documentation may borrow heavily from descriptions of other physical movements, whether that be those found in martial arts text books, reference works on magic tricks or even the Karma Sutra.

Answers on a postcard (or in the comments section) for what you think the biggest new interface will be, and how we could go about describing it.

Andrew

That was the year that was...

Thirteen is considered by some to be an unlucky number, so my first thought as I settled down to write was to wonder why. After a few minutes of pleasurable distraction (what did we do before search engines?), I’ve discovered that there are a lot of theories but no hard evidence to support one over another. So how was 2013 for us, good or bad?

Well, as with every small business, we’ve had our ups and downs – sometimes exacerbated by the fact that a family crisis (no matter how small) tends to affect every member of the business when you’re the same family! I’m not going to dwell on the negative, though... there isn’t a lot of that, and I’d much rather focus on the positive.

So, what happened in our world in 2013? Quite a lot, now I come to think of it! In no particular order:

• We changed the legal status of our business – we activated Clearly Stated Limited on 1 November 2013. The company had existed since Clearly Stated started, back in 2004, but had been dormant as until recently the advantages of trading as a company were negated by the extra administrative burden. Now, however, we are beginning to spread our wings a little, and the change in status fits with where we see ourselves going in the future.
• We presented at TCUK 2013 – both Andrew and I delivered sessions at our professional body’s annual conference, and both were well received.
• We delivered more writing skills training courses – both to local authorities and at a university.
• I dusted off my clinical knowledge to work on a health-related application.
• We received a SaBRE Certificate which acknowledges Clearly Stated's support of Andrew's reserve service.
• I developed a CPD framework for the ISTC.
• Andrew passed his first module on the Graduate Certificate in Technical Writing with the University of Limerick.

All things considered, that’s a pretty good year. 2014 is already shaping up quite nicely. We’ve made contact with a few people we’re looking forward to working with and are already planning conference attendance and milestones for the next phase of our development.

Alison

Keeping up-to-date...

Things change so fast in our field (technical communication) that it can be difficult to keep up. What can be even more difficult is providing some evidence that you’re at least making the effort. That’s why I’m pleased that the ISTC’s CPD framework is finally up and running. (I’m also pleased because getting it to this stage has taken an inordinate amount of my time over the last 18 months.)

So, aside from getting my life back, why am I so pleased?

Well, in line (I guess) with just about anyone who takes what they do seriously and want to do it to the best of their abilities, I am constantly learning. I don’t mean I’m constantly attending training courses – although I do some of that too – but that I work on a different project, find out how to use a new tool, come across a technique that someone shares... and I find I’ve learnt something really useful.

My problem, until now, was that although I knew I’d learnt lots of good ‘stuff’, put on the spot in an interview or when writing a covering letter for a job, I couldn’t always remember what I’d learnt when, or what the context was at the time. In short, I couldn’t tell a coherent story to support my application.

Now that’s not a problem.

I’m a Fellow of the ISTC myself – and although all our members have a requirement to keep up-to-date, I can now prove it. I have to maintain a CPD record to keep my Fellow status, which makes it all the more valuable to me.

And having to keep a record means that the information that was previously just swimming around in my head and had been absorbed into ‘normal working practice’ can now be accessed as discrete pieces of information and referenced.

You know what it’s like – you’re writing a covering letter to apply for a contract and you’re desperately trying to think how you can show you’ve met a particular requirement. Now instead of frantically trying to remember, I can just have a quick glance at my learning record instead.

Couldn’t I have recorded this anyway? Well, to be honest, I often did... but not to the same level, as it was only notes for my own use. Now there is a little more meat on the bones.

If I want to think of myself as a professional (and more importantly want others to do so), I need to start acting like one.

Alison

Mixed Messages

I don’t usually touch on politics in my blog posts – I believe it’s against policy – but I was struck by a recent article where our illustrious PM decided to link the quality of state education with the inability of many to find a entry level job on a production line. As a technical communicator, I think he’s wrong. My reasoning is based both on my own experiences in education and training, and my current professional practice.

I remember preparing for my GCSE English exams. Our English teacher received a missive from the exam board on the subject of ‘structured writing’. There was a whole section on the types of phrases we could use to compare and contrast arguments and introduce points of view, which our teacher dutifully read out to us. They became more florid the further into the list you progressed, perhaps reflecting the fact that a lower-grade student would only be expected to remember the first few. Right at the end was “there is a train of thought that runs...” – by this point the class was in hysterics. There was something about the way that our teacher chose to read that list that let us know it wasn’t to be taken too seriously. She finished with the staunch admonition that were we ever to use such a convoluted phrase to convey “others think...” she would hunt us down one by one.

There is, however, a train of thought that runs to the acceptance of such phrasing (it has taken me 15 years to work that into a piece of writing with an almost straight face). The people who hold this view were taught by the other type of English teacher: the ones who didn’t laugh and snigger at the directives being sent down from those who view having an education as having the ability to show off (or as it is called in the north of England, ‘ponce about’). The adherents of this doctrine write as floridly, passively and with as many synonyms thrown in as possible because they have been taught that this is how the educated communicate. (If you don't believe me, watch the tortuous pursuit of definition that is Prime Minister's Questions.)

Of course, this is how the ‘educated‘ tend to communicate. Lead engineers, managers, and those at CxO level (where x is some function of the business) generally communicate from within their own comfort zone, blissfully unaware that to those outside their circle they may as well be using a foreign language. The manager states “we must be flexible with regards to the future” when planning layoffs; meanwhile the employee is wondering when the new yoga classes are going to start. In another example, the lead design engineer has referred to the same binary function selector as a switch, toggle, selector and lever interchangeably within a single paragraph of emergency shut-down instructions... that are being read whilst the machine in question trundles towards a cliff edge. Both examples mirror political communication a little too well.

The real problem is that job seekers don't know exactly what they need to do to get the job they want because they aren't told in a way they understand. Therefore, the issue is not in the education and training of the many, but the education of the few who think their communications strategy is fit for purpose when attempting to get a message across different levels in society, organisations and processes. In many cases the problem lies with message and sender, not the befuddled receiver. This gap is why technical communicators exist. We work with subject matter experts and transform their message into something that the end user can understand.

Whilst my services as a professional communicator are a valuable commodity, I feel that on this occasion I can distil 25 years of experience as a learner, teacher and technical communicator to help the Prime Minister and anyone else who fancies being a politician or leader of men avoid some often identified pitfalls.

Answer the question being asked

You may be a leading expert on a particular subject, but when someone asks “what happens if I press the big red button?” your answer should go along the lines of “when you press the big red button, X happens.” Your audience do not want to know about why you think red is a nice colour, why X is such a favourable outcome, or how brilliant you were in suggesting to a colleague that they have their secretary open a bidding process to pay a large company – run by a family friend – to subcontract an electrician to install the big red button.

Think about the context of the recipient

I have an emergency bandage. The instructions are in 5 steps. Steps 1 to 4 deal with applying the bandage, and consist of big clear illustrations that can be read under a torch in low light. Step 5 deals with removing the bandage and consists of black text on a grey background. The pictures exist because when your mate is bleeding to death at 2 in the morning, you don't have time to read an essay. There are people in society who – for whatever reason – are bleeding out and are relying on you and your team to get the job done, and they really don't have time for anyone to wade through verbiage.

Short words are the best

This pithy piece of tech-comms wisdom stems from one of your predecessors, but it is true. I'd suggest that "yes" and "no" are two of the short words that might come in useful for answering questions. If people want your life-story or to know what you've been thinking about recently they can call you "Dave" and add you on Facebook.

Andrew