A bridge is a working relationship

I care about building relationships between people and institutions that do not ordinarily work together. Universities and companies, engineers and investors, and people with unusual ability who have not yet found a setting in which to use it are all part of that interest.

But “building bridges” is too easy to say. A room can be full of impressive people and still produce no shared work. A delegation can return with photographs and no clearer understanding of what either side needs.

The question I want to hold myself to is simpler: what became possible because someone took responsibility for the space between these groups?

A public example¶

The 2025 WTW series I coauthored grew from a collaboration between the WTW Research Network and Wharton’s Mack Institute Collaborative Innovation Program. Six of us contributed to work about models, deployment, and hardware. The published articles are a concrete output that someone else can inspect. That is a more useful account of collaboration than a list of the people who were in the room.

Start with a problem someone owns¶

An ecosystem is not a single person with a single objective. A university can contain researchers seeking publishable questions, administrators concerned with institutional commitments, and students looking for practical experience. A company can contain an enthusiastic technical champion and a budget owner who sees no reason to act.

Cross-border language adds another layer of abstraction. Saying that one region has capital and another has talent can be a conversation starter. It is a poor substitute for identifying actual people, capabilities, and constraints. Neither region is homogeneous, and the proposed complementarity may disappear when the particulars are examined.

I would begin with a problem, an owner, and a reason the owner cannot solve it alone. Then I would look for the missing capability. The resulting collaboration may be small: an independent test, an engineering exchange, a customer evaluation. A small project that works can teach more than a large partnership whose purpose is unclear.

Translation is part of the work¶

The interesting translation often has little to do with language. A researcher says the method is promising; an operator hears that it is ready. A founder says a pilot was successful; an investor assumes a purchase is next. A corporate sponsor says there is interest; the startup assumes there is a budget.

These statements can all be sincere. They refer to different thresholds.

The person in the middle creates value by making the thresholds explicit. What has actually been demonstrated? Who will evaluate the result? What would make the next commitment reasonable? What does each side believe the other has promised?

That work can feel less glamorous than arranging the meeting. It is also harder to replace with a contact list. A relationship becomes more useful when it carries accurate context and reliable follow-through.

Design the first piece of shared work¶

Consider a hypothetical collaboration between an industrial customer, a sensing startup, and a university laboratory. The customer has an operational question. The startup has an instrument. The laboratory can evaluate a measurement against an independent reference.

Before announcing a partnership, I would want a short shared brief: the question being tested, the samples available, who owns each part of the work, which data can be used for which purpose, and the decision after the result. I would also want to know what happens if the answer is negative.

If the customer thinks it is purchasing a deployable solution while the laboratory thinks it is exploring an open research question, the project is already in trouble. No amount of goodwill resolves a mismatch that remains unnamed.

The brief is not a replacement for the necessary agreements. It is a way to discover whether the parties are trying to do the same thing before investing heavily in doing it together.

Access should compound beyond the introducer¶

There is a version of bridge-building that keeps the intermediary essential forever. Every conversation must pass through them. Every relationship remains proprietary. The network grows, but the people in it gain little independent ability to work together.

I prefer an arrangement that becomes stronger after the introduction. The people doing the work should develop their own trust, shared vocabulary, and direct communication. The intermediary can remain useful by solving new problems rather than controlling old connections.

This is also the version that makes access more meaningful for people who begin outside established networks. An invitation is helpful. A substantive role in work that builds evidence of ability can be much more useful. The measure I care about is whether participation becomes consequential.

The limits of the thesis¶

Some connections will not produce projects, and that does not make them worthless. Friendship, curiosity, and intellectual exchange do not need to justify themselves with a transaction. I am describing what I would demand when claiming to create institutional or commercial value.

I also do not assume that a well-connected intermediary can overcome every structural constraint. Incentives may remain incompatible. The product may be wrong. Trust may take longer than the project allows. Sometimes the honest service is to explain why a proposed collaboration should not proceed.

The bridge I want to build is something people can cross: a relationship with enough shared understanding and practical structure for useful work to travel in both directions.