We often take visibility as a sign of truth. The things we notice first become the things we believe are real, important or working. They’re the ones that get measured, resourced and scaled. But some of the most meaningful shifts happen long before they become visible—quietly, internally and without clear markers. Before a student raises their hand for the first time, something has already changed. Not in posture or volume, but in what they believe about their place in the room. Confidence begins to outweigh doubt. A question becomes worth the risk of asking. That shift, invisible to most systems, is often where real learning begins.
These are the shifts that shape lives and outcomes, but they rarely register on dashboards or funding reports. Not because they’re undocumented—many educators observe and reflect on them with care—but because the systems around them often prioritise what is standardised over what is significant. What we know how to track begins to define what we value. And what we value begins to shape what we build.
Systems are built to recognise. They determine what counts, where attention flows and ultimately, what deserves to be resourced, rewarded or repeated. But not everything worth seeing is visible at first. And not everything that’s visible is worth building on.
This tension—between what matters and what’s measurable—quietly shapes the direction of organisations, policies and entire sectors. In product work, too, we often see priorities shaped by what fits into dashboards or investor updates—momentum becomes something that has to be seen to be believed. What we see becomes what we fund. What we fund becomes what we scale. And what we scale becomes what we believe is working. A framework gets created, a metric defined, a dashboard launched. Before long, the measure becomes the mandate. The signals we choose to track begin to shape not just how success is reported, but how it is pursued.
Learning is one concrete illustration. Across institutions—schools, employers, governments—there is a growing sophistication in how learning is tracked. Alongside completions and attendance, many educators collect observations, reflections and qualitative indicators. But even then, broader systems tend to privilege the visible and the countable. This is true in product development as well, where user activity can easily overshadow user value, and where the loudest feedback loops—not always the most insightful ones—can steer entire backlogs. And in that tilt towards legibility, we risk overlooking deeper shifts: a student rethinking a bias, an employee choosing a harder, more ethical route, a learner asking a better question instead of giving the “right” answer. These are not minor. They are often the earliest signs that something meaningful is taking hold.
The issue isn’t that measurement is flawed. Metrics help us make sense of complexity. But problems arise when visibility is mistaken for value—when we assume that what is easiest to quantify is what matters most. That assumption can subtly reshape how programmes are designed, how people are evaluated and how impact is defined.
This pattern shows up far beyond education. In public policy, it is easier to report activity than to substantiate impact. A programme may reach 5,000 people, but what changed as a result? In international development, funding is often tied to outputs—how many sessions were held, how many materials distributed—rather than long-term shifts like trust, confidence or collective efficacy. These output measures aren’t inherently wrong; they are simply incomplete. But over time, incomplete indicators can become distorted proxies for success.
Some systems have begun to evolve. Education researcher John Hattie’s concept of “visible learning” highlights how clarity—of goals, feedback and expectations—improves outcomes. Not by monitoring everything, but by illuminating the path forward. In another context, the platform Ground News developed a feature called “Blindspot” that shows users what their usual sources are not covering. It’s not about adding more noise, but about surfacing absences—revealing the blind spots in our attention, and what they might be costing us.
Visibility, in both of these cases, becomes a form of design. It shapes what we notice, value and act on. Product teams, like civic movements or policy actors, must consider not only what is surfaced—but what remains hidden. And this is something social movements have long understood.
The #NiUnaMenos movement in Latin America didn’t emerge because of newly discovered data. It emerged because familiar pain was reframed—from personal tragedy to public pattern. Through stories, protests and collective language, it rendered gender-based violence impossible to ignore. That shift in visibility was transformative. What had once been treated as private became political. And once it was visible, it was harder to dismiss.
In Indonesia, the civic hashtag #KawalPutusanMK gained traction in response to controversial constitutional court rulings. It wasn’t just a burst of public reaction—it became a civic method. Citizens tracked court decisions, decoded legal texts and built participatory pressure through visibility. It demonstrated how visibility can be leveraged not just for awareness, but for structural accountability.
But visibility isn’t always a force for depth or equity. In attention economies, what gets surfaced is often what provokes, polarises or performs. Algorithms reward what engages, not what informs. Media cycles elevate what can be sensationalised, not necessarily what most needs to be solved. Visibility, in this sense, can distort as much as it reveals. It can create the illusion that what is seen most is what matters most—even when what is loudest is not what is truest.
The risk is that we end up with systems that optimise for what is already legible. We look for evidence of success where we’ve always looked—activity, output, completion—while missing the slower, quieter, harder-to-capture shifts that actually signal change. Shifts in belief. In trust. In how someone sees their place in the world.
These changes often occur before anything measurable happens. They emerge in a pause, in a reconsidered reaction, in a question asked from a new angle. And if our systems aren’t designed to recognise those moments—or to take them seriously—we may end up designing them out entirely. Not because they’re unimportant, but because we never trained our attention to see them.
Visibility is not a surface concern. It is structural. It shapes how knowledge is validated, how performance is evaluated and how change is recognised. In product contexts, it influences how outcomes are framed, how priorities get roadmap space and how strategy is sold internally. If we want better outcomes—in education, in workforce development, in governance—we need systems that are capable of seeing more.
And that begins by asking: what are we paying attention to? Who decided that’s what matters? And what might we be missing when we only build around what we already know how to track?
As systems thinker Donella Meadows wrote, the most powerful place to intervene in a system is not the metrics or the feedback loops, but the paradigm—the deep assumptions out of which the system arises. If we want to change what gets built, we have to examine what gets seen. Because what we choose to notice becomes what we choose to act on.
And what gets seen, gets built.
References:
· Hattie, J. & Clarke, S. (2018). Visible Learning: Feedback. Routledge.
· Ground News Blindspot: https://ground.news/blindspot
· #NiUnaMenos Movement: https://en.wikipedia.org/wiki/Ni_una_menos
· #KawalPutusanMK: https://twitter.com/hashtag/kawalputusanmk
· Meadows, D. (1999). Leverage Points: Places to Intervene in a System. The Sustainability Institute