Get Tability: OKRs that don't suck | Learn more →

15 examples of It Support metrics and KPIs

What are It Support metrics?

Crafting the perfect It Support metrics can feel overwhelming, particularly when you're juggling daily responsibilities. That's why we've put together a collection of examples to spark your inspiration.

Copy these examples into your preferred app, or you can also use Tability to keep yourself accountable.

Find It Support metrics with AI

While we have some examples available, it's likely that you'll have specific scenarios that aren't covered here. You can use our free AI metrics generator below to generate your own strategies.

Examples of It Support metrics and KPIs

Metrics for Business Systems Support

  • 1. Percentage of Systems Fully Functional

    Measures the percentage of business systems across departments that are fully functional without any issues

    What good looks like for this metric: 90-95%

    Ideas to improve this metric
    • Implement regular system maintenance schedules
    • Upgrade outdated software and hardware
    • Conduct frequent system audits
    • Train staff on system usage and troubleshooting
    • Establish a rapid response team for critical issues
  • 2. Average System Downtime

    Calculates the average time that business systems are non-operational

    What good looks like for this metric: Less than 1 hour per month

    Ideas to improve this metric
    • Optimize backup and recovery processes
    • Use automated monitoring tools
    • Schedule updates during off-peak hours
    • Develop and test robust disaster recovery plans
    • Enhance infrastructure reliability with redundancy measures
  • 3. Support Request Resolution Time

    Measures the average time taken to resolve support requests from different departments

    What good looks like for this metric: Less than 4 hours

    Ideas to improve this metric
    • Set clear priority levels for support tickets
    • Implement a ticketing system with tracking capabilities
    • Provide customer service training for IT support staff
    • Create a comprehensive FAQ and knowledge base
    • Encourage self-service for common issues
  • 4. User Satisfaction Score

    Summarises user feedback on their satisfaction with systems support

    What good looks like for this metric: Above 80%

    Ideas to improve this metric
    • Conduct regular satisfaction surveys
    • Analyse feedback to identify common issues
    • Engage users in system improvement discussions
    • Provide transparent updates on resolution progress
    • Recognise and reward high-performance support teams
  • 5. Frequency of System Changes

    Tracks how frequently systems undergo significant updates or changes

    What good looks like for this metric: Monthly or quarterly updates

    Ideas to improve this metric
    • Plan updates based on user feedback and needs
    • Test updates thoroughly in a controlled environment
    • Communicate changes effectively to users
    • Incorporate user feedback for improvements
    • Balance system stability and innovation

Metrics for IT Department Efficiency

  • 1. Incident Response Time

    The average time it takes for the IT department to respond to an incident after it is reported.

    What good looks like for this metric: 30 minutes to 1 hour

    Ideas to improve this metric
    • Implement automated alert systems
    • Conduct regular training sessions
    • Set up a 24/7 support team
    • Streamline incident escalation processes
    • Utilise incident management tools
  • 2. First Contact Resolution Rate

    The percentage of IT issues resolved during the first contact with the user.

    What good looks like for this metric: 70% to 80%

    Ideas to improve this metric
    • Enhance self-service tools and resources
    • Improve knowledge base quality
    • Conduct specialised training for support staff
    • Implement a feedback loop for continuous improvement
    • Use advanced diagnostic tools
  • 3. System Uptime

    The percentage of time that IT systems are operational and available for use.

    What good looks like for this metric: 99% to 99.9%

    Ideas to improve this metric
    • Regularly update and patch systems
    • Implement high availability solutions
    • Conduct regular system monitoring
    • Perform routine maintenance checks
    • Use redundant systems
  • 4. User Satisfaction Score

    The average satisfaction rating given by users after IT services are provided.

    What good looks like for this metric: 4.0 to 4.5 out of 5

    Ideas to improve this metric
    • Offer regular customer service training
    • Obtain user feedback and act on it
    • Enhance communication channels
    • Implement a user-friendly ticketing system
    • Provide regular updates to users
  • 5. Mean Time to Repair (MTTR)

    The average time taken to fully repair an IT issue after it is reported.

    What good looks like for this metric: 2 to 4 hours

    Ideas to improve this metric
    • Improve diagnostic procedures
    • Use automated repair tools
    • Maintain an updated inventory of spare parts
    • Enhance collaboration between IT teams
    • Conduct thorough post-incident reviews

