System blockers and enablers

System blockers are the cultural, legal, financial and organisational conditions that keep otherwise promising collaborations locked into inherited ways of working.

These blockers aren’t isolated problems. They are patterned constraints: they show up differently across contexts but share recognisable logics, such as risk transfer, fiduciary duty, procurement rules or legacy metrics. The same condition can be a blocker or an enabler, depending on who is experiencing it.

Some genuinely bind. Many are cautious readings of rules that are less clear than they seem, held less for lack of knowledge than for lack of confidence about where the line really is.

A growing set of these surfaced while the Many-to-Many materials were being developed. They show up differently in different kinds of collaboration, so each kind needs its own space to be made legible and tested in practice. Below is a first attempt at making that visible.

Not everything here is a cautious reading. Practitioners also named constraints that bind hard: trustees keep their own legal responsibility, charity law limits what counts as permissible political activity, and holding charitable assets across borders comes with lasting restrictions. What binds, and how hard, also depends on the country. The work is telling the difference, case by case.

A sketch to be correctedDrawn from practitioner conversations, desk research and a workshop in Sheffield.

How we’re exploring this

Three kinds of collaboration, three journeys

Collaborations differ in who holds the money, who decides and who answers for what. To get specific, we look at three archetypes. Each moves through broadly the same stages, but in a different shape, with different conditions along the way.

* We’ve started here loosely and humbly, so that we can get specific while still looking at the whole system. These aren’t perfect archetypes, or the only ones, and a collaboration’s journey is rarely this sequential.

FramingDesignFunding and rolesDeliveryLearning, renewalPhilanthropy-fundedPublic-private, place-basedMulti-geography

Explored through research and conversations

Philanthropy-funded collaboration

Foundations or trusts funding a network of delivery and intermediary organisations towards a shared systems change goal. This is where our conversations, desk research and a workshop in Sheffield went deepest.

Explore where you got stuck

Explored through desk research *

Public-private and place-based partnerships

Local authorities, developers, anchor institutions and community organisations around a shared place or challenge.

Explored through desk research *

Multi-geography collaborations

A funder or programme working through a coordinating consortium with action in many places, where the work depends on what travels between them.

* If you’d like to take one of these forward with us, in conversation or testing, get in touch.

Using this page

How to use it

  1. Start where you got stuck

    Pick the moment in a collaboration where something made the work harder, or easier, than it should have been.

  2. Read the condition

    Who it blocks, who it enables, what it protects, and what others have tried.

  3. Tell us where it’s wrong

    Tell us what you found, what you have already tried, or what you would do.

Everything is labelled:Our hypothesisHeard in conversationsGap in evidence

None of this is legal advice. Whether something binds depends on who you are, where you are and the facts. We hope this page helps you take a better question to your own lawyer.

Philanthropy-funded collaboration · explored through research and conversations

Have you been here?

Think of a collaboration you’ve been part of, where something structural made the work harder than it needed to be.

Where did you feel it?

Pick the moment in the collaboration to see what we’ve mapped there.

  • What was that condition protecting?

    Someone, somewhere in the system, was relying on it.

  • Have you worked around it, or changed it?

    Most of us work around these conditions quietly and alone. Fewer try to shift them, and fewer still do it with others.

  • What risk does your organisation never write down?

    A risk register lists what could go wrong if you act. Where does it record what goes wrong if you don’t?

  • What would make change feel possible?

    If a few people wanted to change one instrument or one process, what would need to be true?

The journey · philanthropy-funded collaboration

Where conditions get fixed

We map conditions against the life of a collaboration. At each stage there are decision points where some certainty gets locked in. Some certainty is genuinely needed at these moments. The question is how it gets created, and at whose cost.

Showing Stage 1: Problem and mission framing

Stage 1

Problem and mission framing

The collaboration’s purpose gets defined: who it is for, what it is trying to change, and on whose terms.

Decision points:Mission and theory of change sign-off

Possible points of crystallisation, blockers and enablers

