Doing Well by Doing Good

In the late 1930’s, two significant political figures discovered new technology.

At the time, the new technology was called Radio. And both of these political figures discovered, pretty much in parallel, its power and influence.

One of these figures was Nazi Propaganda Minister Joseph Goebbels.
The other was New York City Mayor Fiorello La Guardia. Continue reading “Doing Well by Doing Good”

Cherries as Metaphor

At our property in the Languedoc region of France, we’ve had a bumper cherry harvest this year. Seems like it will be an excellent year for fruit in general. I hope so, because the veggies are in desperate shape. Some of our onions are having near-death experiences, for example. The problem with conference season is – you don’t get to work your vegetable garden.

But I digress – back to the cherries. Every year, as I pick the handsful of glorious, abundant cherries, I thank the birds for staying mostly up high.

Low Hanging Fruit
Low Hanging Fruit

Cherry picking, of course, is a time honoured art. We cherry pick through bargain bins at our favourite stores. We cherry pick the best ideas dreamed up by our colleagues. We cherry pick those parts of a political philosophy that are convenient to our world view. Etc.

Anyway, the birds – they get the ones I can’t reach, or won’t climb to, anyway. I go for the low-hanging fruit.

A few years ago, right around cherry picking time, I was telling a few of my colleagues much the same story, and mentioned that I go for the “low hanging fruit.” I then added, “Isn’t it interesting, how a business expression can be applied to a natural activity?”

No one laughed.

I Keep Thinking…

…about all this communication stuff:

  • I keep thinking about how information architects don’t like to be called UX designers. “IA is so much more,” they say. The “more” they’re talking about includes content. Not Lorem Ipsum, but real content. Many IA’s think of themselves as content strategists, too. They probably are. In fact, I think IA and CS are interlocking, interdependent parts of a single, holistic process – whether done by one person or a team.
  • I keep thinking about how Map should be an element used on the publishing side of DITA, not the authoring side. Let’s rename Map to Container (that’s what it is) and then a Map could really be one: you could map a layout out on a graphic of a page or screen of your publication, and fill it with DITA elements: topics, concepts, and the newly named containers. Using these graphical elements, you could have text flows just like in old fashioned desk top publishing programs, and you could control the layout and make it pretty – removing one of the most common criticisms of working with XML.
  • I keep thinking how I really want to do it all myself. Not because I don’t like teamwork, not because I’m jealous of others’ competencies, but because I love all this stuff so much, I just want to have the fun of doing it all. Silly of me, I know.
  • I keep thinking how technical communication is a lot like playing the piano. Not just because you need to make your fingers work a keyboard in both cases, but also because, as you develop your skill and hone your craft, you become aware that you are working with subtleties that no one other than a few other specialists in your field would ever be aware of. Quality assurance people would say that this is “too much quality” – you should provide just as much as the customers ask for, and not a jot more. But we do this, every day, even though we don’t really get paid for it, and users do not – at least consciously – notice. Not only that, I encourage everyone to keep doing it.
  • I keep thinking that everything is connected. I’d better quit it, because in the end, it means thinking about the entire, infinite, exquisite universe – makes my head ache.
  • Yeah, but I keep thinking that the only really valuable skill in this age is the ability, just exactly, to make connections between things where seemingly none exists.
  • I keep thinking that one day, we’ll discover basic principles of electronic networking and break through to achieving the wonderfully facilitating type of many to many communications environments we used to have on The Source back in 1985.
  • I keep thinking that Ted Nelson was right. About just about everything.
  • I keep thinking that the more means we have to communicate, the more we seem to be throwing words and preconceived ideologies at each other like weapons.
  • I keep thinking about silence.

Why Isn’t It?

In 2009, I delivered a short, light-hearted keynote address to the STC France annual conference, entitled, It’s Not in the Job Description. This post answers that presentation with a question: Why isn’t it there? What is it that we really do, anyway?

Defining Our Profession

I’m indebted to Mark Baker for his post, The Web Does Minimalism, which I recommend to everyone, and for his response to my election post on STC’s business model. His remarks crystalized for me a number of things I’ve been reflecting about over the last few years.

We used to have a pretty straightforward idea of what we did. We were technical writers, and we wrote manuals. We provided the bridge between engineers and their world, and users. We were able to translate from the functionality-based thinking of a product’s creators, to the task-based mindset of the end users.

We were also at the end of the food chain. We had to wait until the product was done, then chase engineers around with our notepads to try and get an idea of how something was supposed to work (not necessarily how it actually did). And we always got blamed for release delays.

