<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v10i1e38350</article-id>
      <article-id pub-id-type="pmid">36787170</article-id>
      <article-id pub-id-type="doi">10.2196/38350</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Diversity in Stakeholder Groups in Generative Co-design for Digital Health: Assembly Procedure and Preliminary Assessment</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kushniruk</surname>
            <given-names>Andre</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Adapa</surname>
            <given-names>Karthik</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chaudhry</surname>
            <given-names>Beenish</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Stringer</surname>
            <given-names>Eleah</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Vandekerckhove</surname>
            <given-names>Pieter</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Erasmus School of Health Policy &#38; Management</institution>
            <institution>Erasmus University Rotterdam</institution>
            <addr-line>Burgemeester Oudlaan 50</addr-line>
            <addr-line>Rotterdam, 3062PA</addr-line>
            <country>Netherlands</country>
            <phone>31 10 408 8555</phone>
            <email>vandekerckhove@eshpm.eur.nl</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0858-6563</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Timmermans</surname>
            <given-names>Job</given-names>
          </name>
          <degrees>IR, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4250-275X</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>de Bont</surname>
            <given-names>Antoinette</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0745-4537</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>de Mul</surname>
            <given-names>Marleen</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3447-5920</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Erasmus School of Health Policy &#38; Management</institution>
        <institution>Erasmus University Rotterdam</institution>
        <addr-line>Rotterdam</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Military Management Studies</institution>
        <institution>Netherlands Defence Academy</institution>
        <addr-line>Breda</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Tilburg School of Social &#38; Behavioral Sciences</institution>
        <institution>Tilburg University</institution>
        <addr-line>Tilburg</addr-line>
        <country>Netherlands</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Pieter Vandekerckhove <email>vandekerckhove@eshpm.eur.nl</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>14</day>
        <month>2</month>
        <year>2023</year>
      </pub-date>
      <volume>10</volume>
      <elocation-id>e38350</elocation-id>
      <history>
        <date date-type="received">
          <day>30</day>
          <month>3</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>18</day>
          <month>6</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>28</day>
          <month>10</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>11</day>
          <month>12</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Pieter Vandekerckhove, Job Timmermans, Antoinette de Bont, Marleen de Mul. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 14.02.2023.</copyright-statement>
      <copyright-year>2023</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2023/1/e38350" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Diverse knowledge and ways of thinking are claimed to be important when involving stakeholders such as patients, care professionals, and care managers in a generative co-design (GCD) process. However, this claim is rather general and has not been operationalized; therefore, the influence of various stakeholders on the GCD process has not been empirically tested.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>In this study, we aimed to take the first step in assessing stakeholder diversity by formulating a procedure to assemble a group of diverse stakeholders and test its influence in a GCD process.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>To test the procedure and assess its influence on the GCD process, a case was selected involving a foundation that planned to develop a serious game to help people with cancer return to work. The procedure for assembling a stakeholder group involves snowball sampling and individual interviews, leading to the formation of 2 groups of stakeholders. Thirteen people were identified through snowball sampling, and they were briefly interviewed to assess their knowledge, inference experience, and communication skills. Two diverse stakeholder groups were formed, with one more potent than the other. The influence of both stakeholder groups on the GCD process was qualitatively assessed by comparing the knowledge output and related knowledge processing in 2 identical GCD workshops.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Our hypothesis on diverse stakeholders was confirmed, although it also appeared that merely assessing the professional background of stakeholders was not sufficient to reach the full potential of the GCD process. The more potently diverse group had a stronger influence on knowledge output and knowledge processing, resulting in a more comprehensive problem definition and more precisely described solutions. In the less potently diverse group, none of the stakeholders had experience with abduction-2 inferencing, and this did not emerge in the GCD process, suggesting that at least one stakeholder should have previous abduction-2 experience.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>A procedure to assemble a stakeholder group with specific criteria to assess the diversity of knowledge, ways of thinking, and communication can improve the potential of the GCD process and the resulting digital health.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>collaborative design</kwd>
        <kwd>design methodology</kwd>
        <kwd>stakeholder involvement</kwd>
        <kwd>participatory design</kwd>
        <kwd>digital health</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Stakeholders such as patients, care professionals, and care managers are considered to play an important role in designing and creating digital health [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. A widely used form of co-design that can involve a group of people to develop a digital health product is generative co-design (GCD) [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. GCD is characterized by a collective creative process whereby knowledge is shared by stakeholders to develop a product or service, such as digital health [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. In a GCD process, stakeholders are more actively involved in the creative design process than in a more classical design process [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>A wide variety of people who do not necessarily have a design background, such as patients, care professionals, and health policy makers, can be GCD stakeholders in a digital health project. For instance, content experts such as patients (often referred to as “users”) may improve the uptake of the output, as their needs regarding user guidance, specific reminders, and personal tracking will likely be better addressed [<xref ref-type="bibr" rid="ref13">13</xref>]. Health policy experts may also contribute to digital health development. For instance, it has been suggested that their involvement during the COVID-19 pandemic has led to improved alignment between payers and care professionals, which may have contributed to the rapid uptake of digital health [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p>
        <p>There are both theoretical and practical issues when involving different stakeholders in GCD. From a theoretical standpoint, GCD scholars hypothesize that the more the diverse stakeholders involve in a group in terms of diverse knowledge and ways of thinking, the better the GCD process [<xref ref-type="bibr" rid="ref10">10</xref>]. However, this claim is not clearly explicated, which may be due to the conceptual challenges present, such as the lack of consensus on the definition of “stakeholder” and “involvement” [<xref ref-type="bibr" rid="ref16">16</xref>]. For instance, how one defines involvement depends on how one views stakeholder representation, the time involved in the project, and whether the scope focuses on the project or a wider cultural change [<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref18">18</xref>]. In addition, GCD is part of a larger research field known as participatory design (PD) [<xref ref-type="bibr" rid="ref10">10</xref>]. In PD, specific values are upheld, including democracy, equalized power relations, mutual learning, and situation-based actions [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. However, these values are not currently applied explicitly in the GCD stakeholder selection procedure. For instance, adhering to a democratic principle could mean that not only a hospital manager but also current and future users should be involved in the development process of digital health. However, criteria have not been proposed to justify the selection of ideal participants.</p>
        <p>From a practical point of view, assembling a diverse stakeholder group to design digital technology may require more deliberation in the health care field than in other sectors because the interests of the diverse stakeholders may not be aligned. This may lead to practical challenges for stakeholders in gaining trust and managing multiple stakeholders and time pressure when involving patients and physicians [<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref25">25</xref>]. However, design practice manuals do not address how to overcome these additional challenges when using GCD to develop digital health [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
        <p>When tackling these theoretical and practical issues and involving stakeholders in the GCD process to develop digital health, there is little scientific guidance to help select the best stakeholders. No study has evaluated the performance of different stakeholder groups when using GCD to develop digital health. A meta-review, albeit limited to the development of serious games, has highlighted the need for this research, as the effect of involving some users as stakeholders in PD studies is unclear [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
      </sec>
      <sec>
        <title>Objective</title>
        <p>To provide further scientific guidance on the involvement of stakeholders, we tested the hypothesis that stakeholders with more diverse knowledge and ways of thinking would improve the GCD process. To satisfy this aim, we operationalized the hypothesis through a procedure to assemble distinct stakeholder groups and assess their influence on the GCD process and output. As such, the research question is as follows: <italic>Do stakeholders with diverse knowledge and diverse ways of thinking improve the GCD process for digital health?</italic> The study’s goal is to conduct a preliminary assessment of diverse stakeholder groups assembled through a prescribed procedure in the early stages of a GCD process of a digital health project. This assessment will hopefully provide deeper insights that other researchers and practitioners can consider when deciding the most appropriate stakeholder to involve in their GCD project. With time, this could lead to a validated GCD stakeholder involvement procedure for digital health.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Procedure to Assemble Diverse Stakeholder Groups</title>
        <p>The stakeholder group assembly procedure amounts to the operationalization of the Sanders and Stappers [<xref ref-type="bibr" rid="ref10">10</xref>] hypothesis that stakeholders with more diverse knowledge and ways of thinking could improve the GCD process. To involve stakeholders who meet these requirements in a GCD process, a procedure containing 3 steps was followed: snowball sampling, interviews, and assemblage of stakeholders (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        <p>First, to recruit people, one needs to identify those who are committed to addressing the problem at hand. It can be useful to sample stakeholders through relevant organizations, associations, or events [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. This should help ensure their commitment to solving problems, as these people have directly or indirectly been exposed to the problems and are logically more motivated to develop a solution.</p>
        <p>Second, individual interviews can be conducted to qualitatively assess the diversity of knowledge and ways of thinking of the potential members. To operationalize the term “knowledge,” we define 3 types of knowledge (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>) based on the work of Batens [<xref ref-type="bibr" rid="ref30">30</xref>-<xref ref-type="bibr" rid="ref32">32</xref>]. One key form of knowledge that is also defined in GCD research is the deeper-lying tacit knowledge [<xref ref-type="bibr" rid="ref10">10</xref>], which we measure here as contextual certainties. In addition, there are methodological instructions and relevant statements. Each of these 3 types of knowledge was assessed during an interview on a scale of 0 to 3 (<xref ref-type="table" rid="table1">Table 1</xref>). Stakeholders with extensive knowledge regarding the relevant statements and contextual certainties will be given the maximum score (3); stakeholders who are uncertain are given a score of 2 and those who seemed to have little knowledge, or did not provide relevant information in the interview, were awarded lower scores (1 and 0, respectively).</p>
        <p>To operationalize the other component, “thinking,” we define 4 types of inferences, namely, induction, deduction, abduction-1, and abduction-2 (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>), as categorized initially by Peirce [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref38">38</xref>]. In particular, abduction-2 inferencing is expected to play an important role in the design process [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref38">38</xref>] and is typically attributed to how designers think. Previous experience with these types of inferences can be assessed during an interview by counting the number of times an inference is used (<xref ref-type="table" rid="table1">Table 1</xref>). Abduction-1 can be scored as the number of methodological instructions formulated as concrete solutions (eg, having an overview of one’s energy capacity after cancer treatment to continue work). Abduction-2 can be scored by looking at the use of generative heuristics as analogies or metaphors.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Stakeholder group assembly procedure.</p>
          </caption>
          <graphic xlink:href="humanfactors_v10i1e38350_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <boxed-text id="box1" position="float">
          <title>Working definitions of knowledge and inference types used for assessment.</title>
          <p>
            <bold>Knowledge types</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Contextual certainties</p>
              <list>
                <list-item>
                  <p>Knowledge containing a deeper-lying perspective or philosophical principle</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Methodological instructions</p>
              <list>
                <list-item>
                  <p>An approach to solve a problem or subproblem such as a procedure for operations, instruments, or tools</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Relevant statements</p>
              <list>
                <list-item>
                  <p>Factual knowledge about the problem or the solution</p>
                </list-item>
              </list>
            </list-item>
          </list>
          <p>
            <bold>Inference types</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Induction</p>
              <list>
                <list-item>
                  <p>A sequence of reasoning steps leading to a generalization, whereby several similar utterances are grouped under a new term or name, often in the form of a remark or conclusion following the utterances of others [<xref ref-type="bibr" rid="ref33">33</xref>]</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Deduction</p>
              <list>
                <list-item>
                  <p>A sequence of reasoning steps leading to a conclusion based on several previous utterances [<xref ref-type="bibr" rid="ref33">33</xref>]</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Abduction-1</p>
              <list>
                <list-item>
                  <p>A sequence of reasoning steps leading to the suggestion of a solution in the form of a methodological instruction</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Abduction-2</p>
              <list>
                <list-item>
                  <p>A sequence of reasoning steps leading to the suggestion of a solution in the form of a methodological instruction whereby induction, deduction, abduction-1 and generative heuristics can be used, for example, a metaphor [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>] or analogy [<xref ref-type="bibr" rid="ref36">36</xref>]</p>
                </list-item>
              </list>
            </list-item>
          </list>
        </boxed-text>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Criteria used for stakeholder selection.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="310"/>
            <col width="0"/>
            <col width="660"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Assessment aims and criteria</td>
                <td>Example interview questions and assessment</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4">
                  <bold>Assess knowledge diversity and depth</bold>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="3">
                  <break/>
                </td>
                <td>Professional background</td>
                <td colspan="2">What is your job?</td>
              </tr>
              <tr valign="top">
                <td>Relevant statements</td>
                <td colspan="2">What, in your view, is the core of the problem about cancer and work? (0-3 score)</td>
              </tr>
              <tr valign="top">
                <td>Contextual certainties</td>
                <td colspan="2">Why is this an important problem? (0-3 score)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Assess inference experience</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Induction</td>
                <td colspan="2">How did you come upon this problem, through direct or indirect experience? (0-3 score)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Deduction</td>
                <td colspan="2">Have you previously tested solutions regarding work and cancer? (0-3 score)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Abduction-1 (methodological instructions)</td>
                <td colspan="2">What inspiring solutions arise in your mind to address the work and cancer challenge? (count number of occurrences)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Abduction-2</td>
                <td colspan="2">Abduction-1 with generative heuristics as analogies or metaphors (count number of occurrences)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Assess communication abilities</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Self- assessment</td>
                <td colspan="2">Choice between 3 suggested answers: “OK, but sometimes challenging,” “good,” or “very good”</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>In addition, communication skills can be assessed to determine whether potential stakeholders can effectively communicate their ideas to others in a group. For instance, we can assess whether a patient has the appropriate content expert background with various relevant statements that they feel confident to share during a GCD process with other stakeholders by asking the respondent for a self-evaluation.</p>
        <p>Third, after conducting the interviews and scoring the responses, a diverse stakeholder group can be assembled based on 3 criteria. One can start by combining people from different professional backgrounds. Next, one can ensure that those stakeholders with the highest knowledge scores are included as they have more knowledge. In other words, if there are 2 stakeholders with the same professional background, the one with the highest score is included. Finally, the diversity of inferencing experience can be assessed. Here, one should ensure that a stakeholder group covers all inference types. Once one is satisfied that the stakeholder group covers all inference types, one can seek out the stakeholders with the greatest inference experience. For instance, if there are 2 stakeholders with abduction-2 experience, the one with the most experience (highest score) can be selected.</p>
      </sec>
      <sec>
        <title>Action Research Approach</title>
        <p>To assess the stakeholder group assembly procedure, an action research approach [<xref ref-type="bibr" rid="ref39">39</xref>] was used to guide the practitioners of a GCD project while adding the stakeholder group assembly procedure to simultaneously gain research insights.</p>
      </sec>
      <sec>
        <title>Hypothesis to Test</title>
        <p>The aim was to test how a stakeholder group, assembled using the stakeholder group assembly procedure described in the aforementioned section, would influence the GCD process. We expected that this stakeholder group assembly procedure would produce a group with diverse knowledge and ways and that this would have a positive influence on the GCD process and output. We also expected that, in such a group, the “contextual certainties” knowledge type would be expressed more often by all stakeholders and the “abduction-2” inference type would be more often used specifically by the stakeholders with design expertise than in our less-experienced comparison group.</p>
      </sec>
      <sec>
        <title>Digital Health Project</title>
        <p>A digital health development project in which multiple stakeholders could be involved in the GCD process was sought, and we could test the stakeholder assembly procedure to determine if it could make the GCD process more methodologically sound. Given the expertise of the first author (PV) with the problems faced by patients with cancer, a related project was identified and initiated by a Dutch cancer foundation called oPuce (The Foundation). The Foundation aims to create awareness of the stigmatization of cancer and supports initiatives to help people with cancer continue working during and after the illness and promote their return to paid work [<xref ref-type="bibr" rid="ref40">40</xref>]. The Foundation had planned to start the development of a serious game to help people with cancer address their work-related needs. Although the actual development process had not yet started, The Foundation was interested in using a co-design process to develop the serious game. Because The Foundation had a large network of people who could potentially be involved as stakeholders in the design process to develop the serious game, we chose to add the stakeholder group assembly procedure as a first step in this process and help them with the first GCD activity.</p>
      </sec>
      <sec>
        <title>Ethics Approval</title>
        <p>Ethics approval was granted by Erasmus Medical Centre’s Ethics Committee (MEC-2021-0231).</p>
      </sec>
      <sec>
        <title>Assembled Stakeholder Group</title>
        <sec>
          <title>Overview</title>
          <p>The stakeholder group assembly procedure described in the aforementioned section was followed in this study. The research data were solely managed by the first author (PV). The stakeholders received no financial compensation to participate in this study.</p>
          <p>Here, we describe how snowball sampling, interviews, and group assembly were carried out. The first author initiated the snowball sampling [<xref ref-type="bibr" rid="ref41">41</xref>] by approaching people at The Foundation via email and phone to identify stakeholders. At the end of this process, 13 potential stakeholders who had been involved in the initial conversations over the development of a serious game were identified (<xref ref-type="table" rid="table2">Table 2</xref>).</p>
          <p>The 13 potential stakeholders were each assessed through 45-minute interviews, except for the network coordinator with COVID-19. Before the interviews, the participants were informed about the research and asked for informed consent. The web-based audio and video recorded interviews were carried out by PV and facilitated by creative exercises on Miro’s web-based collaborative whiteboard platform (Miro Corp; <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). The creative exercises helped the interviewees gain a visual understanding of their ideas and become accustomed to the web-based creative software they would use during the GCD workshop.</p>
          <p>Given that there were multiple stakeholders with similar backgrounds but scored differently in terms of knowledge and inference, the stakeholders could be divided into 2 groups (<xref ref-type="table" rid="table3">Tables 3</xref> and <xref ref-type="table" rid="table4">4</xref>). A more potent stakeholder group was formed of stakeholders with diverse backgrounds who scored highly on the knowledge and inference criteria. These stakeholders scored high in terms of providing more relevant statements and contextual certainties. This group had experience with all the inference types. A less potent stakeholder group was formed of the remaining stakeholders who still met the desired range of diverse backgrounds but scored less on the knowledge and inference criteria by showing less extensive knowledge and less inferencing experience during the interviews. Notably, none of the stakeholders in this group had experience with abduction-2 inferencing.</p>
          <p>The stakeholders in both groups were unaware of this selection procedure, or why they were placed in which group, and the detailed aims of the study.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Number of potential stakeholders identified through snowball sampling per professional background (N=13).</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="520"/>
              <col width="480"/>
              <thead>
                <tr valign="top">
                  <td>Background</td>
                  <td>Stakeholder, n (%)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Game developer and designer</td>
                  <td>1 (8)</td>
                </tr>
                <tr valign="top">
                  <td>Employer (employing people with cancer)</td>
                  <td>3 (23)</td>
                </tr>
                <tr valign="top">
                  <td>Employer network</td>
                  <td>2 (15)</td>
                </tr>
                <tr valign="top">
                  <td>Employed cancer survivor</td>
                  <td>1 (8)</td>
                </tr>
                <tr valign="top">
                  <td>Occupational physician</td>
                  <td>1 (8)</td>
                </tr>
                <tr valign="top">
                  <td>Researcher</td>
                  <td>3 (23)</td>
                </tr>
                <tr valign="top">
                  <td>Network coordinator and patient with a previous history of cancer</td>
                  <td>1 (8)</td>
                </tr>
                <tr valign="top">
                  <td>IT manager</td>
                  <td>1 (8)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Scores of stakeholders in the more potent diverse group.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="600"/>
              <col width="400"/>
              <thead>
                <tr valign="top">
                  <td>Background</td>
                  <td>Score<sup>a</sup></td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Game developer and designer</td>
                  <td>11</td>
                </tr>
                <tr valign="top">
                  <td>Employer (employing people with cancer in company A) and facilitator</td>
                  <td>11</td>
                </tr>
                <tr valign="top">
                  <td>Employer (employing people with cancer in company B)</td>
                  <td>9</td>
                </tr>
                <tr valign="top">
                  <td>Employer network</td>
                  <td>9</td>
                </tr>
                <tr valign="top">
                  <td>Employed cancer survivor</td>
                  <td>9.5</td>
                </tr>
                <tr valign="top">
                  <td>Occupational physician</td>
                  <td>10</td>
                </tr>
                <tr valign="top">
                  <td>Researcher</td>
                  <td>11.5</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>Average score per stakeholder is 10 (SD 0.95).</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>Sores of stakeholders in the less potent diverse group.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="500"/>
              <col width="500"/>
              <thead>
                <tr valign="top">
                  <td>Background</td>
                  <td>Score<sup>a</sup></td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Researcher 1</td>
                  <td>5</td>
                </tr>
                <tr valign="top">
                  <td>Researcher 2</td>
                  <td>3.5</td>
                </tr>
                <tr valign="top">
                  <td>IT manager</td>
                  <td>2.5</td>
                </tr>
                <tr valign="top">
                  <td>Employer network</td>
                  <td>3.5</td>
                </tr>
                <tr valign="top">
                  <td>Employer and facilitator</td>
                  <td>6</td>
                </tr>
                <tr valign="top">
                  <td>Network coordinator and cancer survivor<sup>b</sup></td>
                  <td>10</td>
                </tr>
                <tr valign="top">
                  <td>Ecosystem expert<sup>c</sup></td>
                  <td>—<sup>d</sup></td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>Average score per stakeholder is 5 (SD 2.47).</p>
              </fn>
              <fn id="table4fn2">
                <p><sup>b</sup>No formal interview was conducted; information was gathered through informal conversations.</p>
              </fn>
              <fn id="table4fn3">
                <p><sup>c</sup>No interview was conducted because this stakeholder only joined as an observer at the start of the generative co-design workshop.</p>
              </fn>
              <fn id="table4fn4">
                <p><sup>d</sup>Not available.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Data Collection</title>
          <p>Data were collected during individual interviews as part of the stakeholder assessment procedure. In addition, data were collected in 2 identical parallel workshops that were part of a larger web-based event organized by The Foundation regarding the working of their organization. Before the workshops, all the stakeholders were given information about the aim of the identical parallel-running workshops, and a link was provided to familiarize themselves with the web-based Miro platform. GCD workshops are social activities in which stakeholders can share knowledge and work with creative exercises toward achieving the purpose of the design project [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. Web-based workshops were considered the best option given the COVID-19 pandemic restrictions. The 30-minute web-based GCD workshops were audio and video recorded.</p>
          <p>To provide a focus for the assessments, the GCD workshops were slightly artificially divided into 2 phases: the problem phase with the aim to understand the issues to formulate a problem definition and the solution phase to create ideas for a solution. The materials used in the 2 parallel-running GCD workshops were identical and organized specifically to focus on the interactions among stakeholders in both phases. Both groups received 5 identical instructions with a hexagon template delineating both the problem and solution phases, and sticky notes were provided (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
          <p>In terms of roles, PV similarly facilitated both workshops and switched between them to ensure that the instructions were clear while consciously avoiding steering the content development process. Each stakeholder participated in the respective workshops as a co-designer. In addition, before the workshops, 2 stakeholders were asked if they would take on the double role of a participant and an assistant facilitator. All participants, including the assistant facilitators, were blinded to the hypotheses and aims of the study.</p>
        </sec>
        <sec>
          <title>Qualitative Analysis</title>
          <p>The data from the interviews and workshops were iteratively coded and analyzed using ATLAS.ti (Mac Version 22.1.0; Scientific Software Development GmbH). The influences of the 2 diverse stakeholder groups on the GCD process were assessed in terms of knowledge changes (knowledge output) and how the stakeholders processed the knowledge (the use of inferences). Given this focus, the changes in knowledge were assessed by comparing the knowledge displayed during the initial interviews with that developed during the workshop within both groups.</p>
          <p>To compare the 2 workshops, we coded each set of interactions between stakeholders in the problem and solution phases about a certain topic as a sequence in each workshop. In each sequence, we used the deductive and inductive codes described in the following section to be able to compare the knowledge processing of both stakeholder groups in each sequence and phase. We separately compared the sequences of both groups in the problem and solution phases because the knowledge outputs in the problem phase (the problem statement) and solution phase (forms of methodological instructions) were different.</p>
          <p>Thematic and inductive codes were used to assess changes in the knowledge from that revealed in the interviews to that in the workshops. The thematic codes were based on the definitions in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, using 3 types of knowledge and 4 inference types to assess the knowledge processing and output. Using the same definitions of the assessment criteria during the stakeholder group assembly procedure and workshop analysis ensured that we could compare at the level of knowledge and inference types. The interview data can show that an individual stakeholder mentioned a certain fact (relevant statement type) or a certain approach to finding a solution (methodological instruction type) before joining the GCD process. To evaluate the changes in knowledge possessed by the stakeholders over time, that is, interview through workshop, we used codes such as “repetition from interview” if the knowledge generated in a workshop had already been mentioned by one of its members in their interviews. If the knowledge did change during the workshop, we assessed how it had changed in a particular sequence of interactions between stakeholders.</p>
          <p>Thematic inference type codes were used to code group interactions during the GCD workshops. We followed a coding approach similar to that by Cramer-Petersen et al [<xref ref-type="bibr" rid="ref33">33</xref>], whereby inferences were coded and analyzed in an empirical design setting. As such, utterances that bore similarities to the logical inference forms were coded according to the appropriate inference type (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>).</p>
          <p>To further qualify the knowledge processing and knowledge output identified with the above-described deductive codes, 17 inductive codes (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>) were used to identify stakeholder behaviors (eg, suggest a new idea or a reformulation; <xref ref-type="table" rid="table5">Table 5</xref>). These were used to understand why certain knowledge or inference types were used in each sequence.</p>
          <p>To assess the knowledge output in a sequence during the solution phase, 4 inductive codes were used to code knowledge changes through stakeholder interactions (<xref rid="figure2" ref-type="fig">Figure 2</xref>): concrete specific (eg, proposing to use a coach), concrete general (eg, proposing to use artificial intelligence), abstract specific (eg, a virtual angel—a specific object or artifact), and abstract general (eg, an empowering journey—a general image that may contain several specific solutions).</p>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>Examples of inductive code names and definitions to assess changes of knowledge within the workshops (see <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> for complete list).</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="150"/>
              <col width="850"/>
              <thead>
                <tr valign="top">
                  <td>Code name</td>
                  <td>Definition</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Introduce</td>
                  <td>Utterance whereby a new idea is proposed</td>
                </tr>
                <tr valign="top">
                  <td>Reformulate</td>
                  <td>Utterance whereby a previous idea is expressed using different words</td>
                </tr>
                <tr valign="top">
                  <td>Add</td>
                  <td>Utterance whereby aspects are added to a new idea</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Inductive codes to code the knowledge changes: on x-axis from abstract to concrete and on y-axis from general to specific.</p>
            </caption>
            <graphic xlink:href="humanfactors_v10i1e38350_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Main Findings</title>
        <p>Our hypothesis on diverse stakeholders was confirmed, as the more potent stakeholder group had a relatively larger influence on the GCD workshop process and output in the problem phase (see <italic>Greater Processing of Relevant Statements Increased Knowledge About the Problem</italic>) and solution phase (see <italic>Greater Use of Abduction-2 Inferencing Improves the Concreteness and Specificity of Solutions</italic>) than the less potent group (<xref ref-type="table" rid="table6">Table 6</xref>). Regarding the problem phase, in terms of influence on the process, the more potent stakeholders built on each other’s relevant statements, some of which had already been mentioned in the interviews before the workshop. Here, we noticed a dual movement. On the one hand, there was an expansive movement of diverse knowledge as the varied stakeholders shared their knowledge about the problem, and on the other hand, there was a narrowing integrative movement in which the content of ideas changed, and this changed the course of the discussion. In terms of <italic>output</italic>, the more potent group developed a more comprehensive problem definition.</p>
        <p>Regarding the solution phase, in terms of influence on the <italic>process</italic>, the more potent group used more abduction-2 inferences, leading to a greater variety of methodological instructions (<xref ref-type="table" rid="table6">Table 6</xref>). In addition, the more potent diverse stakeholder groups, as in the problem phase, developed each other’s methodological instructions. This made the solutions more concrete and specific. Therefore, in terms of GCD <italic>output</italic> in the solution phase, the more potent stakeholders had a greater influence, as this group produced more precisely described solutions.</p>
        <p>The other 2 subhypotheses were not supported. Only once, and only implicitly, contextual certainties were identified in the GCD workshop (<xref ref-type="table" rid="table6">Table 6</xref>). This was true only among the more potent stakeholder groups. As such, there seems to be no substantial difference between the 2 groups in terms of explicitly sharing more tacit deeper-lying knowledge. Furthermore, although we had expected abduction-2 type inferencing to be applied by stakeholders with a design background, it was not used by the game developer who was the only participant with this background in the more potent diverse stakeholder group. Rather, abduction-2 inferences were made by the nondesigners in this group, which is contrary to our expectations.</p>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Frequency of codes in interactions in the more potent and less potent stakeholder groups.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="400"/>
            <col width="120"/>
            <col width="0"/>
            <col width="120"/>
            <col width="0"/>
            <col width="120"/>
            <col width="0"/>
            <col width="210"/>
            <thead>
              <tr valign="top">
                <td rowspan="2" colspan="2">Code group and code</td>
                <td colspan="4">Frequency in more potent group</td>
                <td colspan="3">Frequency in less potent group</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Problem phase</td>
                <td>Solution phase</td>
                <td colspan="3">Problem phase</td>
                <td>Solution phase</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="9">
                  <bold>Inference type</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <italic>Induction<sup>a</sup></italic>
                </td>
                <td>
                  <italic>10</italic>
                </td>
                <td colspan="2">0</td>
                <td colspan="2">
                  <italic>0</italic>
                </td>
                <td colspan="2">2</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <italic>Deduction</italic>
                </td>
                <td>
                  <italic>9</italic>
                </td>
                <td colspan="2">6</td>
                <td colspan="2">
                  <italic>4</italic>
                </td>
                <td colspan="2">5</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Abduction-1</td>
                <td>0</td>
                <td colspan="2">2</td>
                <td colspan="2">0</td>
                <td colspan="2">5</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <italic>Abduction-2</italic>
                </td>
                <td>0</td>
                <td colspan="2">
                  <italic>13</italic>
                </td>
                <td colspan="2">0</td>
                <td colspan="2">
                  <italic>0</italic>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="9">
                  <bold>Knowledge type</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <italic>Relevant statements</italic>
                </td>
                <td>
                  <italic>14</italic>
                </td>
                <td colspan="2">4</td>
                <td colspan="2">
                  <italic>10</italic>
                </td>
                <td colspan="2">6</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <italic>Methodological instructions</italic>
                </td>
                <td>0</td>
                <td colspan="2">24</td>
                <td colspan="2">0</td>
                <td colspan="2">
                  <italic>8</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Contextual certainties</td>
                <td>1</td>
                <td colspan="2">0</td>
                <td colspan="2">0</td>
                <td colspan="2">0</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table6fn1">
              <p><sup>a</sup>Key differences have been highlighted in italics.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>The Greater Processing of Relevant Statements Increased Knowledge About the Problem</title>
        <p>In terms of interactions about the problem, the stakeholders in the more potent group shared a greater diversity of relevant statements (14 vs 10), which were processed using more induction (10 vs 0) and deduction inferences (9 vs 4) than the less potent diverse stakeholder group did (<xref ref-type="table" rid="table6">Table 6</xref>). Furthermore, the stakeholders in the first group built on each other’s relevant statements, some of which had already been mentioned in the interviews before the workshop. These interactions were related to focusing on the discussion, asking questions, explaining ideas, introducing new ideas, and reformulating old ones, which occurred more frequently in the more potent group.</p>
        <p>How stakeholders in the more potent stakeholder group developed each other’s knowledge about the problem is clearly demonstrated in the examples of the more potent group (<xref ref-type="table" rid="table7">Table 7</xref>). The employer expanded the discussion concerning the self-management of cancer survivors and added that one should consider the resilience of these people and avoid putting them into a victim role. Although he had already mentioned the need for a bespoke resilient solution in the individual interview, this was not in relation to considering the victim role of a patient or in relation to self-management. The employer and facilitator reformulated these points slightly and responded that this comment was related to developing the content of the serious game rather than its implementation. The game developer specified (relevant statement) that these aspects concern the content and didactics behind the content of the serious game. This probably follows from a more abstract principle that the game designers believe in, that “the content of a serious game always has a didactic aim behind it” (contextual certainty). The employed cancer survivor returned to what the employer had mentioned earlier and questioned whether there was a victim role at all. Finally, the employer and facilitator attempted to integrate the different points and reformulate this as a new question.</p>
        <p>Thus, in the more potent group, the stakeholders such as employers and a patient shared their views on the problem by asking questions, reformulating points, and trying to draw connections. They shared their different ways of viewing self-management for people with cancer looking forward to returning to work. As a stakeholder, the technological background of the game developer enabled him to quickly point out how this could be accommodated in a serious game through the underlying didactics. This shows how each of the different stakeholders in the GCD process can rapidly interject useful information to define the problem based on the actual needs while conforming to what is technically needed and possible.</p>
        <p>The interaction between stakeholders in the less potent group (<xref ref-type="table" rid="table8">Table 8</xref>) was more a group conversation without people building on each other’s knowledge (relevant statements). This led to less integration of the knowledge that was being shared. Even though they seemed to make a start to focus on the aspect of the problem as “the barriers preventing people with cancer to resume work,” they did not ask each other what that means or attempted to define the barriers. In the more potent stakeholder group, we observed more concentrated attention on the content of the problem, which led to more integration of knowledge about the problem, for example, the concepts of self-management, the victim role, and serious game development were rapidly connected to a problem definition.</p>
        <table-wrap position="float" id="table7">
          <label>Table 7</label>
          <caption>
            <p>Sequence with codes from more potent diverse stakeholder group (translated into English for reporting purposes).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="430"/>
            <col width="0"/>
            <col width="110"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="160"/>
            <col width="0"/>
            <col width="120"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Stakeholder and sequence of utterances (order of conversation)</td>
                <td colspan="2">Behavior code</td>
                <td colspan="2">Inference-type code</td>
                <td colspan="2">Knowledge-type code</td>
                <td>Repetition code</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1. It feels to me that a user-centered bespoke solution is very general. I mean, doesn’t that apply to any situation?</td>
                <td colspan="2">Focus</td>
                <td colspan="2">Deduction</td>
                <td colspan="2">—<sup>a</sup></td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer and facilitator</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2. How would you make it more concrete?</td>
                <td colspan="2">Focus and ask</td>
                <td colspan="2">Deduction</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>3. For example, coming back to what was said previously, how can we facilitate self-management? How can we avoid creating a victim role?</td>
                <td colspan="2">Introduce</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Because we want to make something bespoke. For example, how can you contribute to the resilience of the candidates looking for work or those who want to maintain work?</td>
                <td colspan="2">Explain</td>
                <td colspan="2">Deduction</td>
                <td colspan="2">Relevant statement</td>
                <td colspan="2">From interview</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>It’s in line with self-management, but a bit more.</td>
                <td colspan="2">Reformulate</td>
                <td colspan="2">Induction</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer and facilitator</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>4. How can you connect that to a serious game? It’s obviously also a general problem.</td>
                <td colspan="2">Ask</td>
                <td colspan="2">Deduction</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>How do you maintain self-management? How do you prevent the victim role? Then, you are in the development process of the serious game.</td>
                <td colspan="2">Reformulate</td>
                <td colspan="2">Induction</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Game developer and designer</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>5. But more content, the didactics behind it.</td>
                <td colspan="2">Introduce</td>
                <td colspan="2">Induction</td>
                <td colspan="2">Relevant statement and contextual certainty</td>
                <td colspan="2">From interview</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>6. The content</td>
                <td colspan="2">Reformulate</td>
                <td colspan="2">Induction</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Game developer and designer</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>7. Yes, indeed</td>
                <td colspan="2">Agree</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employed cancer survivor</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>8. If there would be a victim role?</td>
                <td colspan="2">Ask</td>
                <td colspan="2">—</td>
                <td colspan="2">Relevant statement</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer and facilitator</bold>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="2">
                  <break/>
                </td>
                <td>9. I am thinking about the last point of (employer) and from (researcher) to keep it concrete and small and still also connect it with the piece on implementation.</td>
                <td colspan="2">Focus</td>
                <td colspan="2">Induce</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td>Then we arrive again at the point of how do we make sure that the serious game offers added value for individual employees with cancer, but then we still remain with a big problem.</td>
                <td colspan="2">Reformulate</td>
                <td colspan="2">Deduce</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table7fn1">
              <p><sup>a</sup>Not available.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Over time, the interactions about the problem in the GCD workshop with the more potent stakeholders showed a dual movement that was not present in the less potent group. On the one hand, there was an expansive movement of diverse knowledge as the stakeholders shared more knowledge about the problem and on the other hand, there was a narrowing integration movement whereby the content of ideas changed, which changed the course of the discussion. For example, initially, there was an expansive diverse knowledge movement as various stakeholders discussed the broad theme of user-centeredness. Then, there was a narrowing integration discussion about the definition of the user, whereby the question was raised as to whether one should focus on the development or implementation aspects. Some aspects were considered together, as it was mentioned that self-management was important for users. Here, the initial ideas changed as this was rephrased to clarify that some aspects are relevant during the development phase of the serious game and others during its implementation. Other elements that were discussed concerned resilience and the victim roles to be considered (<xref ref-type="table" rid="table8">Table 8</xref>), although these were not integrated into the problem definition. This dual movement may have contributed to the more potent diverse stakeholder group having a more comprehensive problem definition (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>) than the less potent group. In the problem definition phase, the less potent stakeholder group seemed to have brought together ideas in an expansive movement; however, there was no subsequent integration of or change in the content that formed the problem definition. The more potent group’s more elaborate problem definition seems to have provided a better-founded basis on which to develop solutions.</p>
        <table-wrap position="float" id="table8">
          <label>Table 8</label>
          <caption>
            <p>Sequence with codes from less potent diverse stakeholder group (translated into English for reporting purposes).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="420"/>
            <col width="0"/>
            <col width="120"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="160"/>
            <col width="0"/>
            <col width="120"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Stakeholder and sequence of utterances (order of conversation)</td>
                <td colspan="2">Behavior code</td>
                <td colspan="2">Inference-type code</td>
                <td colspan="2">Knowledge-type code</td>
                <td>Repetition code</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="10">
                  <bold>Researcher 1</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1. If I am now looking. I am focusing on the serious game. That seems to be the starting point. Then, I think a central problem is that we see that the current ways of people getting back to work are not successful. And we want to improve that. Improve self-management. Well, let’s continue here, I am sure you can add to this.</td>
                <td colspan="2">Introduce</td>
                <td colspan="2">Deduction</td>
                <td colspan="2">Relevant statement</td>
                <td colspan="2">From interview</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer and facilitator</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2. Does everyone agree?</td>
                <td colspan="2">Ask</td>
                <td colspan="2">—<sup>a</sup></td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Network coordinator and cancer survivor</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>3. I think also, how can you improve the collaboration? How can you, with each other? Perhaps intercompany or inter-academic? Perhaps, this has nothing to do with…</td>
                <td colspan="2">Introduce and ask</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Ecosystem expert</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>4. What I thought is that solution-oriented thinking is more on the outside of the hexagon (exercise template). I think that the word removing barriers to resume work, that is for example a problem related to the content. I don’t know how others are looking at this?</td>
                <td colspan="2">Introduce, reformulate, and ask</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Researcher 2</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>5. I agree with that.</td>
                <td colspan="2">Agree</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Network coordinator and cancer survivor</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>6. This is about keeping your work?</td>
                <td colspan="2">Ask and reformulate</td>
                <td colspan="2">Deduction</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Ecosystem</bold>
                  <bold>expert</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>7. Keeping your work.</td>
                <td colspan="2">Agree</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table8fn1">
              <p><sup>a</sup>Not available.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <boxed-text id="box2" position="float">
          <title>Problem definitions.</title>
          <p>
            <bold>Problem definition of the more potent diverse stakeholder group</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>How do we realize a bespoke approach and self-management during the implementation of the serious game (whilst taking this into account during development of the serious game)?</p>
            </list-item>
          </list>
          <p>
            <bold>Problem definition of the less potent diverse stakeholder group</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Maintaining work during and after cancer</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Greater Use of Abduction-2 Inferencing Improves the Concreteness and Specificity of Solutions</title>
        <p>In the solution phase, the more potent group of diverse stakeholders used more abduction-2 inferences (13 vs 0), which led to a greater variety of methodological instructions (24 vs 8) than those observed in the less potent group (<xref ref-type="table" rid="table6">Table 6</xref>). In addition, similar to what the stakeholders did in the problem phase, the more potent diverse stakeholder group developed each other’s methodological instructions in the solution phase. This resulted in more concrete and specific solutions. Furthermore, abduction-2 inferencing was used by nondesigners, which was less anticipated because inferencing is typically attributed to designers.</p>
        <p>How stakeholders developed ideas based on each other’s methodological instructions and how this made the solution more concrete and precise are clearly demonstrated in the example of the more potent group (<xref ref-type="table" rid="table9">Table 9</xref>). The researcher suggested a solution that he explained as being a tool for a social network, using a Star Trek metaphor by referring to The Borg. This is an abstract solution, characterized by a metaphor, yet sufficiently specific, as it is further described as a social network. Next, other suggestions, each using a different metaphor, were used as analogies to highlight different features or aspects of the social network. Thus, the solution became more concrete and specific. The occupational physician suggested a buddy system; the researcher suggested a similar swipe function as in a Tinder app; and the employer and facilitator suggested offering personal suggestions based on an artificial intelligence algorithm. The metaphors that were used seem to have come from popular culture or daily use, which may have made them immediately clear to all stakeholders. As such, the solution-related knowledge of the various stakeholders started on an abstract-specific level and moved toward a more concrete and specific level (<xref rid="figure3" ref-type="fig">Figure 3</xref>). Overall, the more potent diverse stakeholder group had a strong influence on the quality of the knowledge output regarding the solution.</p>
        <p>The interaction in the less potent group was more on the level of sharing relevant statements about a solution, for example, improving the skills of people with cancer (<xref ref-type="table" rid="table10">Table 10</xref>). They did not discuss in more detail how skills training could be implemented with, for instance, visual images (abduction-2). Therefore, the solutions did not change from abstract to concrete; instead, they remained relatively the same at a concrete level.</p>
        <table-wrap position="float" id="table9">
          <label>Table 9</label>
          <caption>
            <p>Example sequence utterances from the more potent diverse stakeholder group in the generative co-design workshop with codes (translated into English for reporting purposes).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="420"/>
            <col width="0"/>
            <col width="120"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="160"/>
            <col width="0"/>
            <col width="120"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Stakeholder and sequence of utterances (order of conversation)</td>
                <td colspan="2">Behavior code</td>
                <td colspan="2">Inference-type code</td>
                <td colspan="2">Knowledge-type code</td>
                <td>Repetition code</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="10">
                  <bold>Researcher</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1. You are not as an individual… because in such a game you are addressed as an individual, so how do we keep the social element and your environment? As an image I have The Borg<sup>a</sup>, that’s from Star Trek, and you are being assimilated in a very large network of other individuals.</td>
                <td colspan="2">Introduce</td>
                <td colspan="2">Abduction-2</td>
                <td colspan="2">Methodological instruction</td>
                <td colspan="2">From interview</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Game developer and designer</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2. I didn’t know you were a Trekkie.</td>
                <td colspan="2">Joke</td>
                <td colspan="2">—<sup>b</sup></td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Researcher</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>3. Wait until you see my costume, ha-ha.</td>
                <td colspan="2">Laugh</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Occupational physician</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>4. I am thinking about a sort of buddy system<sup>c</sup>, rather than peers with similar experience, use buddy’s to play together.</td>
                <td colspan="2">Introduce</td>
                <td colspan="2">Abduction-2</td>
                <td colspan="2">Methodological instruction</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Researcher</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>5. Yes, and maybe we can therefore also connect that with a Tinder app<sup>d</sup>, because which buddy would you like?</td>
                <td colspan="2">Introduce</td>
                <td colspan="2">Abduction-2</td>
                <td colspan="2">Methodological instruction</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Occupational physician</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>6. Ha-ha.</td>
                <td colspan="2">Laugh</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer and facilitator</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>7. And, there, the artificial intelligence rises to the surface again? So that you can see on the basis of your use of the game with who you have the best connection<sup>e</sup>?</td>
                <td colspan="2">Introduce</td>
                <td colspan="2">Deduction and abduction-2</td>
                <td colspan="2">Methodological instruction</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Occupational physician</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>8. Exactly.</td>
                <td colspan="2">Agree</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer and facilitator</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>9. That you are not only swiping, but also get a suggestion, like Hi, this person could fit with you.</td>
                <td colspan="2">Explain</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table9fn1">
              <p><sup>a</sup>First visual image.</p>
            </fn>
            <fn id="table9fn2">
              <p><sup>b</sup>Not available.</p>
            </fn>
            <fn id="table9fn3">
              <p><sup>c</sup>Second visual image.</p>
            </fn>
            <fn id="table9fn4">
              <p><sup>d</sup>Third visual image.</p>
            </fn>
            <fn id="table9fn5">
              <p><sup>e</sup>Fourth visual image.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Visualization of iteration of solutions (bubbles) suggested by different stakeholders in terms of specificity and concreteness (different shading for each stakeholder). AI: artificial intelligence.</p>
          </caption>
          <graphic xlink:href="humanfactors_v10i1e38350_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table10">
          <label>Table 10</label>
          <caption>
            <p>Example sequence utterances from the less potent diverse stakeholder group in the generative co-design workshop with codes (translated into English for reporting purposes).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="420"/>
            <col width="0"/>
            <col width="120"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="160"/>
            <col width="0"/>
            <col width="120"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Stakeholder and sequence of utterances (order of conversation)</td>
                <td colspan="2">Behavior code</td>
                <td colspan="2">Inference-type code</td>
                <td colspan="2">Knowledge-type code</td>
                <td>Repetition code</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer network</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1. I am still thinking about an approach including skills, how that would enable people. I put it left under (in Miro), I lost it…</td>
                <td colspan="2">Introduce</td>
                <td colspan="2">Abduction-1</td>
                <td colspan="2">Methodological instruction and relevant statement</td>
                <td colspan="2">From interview</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Network coordinator and cancer survivor</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2. No, but skills are really important. Here, you have to do something completely different, and you are looking at work differently.</td>
                <td colspan="2">Agree and add</td>
                <td colspan="2">—<sup>a</sup></td>
                <td colspan="2">Relevant statement</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Ecosystem expert</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>3. But I think that next to the work environment also, if you assume that that was the work environment where you were, the other one could then call a different work environment. Then those skills arise again, because you can perhaps get the possibilities to develop yourself differently.</td>
                <td colspan="2">Add</td>
                <td colspan="2">Deduction</td>
                <td colspan="2">—</td>
                <td colspan="2">—</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Employer network</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>4. Yes, and when one conquers cancer, for example you have certain perseverance, that you are resilient. And when you focus on that, your employer can you help you realise this.</td>
                <td colspan="2">Add</td>
                <td colspan="2">Conclude</td>
                <td colspan="2">Relevant statement</td>
                <td colspan="2">—</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table10fn1">
              <p><sup>a</sup>Not available.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study aimed to answer the following research question: <italic>Do stakeholders with diverse knowledge and diverse ways of thinking improve the GCD process for digital health?</italic> As a first step in attempting to answer this research question, we assessed how a diverse stakeholder group, put together using the proposed stakeholder group assembly procedure, would influence the GCD process. We also established a second stakeholder group consisting of individuals who scored less well in the preliminary interviews held to assess the required competencies.</p>
        <p>Our preliminary findings confirm Sanders and Stappers’ main hypothesis that a group of stakeholders with diverse knowledge and ways of thinking has a positive influence on GCD. The more potent of the 2 diverse stakeholder groups had a relatively larger influence on the GCD workshop process and output. The stakeholders in the more potent group built more on each other’s knowledge, which led to a more comprehensive problem definition and more precisely described solutions. In the problem phase, the stakeholders in the more potent group shared a greater diversity of relevant statements (14 vs 10), which were processed using more induction (10 vs 0) and deduction inferences (9 vs 4) than the ones in the less potent diverse stakeholder group. Furthermore, the stakeholders in the first group built on each other’s relevant statements, some of which had already been mentioned in the interviews before the workshop. This resulted through a dual movement toward a more comprehensive problem definition. In the solution phase, the more potent group of diverse stakeholders used more abduction-2 inferences (13 vs 0), which led to a greater variety of methodological instructions (24 vs 8) than those observed in the less potent group. In addition, similar to what the stakeholders did in the problem phase, the more potent diverse stakeholder groups developed each other’s methodological instructions in the solution phase. This resulted in solutions that were developed from a more abstract and general level toward a more concrete and specific level.</p>
        <p>The other 2 subhypotheses were not supported. First, there was no substantial difference between the 2 groups in terms of explicitly sharing deeper-lying knowledge (contextual certainties). One contextual certainty was used implicitly in the more potent group. Second, abduction-2 inferences were used 13 times by nondesigners in the more potent group but not by the game designer in the more potent group. This result was contrary to our expectations.</p>
        <p>Using a person’s professional background as the sole criterion for group member selection as, for example, done by Trischler et al [<xref ref-type="bibr" rid="ref44">44</xref>], may not deliver the full potential of a GCD session. Rather, it is the combination of stakeholders with diverse and complementary knowledge in terms of 3 knowledge types (relevant statements, methodological instructions, and contextual certainties) and the most diverse and complementary inference experience in terms of 4 complementary inference skills (deduction, induction, abduction-1, and abduction-2) that enhances the GCD process and its output. Moreover, abduction-2 inferencing did not occur spontaneously in our study in the less potent diverse stakeholder group. Therefore, the involvement of at least one stakeholder with abduction-2 experience (not limited to professional designers) could be critical when using GCD in hierarchical hospital settings [<xref ref-type="bibr" rid="ref25">25</xref>], with stakeholders who are not naturally involved in creative activities.</p>
        <p>Furthermore, the speed brought about by the dual movement of divergence and convergence [<xref ref-type="bibr" rid="ref45">45</xref>] in the problem phase could be due to the diversity of knowledge and thinking among the stakeholders, as each one has the potential to convergence or diverge. Here, each has knowledge that others lack and cannot think in ways that others can. In the problem phase, the example provided was about an idea that was rapidly considered from a patient experience and from the employer and technical development perspectives. This led to reformulations and the raising of new questions, which steered the process in a new direction. This could be viewed as a change of frame, or perspective, brought about through the interaction of different stakeholders. Although there is extensive literature on the framing process [<xref ref-type="bibr" rid="ref46">46</xref>-<xref ref-type="bibr" rid="ref49">49</xref>], the interactions of diverse stakeholders in the framing process have not yet been explicitly described. The example we provided in the solution phase suggests that framing involving diverse stakeholders can be viewed as a knowledge process that looks for a solution from different knowledge contexts that provide different perspectives when looking at a possible solution. During this process, we observed an implicit negotiation process, which has been mentioned by other researchers [<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref50">50</xref>], in the sense that the stakeholders’ responses to the proposed solutions varied. On some occasions, stakeholders laughed, which may signify acceptance of a solution. This was surprising and unexpected given that it did not relate to their own knowledge context. As such, a stakeholder group with diverse knowledge and ways of thinking may be the most effective when it can reframe ideas rapidly.</p>
        <p>The framing process may be accelerated when stakeholders share more contextual certainties. However, we observed only 1 event in the problem phase that demonstrated how a contextual certainty can rapidly bring a new perspective to a discussion; in this case, a didactic perspective that is essential when developing serious games [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>]. This emphasizes the need to share deeper-lying knowledge in the GCD process [<xref ref-type="bibr" rid="ref10">10</xref>] and the need to explicate how they are used by different stakeholders in design theory more broadly [<xref ref-type="bibr" rid="ref53">53</xref>]. The limited expression of contextual certainties in our study may be due to the lack of priming exercises [<xref ref-type="bibr" rid="ref8">8</xref>] ahead of our workshops, coupled with the time pressure and workload of participants. This may have suppressed the participants’ awareness of deeper-lying ideas. This suggests that there may be a minimum critical time before people can share such deeper-lying knowledge that our workshops failed to exceed.</p>
      </sec>
      <sec>
        <title>Implications</title>
        <p>Finally, we reflect on our stakeholder group assembly procedure in light of the normative values present in the GCD that originate in the PD field [<xref ref-type="bibr" rid="ref10">10</xref>]. In PD, broadly defined values are upheld such as democracy, equalized power relations, mutual learning, and situation-based actions [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. Given the lack of theoretical consensus, there are no solid normative grounds on which to judge our stakeholder selection procedure. For instance, the democratic principle might imply that one should involve people who are affected by the design decisions made or the end product [<xref ref-type="bibr" rid="ref19">19</xref>]. In addition, it is emphasized that power relations should be equalized by giving voice to those who may be invisible or weaker [<xref ref-type="bibr" rid="ref16">16</xref>]. In terms of digital health, this could imply that patients and informal caregivers should be involved. As it is often difficult to get involved in a health care setting [<xref ref-type="bibr" rid="ref21">21</xref>], we considered the use of a snowball sampling method. This is potentially more inclusive and faster than a widely advertised recruitment strategy that may not attract susceptible groups. As such, in the protocol, we tried to cast a wide net of possible participants through snowball sampling to include people and other vulnerable populations. However, to participate in and contribute to the GCD process, individuals should be able to bring new or complementary knowledge and inferencing experience to the stakeholder group. On the basis that they lacked these assets, we did not include cancer survivors in the more potent diverse stakeholder group, even though they were in a susceptible position. Furthermore, it is argued that democracy requires educated and engaged people acting in their own interests and in the interest of the common good [<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref55">55</xref>]. Kensing and Greenbaum [<xref ref-type="bibr" rid="ref55">55</xref>] state that, when necessary, this should involve educating people in terms of the required technical jargon and engaging them in the process, an aspect related to the principle of mutual learning [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref55">55</xref>]. In this respect, Kleinsmann argues that in collaborative activities, there should be minimal shared understanding [<xref ref-type="bibr" rid="ref56">56</xref>]. In our protocol, we tried to ensure this by looking for people with a basic interest in the topic through snowball sampling and then using self-assessment to evaluate group communication abilities. In this sense, we believe that the stakeholder group assembly procedure that we used can serve as an example of how these values can be respected while improving the GCD process and output.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The designed stakeholder group assembly procedure was operationalized in a minimally viable form to meet the aim and scope of this study. Although the assessment process was intended to accurately score the knowledge, inference skills, and communication skills of potential group members, there may be a built-in bias in the questions. Although we attempted to limit this by discussing the formation of the groups within the research team, there may still be some errors in allocating individuals to one of the 2 groups.</p>
        <p>Indeed, not all the criteria were sufficiently sensitive to differentiate between the experiences of some stakeholders to ensure robust selection. For instance, all the stakeholders scored similarly on the criteria addressing induction and deduction inference types and communication abilities. This could be due to the snowball sampling that preselected stakeholders who were already part of The Foundation’s network with a certain level of educational training and communication abilities. Even though all the stakeholders showed a similar ability to use induction and deduction inference types in their interviews, the stakeholders in the less potent group used these less often during their workshop, which affected their knowledge output and knowledge processing. It is possible that the stakeholders in this group were less inclined to use these inference types because of a lack of interaction.</p>
        <p>The case was selected based on the background of the lead researcher and the fact that it was a project that had momentum, was about to start, and had good potential to involve various stakeholders. However, the selected case also raised concerns, as it took longer than expected to gain approval to start the stakeholder selection procedure from the project manager. One reason for this could be that GCD is often used as an informal design practice rather than as a formal scientific approach with formal stakeholder selection.</p>
        <p>We would caution readers against drawing any causal relationships based on our study about the influence of the stakeholder groups on the GCD process. To maintain focus in our analysis, back-and-forth interactions between the problem and solution phases, which might occur when addressing a real issue, were not considered. Furthermore, given the exploratory purpose of this study, various variables were ignored, including content-related facilitation, interpersonal relationships [<xref ref-type="bibr" rid="ref57">57</xref>], the creative environment [<xref ref-type="bibr" rid="ref58">58</xref>], mutual learning over time, and the higher-level strategy of the project and host organization [<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref59">59</xref>]. Nevertheless, even without these aspects, this study was still able to provide initial insights into the role of stakeholder diversity in GCD. To ensure this, reflection meetings were organized between the lead researcher and coauthors to identify and avoid any potential biases in the study design and interpretation of the results.</p>
      </sec>
      <sec>
        <title>Further Research</title>
        <p>We would recommend further exploring how to strike a balance between the time and resources spent on snowball sampling and the number of stakeholder assessment criteria (knowledge, inference experience, and communication abilities) used. One option would be to ignore induction and deduction and focus on abduction-1 and abduction-2 inference experiences. One could also ignore communication abilities if the organization under consideration is a hospital that already requires interdisciplinary collaboration and focus instead on visual communication skills and open-mindedness as an indication of creative thinking. Next, to further assess the influence of the selected stakeholders on the knowledge processing component, the role of metaphors (in abduction-2 inferencing) and contextual certainties could be explored. For instance, one could link the dual-processing theory of reasoning, which involves deeper unconscious knowledge processing based on intuition and experience, and the more conscious deliberated processing with different knowledge and inference types [<xref ref-type="bibr" rid="ref60">60</xref>]. Finally, the knowledge processing and knowledge output could, over time, be further assessed in the GCD process, in which the expression of contextual certainties is considered alongside stakeholders’ learning processes.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>A procedure to assess the diversity of knowledge, diversity of ways of thinking, and communication skills in assembling a stakeholder group that meets specific criteria may improve the potential of the GCD process and the resulting digital health. We would encourage the validation of our preliminary findings. Ultimately, this will help researchers make methodologically more robust decisions about stakeholder involvement and report them in an appropriate way, which will improve the scientific rigor of GCD science for digital health.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Interview and workshop template used on online Miro platform.</p>
        <media xlink:href="humanfactors_v10i1e38350_app1.png" xlink:title="PNG File , 277 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Inductive code list.</p>
        <media xlink:href="humanfactors_v10i1e38350_app2.docx" xlink:title="DOCX File , 13 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">GCD</term>
          <def>
            <p>generative co-design</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">PD</term>
          <def>
            <p>participatory design</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zimlichman</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Nicklin</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Aggarwal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Health care 2030: the coming transformation</article-title>
          <source>NEJM Catal Innov Care Deliv</source>
          <year>2021</year>
          <month>03</month>
          <day>03</day>
          <volume>2</volume>
          <issue>2</issue>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://catalyst.nejm.org/doi/full/10.1056/CAT.20.0569"/>
          </comment>
          <pub-id pub-id-type="doi">10.1056/CAT.20.0569</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schwamm</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Chumbler</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fonarow</surname>
              <given-names>GC</given-names>
            </name>
            <name name-style="western">
              <surname>Berube</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Nystrom</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Suter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Zavala</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Polsky</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Radhakrishnan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lacktman</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Horton</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Malcarney</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Halamka</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tiner</surname>
              <given-names>AC</given-names>
            </name>
            <collab>American Heart Association Advocacy Coordinating Committee</collab>
          </person-group>
          <article-title>Recommendations for the implementation of telehealth in cardiovascular and stroke care: a policy statement from the American Heart Association</article-title>
          <source>Circulation</source>
          <year>2017</year>
          <month>02</month>
          <day>14</day>
          <volume>135</volume>
          <issue>7</issue>
          <fpage>e24</fpage>
          <lpage>44</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/27998940/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1161/CIR.0000000000000475</pub-id>
          <pub-id pub-id-type="medline">27998940</pub-id>
          <pub-id pub-id-type="pii">CIR.0000000000000475</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>SG</given-names>
            </name>
            <name name-style="western">
              <surname>Blood</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Scirica</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Disruptive and sustaining innovation in telemedicine: a strategic roadmap</article-title>
          <source>NEJM Catal Innov Care Deliv</source>
          <year>2021</year>
          <month>12</month>
          <day>28</day>
          <volume>2</volume>
          <issue>6</issue>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://catalyst.nejm.org/doi/full/10.1056/CAT.21.0311"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Nijland</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>van Limburg</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ossebaard</surname>
              <given-names>HC</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Eysenbach</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Seydel</surname>
              <given-names>ER</given-names>
            </name>
          </person-group>
          <article-title>A holistic framework to improve the uptake and impact of eHealth technologies</article-title>
          <source>J Med Internet Res</source>
          <year>2011</year>
          <month>12</month>
          <day>05</day>
          <volume>13</volume>
          <issue>4</issue>
          <fpage>e111</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2011/4/e111/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.1672</pub-id>
          <pub-id pub-id-type="medline">22155738</pub-id>
          <pub-id pub-id-type="pii">v13i4e111</pub-id>
          <pub-id pub-id-type="pmcid">PMC3278097</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vandekerckhove</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>de Mul</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bramer</surname>
              <given-names>WM</given-names>
            </name>
            <name name-style="western">
              <surname>de Bont</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>Generative participatory design methodology to develop electronic health interventions: systematic literature review</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>04</month>
          <day>27</day>
          <volume>22</volume>
          <issue>4</issue>
          <fpage>e13780</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/4/e13780/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13780</pub-id>
          <pub-id pub-id-type="medline">32338617</pub-id>
          <pub-id pub-id-type="pii">v22i4e13780</pub-id>
          <pub-id pub-id-type="pmcid">PMC7215492</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bird</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>McGillion</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chambers</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Dix</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fajardo</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gilmour</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Levesque</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mierdel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ouellette</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Polanski</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Reaume</surname>
              <given-names>SV</given-names>
            </name>
            <name name-style="western">
              <surname>Whitmore</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Carter</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>A generative co-design framework for healthcare innovation: development and application of an end-user engagement framework</article-title>
          <source>Res Involv Engagem</source>
          <year>2021</year>
          <month>03</month>
          <day>01</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>12</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://researchinvolvement.biomedcentral.com/articles/10.1186/s40900-021-00252-7#citeas"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s40900-021-00252-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kleinsmann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Deken</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lauche</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Development of design collaboration skills</article-title>
          <source>J Eng Des</source>
          <year>2011</year>
          <month>09</month>
          <day>19</day>
          <volume>23</volume>
          <issue>7</issue>
          <fpage>485</fpage>
          <lpage>506</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/abs/10.1080/09544828.2011.619499"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/09544828.2011.619499</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sanders</surname>
              <given-names>EB</given-names>
            </name>
            <name name-style="western">
              <surname>Stappers</surname>
              <given-names>PJ</given-names>
            </name>
          </person-group>
          <article-title>Probes, toolkits and prototypes: three approaches to making in codesigning</article-title>
          <source>CoDesign</source>
          <year>2014</year>
          <month>03</month>
          <day>06</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>14</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/abs/10.1080/15710882.2014.888183"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/15710882.2014.888183</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sanders</surname>
              <given-names>EB</given-names>
            </name>
            <name name-style="western">
              <surname>Stappers</surname>
              <given-names>PJ</given-names>
            </name>
          </person-group>
          <article-title>Co-creation and the new landscapes of design</article-title>
          <source>CoDesign</source>
          <year>2008</year>
          <month>06</month>
          <day>24</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/full/10.1080/15710880701875068"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/15710880701875068</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sanders</surname>
              <given-names>EB</given-names>
            </name>
            <name name-style="western">
              <surname>Stappers</surname>
              <given-names>PJ</given-names>
            </name>
          </person-group>
          <source>Convivial Toolbox: Generative Research for the Front End of Design</source>
          <year>2012</year>
          <month>11</month>
          <day>05</day>
          <publisher-loc>Amsterdam, The Netherlands</publisher-loc>
          <publisher-name>BIS Publishers</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Boeijen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Daalhuizen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zijlstra</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>Delft Design Guide: Perspectives, Models, Approaches, Methods. 2nd edition</source>
          <year>2020</year>
          <publisher-loc>Amsterdam, The Netherlands</publisher-loc>
          <publisher-name>BIS Publishers</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Langley</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wolstenholme</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Cooke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>'Collective making' as knowledge mobilisation: the contribution of participatory design in the co-creation of knowledge in healthcare</article-title>
          <source>BMC Health Serv Res</source>
          <year>2018</year>
          <month>07</month>
          <day>25</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>585</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-018-3397-y"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-018-3397-y</pub-id>
          <pub-id pub-id-type="medline">30045726</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-018-3397-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC6060522</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Szinay</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Chadborn</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Naughton</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Influences on the uptake of and engagement with health and well-being smartphone apps: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>05</month>
          <day>29</day>
          <volume>22</volume>
          <issue>5</issue>
          <fpage>e17572</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/5/e17572/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17572</pub-id>
          <pub-id pub-id-type="medline">32348255</pub-id>
          <pub-id pub-id-type="pii">v22i5e17572</pub-id>
          <pub-id pub-id-type="pmcid">PMC7293059</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ohannessian</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Duong</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Odone</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Global telemedicine implementation and integration within health systems to fight the COVID-19 pandemic: a call to action</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2020</year>
          <month>04</month>
          <day>02</day>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>e18810</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2020/2/e18810/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18810</pub-id>
          <pub-id pub-id-type="medline">32238336</pub-id>
          <pub-id pub-id-type="pii">v6i2e18810</pub-id>
          <pub-id pub-id-type="pmcid">PMC7124951</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hollander</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Carr</surname>
              <given-names>BG</given-names>
            </name>
          </person-group>
          <article-title>Virtually perfect? Telemedicine for Covid-19</article-title>
          <source>N Engl J Med</source>
          <year>2020</year>
          <month>04</month>
          <day>30</day>
          <volume>382</volume>
          <issue>18</issue>
          <fpage>1679</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/32160451/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1056/NEJMp2003539</pub-id>
          <pub-id pub-id-type="medline">32160451</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Luck</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>What is it that makes participation in design participatory design?</article-title>
          <source>Des Stud</source>
          <year>2018</year>
          <month>11</month>
          <volume>59</volume>
          <fpage>1</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://oro.open.ac.uk/57465/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.destud.2018.10.002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>LB</given-names>
            </name>
            <name name-style="western">
              <surname>Danholt</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Halskov</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hansen</surname>
              <given-names>NB</given-names>
            </name>
            <name name-style="western">
              <surname>Lauritsen</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Participation as a matter of concern in participatory design</article-title>
          <source>CoDesign</source>
          <year>2015</year>
          <month>10</month>
          <day>01</day>
          <volume>11</volume>
          <issue>3-4</issue>
          <fpage>250</fpage>
          <lpage>61</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/citedby/10.1080/15710882.2015.1081246?scroll=top&#38;needAccess=true&#38;role=tab"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/15710882.2015.1081246</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Iversen</surname>
              <given-names>OS</given-names>
            </name>
          </person-group>
          <article-title>Participatory design for sustainable social change</article-title>
          <source>Des Stud</source>
          <year>2018</year>
          <month>11</month>
          <volume>59</volume>
          <fpage>9</fpage>
          <lpage>36</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S0142694X18300425"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.destud.2018.05.005</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van der Velden</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mörtberg</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>van den Hoven</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Vermaas</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>van de Poel</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Participatory design and design for values</article-title>
          <source>Handbook of Ethics, Values, and Technological Design: Sources, Theory, Values and Application Domains</source>
          <year>2020</year>
          <publisher-loc>Dordrecht, The Netherlands</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>1</fpage>
          <lpage>22</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Talaei-Khoei</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Seale</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ray</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Macintyre</surname>
              <given-names>CR</given-names>
            </name>
          </person-group>
          <article-title>Health care provider adoption of ehealth: systematic literature review</article-title>
          <source>Interact J Med Res</source>
          <year>2013</year>
          <month>04</month>
          <day>16</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e7</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.i-jmr.org/2013/1/e7/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/ijmr.2468</pub-id>
          <pub-id pub-id-type="medline">23608679</pub-id>
          <pub-id pub-id-type="pii">v2i1e7</pub-id>
          <pub-id pub-id-type="pmcid">PMC3628149</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Groeneveld</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Dekkers</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Boon</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>D’Olivo</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Challenges for design researchers in healthcare</article-title>
          <source>Design Health (Abingdon)</source>
          <year>2018</year>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>305</fpage>
          <lpage>26</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/full/10.1080/24735132.2018.1541699"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/24735132.2018.1541699</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bowen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McSeveny</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lockley</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Wolstenholme</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Cobb</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dearden</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>How was it for you? Experiences of participatory design in the UK health service</article-title>
          <source>CoDesign</source>
          <year>2013</year>
          <month>11</month>
          <day>05</day>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>230</fpage>
          <lpage>46</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/full/10.1080/15710882.2013.846384"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/15710882.2013.846384</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Palumbo</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <source>The Bright Side and the Dark Side of Patient Empowerment: Co-creation and Co-destruction of Value in the Healthcare Environment</source>
          <year>2017</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Palumbo</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Contextualizing co-production of health care: a systematic literature review</article-title>
          <source>Intl Jnl Public Sec Manag</source>
          <year>2016</year>
          <month>01</month>
          <day>11</day>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>72</fpage>
          <lpage>90</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.emerald.com/insight/content/doi/10.1108/IJPSM-07-2015-0125/full/html"/>
          </comment>
          <pub-id pub-id-type="doi">10.1108/ijpsm-07-2015-0125</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pirinen</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The barriers and enablers of co-design for services</article-title>
          <source>Int J Des</source>
          <year>2016</year>
          <volume>10</volume>
          <issue>3</issue>
          <fpage>27</fpage>
          <lpage>42</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.ijdesign.org/index.php/IJDesign/article/view/2575/749"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Luchs</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Swan</surname>
              <given-names>KS</given-names>
            </name>
            <name name-style="western">
              <surname>Griffin</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Design Thinking: New Product Development Essentials from the PDMA</source>
          <year>2015</year>
          <publisher-loc>Hoboken, NJ, USA</publisher-loc>
          <publisher-name>John Wiley &#38; Sons</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Doorley</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Holcomb</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Klebahn</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Segovia</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Utley</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Design Thinking Bootcamp Bootleg</article-title>
          <source>Stanford University</source>
          <year>2018</year>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dschool.stanford.edu/resources/the-bootcamp-bootleg">https://dschool.stanford.edu/resources/the-bootcamp-bootleg</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>DeSmet</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Baranowski</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Palmeira</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Verloigne</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>De Bourdeaudhuij</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Is participatory design associated with the effectiveness of serious digital games for healthy lifestyle promotion? A meta-analysis</article-title>
          <source>J Med Internet Res</source>
          <year>2016</year>
          <month>04</month>
          <day>29</day>
          <volume>18</volume>
          <issue>4</issue>
          <fpage>e94</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2016/4/e94/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.4444</pub-id>
          <pub-id pub-id-type="medline">27129447</pub-id>
          <pub-id pub-id-type="pii">v18i4e94</pub-id>
          <pub-id pub-id-type="pmcid">PMC4867751</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vandekerckhove</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>de Mul</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>de Groot</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Elzevier</surname>
              <given-names>HW</given-names>
            </name>
            <name name-style="western">
              <surname>Fabels</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Haj Mohammad</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Husson</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Noij</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sleeman</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Verbeek</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Von Rosenstiel</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>de Bont</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Manten-Horst</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Lessons for employing participatory design when developing care for young people with cancer: a qualitative multiple-case study</article-title>
          <source>J Adolesc Young Adult Oncol</source>
          <year>2021</year>
          <month>08</month>
          <volume>10</volume>
          <issue>4</issue>
          <fpage>404</fpage>
          <lpage>17</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33185496"/>
          </comment>
          <pub-id pub-id-type="doi">10.1089/jayao.2020.0098</pub-id>
          <pub-id pub-id-type="medline">33185496</pub-id>
          <pub-id pub-id-type="pmcid">PMC8388252</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Batens</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Contextual problem solving and adaptive logics in creative processes</article-title>
          <source>Philosophica</source>
          <year>1999</year>
          <volume>62</volume>
          <issue>4</issue>
          <fpage>7</fpage>
          <lpage>32</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://philpapers.org/rec/BATCPS"/>
          </comment>
          <pub-id pub-id-type="doi">10.21825/philosophica.82291</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Batens</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Rahman</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Symons</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gabbay</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>van Bendegem</surname>
              <given-names>JP</given-names>
            </name>
          </person-group>
          <article-title>The need for adaptive logics in epistemology</article-title>
          <source>Logic, Epistemology, and the Unity of Science</source>
          <year>2004</year>
          <publisher-loc>Dordrecht, The Netherlands</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>459</fpage>
          <lpage>85</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Batens</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Wouters</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Meheus</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Adaptive logics as a necessary tool for relative rationality: including a section on logical pluralism</article-title>
          <source>Logic, Reasoning, and Rationality</source>
          <year>2014</year>
          <publisher-loc>Dordrecht, The Netherlands</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>1</fpage>
          <lpage>25</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cramer-Petersen</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Christensen</surname>
              <given-names>BT</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed-Kristensen</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Empirically analysing design reasoning patterns: abductive-deductive reasoning patterns dominate design idea generation</article-title>
          <source>Des Stud</source>
          <year>2019</year>
          <month>01</month>
          <day>01</day>
          <volume>60</volume>
          <fpage>39</fpage>
          <lpage>70</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://research.cbs.dk/en/publications/empirically-analysing-design-reasoning-patterns-abductive-deducti"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.destud.2018.10.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hekkert</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cila</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Handle with care! Why and how designers make use of product metaphors</article-title>
          <source>Des Stud</source>
          <year>2015</year>
          <month>09</month>
          <volume>40</volume>
          <fpage>196</fpage>
          <lpage>217</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S0142694X15000514"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.destud.2015.06.007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ippoliti</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Danks</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ippoliti</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Heuristic logic. A kernel</article-title>
          <source>Building Theories: Heuristics and Hypotheses in Sciences</source>
          <year>2018</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>191</fpage>
          <lpage>211</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ball</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Christensen</surname>
              <given-names>BT</given-names>
            </name>
          </person-group>
          <article-title>Analogical reasoning and mental simulation in design: two strategies linked to uncertainty resolution</article-title>
          <source>Des Stud</source>
          <year>2009</year>
          <month>3</month>
          <volume>30</volume>
          <issue>2</issue>
          <fpage>169</fpage>
          <lpage>86</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.destud.2008.12.005"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.destud.2008.12.005</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Burch</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Charles Sanders Peirce</article-title>
          <source>Stanford Encyclopedia of Philosophy (Fall 2021 Edition)</source>
          <year>2022</year>
          <access-date>2021-10-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://plato.stanford.edu/entries/peirce/#dia">https://plato.stanford.edu/entries/peirce/#dia</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dorst</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>The core of ‘design thinking’ and its application</article-title>
          <source>Des Stud</source>
          <year>2011</year>
          <month>11</month>
          <volume>32</volume>
          <issue>6</issue>
          <fpage>521</fpage>
          <lpage>32</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/S0142694X11000603"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.destud.2011.07.006</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coghlan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Brydon-Miller</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <source>The SAGE Encyclopedia of Action Research</source>
          <year>2014</year>
          <month>08</month>
          <day>27</day>
          <publisher-loc>Thousand Oaks, CA, USA</publisher-loc>
          <publisher-name>Sage Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
          <article-title>oPuce foundation</article-title>
          <source>oPuce</source>
          <access-date>2022-08-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://opuce.nl/opuce-foundation">https://opuce.nl/opuce-foundation</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goodman</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <article-title>Snowball sampling</article-title>
          <source>Ann Math Statist</source>
          <year>1961</year>
          <month>03</month>
          <volume>32</volume>
          <issue>1</issue>
          <fpage>148</fpage>
          <lpage>70</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://projecteuclid.org/journals/annals-of-mathematical-statistics/volume-32/issue-1/Snowball-Sampling/10.1214/aoms/1177705148.full"/>
          </comment>
          <pub-id pub-id-type="doi">10.1214/aoms/1177705148</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thoring</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mueller</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Badke-Schaub</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Workshops as a research method: guidelines for designing and evaluating artifacts through workshops</article-title>
          <source>Proceedings of the 53rd Hawaii International Conference on System Sciences</source>
          <year>2020</year>
          <month>01</month>
          <conf-name>HICSS '20</conf-name>
          <conf-date>January 7-10, 2020</conf-date>
          <conf-loc>Maui, HI, USA</conf-loc>
          <fpage>5036</fpage>
          <lpage>45</lpage>
          <pub-id pub-id-type="doi">10.24251/hicss.2020.620</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Visser</surname>
              <given-names>FS</given-names>
            </name>
            <name name-style="western">
              <surname>Stappers</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>van der Lugt</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sanders</surname>
              <given-names>EB</given-names>
            </name>
          </person-group>
          <article-title>Contextmapping: experiences from practice</article-title>
          <source>CoDesign</source>
          <year>2005</year>
          <volume>1</volume>
          <issue>2</issue>
          <fpage>119</fpage>
          <lpage>49</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/abs/10.1080/15710880500135987"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/15710880500135987</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Trischler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pervan</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>DR</given-names>
            </name>
          </person-group>
          <article-title>The value of codesign: the effect of customer involvement in service design teams</article-title>
          <source>J Serv Res</source>
          <year>2018</year>
          <month>02</month>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>75</fpage>
          <lpage>100</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/full/10.1177/1094670517714060"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1094670517714060</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <source>Design Methods: Seeds of Human Futures</source>
          <year>1970</year>
          <publisher-loc>Hoboken, NJ, USA</publisher-loc>
          <publisher-name>John Wiley &#38; Sons</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vermaas</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Dorst</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Thurgood</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Framing in design: a formal analysis and failure modes</article-title>
          <source>Proceedings of the 20th International Conference on Engineering Design Vol 3: Organisation and Management</source>
          <year>2015</year>
          <conf-name>ICED' 15</conf-name>
          <conf-date>July 27-30, 2015</conf-date>
          <conf-loc>Milan, Italy</conf-loc>
          <fpage>133</fpage>
          <lpage>42</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.designsociety.org/publication/37717/FRAMING+IN+DESIGN%3A+A+FORMAL+ANALYSIS+AND+FAILURE+MODES"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hey</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Joyce</surname>
              <given-names>CK</given-names>
            </name>
            <name name-style="western">
              <surname>Beckman</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>Framing innovation: negotiating shared frames during early design phases</article-title>
          <source>J Des Res</source>
          <year>2007</year>
          <month>10</month>
          <day>30</day>
          <volume>6</volume>
          <issue>1-2</issue>
          <fpage>79</fpage>
          <lpage>99</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.inderscienceonline.com/doi/abs/10.1504/JDR.2007.015564"/>
          </comment>
          <pub-id pub-id-type="doi">10.1504/jdr.2007.015564</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kolko</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Sensemaking and Framing: A Theoretical Reflection on Perspective in Design Synthesis</article-title>
          <source>Design Research Society</source>
          <year>2010</year>
          <access-date>2019-10-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.drs2010.umontreal.ca/data/PDF/067.pdf">http://www.drs2010.umontreal.ca/data/PDF/067.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schön</surname>
              <given-names>DA</given-names>
            </name>
          </person-group>
          <source>The Reflective Practitioner: How Professionals Think In Action</source>
          <year>1984</year>
          <publisher-loc>New York, NY, USA</publisher-loc>
          <publisher-name>Basic Books</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dorst</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <source>Frame Innovation: Create New Thinking by Design</source>
          <year>2015</year>
          <publisher-loc>Cambridge, MA, USA</publisher-loc>
          <publisher-name>MIT Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Verschueren</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Buffel</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Vander Stichele</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Developing theory-driven, evidence-based serious games for health: framework based on research community insights</article-title>
          <source>JMIR Serious Games</source>
          <year>2019</year>
          <month>05</month>
          <day>02</day>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>e11565</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://games.jmir.org/2019/2/e11565/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11565</pub-id>
          <pub-id pub-id-type="medline">31045496</pub-id>
          <pub-id pub-id-type="pii">v7i2e11565</pub-id>
          <pub-id pub-id-type="pmcid">PMC6521217</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carvalho</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Bellotti</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Berta</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>De Gloria</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sedano</surname>
              <given-names>CI</given-names>
            </name>
            <name name-style="western">
              <surname>Hauge</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rauterberg</surname>
              <given-names>GW</given-names>
            </name>
          </person-group>
          <article-title>An activity theory-based model for serious games analysis and conceptual design</article-title>
          <source>Comput Educ</source>
          <year>2015</year>
          <month>09</month>
          <volume>87</volume>
          <fpage>166</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://research.tue.nl/en/publications/an-activity-theory-based-model-for-serious-games-analysis-and-con"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.compedu.2015.03.023</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mareis</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>The epistemology of the unspoken: on the concept of tacit knowledge in contemporary design research</article-title>
          <source>Des Issues</source>
          <year>2012</year>
          <month>04</month>
          <volume>28</volume>
          <issue>2</issue>
          <fpage>61</fpage>
          <lpage>71</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jstor.org/stable/41427826"/>
          </comment>
          <pub-id pub-id-type="doi">10.1162/desi_a_00143</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenbaum</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Loi</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Participation, the camel and the elephant of design: an introduction</article-title>
          <source>CoDesign</source>
          <year>2012</year>
          <month>06</month>
          <volume>8</volume>
          <issue>2-3</issue>
          <fpage>81</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/101080/157108822012690232"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/15710882.2012.690232</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kensing</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Greenbaum</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Simonsen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Robertson</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Heritage: having a say</article-title>
          <source>Routledge International Handbook of Participatory Design</source>
          <year>2013</year>
          <month>06</month>
          <day>25</day>
          <publisher-loc>Oxfordshire, UK</publisher-loc>
          <publisher-name>Routledge</publisher-name>
          <fpage>41</fpage>
          <lpage>56</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kleinsmann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Buijs</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Valkenburg</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Understanding the complexity of knowledge integration in collaborative new product development teams: a case study</article-title>
          <source>J Eng Technol Manag</source>
          <year>2010</year>
          <month>03</month>
          <volume>27</volume>
          <issue>1-2</issue>
          <fpage>20</fpage>
          <lpage>32</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S0923474810000044"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jengtecman.2010.03.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Badke-Schaub</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Voute</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Design methodology: where do you go?</article-title>
          <source>Proceedings of the 15th International Design Conference</source>
          <year>2018</year>
          <conf-name>DESIGN '18</conf-name>
          <conf-date>May 21-24, 2018</conf-date>
          <conf-loc>Dubrovnik, Croatia</conf-loc>
          <fpage>25</fpage>
          <lpage>32</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://research.tudelft.nl/en/publications/design-methodology-where-do-you-go"/>
          </comment>
          <pub-id pub-id-type="doi">10.21278/idc.2018.0550</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thoring</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gonçalves</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mueller</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Desmet</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Badke-schaub</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The architecture of creativity: toward a causal theory of creative workspace design</article-title>
          <source>Int J Des</source>
          <year>2021</year>
          <volume>15</volume>
          <issue>2</issue>
          <fpage>17</fpage>
          <lpage>36</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.ijdesign.org/index.php/IJDesign/article/view/4061"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Botero</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hyysalo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kohtala</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Whalen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Getting participatory design done: from methods and choices to translation work across constituent domains</article-title>
          <source>Int J Des</source>
          <year>2020</year>
          <volume>14</volume>
          <issue>2</issue>
          <fpage>17</fpage>
          <lpage>34</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.ijdesign.org/index.php/IJDesign/article/view/3781"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gonçalves</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cash</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The life cycle of creative ideas: towards a dual-process theory of ideation</article-title>
          <source>Des Stud</source>
          <year>2021</year>
          <month>01</month>
          <volume>72</volume>
          <fpage>100988</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/S0142694X20300764"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.destud.2020.100988</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
