Posts Tagged ‘outsourcing’

Corporate Self-Help: Outsourcing Skills Training

Monday, April 26th, 2010 - Posted By: Scott McDonough

Everyone needs some help learning how to do something from time to time. Learning how to tie your shoes. Learning how to ride a bike, learning to swim. Or even learning how not to act at the office holiday party. These are the kinds of things we learn from our parents, older siblings, and friends (and in the case of the last example, our bosses). Good lessons, all of them.

Companies learn how to do things by hiring smart people and paying them to figure out how things are done. Sometimes, even after they figure it out for themselves, they hire other companies to do the work for them. In either case, what needs to be figured out gets figured out, and what needs to get done ultimately does.

But what happens when the smart people don’t have the time or knowledge required to figure out how to do what needs to get done? Simple, you hire someone else to do the work, right? Well, what if that too is not an option? Ignore the need and hope it goes away?

No, of course not. If you don’t have the time or knowledge to complete the task yourself and you can’t outsource the work itself, why not consider outsourcing training that will give your smart people, well, even more smarts?

It’s an attractive compromise for a few reasons:

  • Lower overall cost. It’s generally less costly overall to pay for the training required to perform the work than it is to pay for the work itself.
  • Job and requirements-specific training. These might sound like buzzwords or jargon, but there’s a real point here and this can make a huge difference on the true effectiveness of your training. In our world of content development for example, we would much rather offer training on the use of Frame Maker as it applies directly to the performance and within the context of an individual’s day-to-day job, not as an overview to the sum total capabilities of the software. With outsourcing of the training you have the huge advantage of ensuring the training is 100% applicable to your process and your content. The significance of this distinction cannot be overstated.
  • No long-term commitment to outsourcing. When you target the training you need specifically to your unique requirements, it takes less time to train overall since the objectives of the training are very clear and understood up front. No time is wasted covering irrelevant material. It can be everything you want and nothing you don’t, and this means less redundancy and cost. Once the training has been completed and you now have the skills you need to complete what needs to get done, there’s no commitment to further expenditures on outsourcing, unless you decide you want additional training.

Another way to look at it, (and I’ll apologize in advance for the terribly overused cliché), when you have to get something done would you rather pay for a fish, or learn to fish for yourself?

Outsourcing can be both an incredibly cost-effective and efficient way of getting additional work done without adding the cost of new equipment, software, or additional talent. At the same time, outsourcing can be looked upon negatively in that it can sometimes mean that a job that could potentially be done internally is now going to be outsourced. But it doesn’t have to. There is a middle ground through targeted skills training, and its worth looking into.

What is a Structured Document?

Monday, March 22nd, 2010 - Posted By: John Crews

This is a question commonly asked by our customers when we begin working with them on a single-source solution.  There is a short answer:

A structured document organizes paragraphs (elements) in a logical hierarchy, provides a means to attach tags (attributes) to individual paragraphs (elements), and gives you the ability to view the document in multiple ways.  FrameMaker ® (and other editors) also gives you the ability to manipulate the content of structured documents so that you can supply different outputs from the same document.

For this discussion, I will be using Adobe® FrameMaker® as my editor.  FrameMaker’s what-you-see-is-what-you-get view of structured documents is called the Document View.  If you have worked in unstructured Frame, this should look very familiar:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note, that all text is enclosed in brackets.  These brackets indicate element boundaries on the WYSIWYG view (Document View).  This correlates to the Structure View hierarchy described later.

The second way to view the document is called Structure View in FrameMaker.  The Structure View shows all elements (paragraphs) arranged in a hierarchy.  Each box represents an element.  An excerpt of the element text is displayed to the right of the element.  Below each element are Attributes assigned to the element.

The example highlighted below shows that the first element Bullet1 is assigned a value of 1 for the attribute Output.  The second element Bullet1 is assigned a value of 2 for the attribute Output.

