Developing a Collaborative Team: Lessons Learned from GE Healthcare

  • 4,402 views
Uploaded on

Presented by Jeanette Eichholz at Documentation and Training Life Sciences, June 23-26, 2008 in Indianapolis. …

Presented by Jeanette Eichholz at Documentation and Training Life Sciences, June 23-26, 2008 in Indianapolis.

Global collaborative writing team. Sounds good, doesn’t it? But why would anyone want to develop and maintain a collaborative team, especially over international time zones? Doesn’t everyone want their own autonomy anyway? to control their own destiny? their own budget? be happy within their own writing silow? Why develop a collaborative writing team?

For consistent standards, to share content and processes, reduce costs, to share a one for all and all for one attitude, and to gain the best of all possible worlds, of course. Because the reality of maintaining separate but equal writing silos is costly, redundant, and ‘managed’.

In reality, we’re all working for one company, sharing the same budget, using the same vendors, developing the same templates, following the same style guide… With the business imperatives we all have today to deliver more documentation faster, consistently, and cheaper, can we really afford to work in a silo? And wouldn’t we really have more to gain by sharing costs to develop content, agreeing on standards and templates, and determine how to meet tight schedules by sharing responsibilities by empowering all members of the team?

Managers/Teams will Learn about: How to build, develop, and maintain a global collaborative team and the benefits/challenges of working with a global collaborative team. Here are some of the differences and benefits she’ll discuss about working with a collaborative team vs working in your own separate writing ‘silo’.

