New to corporate relations or alliance management? A 30-60-90 day plan for your first university-industry partnerships role

The first 90 days in a university-industry partnerships role have one job: turn an inherited mystery into a managed portfolio. The role goes by many names: corporate relations, corporate engagement, or industry engagement on the university side, research development or sponsored programs when the office carries it, alliance manager, program manager, or university relations on the company side. The plan is the same for all of them: read everything and promise nothing in the first month, meet every counterpart and install a working rhythm in the second, triage deliberately and land one visible win in the third. The plan below assumes no budget and no authority you don't already have. The checklists follow the plan.

Partnership roles change hands often, and the handoff is usually a folder of documents, a calendar of standing meetings, and a verbal "let me know if you have questions" from someone already mentally gone. What rarely gets handed over is the actual state of the portfolio, because in most organizations nobody knows it. That's the condition you inherit, university or corporate, and it's your job to turn it into a managed portfolio.

Translation Box: portfolio

On the academic side: the set of active sponsored agreements, master agreements, and industry-funded projects across departments, each owned by a PI, and tracked, if at all, by sponsored programs.

On the industry side: a set of external research investments, each with a stage, an expected value, and a decision coming up.

In this post: both. The job is to see the set as a managed set, whichever side you sit on.

What should the first 30 days cover?

Inventory the portfolio. Every active partnership gets a one-page entry: the agreement and its dates, current status as best you can establish it, named contacts on both sides, money in motion, and the last meaningful interaction. Expect surprises. Agreements that lapsed without anyone deciding, partners who consider a collaboration active that your organization has let go, deliverables overdue with no one accountable. Finding these now isn't embarrassing. It's exactly what the first month is for, and in 90 days they become yours.

Score the institution while you still have outsider eyes. The six readiness dimensions (governance, culture, processes, resources, track record, network) can be scored in the free Collaboration Readiness Assessment, and your first month is the best time you'll ever have to do it candidly: late enough to know where things are, early enough that no score reflects on you. Your weakest dimension usually explains most of the backlog you inherited. Knowing whether it's procedural (fixable by you, in months) or institutional (a leadership conversation, in years) sets the ambition for everything below.

Resist the strategy document. The standing temptation of a new role is to spend the first quarter writing the strategy. Delay it. The portfolio is the strategy document. Read it, fix its rhythm, and by day 90 the strategy will write itself from evidence instead of aspiration.

What should days 31 to 60 cover?

One conversation per active partner, and the agenda is one question: what does success look like for you this year? Write the answers down verbatim. The conversation is also where you discover evidence of two things that decide whether a partner stays, trust and commitment. In a study of university-industry relationships in Australia, Plewa and Quester found in the Journal of Services Marketing (2007) that trust was the strongest predictor of a partner's satisfaction and commitment the strongest predictor of its intention to renew. Then compare their answers with your own organization's, where those exist. The divergences you find aren't awkwardness to manage. They're your task list, and finding them in a friendly conversation in month two beats finding them in a dispute in month nine. Readers of the IP and contract negotiation post will recognize the expectations argument. A role transition is the one free chance to re-run the alignment without anyone losing face.

Install the minimum rhythm. Named owners for each partnership, a meeting cadence set in advance, decision rights below the steering level, and one shared status view, even if it's a spreadsheet you maintain by hand for now. This is the Steward-phase minimum. It costs nothing but discipline, and it's the single highest-return move of the whole 90 days, because partnerships drift without rhythm and most of what you inherited has been drifting.

Start the three-sentence habit. Monthly, per partnership: write the status as your counterpart would describe it. When you can't, you've found next month's conversation.

What should days 61 to 90 cover?

Sort the portfolio for renew, redesign, or exit. Every inherited portfolio carries partnerships that persist only because ending them required a decision nobody owned, and the base rate isn't on your side: Hoang and Rothaermel, in MIT Sloan Management Review (2016), put roughly half of all alliance portfolios in the underperforming category. You own it now, and the exits matter as much as the renewals. A respectful, well-run exit returns a reference and a potential future partner. A collaboration kept alive by inertia returns only overhead costs. If leadership resists triage, bring evidence: even just two months of the status view plus the readiness score makes the case better than any memo.

Pick one visible win and land it. One stalled agreement unstuck, one drifting collaboration re-anchored, one sponsor report that assembles itself from the status view instead of a weekend scramble. The win isn't vanity. Credibility at 90 days funds year-one ambition, and "the new person fixed that" travels fast in both institutions.