Metrics for Windows and VMWare Server Support

  • 1. First Call Resolution Rate

    Percentage of issues resolved on the first call without escalation

    What good looks like for this metric: 70-80%

    Ideas to improve this metric
    • Provide comprehensive training for team members
    • Implement a robust knowledge base
    • Utilise remote access tools for rapid solutions
    • Ensure clear communication during ticket handling
    • Optimise ticket categorisation for swift allocations
  • 2. Average Ticket Resolution Time

    Average time taken to resolve support tickets

    What good looks like for this metric: Less than 24 hours

    Ideas to improve this metric
    • Enhance prioritisation of critical tickets
    • Streamline internal workflows
    • Employ ticketing software with automation features
    • Offer frequent skill-improving sessions
    • Regularly review ticket handoff processes
  • 3. Customer Satisfaction Score

    Rating provided by customers after resolution

    What good looks like for this metric: Above 90%

    Ideas to improve this metric
    • Solicit feedback through post-service surveys
    • Provide personalised support where applicable
    • Encourage proactive follow-ups with customers
    • Analyse feedback data to identify improvement areas
    • Reward team members demonstrating high satisfaction scores
  • 4. Ticket Backlog

    Number of unresolved tickets over a specified time period

    What good looks like for this metric: Less than 10% of total tickets

    Ideas to improve this metric
    • Regularly audit ticket queue for overdue items
    • Implement weekly backlog reviews
    • Balance team workload to prevent overloads
    • Develop standard operating procedures for common issues
    • Encourage team accountability for assigned tickets
  • 5. Service Uptime

    Percentage of time the server environment is operational and available

    What good looks like for this metric: 99.9%

    Ideas to improve this metric
    • Conduct regular system health checks
    • Implement proactive monitoring systems
    • Establish a thorough disaster recovery plan
    • Schedule routine maintenance during off-peak hours
    • Ensure redundancy for critical systems

Metrics for Business Systems Support

  • 1. System Availability

    The percentage of time a system is up and running compared to the total scheduled operational time

    What good looks like for this metric: 99.9%

    Ideas to improve this metric
    • Implement regular system maintenance
    • Upgrade infrastructure regularly
    • Monitor systems continuously
    • Utilise redundant systems for backup
    • Train staff on quick troubleshooting
  • 2. Response Time

    The time it takes for support to respond to a reported issue

    What good looks like for this metric: Within 1 hour

    Ideas to improve this metric
    • Set up automated alert systems
    • Ensure adequate staffing during peak times
    • Establish clear response protocols
    • Provide ongoing training for support staff
    • Prioritise critical issues
  • 3. Resolution Time

    The average time taken to resolve system issues from the moment they are reported

    What good looks like for this metric: Within 4 hours

    Ideas to improve this metric
    • Streamline problem diagnosis processes
    • Maintain an effective escalation process
    • Document common issues with solutions
    • Conduct root cause analysis
    • Ensure effective communication with users
  • 4. User Satisfaction

    The degree to which users are satisfied with the system support delivered

    What good looks like for this metric: 80% satisfaction rate

    Ideas to improve this metric
    • Conduct regular user feedback surveys
    • Implement feedback into improvement plans
    • Provide personalised support
    • Enhance user training programmes
    • Improve communication with users
  • 5. Percentage of System Coverage

    The proportion of departmental systems that are under active support

    What good looks like for this metric: 95% coverage

    Ideas to improve this metric
    • Regularly update inventory of systems
    • Ensure all critical systems are covered
    • Conduct regular system audits
    • Increase cross-departmental coordination
    • Establish clear support policies

