Table 4.
Development and evaluation process of ACTsmart.
| Phase 0 | Innovative | Organizational | ||||
| Identification of challenge. Envision of product. User research. Identify end-users. Identify target market. | Gather expertize and resources needed. Create project organization. Identify strategic/operative goals. Secure funding and resource allocation for phase 1. Define work model. | |||||
| Phase 1 | Organizational | Technical development | Content development | End-user insights | Alpha testing and re-iterations | Beta testing |
| Sprint 0 | Establishment of effect map with goals, target groups and user needs. |
Identify basic needs and functionality. Set limitations for phase 1 (focus on patient interface). Make basic technical choices (independent, cloud based, flexible). |
Interviews with clinicians specialized in chronic pain. | |||
| Sprint 1 |
Definition of operationalized short-and long-term goals. Identification of external risk factors and strategies to prevent/manage the risks. |
Decision to use Microsoft Azure cloud-based platform for both content and data collection. Multidisciplinary design studio session to generate ideas for functionalities. |
Identification of types of content (text, audio, video). |
Interviews with patients. Creation of protopersonas. |
||
| Sprint 2 | Production of HTML-prototype for weekly patient reported outcome measures. |
Paper sketches for content structure. Production of first versions of written content. |
HTML-prototype. Content structure sketches. |
|||
| Sprint 3 | Creation of draft for system navigation and system levels. |
Prototype for audio content. Prototype for written content. Draft of first animated video. |
Weekly patient-reported outcome measures. Solution content. Solution structure. |
|||
| Sprint 4 |
Production of first draft of the structure and content of value module. Creations of more animations. Recording of audio tracks. First drafts of treatment illustrations. |
First draft of value module. Animations. Audio tracks. Illustration drafts. |
||||
| Transition period | Creation of messaging function. Bug testing. |
Collection of system generated data. Interviews with alpha testers. Interviews with clinicians. |
First compound prototype of the application. Weekly patient-reported measures. |
Planning of beta testing in clinical feasibility trial. | ||
| Phase 2 | Organizational | Technical development | End-user insights | Alpha testing and re-iterations | Beta testing | |
| Sprint 0 |
Joint application for further funding. Resource allocation for phase 2. |
First sketches of therapist interface. Creation of double authentication login. |
Recruitment of end-users (adult pain patients) for beta testing. | |||
| Sprint 1 |
Development of web prototype for therapist interface. Ongoing debugging. First- and second line technical support. |
Draft sketches of therapist interface. Web prototype of therapist interface. |
Start of 8-week beta testing (clinical feasibility trial). | |||
| Sprint 2 |
Ongoing debugging. First- and second line technical support. |
Preparation of UX-survey and UX-interviews with beta testers. | Web prototype of therapist interface. | Ongoing beta testing (clinical feasibility trial). | ||
| Sprint 3 | Production of differentiated access for therapist interface. | Web prototype of therapist interface. |
In-depth beta UX interviews. Beta UX survey. |
|||
| Sprint 4 |
Workshop on handling of support and bugs. Completion of first version therapist interface. |
Compilation of beta UX insights. | Patient interface. | |||
| Transition period |
Patient interface. Therapist interface. |
|||||