Developing Metrics that Demonstrate the Value of Technical Communications
Upcoming SlideShare
Loading in...5
×
 

Developing Metrics that Demonstrate the Value of Technical Communications

on

  • 581 views

 

Statistics

Views

Total Views
581
Views on SlideShare
581
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • After moving to the next slide, ask for a show of hands: How many people in the room are…? Managers Writers Editors PMs Other Ask for another show of hands: How many of you have…? Planned for metrics Tracked metrics Reported metrics up the chain of command
  • Metrics are quantitative, measurable
  • So, whether technical communications cost a lot or a little, you might be called upon to demonstrate their value. Or you might want to pitch a tech comms project, in which case you’ll need to be able to project the value of the effort.
  • Too much text here…two slides?
  • Same, too much text--,aybe just remove the bullets, add pictures and put bullets in a handout.
  • For the math challenged, like me…
  • Love the camel!!
  • Using the same case study, calculate the ROI. Document your assumptions. Choose a group leader to present your ROI.

Developing Metrics that Demonstrate the Value of Technical Communications Developing Metrics that Demonstrate the Value of Technical Communications Presentation Transcript

  • May 2011 Developing Metrics that Demonstrate the Value of Technical Communications Vic Passion
    • What are metrics?
    • Kirkpatrick’s levels of evaluation
    • The value of the baseline
    • Choosing your metrics
    • Calculating ROI
    • Wrap-up
    What we’ll cover …
    • Measures to demonstrate the value of technical communications
    What are metrics? Let’s explore why metrics are so important…
    • Depends on:
      • Amount and complexity of content
      • Type and number of deliverables
      • Frequency of updates
      • Translation requirements
      • Amount of customization
      • Tools and techniques
      • Format of source material
      • Other factors
    What do technical communications cost?
    • What are metrics?
    • Kirkpatrick’s levels of evaluation
    • The value of the baseline
    • Choosing your metrics
    • Calculating ROI
    • Wrap-up
    What we’ll cover …
  • Source: *Kirkpatrick, Donald L, Evaluating Training Programs: The Four Levels Kirkpatrick’s levels of evaluation and objectives 4. Results 3. Transfer 2. Learning 1. Reactions Performance-based objectives Satisfaction Job task performance Enterprise, division, and departmental objectives
  • Who wants to know the results? 4. Results 3. Transfer 2. Learning 1. Reactions Supervisors, line managers Technical communications managers Managers Department managers, execs, CEO
    • A transit provider has unacceptable outages for its subway escalators and elevators. Management has designated documentation funds to help reduce time out of operation. What would you measure for at each level?
    Business case 4. Results 3. Transfer 2. Learning 1. Reactions
    • What are metrics?
    • Kirkpatrick’s levels of evaluation
    • The value of the baseline
    • Choosing your metrics
    • Calculating ROI
    • Wrap-up
    What we’ll cover …
    • Compelling metrics show the delta between the baseline and the post-documentation data
    The value of the baseline Documentation and website launched in Q3
    • Build all deliverables around what you want end users to be able to do , integrated with corporate strategy
    • Define what they can do before the release—the baseline
      • Number of errors
      • Revenue generated
      • Orders processed
      • Stock shipped
      • Stock returned
      • Etc.
    The ABCs of performance-based metrics
    • You get what you measure
    • Easy to capture…
      • Performance after release (but what was it before?)
      • Performance of groups with most access to documentation vs. groups with least access (but what about complexity of tasks?)
      • Improvement/degradation over time (but what about upgrades?)
    • Characteristics of good metrics
      • A baseline
      • Near-term benefits
      • Meaningful, tangible
      • Careful analysis
    Choosing the right metrics
    • What are metrics?
    • Kirkpatrick’s levels of evaluation
    • The value of the baseline
    • Choosing your metrics
    • Calculating ROI
    • Wrap-up
    What we’ll cover …
    • Break into groups.
    • Read your case study and decide what you would measure to build a compelling case .
    • Choose a group leader to present your measures.
    Building a compelling case
  • Business cases #1: After three severe injuries to machine operators, a national paper products company requires all machine operators and managers to receive training on an updated user’s guide. #2: A technology company delivers training to its employees and partners on a new enterprise software system for quoting and ordering. #3: After a tax season in which the software company is unable to keep up with support calls, the company launches an online knowledge base. #4: After getting feedback from clients and suppliers that translated materials and updates to documentation are taking too long, an international online retailer implements single sourcing. 10 mins
  • Wrap-Up
    • What are metrics?
    • Kirkpatrick’s levels of evaluation
    • The value of the baseline
    • Choosing your metrics
    • Calculating ROI
    • Wrap-up
    What we’ll cover …
  • Calculating ROI Example: Reduce transit technician repair time by 30 minutes per repair 30 min x $100/hour = $50 $50 x 1,500 repairs per year = $75,000 Cost of documentation = $50,000 (Benefit – Cost)/Cost = ROI ($75,000-$50,000)= $25,000 savings $25,000/$50,000 investment = 50% ROI
      • Use conservative assumptions
      • Focus on only one or two compelling metrics
      • Keep it simple
      • Document your assumptions
    Building a case for a technical communications program
    • Break into the same groups.
    • Using the same case study, calculate the ROI.
    • Document your assumptions.
    • Choose a group leader to present your ROI.
    Calculating ROI
  • Business cases #1: After three severe injuries to machine operators, a national paper products company requires all machine operators and managers to receive training on an updated user’s guide. #2: A technology company delivers training to its employees and partners on a new enterprise software system for quoting and ordering. #3: After a tax season in which the software company is unable to keep up with support calls, the company launches an online knowledge base. #4: After getting feedback from clients and suppliers that translated materials and updates to documentation are taking too long, an international online retailer implements single sourcing. 15 mins
  • Wrap-Up
    • Don’t take your budget for granted
    • Use higher levels of evaluation to speak to execs in your organization
    • Capture the baseline before measuring
    • Capture meaningful, tangible metrics with near-term benefits
    • Estimate proposed ROI by:
      • Documenting your assumptions clearly
      • Using conservative assumptions
      • Focusing on only one or two compelling metrics
      • Keeping it simple
    • (Benefit – Cost)/Cost = ROI
    Key points to take home
  • Vic Passion TechProse Walnut Creek, CA, USA 925.956.4231 [email_address] Your turn!
  • Helping clients navigate change www.techprose.com
  • Backup
  • Business case #1 After three severe injuries to machine operators, a national paper products company requires all machine operators and managers to receive training on an updated users guide.
    • Goals:
      • Fewer lawsuits against the company this year
      • Lower employee absenteeism
      • Lower insurance costs
  • Business case #2 A technology company delivers training to its employees and partners on a new enterprise software system for quoting and ordering.
    • Goals:
      • More efficient use of employee and partner time
      • Better retention of partners
      • Ability to see customers with expiring contracts
  • Business case #3 After a tax season in which the software company is unable to keep up with support calls, the company launches an online knowledge base.
    • Goals:
      • Faster response time
      • Better retention of end users
      • Lower technical support costs
  • Business case #4 After hearing from clients and suppliers that translated materials and updates to documentation take too long, an international online retailer implements single sourcing. Goals:
      • Shorter release cycle
      • Better retention of end users
      • Lower technical support costs