The Shelf: How Institutions Delay Without Refusing
By Jayde Fuller - Indigenous Regulatory Practice
Suggested citation
Fuller, J. (2026, 30 July). The Shelf: How Institutions Delay Without Refusing. https://doi.org/10.5281/zenodo.21675488
There is a particular kind of grief that never makes it into the strategy document. It isn't the grief of being told no. It's the grief of never being told anything at all.
You've seen it. You've maybe lived it. An Indigenous-led solution — designed by community, grounded in what actually works, built to change a system that has failed our people for generations — is welcomed. Praised, even. Minuted. Committed to. Resourced. And then it goes quiet. No one rejects it. No one argues with it. It simply stops appearing on anyone's agenda, and the people who built it are left holding something that was purchased but never used.
I want to give that experience language — not as a list of bad behaviours by bad actors, but as what it actually is: a system doing exactly what it was built to do.
Picture multiple separate pieces of Indigenous-led work, commissioned by the same institution, each fully resourced and delivered. Each one revolutionary in its own field — designed to change how the system treats our people. None of them rejected. None of them implemented. Just quietly, permanently, on the shelf. If that scene is instantly familiar to you, you already know everything this piece is trying to explain. What follows is language for the part you've already lived.
Part One: The System
It isn't individual failure - it's design
Oglala Lakota systems analyst Jesse Grey Eagle [1] argues that systemic outcomes are shaped by lineage, inherited demographics, and exclusionary design — not by the effort or intentions of the individuals inside the system. This matters enormously for how we read the shelf. The report that never gets implemented isn't sitting there because a particular manager was lazy, or a particular committee was slow. It's sitting there because the system was built, through inheritance and design, to produce exactly that outcome.
Grey Eagle's concept of coherence as operating condition is the sharpest tool available here. Western institutional systems are built to optimise their parts — a program, a report, a compliance metric, a reputational milestone. Indigenous systems are built to maintain relational integrity across the whole. When an institution commissions transformative Indigenous work and then shelves it, the institution has not failed at coherence. It has succeeded at a narrower, self-referential coherence — protecting its own legitimacy, its own metrics, its own continuity — directly at the expense of the wider system's coherence: the actual wellbeing of the people the work was meant to serve.
This is why naming individual behaviours, on its own, will always feel unsatisfying. You can document every stalling tactic in a single unit and still not explain why the exact same pattern shows up, independently, across regulators, health services, and government departments who have never spoken to each other. That repetition is the signature of a system, not a coincidence of personalities.
The gap, and the two thresholds
In my own framework [2], the space between commitment and structural transformation has two threshold conditions, which must happen in this order: first, rescinding white and institutional power — an actual relinquishment of decision-making authority over the lives, care and futures of Indigenous Peoples, not a consultation or a seat at a table the institution still controls. Second, actively supporting Indigenous self-determination, leadership, knowledges and governance — not advising on outcomes, but ceding the authority to determine them.
Everything I've described so far — the commissioning, the resourcing, the praise, the minuted commitment — sits in the gap before either threshold is crossed. This is the trap in how the pattern gets misread from inside an institution. Visible activity gets mistaken for movement toward threshold one, when in systems terms it's usually a parameter-level intervention, engineered precisely to generate the appearance of progress without ever touching the rule that actually governs where power sits.
Read through a systems lens, the gap and the two thresholds function as competing operating states inside the same institution. The system's stated goal is to reach both thresholds. Its operating goal — the one revealed by what it actually protects — is to remain, indefinitely, in the gap: visibly active, citable as evidence of commitment, and never structurally required to relinquish anything.
Yellowknives Dene political theorist Glen Coulthard [3] names this same gap at the level of the state. In Red Skin, White Masks, he argues that the politics of recognition does not dismantle colonial power — it reproduces it, by offering Indigenous Peoples narrow concessions of acknowledgement in place of an actual redistribution of land and authority. Recognition, in Coulthard's account, isn't a version of threshold one — it's what a system offers instead of crossing it, fluently enough that the gap can be sustained indefinitely without ever being named as a refusal. What I'm describing at the scale of a single commissioned report, Coulthard is describing at the scale of the settler state. Same gap, different altitude.
Stated goals versus operating goals
Donella Meadows [4], whose systems thinking translates cleanly for institutional audiences, makes a claim that reframes this whole pattern: a system's real purpose is revealed by what it does, not by what it says. Not the mission statement. The behaviour.
Applied here: an institution's stated goal is cultural safety. Its operating goal — the one you can actually read off what gets resourced, protected, and allowed to proceed — is the preservation of institutional control and legitimacy. This is not hypocrisy in the moral sense. It is a system accurately, efficiently pursuing its real goal, while the stated goal performs a separate function, covering the system's exterior so it continues to look aligned with the values it has publicly claimed.
This is the same logic that hollows out a Reconciliation Action Plan (I agree with Prof Marcia Langton and other leaders who declared ‘reconciliation is dead’ after the 2023 referendum). A public commitment costs the system nothing to make and nothing to break, because the system was never optimising for the outcome the RAP names. It was optimising for the appearance of alignment — which is a different goal entirely, and one the system meets in full every time it publishes the document.
Sara Ahmed [5] has a precise term for this: non-performativity. She argues that institutional speech acts declaring a commitment to racial equality don't bring about the effects they name — the statement itself becomes the achievement, standing in for the change it claims to describe. A cultural safety strategy, a RAP, a public commitment to an Indigenous-led solution: each is a speech act doing exactly the work Ahmed identifies. It doesn't fail to produce change. It was never built to. Producing the document is what it was built to do.
Delay, and where institutions choose to act
Meadows treats delay inside a feedback loop as one of the most common reasons systems fail to self-correct — a system that takes too long to respond to information about its own impact simply doesn't respond to it, and the loop breaks not through refusal but through elapsed time. Delay is not neutral: whoever controls its length controls whether the system is ever forced to answer for what it's been told. This is the systems-level description of the thing I most want named: no one ever has to say no. A refusal is a decision, and decisions are attributable. A delay is just time passing, and time passing has no author.
Meadows also ranks intervention points by how much power they have to change a system's behaviour. Near the bottom: adjusting a parameter — a new committee, a round of consultation, a revised timeline. Near the top: changing who holds the rules, or changing the system's actual goal. Institutions facing Indigenous-led solutions overwhelmingly intervene at the bottom of that hierarchy — not as failed attempts at the harder change, but as moves precisely engineered to avoid it. Another socialisation round generates visible activity, which serves the operating goal of appearing responsive while never approaching the real leverage point: who holds the power to decide.
Part Two: How This Shows Up
Once you can see the system, the behaviours stop looking like a random assortment of frustrating habits and start looking like a predictable set of low-leverage interventions, all doing the same job — protecting the operating goal from ever meeting the stated one.
Endless "socialisation." The work keeps being shown to more internal stakeholders, and it forever needs "further consultation" before it can move. Consultation becomes the destination, not a step toward one.
The governance loop. It needs to go to the committee, then the next committee, then be "aligned" with a strategy that hasn't been finalised yet. Each loop is individually reasonable. Together, they're infinite.
Quiet reprioritisation. Nothing is cancelled. It just stops appearing on anyone's agenda. No decision was made — which means no one is accountable for the fact that it died.
The compliment that closes the file. The work gets called groundbreaking, important, exactly what's needed — and the praise itself starts functioning as the response. There's nothing left to actually resource.
Waiting for the right sponsor. The work is ready but needs an executive champion who never quite materialises, so it sits fully formed while no one spends the capital to move it.
Every one of these is a parameter-level intervention in Meadows' sense. None of them touch the rule that actually governs the outcome: who has the authority to decide this moves forward, and whether the institution's real goal permits that decision to be made.
The purchase, and what it costs
I think of the moment of commissioning as the point where extraction and commitment become almost indistinguishable. The institution acquires the labour, the intellectual work, the community-designed solution — and retains complete discretion over whether any of it is ever implemented. The power asymmetry doesn't end at the contract. It's built into everything that happens after delivery, and the person who built the solution has no say in it.
I write this as someone now on the other side of that transaction. I, like many of you, have lived experience of what it costs to hold this pattern from inside institutions. I now offer the same kind of solutions as a consultant, to the same kind of institutions — and I feel the stakes of this differently now, because the labour on the shelf could be mine.
This is what makes the delay a slow torture rather than a single wound. There is no moment of rejection to grieve and move past. There is only the ongoing, accumulating experience of watching something built with care, built to work, sit unused — while the system it was meant to change continues exactly as it was designed to.
Chelsea Watego [6] names this directly. In Another Day in the Colony, she refuses to treat bureaucracy and the academic report as neutral instruments — she names the violence that bureaucratic process and the endless production of reports enacts on Indigenous Peoples, precisely because the report and the process are so often mistaken for progress itself. The shelf isn't a passive storage space where good work waits politely for its turn. It's an active site where harm continues to be done, under the cover of process that looks, to everyone outside it, like nothing is happening at all.
Naming it as resistance
Delay is not a process failure to be patiently endured. It is how a system defends its actual goal without anyone inside it having to admit they're defending it. Solutions designed by community are shelved not because they don't work, but because they work — because implementing them fully would require the system to act against its own operating goal of retained control.
This is not a story about slow bureaucracy. It's a system, functioning exactly as designed, wearing the mask of process.
Responding at the level that matters
If low-leverage interventions are how institutions protect the delay, then the response worth prioritising is whatever moves the conversation toward the leverage points institutions are structurally avoiding: who holds the decision, and what the system's real goal is being asked to do.
Name the mechanism in real time, precisely, not accusingly. "This sounds like it needs further socialisation before we can move" can be answered with: what decision, by whom, by when, would count as moving it forward? Loops survive without anyone asking for one.
Require a decision-owner, not a process. "This needs to align with the strategy" is answerable with: who owns that alignment, and when will it happen? A named person with a date turns a parameter-level delay into an accountable, higher-leverage line item.
Contract for outcomes, not delivery. A completed report is not the deliverable — implementation milestones are. This is the single highest-leverage move available at the point of commissioning, because it changes the rule the system is operating under before the work is ever handed over.
Document the pattern as it happens. Not for confrontation — for evidence. When an institution says "we've always been committed to this," a dated record of loops and reprioritisations turns a feeling into a fact, and makes the delay's authorship visible.
Know your walk-away point, in advance. Institutions rely on Indigenous experts staying in the relationship indefinitely, hoping the next meeting is the one that moves it. Naming what "this isn't going to happen" looks like, before you're inside the fog, protects you from the delay becoming permanent.
Name it collectively, not just privately. A pattern one person names can be dismissed as one relationship gone wrong. A pattern multiple practitioners independently recognise, across institutions that have never spoken to each other, is proof the pattern is systemic rather than personal — which is itself a higher-leverage form of naming than any single account can achieve alone.
If you have felt this — watched something you built sit on a shelf while the system it was meant to fix carried on unchanged — I want you to know it wasn't a failure of the work, or of you. It was the system succeeding at exactly what it was built to do. That is worth naming. At the level where it actually operates, and together.
References
Grey Eagle, J. (2024). Indigenous Systems Thinking Vol 1. Indigenous Futures OS.
Fuller, J. (2026, June 8). The Blueprint: How health regulatory bodies can move from cultural safety commitment to structural transformation. Indigenous Regulatory Practice. https://doi.org/10.5281/zenodo.20586944
Coulthard, G. (2014). Red Skin, White Masks: Rejecting the Colonial Politics of Recognition. University of Minnesota Press.
Meadows, D. H. (2008). Thinking in Systems: A Primer (D. Wright, Ed.). Chelsea Green Publishing.
Ahmed, S. (2012). On Being Included: Racism and Diversity in Institutional Life. Duke University Press.
Watego, C. (2021). Another Day in the Colony. University of Queensland Press.
