A directory of resources inthe field of technical communication.

Articles>Collaboration>SMEs

32 found. Page 1 of 2.

About this Site | Advanced Search | Localization | Site Maps
 

1 2  NEXT PAGE »

 

1.
#36618

Becoming the Friendly Neighborhood Tech Writer

Since much of technical writers do is gather information from other people, be respectful of their time. Don’t ask for a minute unless you literally want 60 seconds of their time or less. If I have what I think is a brief question requiring a brief answer, I ask, “Hey Dan, do you have a few minutes to answer a question, or should I come back later?” They’ll usually be honest about whether they need to finish something first or if they can give me their full attention right then.

Minson, Benjamin. Gryphon Mountain (2010). Articles>Collaboration>SMEs

2.
#38683

Conducting Successful Interviews With Project Stakeholders

Looking back over recent months, by far the most common form of research I’ve carried out is that stalwart of qualitative studies—the interview. A simple, semi-structured, one-on-one interview can provide a very rich source of insights. Interviews work very well for gaining insights from both internal and external stakeholders, as well as from actual users of a system under consideration. Though, in this column, I’ll focus on stakeholder interviews rather than user interviews.

Baty, Steve. UXmatters (2007). Articles>Collaboration>Interviewing>SMEs

3.
#36396

Cures for the Information Exclusion Complex

Some years ago, I used to suffer from developer neglect, or to use a more scientific term, from a kind of information exclusion complex. You know what I’m talking about. Developers make updates to the interface, often at the last minute, and don’t let the tech writer know what changed. As a result, the help is wrong and out of date. It’s a frustrating experience from the writer’s perspective.

Johnson, Tom H. I'd Rather Be Writing (2010). Articles>Collaboration>Technical Writing>SMEs

4.
#10350

Documenting Contributory Expertise: The Value Added by Technical Communicators in Collaborative Writing Situations    (peer-reviewed)   (members only)

Technical communicators frequently collaborate in workplace projects and bring a host of different kinds of expertise to this collaboration. Yet the understanding of communicators’ expertise among managers and subject matter experts is grounded in a view of writing as a finished product and authorship as singular. This article documents many different kinds of 'contributory expertise' employed by writers collaborating to produce articles for publication. Expertise in research, textual composition, visual composition, as well as other kinds of expertise garnered on previous projects is often brought to collaborative projects. Often emerging and developing as a function of collaborative work is expertise in framing the project, conducting review processes, and assessing outcomes. These categories are discussed in some detail to provide practicing communicators with ideas for documenting expertise in their specific workplaces, to provide students with ideas for developing expertise in various areas, and to prov

Henry, James M. Technical Communication Online (1998). Articles>Writing>Collaboration>SMEs

5.
#38118

Getting the Right Stakeholder Feedback at the Right Time

Efficient, effective collaboration between UX designers and stakeholders is an essential ingredient of a successful project. Stakeholders bring their unique perspectives to a project, and their feedback can help a designer understand the design problem space and develop solutions that align with business and technology objectives. But simply asking stakeholders for feedback can lead to misaligned expectations and communication problems. By being thoughtful in how you make your request for feedback and by providing simple questions and instructions, you can ensure that you identify potential risks early in the design process, minimize stress, meet your deadlines, and ultimately design a better solution.

Hawley, Michael. UXmatters (2011). Articles>Collaboration>User Experience>SMEs

6.
#35373

How To Effectively Communicate With Developers

If you have ever worked with a developer or a development team, this article will probably strike close to home. As designers, we work with dozens of developers across the globe each year. Some of us are fortunate enough to find a gem; a developer that just gets it. A developer that you feel is on your same wavelength in terms of what needs to be accomplished with the user interface, and what it needs to happen. Most often, however, we find developers that we generally don’t see eye to eye with.

Scherf, Ryan. Smashing (2009). Articles>Collaboration>Programming>SMEs

7.
#32788

