2010 sigdoc keynote
TRANSCRIPT
SIGDOC over the past 10 years - a practioner’s perspective
Robert Pierce
Advisory Information Developer
IBM Corporation
Areas of discussion
• Changes in technical communication• Changes in the role and scope of the work:
– technical writer -> technical communicator– technical communicator -> information developer – information developer >user assistance developer
• Less time spent doing content development• Broader list of tasks to perform
Examples of name changesin the field
• Documentation > Design of Communication
• Computer science > Informatics
• Technical Communication > Human Centered Design & Engineering
Informatics at Indiana University (site of SIGDOC 2009)
• Where other schools excel in engineering, Informatics is building its reputation on human-centered and area-specific informatics balanced by strong foundations, systems, AI/CogSci, e-science, databases and programming languages provided by the Department of Computer Science.
• What is Informatics?• Informatics is…
– converting data into information
– humming a tune and your search engine correcting the pitch
– predicting the spread of the next flu epidemic
– combating malicious hackers
– understanding the human genome
– exploring virtual reality
– supporting cutting edge research
– developing business solutions
– and more…
– Informatics develops new uses for information technology, is interested in how people transform technology, and how technology transforms us.
HCDE at University of Washington (site of SIGDOC 2012)
• TECHNICAL COMMUNICATION school was renamed to HUMAN CENTERED DESIGN AND ENGINEERING
• HCDE - The Department of Human Centered Design & Engineering (HCDE) offers seven different degree programs
• HCDE faculty and students are advancing design knowledge by using innovative techniques to study human activity and then translating that knowledge into meaningful information and system designs. HCDE is designing the future by:
– Considering the role of communication and technology in human activity.
– Prioritizing the needs, desires, and behaviors of people and communities who interact with technical systems.
– Addressing the specifics of design by working with interdisciplinary communities of researchers to build innovative technological solutions.
Changes in industry/practice
• Information – considered amongst multiple repositories and created by multiple groups of stakeholders
• Information types – including multimedia, • Information design and architecture – managing and
leveraging the complexity of content use and reuse• Information delivery – and channels such as blogs and
forums• Information currency – real time updates and feedback• Information relevance – based on context
Past focus
• Content development
• Usability
• “Know your audience”
• Don’t use passive voice
• Developing quality technical content
Examples from 2001 Proceedings
• Communicating in the New Millenium• Design Issues• Documentation Roles• Globalization Issues• Just-in-Time Documentation (such as
Open-Source, Learning, Wiki, CSH)• Online Documentation• Searching and Indexing
Newer focus
• Content (development)• Presentation of content (design and user
experience)• Delivery of content (mediums such as
web, graphics, audio, movies, no hard copy)
• Consumability of content (user experience and ongoing enhancements for role-based, filtered and aggregated content)
Current focus
• Design of communication – more engagement with field and customers, more global audience (and globally distributed collaboration and development)
• Web-focus• Metadata design and application• Translation of all content• Content accessibility• Scope of tech comm across wider ranges of info.
resources and spectrum of content including corporate web sites, Support dbs, and other repositories.
Examples from 2009 Proceedings
• Designing for Users• Accessibility• Teaching and Disciplinarity• Web Design and Analysis• Help Systems• Applications and Architectures• User Assistance and Documentation• Document Use and Reuse• Web Design and Development• The Design of Documentation• Analyzing Texts• Interactivity in the Design of Communication• Online Information Exchange, Use, and Adoption• Online “Fact-building” and Meaning-making
More content reuse and packaging
• Products -> modular capabilities– Make areas of functionality in a product
componentized and available for reuse (as well as the technical content that supports that capability)
• Integrations -> workbenches– Make capabilities from different products available in
an offering/solution (as well as the technical content that supports those capabilities and how they work, and how to make them work, together)
Similarities
• Quality content
• Completeness
• Know your audience
• Don’t use passive voice
• Try to automate as much as possible when content resides in dev. source files (examples – log files, error messages, api ref content)
Differences
• Quality content diversity and scope – more deliverable types expected in more accessible ways.
• Know your audience in far more detail. Know them by roles, uses cases, scenarios, and goals.
• Be customer-driven – seek out and use customer feedback
• Link multiple information resources together to assist all audiences.
• Work on context-based information/technical contetn/communication. For example use feeds and metadata to filter and aggregate content collections.
Practical matters
• Hardware and software designs and limitations. For example, the best design of communication needs to help prevent errors such as this:
Bandwidth Limit Exceeded: The server is temporarily unable to service your request due to the site owner reaching his/her bandwidth limit. Please try again later.
Information and DOC examples
• College information:Brochure -> web site
• Technical content:Manual -> web help, such as online information
centers, wikis, portals - increasingly contextualized, customizable, annotatable
Are enhancements should be customer-driven?
Is findability a key mark of success?
• DOC in academic settings – for a college web site – who designs and develops and studies it?
• Customers/consumers (student, faculty, parents, alumni, prospective students)
• Developers/IT department (both computer science departments and web developers)
• Researchers (faculty)