The Helikon Method in Practice

Who it's for

The leadership group of a research office, technology transfer office, or sponsored programs unit that wants a common picture of its partnership portfolio. On the company side, the corporate R&D or open innovation leads who approve university work and the alliance managers who run it. It's also effective as a mixed room when a university and a company share several projects.

The problem it fixes

Most organizations run partnerships one at a time, with the method depending on whoever set each one up. Faculty in our primary research described processes adapted around desktop applications and email, rather than strategically designed. Selection, governance, reporting, and evaluation then differ by project, missing the standardization needed to discern which processes need improvement. Kale, Dyer and Singh (2002) found that firms with a dedicated alliance function reported 63% of their long-term alliances as successful against 50% for firms without one. In this workshop, we put our proprietary framework for managing the full research collaboration lifecycle, The Helikon Method, into practice for your organization, ending with a prioritized action plan your team has agreed to.

Agenda

Pre-work drives the day. At least five people from different functions complete the Organizational Maturity Assessment, and we consolidate their ratings before the session, so every block starts from your scores and from the places where your own raters disagree. Six blocks of about 60 minutes, with lunch after the third. Each phase block runs the same way: what the phase is for in the Helikon Method, your results on the assessment items that bear on it, then the work on your own partnerships. Phases where you scored lowest get more of the day.

• 0:00 to 1:00. The Helikon Method and your baseline. The four phases, Match, Unite, Steward, and Evaluate, and the decisions each one owns. Then your results on that map: your score on each of the assessment's five dimensions (strategy, structure, people, process, and technology), where those gaps show up phase by phase, and the statements your raters scored furthest apart, which become the questions the day has to settle.
• 1:00 to 2:00. Match. How partners and projects should be chosen: a written partnership thesis, an intake route, and fit-based evaluation. Your results on those items. Then we sort your portfolio into partnerships that came by design and those that came from whoever emailed first, and test the by-design ones against your thesis, or draft one if you don't have it.
• 2:00 to 3:00. Unite. How a partnership is formed: decision rights, roles across counsel, sponsored programs, technology transfer and the research team, and the templates that shorten negotiation. Your results on those items. Then, for two or three partnerships you bring, we map who decides what, where the steering committee sits, and what happens when a milestone slips.
• 3:00 to 4:00. Steward. How a running collaboration is managed: cadence, research-adapted milestones, escalation, and compliance built into the workflow. Your results on your partnership function, escalation paths, project-management method, and portfolio visibility. Then we trace meeting cadence, milestone tracking, and sponsor reporting across your portfolio, and find where status is opaque to the funders.
• 4:00 to 5:00. Evaluate. How partnerships are measured, renewed, or closed. Your results on leadership review, lifecycle KPIs, post-mortems, and whether lessons reach the next partnership. Then: what leadership sees about these partnerships, what it should see, and how renew-or-exit decisions get made.
• 5:00 to 6:00. Foundations and priorities. The program-level items no single phase owns: executive sponsorship, budget, reporting line, career paths and incentives for partnership staff, and how your systems connect. Then the team ranks every fix it flagged during the day, picks the three with the best return, names an owner and a 90-day target for each, decides whether the next step is internal or needs extra help, and checks the choices against the assessment's own recommended next move.

What you bring

• Organizational Maturity Assessment ratings from at least five people across functions, completed two weeks before the session
• A list of your research partnerships, with two or three to examine in detail
• The people who can change a process, a role, or a budget line

What you leave with

• Your assessment scores, calibrated by the room, with each gap placed in the phase of the Helikon Method
• A one-page portfolio map sorting partnerships by phase and by health
• Three prioritized fixes, each with an owner and a 90-day target

Included instrument and pre-work

The Organizational Maturity Assessment is issued at booking and completed two weeks before the session, so the day starts from your scores. It's the default anchor because it reads the organization, which this workshop works on: strategy, structure, people, process, and technology across all your partnerships. It's designed for several raters, ideally from research leadership, sponsored programs, technology transfer, finance, legal, and at least one industry-facing role, and the workshop is where their ratings get reconciled.

Two swaps are available at the customer team's request, and the agenda stays the same: each phase block reads the swapped instrument's results for that phase. The Collaboration Readiness Assessment suits a unit earlier in building its partnership program, such as a new corporate engagement office or a college standing up industry work. It reads how ready you are to partner across governance, culture, processes, resources, track record, and network, and ranks the gaps with the most leverage. The Digital Maturity Assessment suits a team whose question is digital. It reads how well your systems, data, and digital governance support partnership work, and reports that support phase by phase, so the day runs with a digital lens.

Logistics

Capped at 12 participants: J. Richard Hackman's team research found that coordination and candor erode once a working group climbs into the double digits (Hackman, interviewed in Harvard Business Review, 2009), and a working session needs everyone contributing, so larger teams add breakouts or split into additional sessions. Virtual by default, onsite available with travel billed at cost at federal per-diem rates. Series pricing is 15% off three or more workshops. We schedule within one business day of booking.

Frequently asked questions

Can we run it for a mixed university and company group?

Yes, and it can be even more effective this way. Both sides hear the same debrief in one room, see where their results already differ, and make decisions that would otherwise take months of meetings.

What if we already own the tool?

The instrument's price is not deducted from the workshop fee. We use your existing results as the pre-work, and you keep the second license for a second team or partnership.

Which assessment should we use?

The Organizational Maturity Assessment, unless you want to swap. Pick the Collaboration Readiness Assessment when your unit is still building its partnership program and you want a read of whether it's ready to partner. Pick the Digital Maturity Assessment when the question is how your systems, data, and tools should change alongside a digital transformation. If unsure, say so at booking.