20. Do you want to partner with
Industry?
+ Funding
+ Rapid Action
+ Breadth of Impact
+ Expertise
+ Cutting Edge Innovation
-
Differing cultures
Some loss of control
Uncertain career benefits
Publication complexities
IP complexities
33. Ideal Partner
• Experience with academic research
• Realistic expectations
• High level of commitment at high levels in the
company
• Engage as equals
• Flexible approach
• Personable interactions
34. Step 1. Know Thyself
Step 2. Know Thy Partner
Step 3. Lay Out the Vision
Step 4. Develop the Contract
Step 5. Define the Infrastructure
Step 6. (Serious) Project Planning
Step 7. Do the Work
Step 8. Review, Articulate, Iterate
49. Are IP Issues Addressed?
• Who will own the IP?
• Do you have the ability to make assurances?
– University requirements
– Multiple university affiliations
• Involvement of researchers not part of this
contract?
• Relationship between IP and publications
50. Publication Rights
• Ensure freedom to publish
• But expect oversight from technical to
‘interpretive’
• Build in time for reviews and IP consideration
• Shared authorship brings complexity
• Recommend a Publication Committee
64. Project Leads Should Be…
•
•
•
•
Genuinely interested and invested in the topic
Collaborative in nature
Aware of the overall partnership vision
Provided sufficient resources (FTE, PM, admin)
65. Write a Comprehensive Project Plan
• Be explicit about the division of labor in
preparing the project plan
• Be aware of any protocol review requirements
(e.g., IRB, DRC) up front
• Provide buffer in project execution,
recognizing communication challenges
66. Do both sides still see value in
the project that has emerged?
67. Step 1. Know Thyself
Step 2. Know Thy Partner
Step 3. Lay Out the Vision
Step 4. Develop the Contract
Step 5. Define the Infrastructure
Step 6. (Serious) Project Planning
Step 7. Do the Work
Step 8. Review, Articulate, Iterate
75. Articulate the value of your
partnership to your stakeholders.
Help your partner do the same.
76.
77. Steps to Creating a Successful
Academic-Industry Partnership
1. Know Thyself
2. Know Thy Partner
3. Lay Out the Vision
4. Develop the Contract
5. Define the Infrastructure
6. (Serious) Project Planning
7. Do the Work
8. Review, Iterate, Articulate
Many of you have flipped through a magazine, seen the drug ads with people frolicking in the fields…Now turn the page-- 6 point font, dozens or even hundreds of side-effects listed.Partially medico-legal reasons, partially just due to thorough studies.I do not have data on average number of side-effects per drug, but based on my work in this project, it is between 65 and 70; with several >200.
Early in academic season for fellowsA true work in progressFeedback, suggestion, critiques To shape direction over next 2 years
Early in academic season for fellowsA true work in progressFeedback, suggestion, critiques To shape direction over next 2 years
Different cultures, different expectations on timing, workflow, etc
Some loss of control over projects
Questionable benefit to your career
Publications layer of complexity
IP complexities
Translational potentialUnderlying technology?Application / implementation?Enhance awareness, improve use of a technology, adherence, etc
[For this talk, we are assuming you have a partner in mind; Will have a separate talk on how to identify potential partners]
The obvious question is do you know what they want?
The better question is..
The better question is..
The better question is..
Depends how much time and energy you will invest
You want this commitment to be at as high a level as possible, to avoid rug getting pulled out prematurely. Goes to VISIBILITY.
The better question is..
[Recognizing that some partnerships will be large scale with mission statements etc, and others will be smaller, but all should have some “Vision”]
Avoid tendency to lovefest
OsteoCoE, domain agnostic, focus on information, methodologies etc
Expect that the details will change as you get to better understand each other’s organizations
May be huge, may be small. But we can articulate and justify why we are doing it. We have a mutual understanding of what may be involved. We know where each other’s drivers are.
[Could be a topic unto itself, but to focus on the basics]
Took us 6 months
Time funding,
Time funding, etc
Took us 6 months
GOVERNANCE. Steering committee, and recourse (tie breakers).
Took us 6 months
Keep the lines of communication open throughout the contracting process. Don’t let the drafting process lose the momentum for what you are trying to do.
[Recognizing that some partnerships will be large scale with mission statements etc, and others will be smaller, but all should have some “Vision”]
Program manager, project managers
Program manager, project managers
Program manager, project managers
[Recognizing that some partnerships will be large scale with mission statements etc, and others will be smaller, but all should have some “Vision”]
Planning. Take high level ideas
Planning. Take high level ideas
No love fest!
[Recognizing that some partnerships will be large scale with mission statements etc, and others will be smaller, but all should have some “Vision”]
Papers, Presentations, Visible Output
Trans- Status ReportsTeam Relations – leads may not get alongAssumptions- CRO vs Collaboration
Trans- Status ReportsTeam Relations – leads may not get alongAssumptions- CRO vs Collaboration
[Recognizing that some partnerships will be large scale with mission statements etc, and others will be smaller, but all should have some “Vision”]
No love fest!
Need to articulate the value both internally and help your partner to articulate the value to their own stakeholders . Go back to the drivers.
[Recognizing that some partnerships will be large scale with mission statements etc, and others will be smaller, but all should have some “Vision”]