Build the rail - save the Snail

Build the Rail - Policy Challenges - A report by Dan Davies

Reference

Build the rail! Save the snails! — Labour Together

Can you provide a synopsis of the build the rail save the snail report

Gemini said

The report “Build the rail! Save the snails!” by Dan Davies (published by Labour Together in January 2026) provides a systemic critique of the UK’s infrastructure planning system and proposes a shift from an adversarial to a collaborative model.

The Core Problem: Defensive Over-Mitigation

The report argues that UK infrastructure projects cost significantly more and take longer in pre-construction than European equivalents. This is attributed to a system that treats projects as “guilty until proven innocent”.

• Adversarial Default: The UK system relies on an adversarial process between interested parties, which incentivizes pre-emptive risk aversion.

• Defensive Planning: Similar to “defensive medicine,” developers and authorities over-mitigate every potential objection to avoid the tiny probability of total project collapse via judicial review.

• The “Problem Factory”: The UK’s large professional services sector has an economic interest in “manufacturing” objections (such as snails or bats as pretexts) to sell mitigation solutions, creating an inefficient “guessing game” for developers.

Drivers of Risk Aversion

The report identifies several features unique to the British system that stifle delivery:

• Fog of War: Siloed and summarized information makes it difficult for decision-makers to access necessary technical details.

• Asymmetry of Reward: Officials face high career risk from losing a judicial review but face little penalty for a project failing to be delivered.

• All-or-Nothing Events: Development consent is often binary; if a project is refused, years of effort are wasted, forcing developers to anticipate every conceivable objection early on.

• Capacity Squeeze: Examining authorities are often small teams that lack the broad scientific and environmental expertise needed for complex projects.

Case Studies: Sussex Snails vs. Hinckley Rail

• The Success (Sussex): In 2021, the endangered Ramshorn Whirlpool Snail habitat caused a four-year planning impasse in Sussex. The logjam was broken in 2025 by the DEFRA Water Delivery Task Force, which used a multidisciplinary, collaborative approach to reach a win-win compromise that protected the habitat while allowing 20,000 homes to proceed.

• The Failure (Hinckley): The Hinckley Rail Freight Interchange was refused in 2025 because two specific safety and noise issues were raised too late for the developer to correct efficiently. This illustrates the failure of a system with long feedback cycles and no mechanism to prioritize material issues early.

The Proposed Solution: The Infrastructure Directorate

The report proposes replacing the Planning Inspectorate’s infrastructure role with a well-resourced Infrastructure Directorate (ID) with a statutory mandate to get projects built quickly while upholding protections.

• Early Prioritization: The ID would issue a “Key Issues Report” early in the process to identify which objections are material and which are irrelevant or political disagreements.

• Collaborative Problem-Solving: Instead of adjudicating objections, the ID would lead project-specific teams (including secondees from regulators and industry) to solve technical problems in iterative cycles.

• Statutory Statement of Relevance: The final decision would include an explicit record of which mitigations were considered unnecessary, making judicial reviews harder for “hopeless” or cynical challenges.

Conclusion: The “Free Lunch”

The author concludes that a “genuine free lunch” is available: by rearranging existing people and resources to work cooperatively rather than adversarially, the UK can protect the environment and build essential infrastructure faster and cheaper. The report asserts that the current adversarial system is a default adaptation to an Anglosphere economy, not a legal requirement, and that “it doesn’t have to be like this”.

QSet Recommendations from STPrism

Can you suggest ways in which ideas and practices from the QSet framework can help with the challenges in 'build the rail'.

Gemini said

Based on the provided sources, the “Build the rail! Save the snails!” report describes a classic “wicked problem”—a situation where identifying the problem is difficult, and every attempt at a solution counts significantly and cannot be undone.

The QSet framework offers several systemic tools to address the specific dysfunctions (such as the “Problem Factory” and “Risk-Surface reasoning”) identified in the UK infrastructure planning system.

1. Navigating Uncertainty: The “Italian Flag” Risk Model

The report argues that the UK system generates “unquantifiable, downside-only risk surfaces” where rational actors overspend to avoid tiny probabilities of project collapse.

• The QSet Solution: Apply the “Italian Flag” Model used by “The Other Group” (TOG). Instead of a binary “Guilty/Innocent” or “Pass/Fail” logic, this framework sorts evidence into three zones: Green (settled evidence of value), Red (settled evidence of failure or hard constraints), and White (the “White Space” of uncertainty or entropy).

• Application: The proposed Key Issues Report would function as a “trip to the White Space.” Its role is to perform the “work” required to move issues from White to either Green (identifying workable mitigations) or Red (explicitly discounting irrelevant objections).

2. From “Problem Factory” to “Webs of Causality”

The report notes that in an adversarial system, constraints are “manufactured, not found,” with environmental protections often used as a cynical pretext.

• The QSet Solution: Move from Direct Causation thinking (“The snail stops the rail”) to Webs of Causality.

• Application: Using DSRP Theory (Distinctions, Systems, Relationships, Perspectives), planners can deconstruct an objection to see if it is a “secondary” property of a different underlying goal. This allows the “Infrastructure Directorate” to identify if an environmental objection is actually a Perspective issue (NIMBYism) disguised as a System issue (ecological protection).

3. Resolving the “Tree of Disappearing Knowledge”

The report describes an information bottleneck where data is degraded as it crosses organisational boundaries between specialists, developers, and authorities.

• The QSet Solution: Utilize “Boundary Objects” and “Trading Zones”.

• Application: The proposed multi-disciplinary project teams would act as a “Trading Zone” where different professional cadres (ecologists, lawyers, engineers) negotiate constraints in real-time. By using a “Shared Environmental Impact Assessment” as a Boundary Object, information remains “interlaced” rather than siloed.