Close the quarter with a re-score. Run the free assessment again at day 90. Most of the movement will be in governance and processes, because that's where your effort went, and the difference is your first evidence to leadership that the function is being managed.

What does this plan leave out on purpose?

No alliance-management function built from scratch by day 90. Kale and Singh, in Academy of Management Perspectives (2009), put the time to build that capability at five to ten years. The first quarter is where it starts, not where it finishes. No system procurement in the first quarter. The habits come before any tools you'd have to buy, and the plain guide to managing a research collaboration says why. No reorganization proposals. No partnership pursued just to show motion. The portfolio you inherited is your curriculum, and new commitments made before the triage finish line tend to repeat the old selection habits.

And no going it entirely alone. A first quarter raises the same recurring questions for almost everyone: is this agreement term normal, how do I run the alignment conversation, is this partnership salvageable or a respectful exit? Line up someone you can ask, inside your organization or outside it, before the first of them lands on your desk.

Days 1 to 30: the checklist

• One-page entry for every active partnership: agreement dates, status, contacts on both sides, money in motion, last meaningful interaction
• List of lapsed, orphaned, or disputed agreements, with the decision each one needs
• The free Collaboration Readiness Assessment completed, with the weakest dimension named and tagged procedural or institutional
• Standing meetings inherited from your predecessor reviewed: keep, merge, or cancel
• No strategy document started

Days 31 to 60: the checklist

• One "what does success look like this year?" conversation per active partner, answers written verbatim
• Divergences between their answer and your organization's answer listed, with an owner for each
• A named relationship owner on both sides of every active partnership
• A cadence written down for each: operational sync (weekly to monthly) and management review (quarterly)
• A one-page decision-rights table: what project leads decide, what needs both owners, what goes to steering committee review
• One shared status view, even a spreadsheet, updated on a schedule
• The three-sentence status written for every partnership, from the counterpart's point of view

Days 61 to 90: the checklist

• Every partnership sorted: renew, redesign, or exit, with the evidence for each call
• Exits planned: a closing conversation, a final report, a record of what was learned, a door left open
• One visible win chosen by week nine and landed by week 13
• The Collaboration Readiness Assessment re-run at day 90, with the change in governance and processes noted
• A one-page quarter summary for leadership: the portfolio as a set, the triage calls, the win, the re-score
• Your open questions for the next quarter

Where should a newcomer start?

Start your portfolio inventory with your organization's profile page on our Helikon platform. Most research active organizations already have a profile page built from public research records, and you can filter researchers to your own university or company, including people who haven't signed up yet. That's a first look at the people behind the portfolio you've inherited. The free plan lets you follow the researchers, organizations, and technologies you've taken on, so the whole inheritance sits in one list. It also lets you put your most active collaborations into projects, each with its members, milestones and owners, files, and contracts in one shared record. Setting up two active projects is enough to start the status habit on the partnerships that matter most this quarter.

Start free on Helikon Labs

If you'd like a senior sounding board for the "is this normal?" moments of a first quarter, see Office Hours.

Sources

• Plewa, C. and Quester, P. (2007). "Key drivers of university-industry relationships: the role of organisational compatibility and personal experience." Journal of Services Marketing 21(5), 370 to 382. https://doi.org/10.1108/08876040710773679
• Hoang, H. and Rothaermel, F. T. (2016). "How to Manage Alliances Strategically." MIT Sloan Management Review 58(1), Fall 2016. https://sloanreview.mit.edu/article/how-to-manage-alliances-strategically/
• Kale, P. and Singh, H. (2009). "Managing Strategic Alliances: What Do We Know Now, and Where Do We Go From Here?" Academy of Management Perspectives 23(3), 45 to 62. https://doi.org/10.5465/amp.2009.43479263
• The six readiness dimensions are those scored by the free Collaboration Readiness Assessment: https://helikonlabs.com/readiness
• Office Hours terms (prepaid blocks, 12-month validity): https://helikonlabs.com/consulting/office-hours
• The triage and 90-day plan itself is practitioner framing.

Related

• You signed the research agreement. Now what? How to run the project from day one
• How to manage a university-industry research collaboration: the plain guide
• IP and contract negotiation: the most-cited breakdown in research partnerships
• Manage your partnership pipeline on the platform
• Follow researchers, organizations and technologies
• Glossary: alliance manager, decision rights
• Want a senior sounding board through your first quarter? Our Office Hours are senior advisory by the hour, in prepaid blocks, with 12 months to use them. A five-hour block typically covers a whole first quarter of "is this normal?" moments, and the questions you bring are confidential.