In addition to managing the attributes and hierarchy of elements, you can also perform some edits in the Structure view.  If you right-click on an element, a context menu appears that describes several possible actions.  Typical shortcut buttons (ctrl+C for copy, ctrl+v for paste) function normally.  You can also drag-and-drop elements to move their location or to change their place within the hierarchy.

Most users who are accustomed to unstructured FrameMaker are used to working with the formatting toolbar.  Structured Frame does have this functionality; however, it also introduces an Element Catalog in place of the paragraph catalog.  The Element Catalog lists elements that may be selected to insert into the document and provides a tool-set for managing elements as you create them.  Using this catalog, you can insert an element into an existing element, wrap an existing element inside of a new element, and change the type of an existing element.  This tool set helps to minimize the complexity of managing the content from the Structure View.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Once you have an element in place, you can assign attributes using the Attribute Editor.  The editor displays potential attributes for a selected element and lists the predefined values that may be assigned.  Select the desired attribute, assign an attribute value, and then select the Set Value button.  This assigned value is then visible in the Structure View.

 

 

 

 

 

 

 

 

 

 

Using the Structured FrameMaker tool set helps to make management of complex single-sourced documents easier.  Creating a functional hierarchy allows you to manage content at all levels.  Attributes allow you control several output levels and types while ensuring that you are able to maintain accurate content.

Sometimes, you’ve got to call in SWAT

Monday, March 8th, 2010 - Posted By: Scott McDonough

Everyone knows that when a situation gets out of hand and the first responders are in over their heads, sometimes you’ve got call in SWAT. 

Police work? No, something far more adrenaline-fueled and dangerous. Documentation.

Picture this:

A manufacturer is scrambling to finish up and prepare for delivery the latest iteration of one of their most popular pieces of equipment. Three weeks before it is scheduled to ship, someone realizes they forgot to prepare the operator and service documentation that is required to accompany the equipment to their customer overseas.

Internal resources are tapped. Engineers and technicians work day and night preparing the machine for shipment and delivery. In an office adjacent to the assembly floor,  the engineering manager and product line manager furrow their brows with growing concern. Completing the documentation on time is only one-half the problem. The other half is doing so in such a way that corresponds favorably with the quality and innovation of this new piece of equipment. A hastily assembled three-ring binder full of notes and photocopied vendor-supplied spec sheets just weren’t going to cut it this time.

What do they do?

They call in a SWAT team. Well, ok. Maybe not the guys with the bullet proof vests and flash-bang grenades, but a documentation SWAT team. (Which, let’s face it, is almost as cool.) This team shows up in khakis and button-down shirts, armed with notebooks, digital cameras and laptops loaded with high-power publishing software.

And like the real SWAT, this documentation team is equipped with special training.  Armed with the education and real-world experience of mechanical and electrical engineering as well as computer science and communications, a well-rounded team of specialists that is singularly focused on the mission of getting in and getting back out with minimal long-term cost.

When the team shows up on site, they rapidly assess the situation and map out a plan. In short order, a project scope is hammered out, and the team goes to work.

The team descends on the equipment and rapidly determine how it works, what the major components are, and what needs to be included in the documentation. Encounters with engineers and technicians might prove troublesome for some teams, but not this one. They speak the language; fluent in “engineer” and well-versed in the world of equipment manufacturing. At the same time, the teams’ offsite support are already preparing a template to house the content.

The team supplies everything. Need a picture of this component? No problem. Need to facilitate the inclusion of  CE warning labels but can’t find all of them? They’ll find them. Need an engineering drawing converted or modified? They’ve got you covered. Need to facilitate the upload of  large files for inclusion into the documentation? The team will have a secure file transfer site up for you in minutes. Want to design a completely new documentation layout to better represent your company? The team will provide you with samples to choose from, or create a completely new one. Have a requirement for an additional language? They have specialists for that, too.

Digital cameras flash. The rapid firing of keystrokes punctuates the noise of the assembly floor. Notepads are exhausted and pens run dry.

