Partnerships · Independent perspective
A better first conversation about a technical partnership
Clarify the shared purpose, complementary capabilities, and evidence needed for a useful first collaboration.
Nate Shakouri · September 2026 · 3 minute read
Name the shared problem
A partnership conversation becomes concrete when both sides can describe the same problem and why solving it would be useful. Begin with the application, the intended user, and the outcome worth exploring together.
A broad overlap of interests can start a conversation. A specific question gives the conversation direction.
Make the contribution of each side explicit
Map the capabilities needed to answer the question. These may include scientific expertise, materials, experimental methods, manufacturing knowledge, application access, or engineering integration. Identify the gaps without assuming that a potential partner can fill all of them.
The objective of this first map is to understand why working together could improve the development path. It also makes it easier to recognize when a focused technical exchange is the appropriate next step.
Agree on the evidence that would be useful
Discuss what each side would need to see before making a larger commitment. A proposed evaluation should specify the question, relevant conditions, success criteria, and how results will be interpreted.
At this stage, a non-confidential overview can describe the need and available capabilities. Any later exchange of detailed information should follow arrangements appropriate to the participants and the work.
Keep the first step focused
An initial collaboration can be framed around one decision: whether an application deserves a deeper evaluation, whether two approaches are compatible, or which uncertainty needs to be resolved first.
A clear first-step brief names the question, each contribution, the expected output, the timing, and the decision that follows. This is an illustrative planning framework, rather than a report of a completed partnership.