How to Get Someone to Answer Your Questions

Send the mail to the person or group of people, but rather than asking the question, state what you know is the wrong answer. “I think the way it works is Foo, right Bob?” You'll be amazed at how quickly someone will take the time to correct you, particularly if the question was aimed at more than one person, since it's an opportunity for that person to prove their knowledge in front of others (which is just human nature).

Lemson, K.C. KC on Exchange and Outlook (2008). Articles>Collaboration>SMEs

8.
#28176

Improving Technical Reviews

Improving technical reviews, when subject matter experts, or SMEs, review content for technical accuracy, is a challenge every technical communicator faces sometime during their career. Every year, journal articles are published, presentations are made, and discussions are initiated on this very topic. Most of them conclude that SMEs are difficult. It's your job to bribe, cajole, or coerce a better review out of your SME. I don't agree.

Idoura, Alexia. Carolina Communique (2004). Articles>TC>Collaboration>SMEs

9.
#32228

Inspiring Reviewers to Review Your Documents

To obtain good reviews, you must make the process as painless as possible for reviewers.

Hart, Geoffrey J.S. TECHWR-L (2008). Articles>Editing>Collaboration>SMEs

10.
#35601

IxD and SMEs Working Together

An SME is someone who has been trained and has worked in the area that is being targeted for the new application. At Autodesk, we have found that pairing SMEs with Interaction Designers is the most efficient and successful way of meeting user centered design goals.

Hooper, Ian. Designing the User Experience at Autodesk (2009). Articles>Collaboration>Interaction Design>SMEs

11.
#36724

Knowledge Transfer

A little introspection and a rewind of sequences from my years of experience as a technical writer, revealed a patterned behavior in most developers. The basic fact that some developers have no idea about what inputs to give and what to expect of a user document is the primary cause of such inputs.

Gopalakrishnan, Deepa. Indus (2010). Articles>Collaboration>SMEs

12.
#30326

Listening: the Often Forgotten Ingredient

If listening isn't in the mix when developing documentation, then the project may not cook.

Allen, Clare. Boston Broadside (1992). Articles>Documentation>Collaboration>SMEs

13.
#30005

Location is Everything When it Comes to Getting Information from SMEs

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.

Johnson, Tom H. Tech Writer Voices (2007). Articles>TC>Collaboration>SMEs

14.
#35966

Location is Everything When it Comes to Getting Information from SMEs

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.

Johnson, Tom H. Tech Writer Voices (2007). Articles>Collaboration>SMEs>Podcasts

15.
#32193

Managing SMEs - Part 1: A Primer for Success

Just the thought of dealing with Subject Matter Experts (SMEs) can create stress in the life of any documentation manager. Some SMEs can be self consumed, preoccupied, distant, and even rude. But why do these behaviors exist? This article briefly describes how to interact with people who might be difficult to motivate and how to work with people who have priorities different from yours.

Rastocny, Philip. TechCom Manager (2007). Articles>Management>Collaboration>SMEs

16.
#31720

Managing SMEs - Part 2: Selling the Concept to Management

Part 2 switches the focus to members of your management team and what you can do to sell your team’s professionalism. Also included are hints on how your writers can individually sell themselves to gain cooperation from SMEs.

Rastocny, Philip. Writing Assistance (2007). Articles>Management>Collaboration>SMEs

17.
#32190

Managing SMEs - Part 2: Selling the Concept to Management

Focusing on your professionalism could be the key to successfully managing your working relationships with SMEs.

Rastocny, Philip. TechCom Manager (2007). Articles>Management>Collaboration>SMEs

18.
#24358

Managing the Communication Between Writers and SMEs   (PDF)

The development of a modern software product is a complex process involving a variety of disciplines, including that of the technical writer. It is essential that the writers establish close relationships with all other groups in the process and that they build effective and efficient systems of communication between them. The job of the writing manager is to ensure that the writing team obtains the information it needs in a timely manner and that the group interacts effectively with other groups in the process. This can be achieved by a blend of intergroup communication, background research, documentation and schedule planning and a well organized documentation review process.