Metrics for Showcase Team Performance

  • 1. Incident Response Time

    The average time taken by the team to respond to reported incidents

    What good looks like for this metric: Less than 30 minutes

    Ideas to improve this metric
    • Implement automated alert systems
    • Conduct regular training on incident management
    • Set clear response time goals
    • Prioritise incidents based on severity
    • Review and analyse past response times for improvement
  • 2. System Uptime

    The percentage of time systems are operational and available

    What good looks like for this metric: 99.9% or above

    Ideas to improve this metric
    • Conduct regular system maintenance
    • Implement redundancy solutions
    • Perform load testing to understand capacity
    • Monitor system health in real-time
    • Establish a disaster recovery plan
  • 3. User Satisfaction Score

    Survey score given by users based on their satisfaction with team support

    What good looks like for this metric: 8 out of 10 or higher

    Ideas to improve this metric
    • Regularly survey users to gather feedback
    • Implement a user-friendly ticketing system
    • Ensure timely updates to users
    • Provide training in customer service skills
    • Analyse feedback and address common issues
  • 4. Ticket Resolution Rate

    The percentage of tickets resolved within the agreed service level agreement (SLA)

    What good looks like for this metric: 95% or higher

    Ideas to improve this metric
    • Establish clear SLAs for ticket resolution
    • Use ticketing software to prioritise workload
    • Encourage team collaboration on complex issues
    • Track pending tickets and address bottlenecks
    • Hold regular reviews on ticket performance
  • 5. Change Success Rate

    The percentage of system changes that are successfully implemented without causing incidents

    What good looks like for this metric: 90% or higher

    Ideas to improve this metric
    • Establish a change management process
    • Conduct risk assessments before changes
    • Communicate changes to all stakeholders
    • Provide training on implementing changes
    • Review and learn from failed changes

Metrics for Container Movement Tracking

  • 1. On-time Arrival Rate

    Percentage of containers arriving at the port on schedule

    What good looks like for this metric: 95%-99%

    Ideas to improve this metric
    • Automate scheduling notices
    • Use real-time tracking tools
    • Coordinate with logistics partners
    • Optimise route planning
    • Implement contingency protocols
  • 2. Container Dwell Time

    Average time containers remain at the terminal before offloading

    What good looks like for this metric: 2-3 days

    Ideas to improve this metric
    • Upgrade processing systems
    • Streamline customs procedures
    • Enhance coordination with transport
    • Schedule timed offloading
    • Implement penalty charges for delays
  • 3. Container Utilisation Rate

    Percentage of container space effectively used during transport

    What good looks like for this metric: 80%-85%

    Ideas to improve this metric
    • Conduct regular audits
    • Implement container sharing
    • Evaluate cargo plans
    • Invest in container optimisation software
    • Train staff on best loading practices
  • 4. Compliance Incidents

    Number of compliance-related issues reported in container tracking

    What good looks like for this metric: 1-2 per quarter

    Ideas to improve this metric
    • Conduct regular staff training
    • Update compliance protocols
    • Implement an incident reporting system
    • Review past incidents for trends
    • Foster a culture of transparency
  • 5. System Uptime

    Percentage of time the Trutrack system is operating without issues

    What good looks like for this metric: 99%-99.9%

    Ideas to improve this metric
    • Schedule regular system maintenance
    • Use reliable servers
    • Ensure adequate IT support
    • Implement redundancy measures
    • Monitor system performance continuously