4. Seeking “Accommodation” Over “Consensus”

UK planning currently acts as a quasi-judicial arbiter, which the report suggests is not well-adapted to technical questions of public benefit.

• The QSet Solution: Shift the goal of consultation from “Consensus” to “Accommodation”.

• Application: Soft Systems Methodology (SSM) teaches that total agreement on values is rare. Success lies in finding an “accommodation”—a version of the project that conflicting worldviews can “live with”. The DEFRA Water Delivery Task Force success in Sussex is a perfect example of SSM in practice: finding a “sensible risk-based compromise” that allowed building to resume while protecting habitats.

5. Precision Intervention: “Negative Explanation”

Developers currently spend years anticipating every possible objection because they don’t know which one might be fatal.

• The QSet Solution: Use “Negative Explanation” and “Minimalist Intervention”.

• Application: Instead of asking “What do we need to prove to build this?”, ask: “What specifically is preventing this project from being consented right now?“. This “filtering” approach (rather than modeling the whole world) aligns with the report’s suggestion to identify the “genuinely binding constraints” early and dismiss “hypothetical pseudo-problems”.

Summary: Systems-Age Transformation

The report concludes that the UK has slipped into its current adversarial system by default and that “it doesn’t have to be like this”. QSet thinkers like Russell Ackoff would describe this as a shift from Machine-Age analysis (breaking things down) to Systems-Age synthesis (improving the interactions between the parts).

Planning Challenge	QSet Concept	Practical Shift
Defensive Over-mitigation	Italian Flag Model	Explicitly label what is “settled” vs. “uncertain.”
Information Degradation	Trading Zones	Move capacity inside the project team via secondments.
Cynical Objections	Boundary Critique	Ask: “Whose interest is served by this definition of risk?”
Stalemate/Impasse	Accommodation	Find a path all parties can “live with,” not a total consensus.
Late Feedback	Negative Explanation	Identify the “lynch-pin” constraints in the first 3 months.

Using the STPrism to get the recommendations from John Seddon

Can you suggest ways in which ideas and practices from the john seddon framework can help with the challenges in build+the+rail

Gemini said

Applying the John Seddon (Vanguard Method) framework to the challenges identified in “Build the rail! Save the snails!” involves a fundamental shift from a “Command and Control” mindset to a systems-oriented “Outside-In” approach.

The core challenges of defensive over-mitigation, late feedback, and the “problem factory” in UK planning can be addressed through the following Seddon-inspired shifts:

1. Reframing the System’s Purpose (Outside-In)

The report argues that the UK system currently acts as a “neutral arbiter” in an adversarial game. Seddon’s methodology starts by defining purpose from the customer’s point of view.

• The Shift: Instead of defining the purpose as “adjudicating objections,” the Infrastructure Directorate (ID) should define it as “getting designated infrastructure built at pace while upholding protections”.

• Action: Measures should be derived from this purpose (e.g., end-to-end time from designation to construction) rather than administrative “milestones” or the absence of judicial reviews.

2. Eliminating “Failure Demand”

Seddon distinguishes between Value Demand (what the system exists to do) and Failure Demand (work created by failing to do something right for the customer).

• The Challenge: The “problem factory”—where professional services manufacture cynical objections to sell mitigation solutions—is a form of failure demand.

• The Solution: By issuing an early Key Issues Report (as proposed in the report), the system “absorbs variety” early. This provides the developer with “knowledge” of what actually matters, stopping the “guessing game” that fuels failure demand.

3. Expertise at the Point of Transaction

A key Seddon principle for handling complexity (high variety) is to put expertise at the point where work is done.

• The Challenge: The report notes a “capacity squeeze” where small teams of inspectors lack the broad expertise to handle complex environmental/technical variety.

• The Solution: The proposed multi-disciplinary project teams (including secondees from regulators and industry) put the “inspectors” inside the design process. This allows the system to respond flexibly to unique environmental constraints (like the Sussex snails) in real-time rather than through formal, episodic feedback loops.

4. Changing Management Thinking (System Conditions)

Seddon argues that 95% of performance issues are in the system, not the people, and the root cause is management thinking.

• The Condition: The “asymmetry of reward” (fear of judicial review vs. no penalty for non-delivery) is a system condition that forces defensive over-mitigation.

• The Shift: Leaders must “unlearn” the assumption that being a “neutral arbiter” is the only lawful path. The ID must change the system conditions—such as introducing the Statutory Statement of Relevance—to make the “right thing” (building) easier than the “wrong thing” (defensive stalling).

5. Managing “Economy of Flow”

In Seddon’s view, costs are contained in the flow of work, not in “economies of scale”.

• The Challenge: The Hinckley Rail failure illustrates a broken flow; show-stopping issues were raised too late for the developer to correct them.

• The Solution: By collapsing organizational boundaries and moving capacity inside the ID, the system eliminates the “tree of disappearing knowledge”. This creates a continuous flow of information between developers and regulators, drastically reducing the pre-construction “waste” of time and money.

Summary Table: Vanguard Method vs. UK Planning

UK Planning Challenge	Seddon Concept	Practical Action
Manufactured Objections	Failure Demand	Dismiss “cynical pseudo-problems” in the first 3 months.
Late/Formal Feedback	Economy of Flow	Use collaborative “problem-solving cycles” instead of adjudication.
Lack of Technical Depth	Point-of-Work Expertise	Embed ecologists and regulators directly in project teams.
Risk Aversion	System Conditions	Use “Statements of Relevance” to shield builders from “hopeless” reviews.