Today we do many things that have never been thought of in the context of technical “writing:”

  • Interface design – user assistance is embedded in the interface. How can we design it if we don’t get involved with interface design?
  • Software information content – software today is an information rich environment, and often has to talk to users in one or more clearly defined voices. We write a lot of this content, whether or not it concerns user guidance.
  • Content strategy – this is a new buzzword, more or less since 2009, but if anyone thinks we didn’t do this before, they’re nuts. We’ve always had to make our work fit into an existing strategy, when there was one, and we’ve often helped define one when there wasn’t – it just wasn’t formalized. Now it’s getting more so.
  • Information Architecture – most of us don’t like being told we’ve got to fill in all the lorum ipsum’s that some designer has created for us without ever asking us what we needed to write and what prominence it needed. But we also can’t really start writing if we don’t have an idea of the structure it’s going into. In truth, content and structure need to evolve together and in parallel. So we do a bit of IA as well, and work with designers and information architects to make sure our content has a place to go – the right place to go.
  • Localization – Most of us don’t do translation, even if we are able to. But localization is not just translation. All the activities above also need to take localization into account. You need a good 30% more screen space for material in French or German than you do in English, just take a mundane example. Then there is the HOW you write – there are ways to write that make translation easier – and less costly, too. We have to know about them. Fortunately, most of these techniques also make better source language content.

I’m sure we could find a few more, but you get the idea. The fact that we do all of the above does not necessarily make us experts in all the fields mentioned. We are technical communicators: jacks of all trades, masters of some. We work in teams with other content workers, engineers and developers, marketers and designers, to create content in a variety of environments and situations.

Our skill, today, is not knowledge of English grammar or good style – though these are tools we must have in our kits. It’s not our knowledge or this or that desktop publishing solution, DITA schemas, or CMS systems, though these are also important.

Our primary and most important skill in today’s market is the ability to find information quickly, synthesize it, and make connections where relationships don’t seem apparent.

To quote Mark Baker, knowledge is no longer a salable commodity. Instead, it is “the calling card of expertise.”

In this context, all the definitions of our profession in all the labour bureaus throughout the world are obsolete and out of date.

Find Your User’s Voice

I’m working on an interesting problem these days. I have a client who is about to release a new software product. I can’t tell you what it does, for obvious reasons, but I can tell you that it does some neat things. Perhaps too many.

It provides users with all kinds of useful information. Some of it is useful for a group of users – call them Group A. Some of it is useful for another Group B.  They aren’t interested in the same things, and for some information,  Group B wants to know about it, but Group A not only isn’t interested, they’re not authorized to see it.

Access to sensitive information can obviously be solved with user profiles, but it’s a challenge to sell the same software to two different audiences. To facilitate the task, we’ve decided to create two different interfaces, one for each of the groups. When a user logs into the software the interface s/he sees is dependent on a user profile associated with the login. The other interface is not available.

That was the easy part. Next, we have to design the interfaces. And each interface has to communicate with its user group in language that makes them comfortable, and, above all, inspires confidence in the software.

It’s early days, but here are a few guidelines I’m working on that you might also find useful:

  • The design (look and feel, user interaction model) of the two interfaces needs to be sufficiently similar that should someone need to have access to both, they don’t need to relearn everything to use it.
  • At the same time, the same elements of the interface need to be fine tuned to appeal to very different user populations – for example, one might be technical, or engineering oriented, the other might be business oriented. One might be implicated in operations, the other might be financial, etc.
  • The language, labels, messages used in each interface need to be 100% adapted to the user group’s profile.
  • When writing the messages and content delivered by the software, we need to think about subtext as well as overt meaning. When two people have a conversation, there is enormous subtext based on power relationships, expectations, tone of voice, etc. When software provides information to a user, there is an implied notion that one or the other is the expert. How the software communicates with the user needs to be aligned with whether the software or the user is expected to be the expert, and the tone of the communication needs to be equally adjusted.
  • The user guidance, also needs to respect the target audience. This is harder the it might seem. Some of the user guidance is common to both interfaces – and needs to maintain that level of confidence for both, despite the fact that the two groups tend to favor very different communication styles.

My takeaway from this exercise so far: when we talk about content strategy for software, we really need to take a holistic approach, and realize that content and style need to be coherent, and in resonance with the nature of the information itself, and the user who must interact with it. Interactivity, in this sense, needs to take certain aspects of human communication into account if it is to succeed at convincing users and gaining their trust.

