46 of 46 patterns.
Philanthropy-funded · Before it started · Ecosystem strategy
Who is in the room
Eligibility follows existing infrastructure (a bank account, a constitution, a track record), so the places and groups with least infrastructure are excluded before anything starts.
- Blocks:
- Grassroots and unincorporated groups, and places with little civic infrastructure. A door that was never open to them.
- Enables:
- Grant teams and boards. A pool of applicants who can be checked, paid and held to account.
The rule behind it: Funding groups without a legal form · What the regulator actually requires
Tested in workshops
Philanthropy-funded · Before it started · Governing system
How fiduciary duty is read
Fiduciary duty is often read as a reason to keep decisions close, and the cautious reading tends to win.
- Blocks:
- Collaborations and pooled funds trying to form. A cautious answer that is hard to question, because it sounds legal.
- Enables:
- Boards and their advisers. A clear line of accountability for every pound spent.
The rule behind it: How trustee duties are read · How legal advice is bought
Tested in interviews
Philanthropy-funded · Before it started · Governing system
Who can take part in governing
Governing roles are usually unpaid and time-heavy, so they tend to be filled by people who already have the time and security to give.
- Blocks:
- People with lived experience, and people on low incomes or benefits. A seat that is open in principle but hard to take up.
- Enables:
- Existing trustees and regulators. Protection against conflicts of interest and private benefit.
The rule behind it: Who can be paid to take part · What trustees can delegate
Tested in interviews
Philanthropy-funded · Problem and mission framing · Ecosystem strategy
Mission and outcome framing
Mission and outcome language gets fixed internally by the lead organisation or funder before local actors can meaningfully contribute.
- Blocks:
- Community organisations, local authorities, delivery partners. They join a collaboration whose purpose was already decided. Ownership is performed rather than real.
- Enables:
- Boards, strategy teams, programme leads. A stable narrative for resource approval, and a defensible scope before launch.
The rule behind it: How trustee duties are read · What a charity may be and do
Tested in interviews and workshops
Philanthropy-funded · Problem and mission framing · Ecosystem strategy
Funders’ goals don’t line up
Each funder brings its own strategy, so the shared aim is written loosely enough for every strategy to fit inside it.
- Blocks:
- The collaboration and its backbone. A mission that means different things to each funder, and reporting to all of them.
- Enables:
- Each funder’s board. A way to join without changing its own strategy.
The rule behind it: To be mapped
Based on research
Philanthropy-funded · Problem and mission framing · Ecosystem strategy
Whose name is on it
Funders need to show their own contribution, so credit is claimed separately, and shared outcomes are cut into attributable pieces.
- Blocks:
- Partners doing shared work. Pressure to show which funder’s money did what.
- Enables:
- Communications and fundraising teams. A story they can tell their own donors and board.
The rule behind it: To be mapped
Based on research
Philanthropy-funded · Portfolio and collaboration design · Organising system
Coordination and learning infrastructure
Coordination, convening and learning work gets absorbed into indirect cost lines or left unfunded, because overhead should be minimised and money should reach frontline delivery.
- Blocks:
- Backbone organisations, coalitions, learning partners. Glue work happens invisibly. One person carries several informal roles with no budget and no recognition.
- Enables:
- Finance teams, programme leads, boards, donors. Overhead ratios stay low, funds are visibly directed to delivery, audit requirements are met.
The rule behind it: Value counted only in money
Tested in interviews and workshops
Philanthropy-funded · Portfolio and collaboration design · Ecosystem strategy
Call and programme design
Calls are designed around individual projects first, with collaboration mentioned but not structurally supported or scored.
- Blocks:
- Coalitions, intermediaries, community organisations trying to collaborate. Partnership in name only: one lead with others attached, because the call rewards individual track records.
- Enables:
- Programme teams, selection panels, boards seeking comparability. A manageable, comparable application pool with clear scoring and a defensible selection.
The rule behind it: To be mapped
Tested in interviews and workshops
Philanthropy-funded · Portfolio and collaboration design · Legal architecture
One lead, or many-to-many?
One lead partner is the default, because a funder needs a single accountable entity, so a network is contracted as a hierarchy.
- Blocks:
- The other partners. Junior status in a collaboration they co-own, and by the lead, as liability for others’ work.
- Enables:
- Funders and their auditors. One contract, one report and one place to look when something goes wrong.
The rule behind it: Who is liable to whom · How trustee duties are read · VAT on money moving within a collaboration · Who the lawyer works for · What audit and board oversight expect
Tools: Many-to-Many Agreement (Field Guide example)
Tested in interviewsWorked through in full below
Philanthropy-funded · Portfolio and collaboration design · Governing system
Who decides
Decisions stay with the board, because delegating feels legally risky, even where the governing document allows it.
- Blocks:
- Communities and panels asked to advise but not decide. Participation without power.
- Enables:
- Trustees. Keeping hold of decisions they remain accountable for anyway.
The rule behind it: What trustees can delegate · How trustee duties are read
Tools: Role cards for flexible governance (Field Guide)
Tested in interviews
Philanthropy-funded · Portfolio and collaboration design · Organising system
Many pots, one collaboration
Each pot comes with its own rules, timings and reports, so the collaboration is stitched together from pieces that were never designed to fit.
- Blocks:
- Backbone organisations. Time spent reconciling funders instead of doing the work.
- Enables:
- Each funder. Control over exactly what its own money buys.
The rule behind it: To be mapped
Tested in interviews
Philanthropy-funded · Funding, roles and conditions · Legal architecture
Risk and liability allocation
Standard grant terms concentrate legal and financial exposure at the bottom of the funding chain, because a single accountable entity must sit at the top and fiduciary duty must be protected.
- Blocks:
- Small NGOs, community groups, local delivery partners. Exposure their insurance doesn’t cover. They take part defensively, or not at all.
- Enables:
- Boards, legal teams, finance and risk committees. Protects the lead organisation’s fiduciary position and gives the board a clean line of accountability.
The rule behind it: How trustee duties are read · Who is liable to whom · Indemnities, clawback and insurance · Who the lawyer works for · How legal advice is bought
Tools: Charting risk flows (Field Guide), and an alternative risk register (in development)
Tested in interviews and workshopsWorked through in full below
Philanthropy-funded · Funding, roles and conditions · Legal architecture
More checks than the law asks
Checks are set at the level that would protect the funder in the worst case, and every funder repeats them.
- Blocks:
- Small organisations. Weeks of paperwork for every grant, and by collaborations, as the same checks done again by each funder.
- Enables:
- Boards and risk committees. A defensible record if anything goes wrong.
The rule behind it: What the regulator actually requires · How legal advice is bought
Tested in interviews
Philanthropy-funded · Funding, roles and conditions · Legal architecture
Someone has to hold the money
A fiscal host or lead partner holds the money and the risk, usually without being paid for carrying the risk.
- Blocks:
- Hosts. Liability with no budget, and by the groups hosted, as dependence on someone else’s systems.
- Enables:
- Funders. A way to reach groups they could not fund directly.
The rule behind it: Funding groups without a legal form · Who is liable to whom
Tested in interviewsWorked through in full below
Philanthropy-funded · Funding, roles and conditions · Ecosystem strategy
Money that can’t be spent
Endowment is treated as untouchable, so the foundation’s largest resource sits outside the collaboration.
- Blocks:
- Collaborations needing scale or long horizons. The foundation’s wealth being off the table.
- Enables:
- Trustees and investment committees. The foundation surviving to fund in future.
The rule behind it: How investment duties are read
Based on research
Philanthropy-funded · Funding, roles and conditions · Organising system
Paying people for what they know
Payment is avoided or kept token, because tax, benefits and employment rules make it complicated.
- Blocks:
- Participants. Giving expertise for free, or risking their benefits.
- Enables:
- Organisations. Avoiding liabilities they don’t know how to manage.
The rule behind it: Who can be paid to take part
Tested in interviews
Philanthropy-funded · Delivery and coordination · Legal architecture
Delivery agreements and milestone design
Grant agreements lock collaborations into predefined milestones and outputs, because fixed plans are easier to track, defend and audit.
- Blocks:
- Delivery organisations, public partners, communities, learning partners. They keep delivering work they don’t believe in, because changing course means renegotiating the grant.
- Enables:
- Programme managers, MEL teams, boards, reporting functions. Stable plans that can be tracked against budget, reported to the board and defended to auditors.
The rule behind it: What audit and board oversight expect
Tested in workshops
Philanthropy-funded · Delivery and coordination · Learning system
Every funder wants a different report
Each funder sets its own format and timing, so a collaboration with several funders writes several reports about the same work.
- Blocks:
- Partners and backbones. Reporting time taken from delivery.
- Enables:
- Each funder’s board. Information in the shape it already knows how to read.
The rule behind it: What the regulator actually requires
Tested in interviews
Philanthropy-funded · Delivery and coordination · Organising system
When the coordinator leaves
The collaboration depends on one or two people whose coordinating work was never funded as a role, so it stalls when they go.
- Blocks:
- The collaboration. Losing its memory and its relationships at once.
- Enables:
- Funders. Low running costs while it lasts.
The rule behind it: To be mapped
Tested in interviews
Philanthropy-funded · Delivery and coordination · Learning system
Not safe to say it’s going wrong
Partners report success, because admitting problems feels like risking the next grant.
- Blocks:
- The collaboration’s learning. Problems that surface too late to fix.
- Enables:
- Grantees and funders alike. A clean report that keeps the relationship calm.
The rule behind it: To be mapped
Tested in interviews
Philanthropy-funded · Delivery and coordination · Governing system
The risk register is kept for the funder
The register records risks to the institution, its money and reputation, and has no line for the risk of not acting.
- Blocks:
- Partners and the collaboration’s purpose. Caution always winning.
- Enables:
- Boards and auditors. A familiar and defensible record.
The rule behind it: How trustee duties are read
Tools: An alternative risk register (in development)
Tested in interviews
Philanthropy-funded · Learning, adaptation and continuation · Learning system
Renewal and continuation criteria
Renewal decisions are shaped by visible outputs and legible stories, because boards need defensible evidence and communications teams need narratives that travel.
- Blocks:
- Backbone organisations, coalitions doing governance and trust-building work. They lose funding despite holding the collaboration together, because relational progress never appeared in a report.
- Enables:
- Trustees, senior leadership, communications and fundraising teams. The next funding round secured with a strong impact narrative and a board that can defend it.
The rule behind it: Value counted only in money
Tested in workshops
Philanthropy-funded · Learning, adaptation and continuation · Learning system
Learning that changes nothing
Learning is gathered and reported, but no decision is waiting for it, so it changes nothing.
- Blocks:
- Learning partners and the collaboration. Insight with nowhere to go.
- Enables:
- Funders. Evidence of rigour without having to change course.
The rule behind it: To be mapped
Tested in interviews
Philanthropy-funded · Learning, adaptation and continuation · Ecosystem strategy
New over what works
New projects are favoured over continuing ones, so work that is working is not renewed.
- Blocks:
- Established collaborations. Having to reinvent themselves to stay funded.
- Enables:
- Funders and their boards. A fresh story and room in the budget.
The rule behind it: To be mapped
Based on research
Philanthropy-funded · Learning, adaptation and continuation · Ecosystem strategy
The funder leaves
Grants end with a strategy change, often with little notice or explanation.
- Blocks:
- The collaboration. A cliff edge.
- Enables:
- The funder. Freedom to move its money where its new strategy points.
The rule behind it: To be mapped
Tested in interviews
Philanthropy-funded · Learning, adaptation and continuation · Governing system
Afraid of being blamed
Boards avoid funding anything that might fail visibly, so experimental and long-term work struggles to start.
- Blocks:
- Experimental and long-term work. Never being funded in the first place.
- Enables:
- Trustees. Protection for their own reputation and the foundation’s.
The rule behind it: How trustee duties are read
Tested in interviews
Public-private, place-based · Before it started · Governing system
System users underrepresented in early design
People who use or are affected by the system are weakly represented when missions and designs are set.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: No rule strictly. Sometimes formal consultation requirements.
Desk research
Public-private, place-based · Problem and mission framing · Ecosystem strategy
Mission negotiated between corporate partners
The mission is negotiated mainly between corporate partners, with limited public or civic input.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Directors’ duties to shareholders. Directors’ duties, and what boards and investors will accept.
Desk research
Public-private, place-based · Portfolio and collaboration design · Legal architecture
Partnerships run like procurement
Partnerships are structured like buyer and supplier relationships, which limits joint problem-solving.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Public procurement rules. Public procurement rules, competition law and conflict-of-interest rules.
Desk research
Public-private, place-based · Funding, roles and conditions · Ecosystem strategy
Short payback pressure
Corporate partners need short payback periods, which limits investment in long-term system infrastructure.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Directors’ duties to shareholders. Shareholder expectations, internal hurdle rates and capital rules.
Desk research
Public-private, place-based · Funding, roles and conditions · Legal architecture
Liability lands on the public or civic partner
Contracts place most delivery and reputational risk on public or civic partners, even where private actors drive key decisions.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Public accountability for failure. Public accountability for failures, and corporate risk frameworks.
Desk research
Public-private, place-based · Funding, roles and conditions · Legal architecture
IP defaults to the corporate partner
Intellectual property made together defaults to corporate ownership, which limits wider use.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Intellectual property defaults. IP law, freedom of contract and corporate IP policies.
Desk research
Public-private, place-based · Delivery and coordination · Governing system
The corporate calendar sets the rhythm
Meetings and decisions follow corporate quarter-ends, and public timelines and community rhythms come second.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Corporate planning and approval cycles. No rule as such.
Desk research
Public-private, place-based · Delivery and coordination · Learning system
Data locked behind commercial walls
Useful data is held back because of IP, confidentiality or competition concerns.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Data protection, competition and confidentiality. Data protection law, competition law and commercial confidentiality.
Desk research
Public-private, place-based · Delivery and coordination · Governing system
Decisions made in side meetings
Issues are settled through informal channels, which sidelines partners with less access.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: No rule. Often against the partnership’s own governance documents.
Desk research
Public-private, place-based · Learning, adaptation and continuation · Learning system
Brand decides what continues
Decisions to continue or scale follow brand and PR value more than system impact.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Brand and investor confidence. No rule as such.
Desk research
Multi-geography · Problem and mission framing · Ecosystem strategy
Wide mission, narrow local bandwidth
A broad mission is set centrally, while local actors have little time or support to interpret it.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research
Multi-geography · Problem and mission framing · Ecosystem strategy
Wide mission or project aims?
People struggle to tell the long-term mission from near-term project objectives.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research
Multi-geography · Portfolio and collaboration design · Organising system
One template for many places
Central templates for workplans don’t fit the diversity of places and actors.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research
Multi-geography · Portfolio and collaboration design · Organising system
Relational labour nobody sees
People doing local convening and emotional labour are not recognised or resourced as core roles.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research
Multi-geography · Funding, roles and conditions · Legal architecture
One fiscal host per place
Money flows through one or two organisations per place, which concentrates power and administration.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: Holding and moving assets across borders
Desk research
Multi-geography · Funding, roles and conditions · Governing system
A consortium caught in the middle
The coordinating consortium is pulled between supporting local actors and enforcing funder conditions.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research
Multi-geography · Delivery and coordination · Governing system
Light but fragile local governance
Local governance stays informal to avoid bureaucracy, so decisions and conflicts have no clear route.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research
Multi-geography · Delivery and coordination · Learning system
Learning as reporting
Learning sessions across places default to updates, with little time to make sense of things or adapt.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research
Multi-geography · Learning, adaptation and continuation · Ecosystem strategy
Early allocations stick
Early choices of places and partners become hard to change, even when the evidence shifts.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research
Multi-geography · Learning, adaptation and continuation · Ecosystem strategy
Cliff-edge endings
Funding ends abruptly at programme close, with little planning for a responsible ending.
- Blocks:
- We have not identified who.
- Enables:
- We have not identified who.
The rule behind it: To be mapped
Desk research