* Team Leader vs Separate managers for each writing group
* Developing a Style Guides collaboratively vs Maintaining consistent styles across all the writing groups
* Getting everyone to do the same thing willingly vs Enforcing standardized templates and processes
* Srategizing translation cost trade-offs with everyone’s input vs Being told to reduce translation costs by 20%
* Meeting ‘creative’ schedules by splitting up the tasks vs Missing tight schedules
* Controlling quality and consistency collaboratively vs Getting the go-ahead to hire for a department editor
* Agreeing to write and reuse one set of content vs ‘Enforcing’ no changes in order to minimize translation costs
* Implementing a content management system with 4 months to write a 1000-page manual for two products with development in two different countries by working together vs doubling the resources, doubling the time, and doubling the cost
* Validating Chinese, Korean, Japanese translations with team members overnight vs Using costly external experts that takes one week to turnaround
* Gaining the best from 8 global teams vs Utilizing the best of one team
* Having an on-site writer working alongside the subject matter expert in another country vs Developing content for software written in another country
* Empowering everyone, sharing best practices, and gaining from the global interchange of information and technology vs Keeping expertise with the chosen few and enforcing their guidelines
* Developing a shared repository of content vs. Developing unique documentation sets and translations
* Collaborating on schedules, standards, and costs vs Managing schedules, standards, and costs

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,402
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
211
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Developing a Collaborative Writing Team My Experience at GE Healthcare Jeannette Eichholz GE Healthcare Clinical Systems Ultrasound
  • 2. Imperatives Within Corporate Medical Writing Environment
    • MUST
      • Meet Global Regulatory Requirements
      • Control Costs
      • Ensure Quality
      • Launch Products Simultaneously to Global Markets
      • Within Shorter Project Cycle Times
    • With Flawless Execution
  • 3. Imperatives Within Global Regulated Environment
    • FDA Regulations require that we all follow the same processes and SOPs
        • Compliant
        • Increased Quality and Consistency
        • Verifiable
        • Repeatable
        • Cost-Effective
  • 4. CMS Imperative
    • Imperative to standardize processes globally to meet regulatory requirements and to improve processes to meet business requirements to reduce costs and cycle time to reach global markets simultaneously.
    • From
      • Content Developed on their own PCs
    • To
      • Shared Content Management System
  • 5. GE Ultrasound successfully implemented a CMS for its user documentation. In 7 years we’ve gone from 2 products to 30 products and from 10 languages to 31 languages.
  • 6. Benefits of Implementing a CMS
    • Reduced overall translation costs by 50-60%
    • Translation costs even over past 7 years
  • 7. Reduced Translation Cost -- JME 2 Systems 10 Languages 22 Products 31 Languages
  • 8. Benefits of Implementing a CMS
    • Global Simultaneous Product Launch in all Required Languages (31 and counting)
  • 9. Simultaneous Global Rollout 1999 2001 forward
    • Collaborative
    • Simultaneous
    • Reusable
    • Translate
    • incrementally
    Program Start Clinicals Product Launch Full Production
    • 1 Writer
    • works serially
    • on each product
    • Translate as
    • complete book
    Translation Complete AFTER Product Launch Translation Ready at Clinical Release Program Start Clinicals Product Launch Full Production
  • 10. Benefits of Implementing a CMS
    • Increased Market Coverage
  • 11. Reached more markets JME
  • 12. Benefits of Implementing a CMS
    • Established Collaborative Writing Team
  • 13. User Documentation Paradigm US Israel Norway China Korea Japan India 8 Product Centers Collaborative Global Effort VIVID Content LOGIQ Content Structured SGML Content Management System Individual Products Germany Xslt Conversion PDFs eDOCs Translate Online Help 1-Step Process Paper Docs only on Request 1-Step Process Increased Consistency 31 Languages No Desktop Publishing Cost Via F1 on Scanner eDOCs Decrease Cost Electronic Documentation Ship Complete Leveraged Translation Memory Austria
  • 14. Why has GE’s CMS Implementation been Successful? A CMS implementation CANNOT succeed without a successful collaborative writing team. Indeed, our collaborative team is the cornerstone to our successful CMS implementation.
  • 15. What Did We Overcome? Let’s take a look, Before, and After.
  • 16. “Before” Scenario, without CMS
    • Writing Silos – Mfg Centers in US, Japan, Korea, China, India, Norway, Germany, Austria, Israel
    • Used tools where sharing or single sourcing was impossible
    • Content / Templates started out the same, but diverged over time
    • New acquisition assimilation difficult
  • 17. Redundant, Cumbersome, Expensive L700 L500 L400 L200 L100 Help Paper CD-ROM Spanish French German Italian Portuguese Swedish Danish Russian Turkish Greek Each Documentation Set was Translated into 10 Languages
  • 18. Writing Silos  Collaborative Team
    • Stand-Alone Writers
    • Author-Controlled Content
    • Tweaked Templates
    • Independent Budgets
    • “ Their” Content
    • Content on Writer’s PC
    • Collaborative Writing Team
    • Team-Controlled Content ;
    • Controlled “Brand” Identity
    • Shared Budget
    • Corporate Intellectual Capital
    • Content in Controlled Content Management System
  • 19. What improved and how did it get better when we moved to this environment?
    • We learned that there are a lot of benefits to having a collaborative writing team.
  • 20. Benefit: Shared Content Reuse Strategy
    • Eliminated Redundant Content Development in Each Manufacturing Center
    • Develop Reuse Strategy – Plan Yearly
    • No Duplication of Effort / No Redundancy
    • New features written by writer where new feature was developed – Migrated to product line as feature added to product’s feature set
  • 21. Benefit: Shared Costs
    • Share Template Development Costs (FrameMaker, Online Help, Translated Templates)
    • Share CMS and CMS Customization Cost
    • Share Automated Tool Cost
    • Share Translation Cost
    • Centralized Control & Management
  • 22. Benefit: Wrote Collaboratively
    • Write Content Once – Reuse Many Times
    • Write Generically to Fit Multiple Products
    • Consistent Content – Changes Decided Upon as a Team
    • Content Easily Migrated Across Product Lines
    • Content Reviewed Continually
  • 23. Benefit: Developed Automated Publishing Tools
    • Manually created FM Books, TOCs, Indexes, PDFs, Online Helps vs Using automated tools
    • Now automatically generate FM Books, TOCs, Indexes, PDFs from sgml file
    • Use Batch File to generate 30 translated files
    • Online Help auto generated from sgml  xml  xslt transformation  html help
  • 24. Benefit: Standardized within GE Brand
    • Controlled Templates
    • Controlled Content
    • No more copying and pasting
    • Change content in one place; updated in every reuse
    • Assures content integrity
    • Achieves Brand
  • 25. Benefit: Increased Consistency, Accuracy, & Quality Content
    • Consistent Content
    • Accurate Content
    • Tested Content
    • Subject Matter Expert Verified Content
    • End User Validated Content
  • 26. Benefit: Re-Purposed Content
    • Can re-purpose content to be used by Marketing, by Training, Help Desks
    • Single source content for pdf and chm files Automatic (Not a Separate Effort)
    • Can re-purpose same content into different manuals
    • Multi-functional purposes: training, marketing, across product lines
  • 27. Writers’ Jobs Didn’t Go Away, They Evolved
    • Content Analysis, Metadata Strategy
    • Reuse Analysis and Strategy
    • Tool / Techology Selection, Upgrade, Migration
    • Concise Source Content – Editing Skills, Testing, Verification with SMEs, Validation with End Users
    • Template, CSS Management, Automated Processes
    • More Techno Savvy (sgml, xml, sgml, DITA, language encoding, unicode…)
    • Better, Smarter Writing, NOT More Writing
  • 28.  
  • 29. Benefit: Leveraged Translation Memories – THIS IS HUGE!!!
    • No longer unique product documentation sets, generating multiple sets of translation memories -- Now only one set of Core Content
    • One Core Content
    • One Core Content Translation Memory
    • One TM Leveraged across Multiple Products
    • Consistent, Correct, and Clean TMs
  • 30. Without With Collaboration Collaboration
    • $.25 Per Translated Word
    • Each Page = ~250 Words
    • Or $62.50 Per Translated Page
    • X 1000 Pages = $62,500
    • X 30 Languages = $1,875,000
    • X 15 Products
    • or $28,125,000
    • Additional Writers Required
    $.25 Per Translated Word Each Page = ~250 Words Or $62.50 Per Translated Page X 1000 Pages = $62,500, X 30 Languages = $1,875,000, /5 Manufacturing Centers, or $375,000 No Additional Writers Required EXCEPT that it’s even less. We only write and pay to translate the delta. So, the actual cost yearly is now $400,000 per year, or $80,000 per mfg ctr.
  • 31. And that’s not even counting the time savings…
    • Faster Turnaround Time (1000 page manual ‘written’ in ~ 2 weeks, ‘translated’ in ~ 1 week, ‘dtp’d’ in 1 week, validated and released in 1 week.
    • Start to end, ~5 weeks, in as many languages as you want.
  • 32. Translation Notes
    • Only pay to translate the delta in the database (fuzzy + no matches)
    • Over the past 7 years, the budget has remained constant, between $250,000-$350,000 even though we’ve gone from 10 to 30 languages and from 5 to 16 products
    • And this $250,000 - $350,000 cost is divided by the number of manufacturing centers
    • So each manufacturing center pays roughly $70,000
  • 33. So, Finally, Let’s talk about what it takes to get a Collaborative Team Off the Ground
    • Definition
    • Getting Buy-In
    • Planning Your Team
    • Operating Mechanism
    • Developing and Nurturing Your Team
    • Team Meetings
    • Tracking Progress
    • Standardizing Tools/ Processes
    • Sharing Budgets
    • Accountability
    • Escalating Issues
    • Hiring for a Collaborative Team
    Group Hugs
  • 34. Definition
    • A Collaborative Team is a group of individuals who share common beliefs and work towards common goals. They meet regularly over an extended period of time. Team members share decision making, flexibility, and creative problem solving strategies.
  • 35. Getting Buy-In
    • From Managers
    • From Writers
    • From Finance
    • From Marketing
    • From Program Team Leaders
    • From HR
  • 36. Planning the Team
    • Need to convince team members of the value of working on a team.
    • Share templates and develop together
    • Develop standards
    • Validate translations
    • Automate processes
  • 37. Operating Mechanism
    • Communicate almost daily
    • Meet every 2 weeks
    • Plan, collaborate, strategize, analyze, write
    • Always Improving processes
    • Ensuring integrity of one set of content
  • 38. Developing & Nurturing Your team
    • Changed the way we wrote
    • Train on an on-going basis
    • Empower each team member
    • Know each person’s strengths & rely on them
  • 39. Team Meetings
    • Regular, Scheduled
    • Work from an Agenda
    • Prepare a Standard Status Report
    • Communicate Issues
    • Track Progress
    • Give / Take
  • 40. Tracking Progress
    • Celebrate Wins
    • Track Progress / Changed Milestones
    • Communicate Issues in Plenty of Time
  • 41. Standardizing Tools/Processes
    • Keep infrastructure up to date
    • Ask team members to research new tools
    • Plan future together
    • Communicate issues as they occur
    • Agree on templates
  • 42. Sharing Budgets
    • Prepare yearly budget
    • Determine program requirements, deliverables, translations resources
    • Track costs
    • Report out
  • 43. Accountability
    • Team members must do their own work
    • Must prepare content on time
    • Must follow due diligence (review, validate, follow style guide, abide by template rules)
    • Be a good team member
  • 44. Escalating Issues
    • Some teams only show up when they need something or when their project is active
    • Have an escalation process (go to their direct manager, or to the program leader, or to your manager)
  • 45. Hiring for a Collaborative Team
    • Need to hire team players
    • Not just looking for technical skills or industry knowledge
    • Interpersonal skills near the top of the list
    • Screen out lone wolves, the not-so-nice
    • Involve the team in the hiring process
  • 46. Group Hugs
    • Thank everyone for their hard work
    • All for one, one for all
    • Celebrate each other’s successess
    • Recognize hard work
    • Recognize good work
  • 47. Conclusion
    • The Whole is Greater than the Sum of Its Parts
    • Each writer learns from everyone’s strengths
    • Together as a team, we accomplish more, cheaper, faster, with increased quality and consistency
    • Can generate a 1000-page manual as quickly as 2 days, but normally within 2 weeks
    • Can translate a 1000-page manual into pdfs and online help within 3 weeks
  • 48. Collaborative Team Success Transfers directly to your company’s bottom line.
    • Enabling global content on time – no longer a cost center, but a corporate asset
    • Information becomes capital
    • when it is employed to produce profit.
    • Developing the Content Management System to manage our corporate knowledge assets allows us to easily find, use, and re-use content in a way that maximizes its value to our organization and minimizes the cost to create, maintain, and assemble it for a particular business need.