|
Interpersonal Recommendations
|
|
Foster long-term relationships aid in collaboration initiation and implementation
|
| □ Consider leveraging personal and/or professional network to initiate AIC □ Avoid transactional partnerships (e.g., one-off projects or contracts) or last-minute urgently requested collaborations □ Consider community-based participatory research best practices when convening all collaborators □ Practice health literacy principles and remain culturally responsive to each sectors' terminology □ Allow strengths of each collaborator to thrive (e.g., science, research methods, product development, market research, commercialization) □ Verbally identify and agree on areas of complementary strengths to build mutual respect |
|
Build trust among collaborators
|
| □ Allow time for trust to establish among collaborators, avoiding transactional partnerships □ Assume good intent for all parties involved, anticipating differences □ While convenience partnerships are ideal for trust, diversify AIC with new collaborators to foster innovation and avoid groupthink □ Raise and address health equity considerations for digital health collaboration |
|
Level set on shared value of collaboration
|
| □ During ideation phase, raise awareness of values and co-create action plan to complement diverse values □ Establish buy-in from all stakeholders to encourage characteristics for success and alignment of goals/deliverables □ Outline values and motivations contractually and verbally during initial collaboration stages □ Conduct value proposition exercises to bring clarity on diverse interests early in collaboration □ Judiciously negotiate conflicting interests to mutually benefit from partnership |
|
Implement clear roles and responsibilities
|
| □ Define role clarity and areas of dependence of other partners □ Hire talent with experience in multiple industries, translating between sector's terminology □ Ensure industry partner obtains a doctoral-level degree, serving as the scientific “broker” between sectors □ Convene early to openly discuss diverse value propositions □ Encourage regular cadence of meetings (appropriate for phase of project/product) to connect on issues pre-emptively |
|
Encourage positive and product team dynamics
|
| □ Promote inclusion and diversity best practices to establish an inclusive culture □ Resolve conflicts throughout collaboration rather than waiting for project to finalize □ Execute principles of teamwork with collaborators as you would your own internal organization |
|
Contextual recommendations
|
|
Initiate collaborations thoughtfully
|
| □ Identify a “formula for best collaborator fit” based on situation (e.g., phase of project, type of product, collaborator attributes) □ Recognize and address sources of conflict early during collaboration initiation □ Identify and discuss institutional or organizational structures that may limit flexibility (e.g., IRB timelines, legal processes, indirect costs) □ Establish formalized agreements, confidentiality agreements, and encourage intellectual property discussions □ Define scope of work and delegate responsibilities to maximize strengths and expertise |
|
Define a collaboration structure (e.g., governance, partnership model)
|
| □ Consider a governance structure or larger stakeholder body guiding the work □ Capture diverse subject matter expertise and end-user input for all projects/collaborations □ Ensure all stakeholders are a part of the collaboration structure, including non-profits, community partners, and government bodies □ Create opportunity for end-user (e.g., patient, consumer) to engage in structure □ Agree on coordination preconditions for collaborative decision-making and partnership implementation |
|
Promote knowledge sharing across collaborators
|
| □ Each sector has a responsibility to inform other collaborative party of knowledge gaps (e.g., IRB, legal, human subjects, subject matter expertise, UX/UI best practices) □ Collaborators are not expected to be experts but aware of processes (e.g., IRB or FDA approval, academic budget restraints) □ Create a knowledge sharing environment and avoid penalizing other sector for not obtaining expertise □ Create social and physical environments that facilitate cross-sector learning (e.g., workshops, kickoff meetings, lunch, and learns) □ Create a culture of collaborative learning for collective impact, including end-users, community stakeholders, collaboration key players at all levels of organizations |
|
Execute rigorous project management
|
| □ Hire project/product managers on both sides of collaboration to execute the day-to-day work □ Identify collaboration champions to serve as decision-makers and brokers between parties □ Create a list of anticipated blockers that may inhibit timeline and strategize methods to overcome □ Share forecasted or upcoming barriers during meetings, virtually, or in-person □ Meet often during initial stages and regularly during AIC to avoid challenges that arise |
|
Blend both design and research for digital health AIC
|
| □ During the design, consider how products/services many intervene on individuals and communities (social ecological model) □ Build business cases (e.g., regulatory guidelines, commercialization) to offer sustainable dissemination strategies □ Advocate and instruct on scientific best practices (e.g., IRB, outcomes research, human subjects) to promote scientific rigor and attention to health inequities □ Discuss unintended consequences of digital health product or project early to avoid pitfalls □ Create logic models and discuss societal and environmental impacts during design and development □ Industry should differentiate between the execution of product research (UX/UI) and outcomes research (clinical trials) |
|
Value an iterative human-centered design approach and principles
|
| □ Train partners in human-centered design phases (i.e., empathy, define, ideate, prototype, test) □ Allow for iterative approach both in research and product development □ Include trainings and iterative approaches into grants and contracts for flexibility and accountability |
|
Expectation recommendations
|
|
Set expectations about collaboration implementation
|
| □ Create expectations based on both academic and industry interests and timelines, document contractually and discuss orally □ Align objectives with defined contractual agreements (e.g., data ownership, legal rights) □ Understand costs for clinical validation and fees for service (e.g., indirect costs, full-time equivalent salary costs, publication fees) |
|
Create metrics of success and evaluate collaboration progress
|
| □ Similar to the scientific process, evaluate short- and long-term outcomes of AIC and the digital health product □ Consider capturing relationship dynamics through surveys, interviews, or working group meetings □ Conduct retrospective meetings to discuss what worked, what didn't work, and areas of opportunity with each sector's stakeholders □ To avoid loss of knowledge or partnership understanding; document partnership as much as a product portfolio or grant deliverable □ Track process and results for quality improvement throughout collaboration |
|
Evaluate the design and the performance of the digital health product
|
| □ Consider identifying academic collaboration in the design of intervention to serve as subject-matter experts □ Initiate collaboration with already commercialized products to build evidence □ Recommend iterative clinical validation of digital health products (e.g., feasibility, usability, clinical trial) prior to full-scale commercialization □ Avoid consumer-level digital health products (e.g., B2C), as it only impacts individual via Public Health Pyramid □ Improve evaluation methods using innovative models of analysis □ Capture end-user feedback (e.g., patients), system professionals (e.g., providers), and system leadership (e.g., hospital administration) |
|
Establish shared expectations for dissemination
|
| □ Outline methods of reach and scale for broad adoption, building on business models specific to digital health interventions □ Consider sustainable methods found in the business model literature (e.g., B2B or B2B2C) □ Work with tech transfer offices or legal to determine options for intellectual property and data handling □ Early in AIC, set up publication agreements and discuss intellectual property early in negotiation and contracting □ Publish case studies describing experiences with AIC and digital health product outcomes |