Metrics for iOS Device Migration

  • 1. Migration Completion Rate

    The percentage of iOS devices successfully migrated to Microsoft Intune

    What good looks like for this metric: 90-95%

    Ideas to improve this metric
    • Develop a detailed migration plan
    • Conduct pilot testing before full rollout
    • Ensure adequate training for IT staff
    • Engage in continuous monitoring and feedback
    • Allocate sufficient resources for the project
  • 2. Post-Migration Device Performance

    Measure the performance of devices post-migration, focusing on speed and application responsiveness

    What good looks like for this metric: Performance increase of 10-20%

    Ideas to improve this metric
    • Optimize device settings during migration
    • Update applications to the latest versions
    • Conduct regular performance assessments
    • Encourage employee feedback for improvements
    • Monitor and address any reported issues promptly
  • 3. Security Incident Reduction

    Track the number of security incidents after migration compared to before

    What good looks like for this metric: Reduction of incidents by 30%

    Ideas to improve this metric
    • Enhance device security configurations
    • Educate users about security best practices
    • Implement regular security audits
    • Continuous monitoring for any anomalies
    • Use threat intelligence platforms
  • 4. User Satisfaction Score

    Survey scores from users regarding their satisfaction with the new system

    What good looks like for this metric: 70% satisfaction rate

    Ideas to improve this metric
    • Conduct user training sessions
    • Offer a user-friendly interface
    • Provide efficient troubleshooting support
    • Incorporate user feedback into improvements
    • Continuously update support materials
  • 5. Network Access Success Rate

    The percentage of successful network access attempts post-migration

    What good looks like for this metric: Above 95%

    Ideas to improve this metric
    • Ensure seamless network integration
    • Update network policies for Intune compatibility
    • Test network access at regular intervals
    • Implement redundancy measures
    • Provide support for network connectivity issues

Metrics for IT Service Agreement Compliance

  • 1. % Compliance with SLA

    The percentage of time that IT services are delivered within the predefined terms of the service level agreement

    What good looks like for this metric: 90-99%

    Ideas to improve this metric
    • Increase training for service delivery teams
    • Enhance monitoring and reporting tools
    • Conduct regular SLA reviews and updates
    • Ensure clear communication of SLA terms to all stakeholders
    • Implement more efficient service processes
  • 2. Response Time to Incidents

    The amount of time taken to respond to IT incidents from the time they are reported

    What good looks like for this metric: 30 minutes

    Ideas to improve this metric
    • Automate incident alert systems
    • Improve resource allocation during peak times
    • Provide advanced training for incident management
    • Utilise real-time monitoring and dashboards
    • Regularly measure and adjust response strategies
  • 3. Resolution Time to Incidents

    The amount of time taken to resolve IT incidents from the time they are reported

    What good looks like for this metric: 4 hours

    Ideas to improve this metric
    • Implement root cause analysis for recurring issues
    • Enhance collaboration across IT teams
    • Use advanced diagnostic and repair tools
    • Schedule regular knowledge sharing sessions
    • Review and optimise workflows for resolution
  • 4. User Satisfaction Rate

    Percentage of users satisfied with the IT services provided in accordance with the SLA

    What good looks like for this metric: 85-90%

    Ideas to improve this metric
    • Conduct regular satisfaction surveys
    • Implement feedback loops for continuous improvement
    • Analyse survey data for actionable insights
    • Ensure rapid follow-up to any user complaints
    • Continuously train staff in customer service skills
  • 5. Change Success Rate

    The percentage of changes to the IT system that are successful and do not result in incidents

    What good looks like for this metric: 95%

    Ideas to improve this metric
    • Perform rigorous change testing before implementation
    • Develop clear guidelines for change management
    • Ensure thorough documentation of all changes
    • Utilise change advisory boards to approve changes
    • Conduct post-change reviews to identify improvement areas

Metrics for Help Desk Performance Tracking

  • 1. Average Ticket Resolution Time

    The average time taken to resolve a ticket from the moment it's opened until it's closed. This measures efficiency in handling support requests.

    What good looks like for this metric: 24 hours or less

    Ideas to improve this metric
    • Automate repetitive tasks
    • Improve staff training
    • Streamline ticket prioritisation
    • Use performance-boosting software
    • Implement a robust knowledge base
  • 2. First Contact Resolution Rate

    The percentage of tickets resolved during the initial contact with the help desk. A high rate indicates effective support processes.

    What good looks like for this metric: 70-75%

    Ideas to improve this metric
    • Equip staff with decision-making power
    • Enhance customer service scripts
    • Provide ongoing training
    • Utilise integrated support tools
    • Conduct regular process reviews
  • 3. Customer Satisfaction Score (CSAT)

    A measure of customer satisfaction with the resolution of their support tickets, often gathered via surveys after ticket closure.

    What good looks like for this metric: 85% or higher

    Ideas to improve this metric
    • Conduct feedback analysis
    • Enhance communication channels
    • Personalise support interactions
    • Reduce wait times
    • Regular staff empathy training
  • 4. Ticket Volume Per Channel

    Tracking the number of tickets received via each support channel (e.g., email, phone, chat) helps understand customer preferences.

    What good looks like for this metric: Balanced distribution across channels

    Ideas to improve this metric
    • Promote diverse contact options
    • Evaluate efficiencies of each channel
    • Optimise routing based on traffic
    • Balance workforce allocation
    • Improve multi-channel integration
  • 5. Backlog Ratio

    The ratio of unresolved tickets at any time, measuring how well the help desk manages its workload.

    What good looks like for this metric: 10% or lower

    Ideas to improve this metric
    • Implement extra shifts during peak times
    • Regularly review and close stale tickets
    • Prioritise high-impact cases
    • Automate low-priority ticket handling
    • Improve resource planning