Pick a point to read its card. Larger dots are the cards from the Sheffield workshop; the rest are draft cards from desk research.

Mission and outcome framing

Our hypothesis

Based on research, tested in interviews and workshops · Sheffield workshop card

The moment

The collaboration’s purpose gets defined. This moment sets the frame that everything else will be measured against.

The pattern

Mission and outcome language gets fixed internally by the lead organisation or funder before local actors can meaningfully contribute.

Felt as a blocker by

Community organisations, local authorities, delivery partners. They join a collaboration whose purpose was already decided. Ownership is performed rather than real.

Felt as an enabler by

Boards, strategy teams, programme leads. A stable narrative for resource approval, and a defensible scope before launch.

Questions to ask here

Example answer · “Who shaped the mission before local actors could contribute?”

What the material holds, as a range, with where each item comes from:

  • Our hypothesisMission and outcome language often gets fixed inside the lead organisation or funder before local actors can meaningfully contribute (workshop card).
  • Heard in conversationsSeveral people described strategy being set before the people closest to the work are in the room.
  • Heard in conversationsSome funders are giving up OKRs and fixed outcomes, and funding hypotheses and learning questions instead. What is possible depends on the country and the funder’s legal form.
  • Gap in evidenceNo published account yet of how an open mission was approved and held over time.

A better question to take away

What would it take for the mission to be something partners shape, rather than join?

This shows what people have said and tried. It isn’t legal advice, and it doesn’t tell you whether anything binds you.

Ask, correct or share

We don’t give live answers yet. Send a question, a correction or what you’ve tried, and we’ll review it before it feeds into the wiki.

What would you like to send?

Only Dark Matter Labs sees your email. We use it to reply to you and delete it once we have.

We review everything first. Please leave out names and anything confidential.

Across all three archetypes

Look across collaborations

Every pattern we hold so far, and the rules and readings behind them. Philanthropy-funded collaboration is the one we have gone deepest on. The other two come from desk research only, so treat them as a thinner sketch again.

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

Three entries, worked end to end

From a pattern to what could be done

For three patterns we have followed the whole chain: the rule itself, how it tends to be read, the practice built on it, our own read, and what could be done at three levels. The evidence behind each is shown as a range, including where it is thin. None of this is legal advice.

The rule behind it · How trustee duties are read

1 · What it says

Trustees must use the charity’s assets only for its purposes, act reasonably and prudently, safeguard its assets, act in its best interests, and act lawfully.

As set out in a legal view prepared for one foundation’s trustees (2024).

2 · How it is read

The duties are often read as a duty to avoid risk, and above all to avoid personal liability. So exposure is passed down the chain to the party least able to carry it. The same legal view reads it differently: risk “is not necessarily to be avoided”, and trustees weigh the risks of entering an arrangement against the risks of not entering it. It calls personal liability “extremely rare”.

3 · The practice built around it

Master grant templates, indemnity and clawback clauses, insurance requirements and sub-granting terms. Advice is usually commissioned by the funder alone, and leans to the most cautious reading.

4 · Our read, to test

Mainly the reading and the practice, not the rule. That is our working view, and a lawyer should check it.

What could be done

  1. 1. A workaround, now

    Negotiate the terms. Replace a broad clawback with a narrow indemnity and a named mediator. Share risk by each party’s capacity to carry it. Chart where risk sits before anyone signs.

  2. 2. Shift how it is read

    Show the board, duty by duty, how the arrangement meets each duty, and ask it to approve the approach once rather than deal by deal. Commission advice from counsel the board already trusts. Brief lawyers jointly, through a collaborative engagement letter, rather than one party at a time. Write down the risk of not acting next to the risk of acting.

  3. 3. Shift it together, upstream

    Build shared legal capacity: precedents and model clauses others can use, and a reading of the duties, tested with practitioners, that boards can rely on.

How much evidence we have

Shown as a range on purpose. The thin lines are the honest part.