It’s the end of day one, and the team is ready to present a working outline. By the end of week one, the team will have draft content ready for review. By the end of week three, the documentation has been completed and delivered. Along the way, the team has reported daily and weekly progress, organized and facilitated review meetings, and managed the process of seeking out, capturing, and maintaining content edits.

Wouldn’t it be great if such a team existed? A team of specialists that you could call in to respond to your product documentation needs without having to hold their hands? A team that has the skills, know-how and appreciation for your time and resources? A team that could get in, get out and provide you with a quality and on-time deliverable with no long-term investment? Sound too good to be true?

Some questions for equipment manufacturers out there:

Have you ever wished for a documentation “SWAT” team? What would prevent you from utilizing such a team? What questions or concerns might you ask or want to discuss with this team?

I’d love to hear your thoughts. Drop us a note here or feel free to use the comments feature.

 

Response to an Outsourcing Question Posted on LinkedIn’s Documentation Managers Group

Tuesday, February 9th, 2010 - Posted By: Scott McDonough

Recently, someone from a language translation services provider posted a good question in LinkedIn’s Documentation Managers group. As a language services provider, this person’s company is considering the addition of technical writing to their service offerings. The questions were “why do companies outsource technical writing, how frequently and to what extent?”

These are great questions, and I thought I’d re-post my thoughts here:

-The reasons why our clients choose to outsource technical writing are as varied as the companies themselves. In better economic times, it was often because thier internal resources simply did not have the capacity to meet the requirements. More recently, as internal staff levels have tapered off, we are seeing requests for assistance because the in-house resources that once were simply do not exist any longer.

Also, as [another commentor] pointed out, “technical writer” is a catch-all job title. All of our staff here would be more appropriately described as “content developers” as they have experience not only developing content for, say, product documentation but training curriculum and content for web applications as well. So there sometimes exists a disparity between what a potential customer thinks they need versus what they should be looking for. This subtle issue is one you should be aware of and one we deal with everyday. You may advertise that you are offering “technical writing” services, but your target customer may not equate their particular content development needs with technical writing necessarily because their subject matter happens to be training currciculum.

Some clients simply need an existing document edited to reflect some recent updates. Sometimes a file format conversion is required. Sometimes a person is needed on site to work with product teams to develop and deliver content. Sometimes clients hand over entire product documentation projects to be managed either on-site or remotely start to finish. Again, the reasons for and extent of outsourcing varies greatly.

-It has been our experience that larger companies having strong internal technical writing departments or resources, are often resistant to outsourcing, which makes sense and is to no one’s surprise. However, even these groups will often be receptive to learning more about how to manage their content more effectively. They may not want any help developing the content, but chances are they are drowning in a sea of it and may even be feeling pressure from the KM/ECM folks in their organization to do something about it. In this case, outsourcing the writing of their content probably isn’t going to be very attractive, but the services of a company or experienced technical writer may in fact be. Technical writers experienced with extensible content structure and delivery can still be a viable outsource option.

-A question that comes up frequently when discussing the outsourcing of technical writing is validation and verification of quality. This is especially relevant since the rise of lost-cost outsourcing across the globe. A low per-piece or per-hour rate can sound incredibly attractive to those considering outsourcing, but it must be evaluated to include the additional expenses of the contracting company’s project management and validation/verification time. The reality is that it is just not that simple as outsourcing to take advantage of a favorable exchange rate, there are real additional costs that have to be considered.

-More and more, and back to [another commentor's] point, it is simply not enough to offer pure content development work. While a valuable skill in and of itself, technical writers have found themselves having to respond to the needs of organizations that are shifting the focus to the management of their content. We have seen, over the last few years, more and more clients looking to us for assistance with the structure and management of their content, not just the development of the content. It seems it’s simply not enough to be able to develop content, it pays to know a thing or two about content management as well.

-Your position as a language services provider is probably a good one. We currently partner with a couple of similar service providers and those relationships have proven to be worthwhile.

For the complete discussion, here’s the link. (Though you may have to register for the group if you have not already.)