Metrics for End-User Hardware Performance

  • 1. Uptime Percentage

    The percentage of time the hardware is operational and available to the user without unplanned outages

    What good looks like for this metric: 99%

    Ideas to improve this metric
    • Conduct regular maintenance checks
    • Implement automated monitoring systems
    • Invest in high-quality hardware components
    • Train users on proper device handling
    • Have immediate on-call technical support
  • 2. Mean Time to Repair (MTTR)

    The average time taken to repair a hardware failure and restore functionality

    What good looks like for this metric: Less than 4 hours

    Ideas to improve this metric
    • Streamline repair processes
    • Stock essential spare parts
    • Conduct regular technician training
    • Utilise detailed error logging
    • Develop a priority repair system
  • 3. Mean Time Between Failures (MTBF)

    The average time interval between hardware failures

    What good looks like for this metric: Over 30,000 hours

    Ideas to improve this metric
    • Use high-reliability components
    • Ensure environmental conditions are optimal
    • Regularly update drivers and software
    • Perform thorough pre-deployment testing
    • Implement predictive maintenance strategies
  • 4. Hardware Replacement Rate

    The frequency at which hardware needs replacing due to failure or obsolescence

    What good looks like for this metric: 0-5% annually

    Ideas to improve this metric
    • Analyse end-of-life cycles
    • Prioritise purchasing from reputable manufacturers
    • Develop a proactive upgrade schedule
    • Conduct cost-benefit analysis for replacements
    • Ensure comprehensive warranty coverage
  • 5. User Satisfaction Score

    A measurement of user satisfaction regarding hardware performance and reliability

    What good looks like for this metric: Above 85%

    Ideas to improve this metric
    • Gather regular user feedback
    • Implement user-centric design improvements
    • Ensure consistent hardware updates
    • Offer convenient user support options
    • Address common user complaints proactively

Metrics for Empowering Innovation and Service Delivery

  • 1. System Uptime

    The percentage of time the infrastructure is operational and accessible to users.

    What good looks like for this metric: 99.9%

    Ideas to improve this metric
    • Implement redundancy systems
    • Perform regular maintenance checks
    • Upgrade hardware components
    • Monitor using advanced tools
    • Develop a disaster recovery plan
  • 2. Service Response Time

    The average time taken to respond to service requests or queries from users.

    What good looks like for this metric: Less than 3 seconds

    Ideas to improve this metric
    • Optimise server configurations
    • Use load balancing techniques
    • Increase bandwidth availability
    • Implement caching strategies
    • Enhance database management
  • 3. User Satisfaction Score

    A measure of user satisfaction collected through surveys and feedback forms.

    What good looks like for this metric: Above 85%

    Ideas to improve this metric
    • Conduct regular user feedback sessions
    • Implement a user-friendly interface
    • Deliver consistent customer support
    • Analyse feedback for improvements
    • Introduce regular updates based on suggestions
  • 4. Innovation Adoption Rate

    The percentage of new features or innovations adopted by users over time.

    What good looks like for this metric: Above 60%

    Ideas to improve this metric
    • Promote new features actively
    • Provide training sessions for users
    • Offer incentives for early adoption
    • Simplify the onboarding process
    • Use user testimonials to encourage uptake
  • 5. Incident Resolution Time

    The average time taken to resolve incidents or issues reported within the infrastructure.

    What good looks like for this metric: Under 4 hours

    Ideas to improve this metric
    • Maintain a knowledgeable support team
    • Use automated incident detection
    • Streamline the issue escalation process
    • Maintain a robust incident management tool
    • Review and refine resolution procedures

