System literacy is the ability to understand the rules, data, dependencies, decisions and governance behind the digital systems we use — not simply how to operate their interfaces.
That distinction is becoming increasingly important because digital systems now mediate much of ordinary life. We use them to access education, banking, healthcare, public services and work. They influence what information reaches us, how applications are processed, which choices are available and, increasingly, which decisions are made or recommended by automated systems.
Most digital-literacy efforts have understandably focused on helping people use technology effectively and safely. We learn how to access platforms, create content, protect accounts, evaluate information and increasingly work with AI. Those skills remain essential. But they do not necessarily tell us why a system works the way it does, who designed its rules, where its data travels, who can change it or what happens when we disagree with its decisions.
That is the gap we mean when we talk about system literacy.
What is system literacy?
System literacy means being able to look beyond what appears on the screen and understand enough of the structure underneath it to ask meaningful questions about how the system works.
A school portal, for example, is not simply a collection of pages and buttons. It contains decisions about who can see information, which actions different users are allowed to perform, how students are classified, where data is stored and which other systems it exchanges information with.
A public-service form contains similar choices. A mandatory field is not merely a design feature. It represents a rule about what information the institution considers necessary. A dropdown menu establishes categories into which people must fit. An automated workflow may determine which applications move first, which require additional checks and which are sent somewhere else.
The interface is therefore only the visible part of a much larger system.
At REDefine, we look at system literacy through several connected questions: What rules does the system contain? What data does it depend on? What other systems or suppliers does it rely on? Who governs it? And what practical ability do people have to question, change or leave it?
These questions do not require everyone to become a programmer. They require people to understand enough of the architecture around them to exercise judgement and agency.
Why is digital literacy no longer enough?
Digital literacy usually helps us become competent users. System literacy asks whether competent users can also understand the environment in which they are acting.
The difference becomes clearer when something goes wrong.
Imagine that an online application refuses to continue because your situation does not match any available category. Digital literacy may help you navigate the platform correctly. System literacy leads to a different set of questions: who created those categories, whether they reflect the actual policy or legislation, whether somebody can override them, and whether the software has quietly narrowed the choices available to both the citizen and the institution.
This is why digital systems cannot be understood only as technical objects. They are also organisational and civic structures.
A form is not a law, but it can determine how a law meets a person.
The same is true of recommendation systems, education platforms, workplace software, digital identity systems and AI-assisted services. Their rules often become part of how institutions interact with people, even when those rules were originally introduced as technical configurations.
How is system literacy different from AI literacy?
AI literacy is becoming an increasingly important part of digital competence, but system literacy asks a wider question.
AI literacy helps people understand how AI systems work, what their limitations are, how to evaluate their outputs and how to use them responsibly. System literacy also asks how the AI system fits into the larger environment around it.
Who decided to introduce it? What data can it access? Which decisions can it influence? Who checks its outputs? Is a human able to override it? What happens when it connects to other organisational systems? Which supplier controls the technology, and how easily could the organisation replace it?
This broader perspective is becoming increasingly relevant as AI makes it easier for people to create automations, workflows and technical solutions without conventional software-development expertise.
That is potentially very useful. It also means we can create systems faster than organisations develop a shared understanding of what those systems actually do.
Why does system literacy matter for citizens?
System literacy is ultimately a question of agency.
When digital systems mediate access to education, employment, welfare, healthcare, information and democratic participation, people need more than the ability to follow the instructions presented on a screen. They also need some capacity to recognise that the instructions themselves were designed by someone and can therefore be questioned.
That does not mean every citizen needs detailed knowledge of databases, APIs or software architecture. It means understanding that digital systems contain choices, that those choices have consequences, and that technological arrangements are not necessarily fixed or inevitable.
This is where system literacy becomes part of civic literacy.
If a platform affects an important part of our lives, we should be able to ask who governs it, what evidence its decisions rely on, what rights we have inside it and what mechanisms exist for challenging mistakes.
Why does system literacy matter for organisations?
The organisational version of the problem is slightly different.
An organisation may have dozens of people who know how to use a critical system while having very few people who understand how the system works as a whole.
IT understands one part. Procurement understands the contract. Programme staff understand the operational workflow. A supplier understands the configuration. Someone in finance knows about an integration. Another colleague remembers why a particular rule was introduced four years ago.
Each person may understand their piece perfectly well.
The problem appears when nobody can reconstruct the whole.
This creates a form of institutional dependency that is easy to miss because the technology may continue working perfectly well. The organisation only discovers the weakness when a supplier changes, a knowledgeable employee leaves, an integration fails, a new regulation arrives or someone finally asks why the system behaves the way it does.
The issue is therefore not simply whether an organisation owns its software or has access to its data. It is whether the organisation retains enough knowledge to understand, govern, change and, if necessary, replace the systems on which it depends.
What does AI change inside organisations?
AI lowers the technical barrier to building.
Employees can now create workflows, automated processes, scripts, data transformations and internal tools much more easily than before. In many cases, that is a genuine improvement. Work that previously required specialist development can be prototyped or automated by the people closest to the problem.
But easier building does not automatically produce better institutional understanding.
An AI-assisted workflow may become important long before anyone formally recognises it as part of the organisation’s infrastructure. A spreadsheet can become a database. A prompt can become a procedure. An automation can become a dependency.
The organisation may therefore become more capable of executing technical tasks while becoming less certain about how those tasks fit together and who remains accountable for them. AI can accelerate execution, but accountability still has to be designed and maintained by people.
How can organisations improve system literacy?
The first step is not another general digital-skills course.
Organisations need to make the knowledge surrounding their systems visible.
That means identifying critical systems, documenting where knowledge about them actually lives, understanding their external dependencies, preserving the reasoning behind consequential decisions and checking whether somebody other than the current expert could reconstruct enough understanding to govern the system if necessary.
It also means treating informal infrastructure seriously. If a colleague manually transfers data between two systems every Friday, that person is effectively performing an integration function whether or not the organisation has ever described it that way.
Some humans are really bad APIs. More importantly, they are also vulnerable ones.
The goal is not perfect documentation of every technical detail. It is institutional intelligibility: enough shared understanding that an organisation can explain what its important systems do, why they work that way, where the dependencies are and what options exist when something needs to change.
System literacy is becoming a civic and organisational capability
The systems around us are becoming easier to operate while the architecture underneath them becomes increasingly complex.
That creates an odd possibility: a society can become more digitally skilled while becoming less capable of understanding the infrastructures on which it depends.
The same can happen to organisations.
System literacy offers another direction. Instead of asking only whether people can use technology, we can ask whether they can see enough of the system to understand its rules, recognise its dependencies, challenge its decisions and participate in changing it.
That is the argument we explore in the latest instalment of The Code Beneath the Floorboards: Who Builds the Builders?
The full article goes further into system knowledge fragmentation, institutional intelligibility, decision lineage, epistemic dependency, AI-driven shadow architecture and reconstruction readiness. For professional readers, it also includes the REDefine System Literacy & Institutional Knowledge Map, a connected workbook for examining where critical system knowledge actually lives and where organisational dependencies may be hiding.
Read the full analysis
Continue with Who Builds the Builders? on the REDefine Substack, where you can read the complete civic and professional analysis, watch the video explainer and access the practical resource.
