Tag Archives: infographic

DITA adoption: What are the numbers?

I just saw this infographic from IXIASOFT about a subject near and dear to my heart: the adoption of DITA.

Cg_W9ieUoAEuhEC.jpg largeLike so many infographics, unfortunately, this one is a mess. It’s cluttered, with so many elementsĀ competing for my attention that I can’t tell what its key messages are.

I don’t expect IXIASOFT to know how to create good infographics. That’s not their business. But I expect them to know about DITA and about the technical writing community in general.

That’s why I’m taken aback by some of their numbers:

  • There are 150,000 technical writers on LinkedIn? Even if that’s a worldwide total, itĀ  seems high. What occupations does IXIASOFT lump under the heading “technical writer”?
  • Only 9,000 say they know DITA? That seems about right – as an absolute number, but not as a percentage of the total. Of the people who are true technical writers, surely more than 6 percent know DITA.
  • 4.0 percent of job ads ask for DITA experience? That’s surprisingly low, considering that by IXIASOFT’s own count more than 600 companies have adopted DITA and a growing number of writers claim to know it. I recall seeing another presentation that put this number in the 10-to-20 percent range, but I can’t place my hands on it. Does anybody have data on this?

I looked on IXIASOFT’s website for illumination. There I found a piece in which Keith Schengili-Roberts put the 6 percent figure into context by noting that only 15 percent of technical writers claim to know FrameMaker. That makes me wonder all the more how broad their “technical writer” umbrella is.

I also discovered that this infographic has been around since at least November 2014. In the earlier version (which you’ll find in Keith’s article) the numbers are slightly different. But they still look suspect.

I’d like to find a truer picture of DITA adoption. Does anybody know of one?

What good technical communication looks like

To mark the fifth anniversary of the Deepwater Horizon oil spill, the Tampa Bay Times published a story containing a set of excellent infographics. Although I’m not usually a fan of infographics, I think this piece stands out as an example of good technical communication.

Image of bluefin tuna with accompanying text

Detail from one of the infographics (Source: Tampa Bay Times)

It’s visually appealing: The artwork is well drawn, it supports the text, and it captures the reader’s interest.

It makes technical content accessible to a lay audience: The tone is professional yet personable. Scientific terms (like flocculated) and concepts are explained neatly. Metaphors, like the “dirty blizzard,” adapt the material to the reader’s frame of reference.

It stays neutral: Deepwater Horizon remains a sensitive, politically charged topic for many. This piece sticks to the facts and lets readers draw their own conclusions.

How could the piece have been even better?

Smoother transitions: The first infographic doesn’t contain introductory text. The regular HTML text — not part of the infographic — serves as an introduction. The other two infographics, Effect on Marine Life and Tracking the Oil, contain their own introductory text. (Tracking even contains sub-sections with more introductory text.) As you read, you might not notice that you’re moving from one infographic (major topic) to another unless you detect a font change. Then, suddenly, you realize that the subject matter has shifted. If the transitions were handled better, and more consistently, the reader would experience a less bumpy ride.

Editing for consistency: A good edit would’ve caught some little things, like quote marks used for “dirty bizzard” in two of the infographics but not in the third, or for “downhill” in just one of them. I’m guessing that the infographics were produced independently, perhaps even at different times, and then pulled together for this anniversary story. If that’s the case, then it’s remarkable how little inconsistency there is.

All things considered, the flaws in this piece are minor and are far outweighed by the strengths. The story conveys useful information in an effective and engaging way. It’s a nice piece of technical communication.

What do you think?

Kudos to Times staffers Cam Cottrill, Steve Madden, and Don Morris.