As Real Good has developed as a portfolio rather than a single programme, I have become more attentive to the distinction between an initiative’s direct outputs and the capabilities it leaves available for subsequent work.
A project may be commissioned to produce one thing and still generate several others incidentally. A programme develops a facilitation method. A collaboration establishes a trusted relationship with an institution. A service requires a piece of technology that solves a more general problem. A pilot generates knowledge about participation that becomes relevant to another initiative.
These residual capabilities can have significant organisational value because they change the starting conditions for future work.
The effect is straightforward in principle. If a useful method already exists, it does not need to be rediscovered. If trust has already been established between organisations, the next collaboration can begin further along. If technology has been designed with sufficient generality, a second programme may be able to reuse it. If knowledge has been retained in a form that others can understand, later decisions can draw on evidence rather than institutional memory alone.
This is one of the potential advantages of a portfolio organisation. Capabilities can move laterally between initiatives rather than remaining enclosed within the project that originally financed or developed them.
But there is an important design tension. Reuse can become an excuse for premature standardisation. A tool designed for one context may perform poorly elsewhere. A common platform can impose unnecessary dependencies. An organisation can spend more effort trying to extract synergies than those synergies are worth. The promise that “everything connects” is often more aesthetically satisfying than operationally true.
I therefore think the useful principle is narrower: preserve optionality for reuse where the cost is justified, but do not require artificial integration.
That may mean documenting a method rather than converting it immediately into an organisation-wide standard. It may mean maintaining a partnership because it has continuing mutual value, not because every initiative must use it. Shared technology should be modular where feasible, but initiative-specific requirements should remain allowed to diverge.
What matters is that useful capability does not disappear merely because the project that created it has ended.
This also changes how organisational accumulation can be understood. Growth is often described through staff, revenue, programmes or geographic reach. Another form of growth occurs when the organisation acquires a richer stock of relationships, methods, knowledge, technical assets and institutional understanding that makes subsequent work easier or better.
That is the form of accumulation I want Real Good to cultivate deliberately. The objective is not an increasingly complicated internal ecosystem. It is an organisation whose previous work improves the quality and feasibility of what it can attempt next.
The relevant evaluative question is therefore not whether every capability is reused, but whether valuable capabilities remain legible and accessible enough that they can be reused when the opportunity is real.