No Pride of Authorship. Pride of Partnership.

By Laurence Kalinsky, Executive Director, Family Offices For Sustainable Development (FOSD), at PVBLIC Foundation

Originally posted on Medium

I’ve been thinking about this more than I expected lately.

There is a shift underway in how real development is being executed, and it is becoming more visible the closer you get to the work itself.

Not in the announcements, and not in the narratives that tend to frame progress, but in the way things are actually moving underneath. In how capital is aligning. In how institutions are beginning to rely on each other differently. In how execution is starting to take precedence over positioning.

I have found myself coming back to this repeatedly. Not as a concept, but as something that shows up consistently across conversations, partnerships, and decisions. The closer I get to the systems we are trying to help innovate, the clearer it becomes that one of the greatest constraints is not a lack of resources or ideas. It is the quiet but persistent need for authorship.

The need to be seen as the one who led it, structured it, or drove it forward. It is not always explicit, and it is not always intentional, but it shows up often enough to slow things down and, in some cases, limit what is actually possible. Because the systems we are working within today do not respond well to ownership in that sense. They are too interconnected, too dependent on alignment across actors who each hold a necessary part of the equation.

I have felt that tension myself at times. The instinct to define the lane, to make sure the structure is clear, to ensure that what is being built is understood as coming from a specific place. But what I have come to realize is that the moment that instinct takes hold too tightly, the work starts to narrow. This is compounded by the basic human need to be recognized for effort and results.

Real change happens when the work itself has evolved beyond what any single institution or individual can claim.

When you are operating across governments, multilateral institutions, family offices, technology partners, capital platforms, and increasingly complex pathways for technology transfer, the idea that one group,or one figurehead, can own the narrative begins to break down.

More importantly, it becomes counterproductive. It creates friction where there should be coordination, and it narrows participation where scale depends on openness.

Technology transfer, in particular, makes this unavoidable. It is not a linear process. It requires alignment between those who build the technology, those who regulate it, those who finance its deployment, and those who ultimately implement it on the ground. If any one of those actors attempts to control the process, the system stalls. When they operate in coordination, the system begins to function as intended, and then development flourishes.

What I have found, and continue to see more clearly over time, is that the work moves differently when that instinct for ownership is set aside.

Not because authorship is unimportant, but because it is redefined.

The most effective actors in this environment are not the ones trying to consolidate recognition. They are the ones who understand how to contribute to a system larger than themselves and do so in a way that allows others to operate at full strength alongside them. There is a level of confidence required in that, and also a level of restraint.

But the key factor is that, regardless of ownership and authorship, the return is real.

When that posture is present, trust builds faster. Conversations that would normally take months begin to align in a matter of weeks. I have seen situations where doors that felt firmly closed simply opened once the dynamic shifted away from ownership and toward contribution.

Governments engage differently. Multilateral institutions respond with more openness and clarity because the interaction is not perceived as extractive or self-serving, but as additive.

That is particularly evident in how partnerships form with institutions such as the World Food Programme (WFP) and the United Nations Office for Outer Space Affairs (UNOOSA), where the work is grounded in mandate, continuity, and scale. These are not environments where visibility drives outcomes. They are environments where alignment, credibility, and long-term consistency determine whether something moves or not.

The same dynamic is emerging more clearly within the Family Office community. Those that are mission-driven are leaning in most effectively, not by asking how they are positioned within the work, but by asking how they can be useful within it. Recognition will inevitably be part of the equation, but the development that works is almost always led with the question of how they can actually strengthen the system rather than their own personal portfolio. That is a different conversation, and it leads to very different outcomes.

That shift leads to a very different kind of partnership.

Internally, thanks to an incredible partner at the foundation, I have started to think of these individuals and families as transmitters. Not in a conceptual sense, but in a very practical one. They move capital, trust, and alignment through systems that require all three to function. They connect institutions that might not otherwise engage. They support structures that are designed to operate beyond any single actor. And the energy they bring permeates the scope of the projects meant to facilitate development on the ground.

And importantly, they do so without needing to anchor the work back to their own authorship.

That is not a passive role. It is an active discipline.

It requires being comfortable with ambiguity, with shared ownership, and with outcomes that are not always directly attributable. It also requires a clear understanding of the system itself, because contributing effectively without controlling the narrative demands a higher level of awareness and intention.

But when it works, the effect is unmistakable. You see it in the speed of execution. You see it in the depth of partnership. In the way capital begins to move with purpose instead of hesitation. And most clearly, you see it at the point where system-level design, including the transfer of technology and capability, translates into real outcomes at the community level. This is where alignment either holds or falls apart. This is where the distinction matters most.

System-level thinking is only meaningful if it carries through to implementation. It must reach the entrepreneur within a REIN hub, the policymaker navigating deployment, and the communities that ultimately experience the impact. If the system does not connect end-to-end, it remains conceptual.

That is why partnership, in this context, is not a preference. It is a requirement.

No single institution can design, finance, and execute across all of these layers. The work depends on a distribution of responsibility that reflects the complexity of the challenge itself. It depends on people and institutions showing up with clarity of role, but without the need to control the entirety of the outcome.

In many ways, this is already reflected in how we are evolving more broadly, moving from individual programs toward something more institutional. Something designed to hold across sectors and geographies as a functioning system, rather than a collection of initiatives.

That evolution has required me, personally, to rethink what it means to contribute.

Less about defining ownership and more about ensuring that what is being built can actually hold.

It requires letting go of the idea that impact must be owned to be meaningful, and replacing it with the understanding that the most durable impact is almost always shared. Not diluted, but strengthened through contribution.

There is a discipline to that. It does not happen naturally, and it is not always comfortable. But it is increasingly clear that it is necessary.

Because the work that endures is not built by those who need to be seen as the authors.

It is built by those willing to be part of something that works.

No pride of authorship. Pride of partnership.