The product requirements to scale a cardiac-monitoring solution
Clinician interviews
Patient focus group
Product strategy
One-to-one interviews with heart-failure nurses and cardiologists, triangulated with a patient and caregiver focus group and analysed through the Four Forces and Jobs To Be Done, to define what a cardiac-monitoring product must do to be adopted at scale.
What will drive clinicians, patients and hospital buyers to adopt a new cardiac-monitoring solution at scale, and what must the product do to improve their workflow?
Clinicians and patients, side by side
Remote one-to-one interviews with around nine heart-failure nurses and cardiologists at St. Luke's, Kansas City, triangulated with a focus group of four device patients and a caregiver, and analysed through the Four Forces, push, pull, inertia and anxiety, and Jobs To Be Done. Eight weeks end to end.
What we found
Integration is the single biggest pull. EMR and Epic integration and automated readings would remove the double jobbing of fragmented portals: "It's duplicating work. A tab in Epic would be great," as Anthony, a cardiologist, put it. Trust in the data is the gate to buy-in: clinicians need confidence in accuracy, patient-visible data boosts compliance, and alert fatigue slows decision-making.
Patients switch at a specific intersection of repeated hospitalisations, family influence and trust in the care team. In Kerm's words: "I had three pulmonary edema episodes in a year and a half before saying yes."
The impact
A clear set of product requirements for adoption at scale: EMR integration, automation of readings, a simpler implant pathway, ROI evidence and strong vendor support, grounded in both clinician workflows and the real triggers behind patient adoption.
Ecommerce 