Morgan, Sharon. STC Proceedings (1998). Articles>TC>Collaboration>SMEs

19.
#36568

Praise: The Worst Feedback You Can Give Developers?

If developers only hears about bugs, problems, quirks, errors, and other issues, where’s the motivation to code? In a recent post on Joel on Software, Joel Spolsky stresses the importance of giving positive feedback to developers, not just negative. But there was no where to log my praise in our bug tracking system.

Johnson, Tom H. I'd Rather Be Writing (2010). Articles>Collaboration>Programming>SMEs

20.
#37540

Questions Every Technical Writer Needs to Ask Engineers!

What should technical writers ask engineers when writing support materials for a product’s end users? Guest blogger and leading tech comms expert David Farbey wraps up his ‘What to ask…’ series with questions for engineers.

Cullinan, Fiona. Firehead (2010). Articles>Collaboration>SMEs

21.
#30597

The Role of Double Agents in Writing Projects   (PDF)

Double agents on writing teams provide benefits to both product developers and technical writers with their unique skills and perspectives. You'll be more likely to get the information you need when you need it because your double agent has already set the stage for success. Learn the benefits of having a double agent working with technical writers as a part of the product development team. Discover valuable secrets never before divulged to the public that you can use to work with your product developers. Take out your magnifying glass and look for the clues.

Mobley, Karen L., Kathryn L. Turk and Judith R. Fisher. STC Proceedings (1993). Articles>Writing>Collaboration>SMEs

22.
#21407

SMEs in a Nutshell   (Word)

I admit that I don't know everything about subject-matter experts or SMEs (rhymes with please). But I do know that there are some things that you should avoid asking SMEs, the main ones being 'Does the user know this already?' and 'Do I need to explain this to the user?' The problem with these questions is that the SME is likely to reply 'No!' to both of them when in fact the answer is most definitely 'Yes.' SMEs tend to believe that everyone knows as much about technology as they do. Never, never, never let the SMEs tell you how to write the documentation. A SME is the subject matter expert, not the documentation expert (that's you).

Docsymmetry (2003). Articles>Documentation>Collaboration>SMEs

23.
#30587

Team USA: The USAbility Team   (PDF)

Most companies want to be recognized for producing usable products, for the quality of products must be high if they are to be accepted into today's competitive market. However, usability planning relies on interaction with other departments and their members. In other words, the most successful way to ensure product usability is to set up a test team consisting of representatives from various departments. This paper details the members of that test team and discusses their overall responsibilities in the testing process.

Dorazio, Patti A. STC Proceedings (1993). Articles>Usability>Collaboration>SMEs

24.
#10415

Technical Writer/Subject Matter Expert Interaction: The Writer's Perspective, the Organizational Challenge   (peer-reviewed)   (members only)

Almost a decade ago, Walkowski's (1991) study of the interaction between subject-matter experts (SMEs) and technical writers focused on the perceptions of software engineers toward technical writers. Her findings gave technical writers insights on how to improve critical relationships with these organizational colleagues. This study partially replicates Walkowski's (1991) study of technical writer-SME interactions, but instead of collecting data from SMEs, we surveyed technical writers themselves. We report perceptions collected from 31 technical writers and contrast them with Walkowski's original findings, offering interpersonal and organizational recommendations for addressing tensions between these groups. By examining both the SMEs' and the technical writers' perceptions of their relationship, we are able to provide a two-sided view of a dynamic and complex interaction. We also argue that participants in the SME-technical writer interaction cannot fully alter their relationship without the strategic supp

Lee, Martha F. and Brad Mehlenbacher. Technical Communication Online (2000). Articles>Collaboration>Technical Writing>SMEs

25.
#14631
 
 NEXT PAGE »

 

Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon