Some social opportunities fail for reasons that are relatively easy to identify: there is no viable intervention, the required resources do not exist, or the incentives of the relevant actors are incompatible. Others are more puzzling. The knowledge exists, capable people are available, resources can in principle be found, and several organisations may even agree that the problem matters, yet the pieces never form a coherent activity.
I use orchestration to describe part of what is missing in those situations.
The term is useful because coordination can sound narrower than the problem actually is. The work may begin well before anyone is scheduling meetings or allocating tasks. Somebody has to recognise that capabilities held in different places are complementary. Different actors may need a shared representation of the problem. Professional vocabularies have to be translated. Responsibilities need to become legible. Someone must maintain continuity through the period in which the collaboration is not yet valuable enough to sustain itself.
Much of this work is difficult to see once a collaboration succeeds because the eventual project becomes the visible object. The introductions, interpretation, trust-building and repeated alignment that made it possible disappear into the background. When the collaboration fails to form, however, the absence of those functions can be decisive.
I do not think the implication is that every ecosystem needs a powerful central coordinator. That would often substitute one bottleneck for another. A system in which all valuable activity depends on a single intermediary may appear well coordinated while remaining structurally fragile.
The more interesting question is how orchestration costs can be reduced.
Existing relationships reduce the work required to establish trust. Shared terminology reduces translation costs. Clear contribution pathways help people identify where their skills might be useful. Reusable contractual, governance or programme structures reduce the institutional effort involved in each new collaboration. Communities can give people enough recurring contact that they recognise complementary interests before a formal project exists.
In this sense, orchestration can sometimes be embedded in infrastructure rather than performed anew for every initiative.
That possibility is relevant to Real Good because many of the capabilities I am interested in are distributed. Real Good is unlikely to possess internally all the expertise, institutional access, lived knowledge, resources and authority needed for the problems it encounters. A more plausible role is to become good at forming useful combinations while avoiding unnecessary ownership of capabilities that are already held effectively elsewhere.
There are also important failure modes. Coordination can become an end in itself. Networks can spend substantial amounts of time convening without producing action. Intermediaries can create dependencies or insert themselves into relationships that would function better directly. The costs of participation can fall disproportionately on community organisations or people providing lived knowledge while larger institutions capture most of the value.
A credible orchestration model therefore needs to demonstrate more than activity. It should reduce the total effort required to form useful collaborations, improve the quality of matching between capabilities and problems, or increase the likelihood that worthwhile work proceeds.
That is what makes orchestration interesting to me as an organisational capability. It is not the ability to sit in the middle of more things. It is the ability to make productive combinations easier to form, including combinations that eventually cease to require the orchestrator.