Where Would You Take This Idea?

I invite your comments, thoughts or reflections.

I’m on The Mindtouch Top 400 List

Mindtouch has included my two Twitter personas, @raygallon (number 118) and @gallon4stc  (number 259) on its annual list of top influencers in technical communication and content strategy.

I am really delighted to be included, but share some questions about the methodology with David Farbey. Rather than repeat all his arguments, I’ll direct you to his blog post on the subject. 

In my case, @gallon4stc is a persona that was created exclusively to run my campaign for office in STC, and keep that separated from my main tweet stream. It has relatively few followers and a small number of tweets. If the algorithm is purely quantitative, I don’t know how I made it to the list. If there are qualitative criteria (one might be, for example, the influence of a persona’s followers), I’d like to know more about how they were constructed.

So thanks, Mindtouch, for the honour, and please help us understand better how we got there!

TCWorld/Tekom and STC TC Summit: Two Realities

Since attending the TCWorld/Tekom conference for the first time last October, I’ve been thinking about how it both resembles and doesn’t resemble the STC Technical Communications Summit, an event that I have attended several times.

I had heard a lot of different opinions about this, and find that my own perception of this first dive into the Tekom world is a bit different from many of the comments I’ve heard. Here are a few of my observations, in no particular order, comparing the two events.

Basic Statistics


Number of days:

  • TCWorld/Tekom: 3
  • STC Summit: 4

Cost (member std rates):

  • TCWorld/Tekom: 650€
  • STC Summit: $1 025

Social Events included:

  • TCWorld/Tekom: Refreshment breaks, lunch every day
  • STC Summit: Refreshment breaks, 2 receptions, 1 lunch

Number of sessions:

  • TCWorld/Tekom: English – 62 sessions, 24 workshops German- 82 sessions, 25 workshops
  • STC Summit: 80 sessions, workshops extra

Post event access:

  • TCWorld/Tekom: Some presentation slides available for download
  • STC Summit: Summit@aClick access to full recordings of most sessions

Both conferences include trade fairs (Tekom’s is many times bigger than STC’s), and vendor showcases. Tekom also includes technology sessions that don’t seem to have a direct equivalent at the STC Summit, though some of these themes are treated in STC regular sessions.

Tekom offers a discounted rate to members of TC Europe member organisations. STC members do not receive a discount. STC, to my knowledge, has no discount programme for members of sister organisations anywhere.

Tekom’s trade fair does not include the innovation of the consultant’s corner, the space reserved for small consultancies that has been quite successful at recent STC Summits.

Content

As Kai Weber has pointed out in his overview of Tekom, it really is two parallel events: one in English, one in German. I have the impression (not totally backed up by observation) that more of the German sessions were oriented to practitioners, and more of the English sessions were oriented towards managers or consultants.

Like the STC Summit, presentations are organised in parallel tracks, and you can follow a single track or skip from one to another, as your needs and interest direct you.

Sarah O’Keefe, who speaks fluent German, said that she preferred to attend more of the German sessions. Her reasoning is that she already knows most of the English presenters, and the German presentations offer a different perspective on the themes that occupy our attention. My German is very rusty, and what remains in my head is just enough for me to feel frustrated when I try to decipher a spoken presentation. I must refresh my German before attending another Tekom event, because I would have very much liked to experience what Sarah was talking about.

Scott Abel organized a content strategy day at TCWorld that I took part in, that was the highlight of the conference for me. As I understand it, this was a new initiative for Tekom, not unlike the effort at the Dallas STC Summit. I would have liked to see a more dynamic followup at the Sacramento STC summit, as I have indicated elsewhere.

A major component of the TCWorld/Tekom event is localisation, and GALA is a partner in the event. The result is that if localisation is not at the centre of your concerns, it will seem that a huge part of the event does not concern you. A very high percentage of exhibitors at the trade fair were also vendors of localisation services, software, etc.

On the other hand, TCWorld/Tekom features a separate “Associations World,” a sort of trade fair for not for profits, for which STC has no equivalent. Exhibitors this year included other technical communication organisations such as ISTC (UK) and organisations from India, Japan, Poland, etc. It’s interesting to note that Tekom, a for-profit organisation, hosts associations, and STC, a not-for-profit, charitable organisation, doesn’t really have an equivalent.

Bottom Line

Both TCWorld/Tekom and STC Summits are great events. They have different characters, based in part on cultural differences, and also on the different business models and size of the two organisations. I am pleased to have been able to attend, and present at, both.