Feed aggregator

Lyn Worthen presented to the STC Intermountain chapter tonight on running your own business as a technical communications consultant. She covers almost everything you need to know as a consultant, including rates, billing, contracts, marketing, taxes, business structures, hours, salary, tools, locations, niche services, portfolios, client communications, and more.

A 20 minute monologue about the best way to get information from SMEs: sit by them, permanently if possible. Many IT organizations station the writer remotely from the developers, programmers, and other SMEs, but nothing could be more damaging to getting the information you need. Increasing your proximity also increases the communication you receive.

This podcast features the June presentation that Char James-Tanny gave to the Suncoast Florida chapter on virtual ways of communicating. Char is the secretary of the STC and a well-known expert on AuthorIT, RoboHelp, and other tools.

Although getting a job is the focus of the podcast, I also talk about what technical writers do, how they approach a project, how they decide what to create, and how they generate ideas for tasks. Specifically, I talk about about a project people can work on at tech.lds.org. People can start writing help for the project here.

Devoted followers stay updated with each new post, podcast, or screencast, eagerly awaiting the next new one. They’re intimately familiar with your content and either comment regularly or regularly return to your site.

Devoted followers stay updated with each new post, podcast, or screencast, eagerly awaiting the next new one. They’re intimately familiar with your content and either comment regularly or regularly return to your site.

In this podcast, Sarah O’Keefe of Scriptorium Publishing explains the results of their recent survey about the state of structured authoring in technical communication. In the survey, they found that 84% of respondents are either thinking of moving to structured authoring, are in the process of moving to structured authoring, have already adopted structured authoring, or are undecided. Only 16% of respondents said they were not moving to structured authoring. She also discusses other survey results, such as the adoption of DITA and mistakes people make in moving to structured authoring.

In this podcast, Mike Hamilton of Madcap Software talks about their phased approach to handling DITA with Flare. In Phase I, you’ll have the ability to import DITA topics and export to webhelp and other targets. In this sense, Flare functions as a transform engine. In Phase 2, you can use Flare for native DITA authoring. Phase 1 is on the cusp of release, but Phase II won’t be available until quarter one of next year.

Several weeks ago I wrote about my trip to Brigham Young University-Idaho and the presentation I gave there titled “Debunking the Boredom Myth of Technical Writing.” This podcast is a recording of my presentation.

It all comes down to managing and reusing source. Recycling content (chapters, graphics, etc.) is not new. What is new here is the common set of back-end structure in XML form and the fact that more than one set of tools — including small, mission critical custom tools — are explicitly focused on the specific needs of a given project. Reusing and repurposing content is all about improving efficiency: automating, accelerating, and merging applications, systems, and processes. In a multichannel publishing environment, it is critical that content development — source development — and its management are as efficient as possible.

In this podcast, Nicky Bleiel says we should talk to as many users as we can — conducting on-site visits, sending surveys, gathering information from Marketing, Support, and other departments — so we can have a better understanding of our users’ needs and the formats and mediums that will work best for them. After completing this audience and needs analysis, we can then go out and create the deliverables that will best serve our users.

In this podcast, Joe Sokohl explains how to create user-centered documentation by contacting, observing, and interviewing users to gather information about what types of information they use and the help deliverables they actually want.

XML, a way of tagging and structuring your content, can help solve a number of problems, including storing, mining, reusing, and sharing content. XML helps enable the interoperability of information between systems, allowing you to export and import your content from one application to another. XML is behind much of the collaboration and information sharing Web 2.0 technologies, such as RSS (really simple syndication) and blogs. By storing content in XML, technical writers can ensure greater flexibility among technologies for authoring and publishing their content.

In this podcast, rich media specialist Todd O’Neill explains how to add video to your training and documentation deliverables. Many technical writers are intimidated by the learning curve, equipment costs, and software they think they need to create video, but actually you can create engaging videos with minimal equipment (e.g., $150 for a Flip video camera) and using software you probably already have (e.g, Windows Movie Maker or iMovie). In this podcast, Todd lays out the basics for those who know nothing about video. He explains the equipment you need, techniques for minimizing editing time, ways to publish the video online, filming techniques to focus on, and creative ways to package your video for your users.

Many content management projects fail because organizations are either too focused on tools before properly researching their needs and processes, or because they underestimate the difficulty of migrating and restructuring their content to fit the new content management system. In this podcast, Rahel Bailie explains these pitfalls and what companies can do to avoid them, as well as how companies can climb out of problems they’re currently in. Rahel also talks about how technical communicators can influence business executives and other key stakeholders to make better decisions about content management.

IT project teams often need to increase collaboration and communication, but they’re hampered by the cubicle walls and other physical silos they set up in the workplace. These physical obstacles force teams to have frequent meetings — which can be long and inefficient — just to keep each other updated. In this podcast, Emma Hamer talks about both physical and virtual workspaces that project teams need to increase their performance. She also outlines the rationale for teams to gather better feedback from users, project members, and others who aren’t domain experts.

Heidi Hansen takes 15 minutes to discuss five books that she read over the past year and published book reviews for.

In this podcast, Sarah O’Keefe talks about XSL, Flash, and live blogging. XSL (extensible stylesheet language) is a programming language that transforms XML content into a specific format, such as HTML. She explains what you can do with XSL, why it’s unique, and how the output is created.

In this podcast, Stewart talks about the following: the advantages of using a wiki for your technical documentation; why lack of advanced styles in wikis isn’t a major problem; the relentless focus on simplicity with wikis; choosing the right wiki among dozens of wiki engines.

In this podcast, I talk with Alan Porter, vice president of Operations at WebWorks, about the Web 2.0 technologies they’re using to reach out to their customer base. In addition to using blogs, wikis, and social networks to connect with customers, WebWorks also uses wikis to facilitate communication and collaboration within their company.