The case for shared & end-to-end policy infrastructure

This post was written to follow The case for adaptive and end-to-end policy management, which explored the challenges and opportunities for reforming how we design, delivery, manage and continuously improve policies. This article explores the idea of “policy infrastructure” and why a rethink is needed to enable end-to-end policy management with impact monitoring and policy intent optimisation 🙂 I want to quickly acknowledge all the people who are contributing to this work, especially the folk involved in the Intended and Unintended Impact of Social Policy research project which is worth keeping an eye on 🙂

What is Policy Infrastructure? 

‘Policy infrastructure’ isn’t a term that’s often used in government, and yet we use and rely upon policy infrastructure every day. Policy infrastructure includes the data, tools and platforms that help us to analyse, design, model, implement, iterate, monitor and report on policies and policy interventions, throughout the entire policy lifecycle. Policy infrastructure necessarily includes an enormous range of software, data and platforms, because any one tool that tries to do it all never works 🙂 

Policy infrastructure is used to support both the design and development of new policies, as well as the delivery, ongoing management and evaluation of policy interventions. If we are to include all types of policies (constitution, legislation, regulation, Government objectives, operational requirements, department rules, whole of government requirements, etc), then there is a large and complex canvas of goals, success metrics, rules, requirements, eligibility criteria, formulae and requirements that need to be reflected in the policy infrastructure, relied upon by many. In the age of digitally-enabled governments, the scope of policy infrastructure also includes digital policy delivery and policy as code.

Unfortunately, there is currently no consistent or end-to-end approach to policy infrastructure – policy is created, implemented, measured, and amended by different actors, often working in isolation from each other. This inconsistency means there is no visibility of the whole policy journey by anyone involved, and a significant air gap between how policy is represented in modeling tools, and how policy is represented in the real world systems of service delivery government departments or regulated entities. This also creates a significant gap between the predicted impact policies are expected to have, and the broader impacts they have in reality. No modeling is perfect, and unexpected conflicts or variables will emerge as policy is implemented in the real world, in real time. For instance, social security and taxation legislation is extensively modeled in some policy agencies for the purpose of reform and budget analysis, but the same legislation is implemented separately (and sometimes differently) in delivery departments, where new variables exist such as system constraints, integration with other policy domains, operational rules and, of course, the intersection of cross-jurisdictional policies. Without access to the insights of the people tasked to deliver policy, policy makers and legislative/regulatory drafters may be unaware of the risks or conflicts, and unable to build in mitigations. In any case, when unintended conflicts or impacts inevitably emerge, there are limited ways to influence or iterate policy design.

Policy impact and outcomes are often not consistently measured or monitored across interventions. For instance, policy or evaluation teams might use administrative data to analyse policy impacts at a point in time, but delivery teams tend to monitor for system performance and customer experience. Imagine if all our services also enabled real time measurement of policy outcomes and broader quality of life or environmental impacts? It is possible to have a policy intervention like a public service or grant program might be considered successful in delivery (efficient, good user feedback, etc) that is simultaneously having an inverse policy impact, or creating unintended harms. So measuring and monitoring for both policy and human impact is a critical next step to build into policy infrastructure.

There is also no easy or accessible way to test your implementation against the authoritative policy or policies. No reference implementation of policy. No test suite (for example, a person/family with these characteristics should get these services, or a business with those characteristics has those obligations, etc).

The final challenge in this space is the lack of shared or common policy infrastructure, because it exacerbates interpretation confusion and mutual incomprehension between policy design and policy delivery. The diagram below presents a high level view of the current state challenge of fragmented policy infrastructure, and contrasts it with the idea of shared policy infrastructure.

CC-BY: Pia Andrews, 2023

All actors involved in a given policy domain (including all relevant policy interventions) would ideally have access to the same shared policy infrastructure, the same digital representation of policy (“policy twins”), the same modeling and monitoring tools, feedback loops and perhaps even a shared “policy backlog”. Perhaps policy infrastructure could be shared across policy domains, or even open to the public, to facilitate transparency, alternative modeling, and testing policy options or proposed reforms in a wide variety of contexts to help identify potential or unintended consequences, and to maximise intended policy outcomes.

Policy Twins

Although not all policies are legislation or regulation, almost all government services and programs draw upon some legislation/regulation combined with myriad operational policies. The many and varied interpretations of these building blocks of public administration can make it hard to understand which rules are authoritative and which are operational. If we had reference implementations of policy as code (imagine we had api.legislation.gov.au), then we could remove the interpretation gap and have a better chance at identifying and remediating unintended policy issues as they arise.

A Policy Twin is simply the policy equivalent of a “Digital Twin”. Digital Twins provide a digital representation of spatial information like buildings, roads, water and gas pipes, which is used to model town planning, environmental impacts or other spatially driven analyses. A Policy Twin could be as simple as a digital representation of a policy, but could include legislation as code, relevant data (admin data, policy measures, lead and tail indicators, etc), modeling tools, impact monitoring and more. All the things you have seen emerge in the “Digital Twin” space, are possible with Policy Twins, and in fact some Digital Twins have already started including policy as code, such as the inclusion of resource management regulations in the Wellington City Council digital twin to model and display the impacts of changes to the building code. Here is a great article about how to turn building regulations into a Policy Twin. Inspiring stuff! 

The “Rules as Code” movement to has been growing over the past decade, including the use of policy as code to enable test-driven legislative and regulatory reform. Please see more on “Rules as Code” and the “Better Rules” approach to drafting in this explainer deck. 

