Identifying and understanding the concerns of business: A systematic approach to the development of the Australian WorkHealth Program - Arthritis

Abstract

Objective:

The aim of the Australian WorkHealth Program - Arthritis was to develop and test an education program designed to minimise risk of arthritis and prevent or reduce absenteeism and presenteeism. The objective of the current study was to use a wide-ranging, multifaceted and interactive approach to engage with stakeholders in order to inform the content and delivery of the intervention.

Methods:

Methods used to inform program design included a concept mapping workshop, interviews, surveys, a steering committee and an industry advisory group. Engaging with a wide range of stakeholders in multiple ways early in program development allowed for the comparison and verification of data to obtain a better overall picture of the needs of participants. It also offered the opportunity to share ‘ownership’ of the program with stakeholders by generating a program that was tailored to their ethos and needs.

Results:

The stakeholder engagement process was instrumental in building commitment to the program and establishing an overarching model of action. Interview and survey data indicated that awareness of arthritis was low and musculoskeletal disorders more generally were of greater concern. It was agreed that programs should be relevant, evidence-based, involve senior management education, incorporate a business case, and involve tailored implementation and marketing strategies. The qualitative preparatory phase as well as all the engagement work was key to informing program design.

Conclusions:

The approach taken in this study has the potential to inform a wide range of workplace interventions. Engaging with a wide range of stakeholders in multiple ways from program inception allowed for the comparison and verification of information to permit the generation of a model of intervention that had the highest possible chance of success. It offered the opportunity to not only define program content and implementation processes, but to build genuine ‘ownership’ of the program.