Observed
Raised in several conversations: the cautious reading binds more than the duties do. In the Sheffield room, people described risk held alone that could be held together.
Drafted
A legal view setting out the duties against a many-to-many agreement. A risk-resolution term, drafted and agreed in one collaboration.
Tried, and where
The legal view was used with one foundation’s board. The risk-resolution term has not yet been used in the situation it was written for.
Outcome known — nothing yet
Not yet. No account on record of what changed once the board had the reading.
Not yet tested
Whether the reading holds for other boards, other legal forms, or other countries.

A question for every stage

Binding, or chosen?

Is this constraint actually binding, or a cautious reading of something less fixed? A fiduciary duty is a condition. Meeting it through a one-year grant tied to fixed outputs is a design choice. That is often where the room to move is.

  1. Within the rules

    Done as the rules expect.

  2. Between the rules

    Where the rules are silent, and practice fills the gap.

  3. Beyond the rules, lawful

    New, and still within the law.

  4. Beyond the rules, needs change

    Would need the law, guidance or a governing document to change.

Not every constraint is a choice. Some bind hard, and what binds depends on the country.

A range, not a recommendation

What others are trying

These are patterns we heard across several conversations, not single cases, and none of them is settled.

Heard in conversations

Funding hypotheses instead of fixed outcomes

Some funders are giving up OKRs and fixed outcomes, and funding hypotheses and learning questions instead. What is possible depends on the country and on the funder’s legal form.

Where it bites:Stage 1Stage 5
Heard in conversations

Agreeing in principle, designing later

A board agrees in principle that certain funds will be held for a broader purpose. The detailed arrangements come back for discussion and reflection, not re-approval. Whether that distinction holds over time is still being tested.

Where it bites:Stage 1Stage 3
Heard in conversations

Supporting trustees’ confidence

People who work with boards described how much time goes into supporting trustees’ thinking and confidence, much of it shaped by questions of attribution and risk.

Where it bites:Stage 3Stage 5
Heard in conversations

Commissioning legal advice the board will trust

Funders commission specific legal advice, sometimes at great cost and from firms chosen for their reputation. It can unlock things. Few can afford to keep doing it, one organisation at a time.

Where it bites:Stage 3
Heard in conversations

Reporting differently

Funders and the organisations they fund are experimenting with ways of reporting that hold accountability alongside relational trust, rather than through bureaucracy that undermines the work.

Where it bites:Stage 4Stage 5

Corrections

Tell us where this is wrong

We would rather hear “no, that’s wrong, this is what we found, and this is how” than quiet agreement. Every stage above has its own box for that. You can also register interest in working on one condition with others.

What happens to what you send: we review everything before it feeds into the wiki, and we’ll share anonymised reflections on this page. We won’t use your name unless you ask us to. Please leave out names and anything confidential.

Something else to tell us?

A question, a correction or an experience that doesn’t fit one stage.

What would you like to send?
How is it wrong?

Only Dark Matter Labs sees your email. We use it to reply to you and delete it once we have.

We review everything first. Please leave out names and anything confidential.

Work on a condition with others

Tell us which condition or kind of collaboration you’d like to take forward, in conversation or testing, and we’ll get in touch.

Only Dark Matter Labs sees your email. We use it to reply to you and delete it once we have.

We review everything first. Please leave out names and anything confidential.

Tools

Use them in your own collaboration

We’re still testing these canvases for rigour, so they aren’t published yet.

  • In development

    Journey map canvas

    The five stages, blank, to map your own collaboration.

  • In development

    Working canvas

    For one condition: who it blocks, who it enables, and what it protects.

  • In development

    Decision cards

    The cards from the Sheffield workshop, and a blank one.

About this work

System Blockers is part of Many-to-Many, Dark Matter Labs’ work on the legal and organisational design of complex collaborations. It draws on practitioner conversations, desk research and a workshop in Sheffield, and it builds on the Many-to-Many Field Guide. Everything here is a working hypothesis.

How items are marked

Our hypothesis
A pattern we think we see, still to be tested further.
Heard in conversations
Came up across several practitioner conversations or the Sheffield workshop.
Gap in evidence
Something we don’t yet have evidence for.