Table 1.

Co-design session objectives, methods, and outputs.

Event	Objectives	Methods (analysis)	Outputs
Session 1 (March 27, 2017)	Establish MVPa symptom and quality-of-life measures for patients and physicians 2. Establish parameters for MVP use as communication and self-management tool	Semistructured focus groups (thematic analysis of flip chart data, notes, transcribed notes)	Tool category features: symptoms and activity, red flags/triggers, and guided self-management strategies Summaries, executive summaries
Session 2 (April 18, 2017)	Condense potential functional requirements Determine relative importance and define functionality of MVP requirements Explore how functional requirement use by patients and physicians, to improve patient outcomes	Semistructured focus groups (member check, initial theming and thematic analysis of flip chart data, notes, transcribed notes) Provisional dot voting (frequency counts used as a provisional prioritization criteria for each group)	Categorized tool features Inputs: goal setting, context, symptom tracking, activity tracking, plans/strategies, prognosis prediction (input) Interaction reminders: daily, event-based, periodic outputs; and feedback to patients, physician summary, red flags, prognosis prediction (output) Summaries, executive summaries
Kano presurvey and postsurveys (October 1, 2017 and October 5, 2018)	Determine how stakeholders (patients, physicians, researchers, and decision makers) rated functional requirements by importance and convenience before and after group introduction and review of MVP	Mean (SD) importance score by participant group and all respondents, frequency count by category and participant group) Convenience scores (reported by participant group, frequency count by category and participant group)	Quantified importance/convenience scores for functional requirements Thematic analysis of qualitative comments by group (if required)
Session 3 (October 3, 2018)	To review MVP appearance (wireframes) and mock function, and provide feedback on functional requirements for design iteration with development team and gather a definitive prioritization and ranking of functional requirements for inclusion in the final MVP using dot voting	Semistructured focus group discussion (member check, initial theming and thematic analysis of notes: main take-aways) Dot voting (frequency counts/range on task 1: must-have, won’t-have prioritization and task 2: desirability and actionability prioritization, reported by participant group and all respondents)	Must-have, won’t-have dot voting results by participant group and for all respondents, for each functional requirement Desirability and actionability dot voting results, by participant group, all respondents, for each functional requirement

^aMVP: minimum viable product.