Recently in Australia there was a VERY exciting announcement from GovCMS where they are now offering a “Rules as Code” enterprise capability to all GovCMS customers, providing greater ease of creating policy twins 🙂

Engaging with community infrastructure

Many communities run their own data, analysis and modeling infrastructure. Whether a not for profit NGO, an Indigenous/First Nations community or a town, the insights and intelligence that could help shape and inform policy options and change are worth understanding and building into a policy infrastructure model that is capable of respectfully interacting with such systems. This makes it necessary to consider federated architectural design, and ways of sharing insights and patterns across systems without sharing raw data. The progress made in verifiable claims/credentials, as well as in confidentialised computing provide some excellent opportunities for communities and governments to co-create meaningful and empowering policy twins. It also makes sense for government policy infrastructure to be available to communities for them to model, explore and test policy reform options.

Reverse engineering a future state policy journey

Proposals for reforming how policy is done are often, understandably, met with concerns at whether change would “slow things down”, but if we had a more end to end approach with policies designed for easy implementation, then the total time to realise policy intent could be dramatically shorter, even if it means a little more time up front. So a useful tactic might be to consider the whole “policy journey map”, like we do with user journey mapping.

What if we were to design a better, faster and end to end “policy journey map” to identify the necessary ingredients for modern, shared policy infrastructure? Below is an attempt intended to stimulate discussion and collaboration, as this is an emerging area that needs collective exploration with cross-disciplinary participation. 

Imagine for instance, being able to rapidly develop new legislation/regulation with reference implementations circulated for consultation and testing prior to being enacted by parliament (with the usual democratic rigour) and then available as code that same moment for rapid & consistent implementation by all the relevant policy consumers. It is possible, but only through transforming the policy/service continuum. When we make the rules of government authoritatively consumable by software, we dramatically improve the speed & consistency of delivery, with better policy outcomes and compliance.

Below is a high level “policy user journey” contrasting the current state approach to a more streamlined, test-driven and multi-disciplinary approach, which would dramatically reduce the time to impact.

CC-BY: Pia Andrews, 2023

With the high level journey map above, we can then explore and propose the shared and common policy infrastructure we need to support the journey end to end, as per below.

CC-BY: Pia Andrews, 2023

The very early-thinking, draft model above includes the following elements, aligned to the broad temporal phases of policy delivery:

To support test-driven policy ideation (pink):

• Public engagement tools to explore, co-design & test policy options, both initially (new policies) & ongoing (continuous improvement to policies and policy interventions).
• Linked and integrated admin data for research, policy modelling & patterns monitoring, best hosted by an independent, highly trusted entity, like the ABS.
• Case law and gazettes as a utility to use for analysis and to test new ideas.
• Publicly available modeling tools for testing and exploring policy change.

To support test-driven policy options design, development & drafting (purple):

• Consistently applied Human Impact Measurement Framework used across government, including for new policy proposals and for monitoring.
• Public repository to share policy tools, government models, measurement frameworks, synthetic population data, etc.

To support the Parliamentary processes, publishing and visibility (aqua):

• A linked data representation of the administrative orders to automate reporting, accountability, auditing, security, access & to streamline MOGs.
• Publicly available Policy as code (intended outcomes, legislation, models, defined target group) available at api.legislation.gov.au
• Policy catalogue where all operational and Government policies can be discovered, along with measures and transparent reporting of progress. 

To support policy intervention design & implementation (delivery) (green):

• A “Citizen’s ledger” to record all decisions with traceable explanations, for auditing & citizen access
• Policy test suite to validate legality of system outputs in gov services & regulated entities.

To support policy compliance, iteration & improvement over time (yellow):

• Open Feedback loops for public and staff about policies & services, to drive continuous improvement and to identify and mitigate harm.
• Continuous monitoring of policy & human impacts, including dark patterns & quality of life indicators, alongside usual systems monitoring, to ensure adverse impacts are identified early and often.
• Escalation and policy iteration mechanisms to ensure issues detected are acted upon at portfolio and whole of gov levels.

A shift to “CI/CD Policy”?

It’s clear when you start trying to imagine a more collaborative, adaptive, humane, iterative and test driven approach to policy management, that a lot of the techniques and methods from product management, CI/CD (Continuous Integration / Continuous Development) pipelines, service design and agile become useful. So why not reuse some of the infrastructure, tools, methods and platforms that we have adopted in service reforms over the last decade to help modernise policy delivery?

We could have CI/CD policy pipelines, policy feedback loops, product management for policy, policy monitoring and measurement tools, policy escalation frameworks, policy test suites, policy twins, and public policy engagement/codesign platforms. Perhaps each policy would have a policy manager who owns the end to end outcome realisation (rather than the current baton passing from design to delivery teams), and perhaps each policy intervention could have its own “policy product owner” who owns the delivery of that intervention, but works in concert with other interventions to the policy manager to make sure interventions are effective, complementary and continuously adapting to change and impact? We don’t need to start from scratch here, but we do need to design a good policy journey, so that we can meaningfully leverage what is available, but also identify where there are gaps to fill. 

What do you think?

What do you see as the opportunities and challenges for policy infrastructure? What would your ideal policy journey map look like? Which portfolios would have the right mandate and systemic motivations to run which parts of the concept model above (note, not which department is best functionally/capabilities placed, but which department is best aligned/motivated 🙂)? What other tools, data and platforms would you include? Do you have any examples to share? 

Please share your thoughts and any examples and let’s all take a strategic and proactive approach to modernising our policy infrastructure, so we can be more adaptive and effective in delivering policy and public outcomes.