Metrics for Improving Travel Coordination

  • 1. Communication Error Rate

    Percentage of instances where communication breakdowns occur during coordination

    What good looks like for this metric: 20% or lower

    Ideas to improve this metric
    • Implement standard communication protocols
    • Use clear and concise language
    • Conduct regular training sessions
    • Utilise digital communication tools
    • Collect feedback to identify common errors
  • 2. Time Saved on Coordination

    Average time saved per day by tour leaders through efficient coordination tasks

    What good looks like for this metric: At least 2 hours saved per day

    Ideas to improve this metric
    • Automate repetitive tasks
    • Use scheduling and planning apps
    • Delegate tasks among team members
    • Create templates for common tasks
    • Regularly review and streamline processes
  • 3. Traveller Satisfaction Score

    Average satisfaction score reported by travellers regarding their experience

    What good looks like for this metric: Score of 8 out of 10 or higher

    Ideas to improve this metric
    • Collect and act on traveller feedback
    • Ensure clear and timely communication
    • Enhance the itinerary with engaging activities
    • Provide excellent customer service
    • Offer personalised experiences
  • 4. Task Completion Rate

    Rate at which coordination tasks are completed on time

    What good looks like for this metric: 90% or higher

    Ideas to improve this metric
    • Set realistic deadlines
    • Prioritise tasks based on urgency
    • Monitor task progress regularly
    • Utilise task management software
    • Identify and address bottlenecks
  • 5. Communication Technology Adoption

    Percentage of team members effectively using approved communication tools

    What good looks like for this metric: 85% or higher

    Ideas to improve this metric
    • Provide training on communication tools
    • Offer support and resources
    • Encourage feedback on tool effectiveness
    • Ensure tool accessibility on all devices
    • Regularly update communication tools

Metrics for Infrastructure Productivity Management

  • 1. Uptime

    The percentage of time that the infrastructure is operational and available

    What good looks like for this metric: 99.9% or above

    Ideas to improve this metric
    • Implement proactive monitoring tools
    • Establish robust disaster recovery protocols
    • Regularly update software and firmware
    • Schedule regular maintenance windows
    • Utilize redundant systems for critical components
  • 2. Mean Time to Resolution (MTTR)

    The average time taken to resolve a failure or issue

    What good looks like for this metric: 1 to 4 hours

    Ideas to improve this metric
    • Streamline incident response processes
    • Provide ongoing training for IT staff
    • Utilize automated diagnostics tools
    • Maintain comprehensive documentation
    • Conduct regular post-incident reviews
  • 3. Cost Efficiency

    The measure of operational costs in relation to infrastructure output

    What good looks like for this metric: Cost reduction of 10-20% annually

    Ideas to improve this metric
    • Optimize resource allocation
    • Negotiate better vendor contracts
    • Implement energy-efficient technologies
    • Regularly review spending against budget
    • Leverage cloud services where applicable
  • 4. Capacity Utilisation

    The percentage of total infrastructure capacity being used efficiently

    What good looks like for this metric: 75-85%

    Ideas to improve this metric
    • Monitor usage trends closely
    • Adjust resources based on demand
    • Implement virtualization strategies
    • Plan for future capacity needs
    • Eliminate underutilized resources
  • 5. Security Incident Frequency

    The number of security incidents reported over a specific period

    What good looks like for this metric: Less than 2 incidents per month

    Ideas to improve this metric
    • Enhance security training for employees
    • Regularly update security protocols
    • Utilize advanced threat detection systems
    • Conduct frequent security audits
    • Implement robust access control measures

