Software Development Times has an interesting article on about APIs: If you believe a recent report from analysis firm Gartner, in just two years, we'll be overrun by citizen developers (normal, untrained computer users) building 25% of new business applications. A major facilitator for these newbies? Some have posited that cloud-based API mash-ups would be so easy to use, toddlers would soon be selling mobile apps. But now, San Francisc...
One traditional stereotype about technical writers is that they work long hours in isolation, almost like a hermit in a lone cell immersed in deeply technical material, trying to make sense of it all by themselves. We know that stereotype is a recipe for failure. Collaborating and sharing information across departments is essential for creating the right content. But exactly how we are to collaborate across departments isn't as well defin...
In my recent tech comm poll about why users can't find information in help, one of the top answers was the following: The answer isn't in the help because the help sticks only with obvious information. No doubt at some point in your life, you've clicked a help file and browsed around only to find that the information is too basic and simple to answer any real troubleshooting questions you have have. Through repeated experiences like thi...
My recent poll on why users can't find answers in help material surfaced an interesting paradox. Consider these two reasons: The answer is buried in a long page, but the user only spends 2 minutes max on a page scanning. The help has been fragmented and dispersed over many small topics so the help is a maze. In other words, help is either too long so users can't find the answer, or help is too short so users can't find the answer....
In my recent poll about why users can't find the answer to help, one of the top answers (so far) is the lack of examples: The help doesn't provide concrete examples that make the concepts understandable. (View total votes.) I've long been a fan of examples in help documentation, but I didn't suspect they played such a large role. In fact, one rarely hears any presentations or reads blog posts on using examples. It's time to give this t...
I'm preparing for an upcoming presentation at a local STC chapter in the SF Bay area. I'm hoping to get some feedback before I finalize this presentation, so if you have some ideas, I'd love to hear from you. Here's my draft: Why Users Can't Find Answers to Their Questions in Help Content One of the main goals of help material is to help users find answers to their questions, but so often this doesn't happen. Users foray into the help ...
One of the forms of writing I like most is the essay, which is a form that has strong origins with 16th-century Michel de Montaigne. Montaigne saw essays as a kind of attempt or test of an idea and his judgement about it (see Montaigne's Moment). Since I like the essay format, it's not surprising that I also like to test content. In fact, testing content constitutes one of the main characteristics of good technical writing. By testing con...
I recently listened to an O'Reilly programming videocast interview with Travis Lowerdermilk about his new book, User-Centered Design: A Developer's Guide to Building User-Friendly Applications. During the videocast, Travis notes that according to Jakob Nielsen, you need only 5 users to identify most of the problems with a UI design. Lowdermilk acknowledges that the idea has been challenged by some, including Jared Spool and others (see Wh...
Since I switched jobs about 6 months ago, I decided that I wanted to move toward writing developer documentation. Not only is the job market for this skill extremely hot, it's also a challenging and interesting landscape to explore. I'm currently writing a lot of code samples for a JavaScript SDK. Even though I'm comfortable with CSS, HTML, and a lot of technical topics, like designing and developing WordPress sites, I've had to ramp up o...
For a long time I pursued findability as a solution to fixing the documentation problem. But lately I've been less persuaded that findability will solve documentation's ills. Instead, I'm become convinced that what's really wrong with help is the content itself, not necessarily allowing people to find it. Why? Because "it" often doesn't exist. The user is trying to find something that hasn't been created. What's really wrong First, a quic...
Etteplan | Tedopres Etteplan | Tedopres releases HyperSTE 5.0 with support for ASDSTE100 Issue 6 and new authoring applications HyperSTE 5.0 is a major update introducing support for new authoring applications, including Madcap Flare and Oxygen. In addition, HyperSTE now fully supports Issue 6 of the ASD-STE100 specification. What is new in HyperSTE 5.0: Full integration of the ASD-STE100 Issue 6 specification. Now also compatible with: ...
Marcia Riefer Johnston recently published Word Up! How to Write Powerful Sentences and Paragraphs (And Everything You Build from Them). I had a chance to read an early draft and provide feedback. I really enjoyed the book, so much that I agreed to appear in a promo video: I gave a short quote in the "Advance Praise" section of the book, noting that Word Up is "Light, fun, and enjoyable to read. Marcia approaches grammar and style with a...
Since I wrote my post about how help needs to be more engaging/appealing to users, I've been mulling over a better approach to help. I'm convinced that one key to creating good help is producing the right information. In my last post, I wrote about the need to answer the user's question as the foundation for creating good help. But then I was reading something Mark Baker wrote about addressing purpose instead of answering questions, and I...
A few weeks ago, I added some social network functionality (Buddypress) to my site as well as a Question and Answer module. You can read about the features here. Unfortunately, the social network plugin added about 5 seconds of load time to my site, and despite my attempts to speed it up, Buddypress is just slow. Caching plugins seem to pose problems with Buddypress, too. The Q&A plugin required user registration to work well (registr...
In my last post, I reflected on the most successful experiences I've had in connecting with users and decided that a foundational principle for successful user help is to answer the user's question. I also realized that if there's been a transformation in the user experience of help at all in the past 50 years, one that has had a positive impact on the user experience, it's this: you can type a question into Google and find an answer. The...