Metrics for Measuring Image Performance

  • 1. Latency

    The time taken for the image to load from the server to the user's end

    What good looks like for this metric: Typical benchmark value is under 100ms

    Ideas to improve this metric
    • Optimize image sizes
    • Use a Content Delivery Network (CDN)
    • Implement lazy loading
    • Enable browser caching
    • Minimize HTTP requests
  • 2. Cost Per Image Delivered

    The total cost incurred for delivering each image to the user

    What good looks like for this metric: A typical benchmark is under $0.01 per image

    Ideas to improve this metric
    • Choose cost-effective hosting solutions
    • Compress images to reduce size
    • Utilise efficient caching strategies
    • Optimise server infrastructure
    • Leverage cost-effective CDNs
  • 3. Image Load Time

    The amount of time it takes for an image to be fully accessible on a user's screen

    What good looks like for this metric: An ideal benchmark is under 2 seconds

    Ideas to improve this metric
    • Reduce image dimensions
    • Utilise responsive images
    • Implement file format that loads faster
    • Use asynchronous loading
    • Optimise server response times
  • 4. Scalability

    The ability to handle increasing load of image delivery without performance degradation

    What good looks like for this metric: Should smoothly handle a 100% increase in traffic

    Ideas to improve this metric
    • Implement auto-scaling infrastructure
    • Utilise robust load balancing solutions
    • Optimise image storage options
    • Conduct regular stress testing
    • Use scalable databases
  • 5. User Satisfaction

    Measures how satisfied users are with image load times and quality

    What good looks like for this metric: Typical satisfaction rate above 80%

    Ideas to improve this metric
    • Conduct user feedback surveys
    • Analyse user interaction data
    • Regularly update images for relevance
    • Ensure high-resolution options as needed
    • Implement faster image formats

Metrics for Reprocessed Plastic Recycling

  • 1. Annual Sales Volume

    The total quantity of plastic products sold within a year

    What good looks like for this metric: 10,000 MT in 2025, increasing to 50,000 MT by 2035

    Ideas to improve this metric
    • Expand market reach through marketing
    • Increase product quality to boost sales
    • Enhance sales team training and incentives
    • Identify and target key industries needing plastic
    • Collaborate with international partners
  • 2. Production Yield

    The percentage of produced items that meet quality standards

    What good looks like for this metric: 95% in 2025, aiming for 99% by 2035

    Ideas to improve this metric
    • Implement quality checks at each production phase
    • Invest in modern machinery and technology
    • Train employees on quality control processes
    • Conduct regular maintenance on equipment
    • Incorporate lean manufacturing practices
  • 3. Customer Retention Rate

    The percentage of customers who continue to buy over time

    What good looks like for this metric: 80% in 2025, increasing to 95% by 2035

    Ideas to improve this metric
    • Enhance customer service and support
    • Implement a loyalty program
    • Regularly seek customer feedback for improvements
    • Offer personalized deals and discounts
    • Ensure high product quality and consistency
  • 4. Cost per Metric Tonne (MT)

    The cost incurred to produce one metric tonne of plastic

    What good looks like for this metric: 10% reduction by 2026, aiming for 20% reduction by 2035

    Ideas to improve this metric
    • Streamline procurement processes
    • Negotiate better deals with suppliers
    • Optimize production scheduling for efficiency
    • Minimize waste during production
    • Utilize energy-efficient machinery
  • 5. Training Hours per Employee

    The average number of hours each employee spends in training annually

    What good looks like for this metric: 20 hours in 2025, increasing to 60 hours by 2035

    Ideas to improve this metric
    • Develop a comprehensive training calendar
    • Encourage online and external training sessions
    • Introduce mentorship programs
    • Link training to career development plans
    • Utilize technology for training modules

Tracking your It Support metrics

Having a plan is one thing, sticking to it is another.

Having a good strategy is only half the effort. You'll increase significantly your chances of success if you commit to a weekly check-in process.

A tool like Tability can also help you by combining AI and goal-setting to keep you on track.

Tability Insights DashboardTability's check-ins will save you hours and increase transparency

More metrics recently published

We have more examples to help you below.

Planning resources

OKRs are a great way to translate strategies into measurable goals. Here are a list of resources to help you adopt the OKR framework:

Table of contents