The readiness challenge
Every era of extraordinary innovation eventually confronts a simpler challenge: what do we owe the people living inside what we create?
A pattern worth noticing
Maria gets home from work on a Tuesday a little after six. The mailbox has the usual—utility bill, flyer, a letter from the state. She opens the state letter first because those are the ones you can’t ignore.
The sentences are long. The vocabulary is procedural: redetermination, substantiating documentation. The deadline is buried in the third paragraph. She reads it twice. She has thirty days to appeal a decision about her benefits. Eight of those days are already gone, eaten by the mail.
She calls the number at the bottom. Eleven minutes on hold, then the line drops. She calls back; a recorded voice tells her the wait is over an hour and points her to the website. The website has a chatbot. The chatbot offers three links. None of them answer her question. She tries again. Same three links.
A banner says she can resolve this faster by creating an account. She starts to. The form asks for a document number she doesn’t have—because the letter that would have told her to get it was returned as undeliverable months ago. She has a job. She has a kid. She has twenty-two days.
Dinner is on the stove. Her kid is asking her something from the next room and she is half-answering while she tries to find the one number that will let her finish the form. If she misses the deadline, she loses more than a bureaucratic argument. She loses time, money, and stability. The system isn’t just “hard to use.” It is a burden that lands on her body and her evening.
The people who built the system Maria is trying to use are not villains. They are public servants, contractors, administrators, program leads, caseworkers, policy analysts. Many of them came to this work because they care about people like Maria. They inherit tangled statutes, legacy tools, risk, and scrutiny—and they try to do good work inside constraints that are often invisible to the public.
They reduce error rates. They shorten processing times. They pass audits. They meet deadlines set by statute. They respond to oversight findings. They keep the lights on.
And still, the system does what it is doing to Maria tonight.
That gap persists—not from malice, but because the choices that shape lived experience are made too early, too late, in the wrong order, or not at all.
The technology is chosen before the problem is understood.
Sometimes the problem itself is still vague and no one has spoken to the people living with it—leaving compliance requirements more clearly defined than human need.
Sometimes the people implementing a new system become focused on whether it works as designed—not whether it actually meets the needs of the people using it.
By the time many designers and researchers are invited in, much of what will matter to Maria’s Tuesday night has already been set.
Maria’s experience may feel like a problem of forms, technology, or bureaucracy. But the pattern underneath it is older and more familiar than we sometimes realize.
Innovation and The Enlightenment
There’s a story we tell ourselves about innovation, and it’s not entirely wrong. It’s just incomplete.
The 1889 Paris Exposition unveiled the Eiffel Tower—a declaration in iron that the future could be engineered. A few years earlier, the Statue of Liberty had been raised on Bedloe’s Island. Four years later, in Chicago, the World’s Columbian Exposition lit the White City with electricity and turned the first Ferris wheel into the sky.
In the decades that followed, a generation of architects in New York and Chicago raced each other upward—the Flatiron, the Woolworth, the Chrysler, the Empire State—each building briefly the tallest thing humans had ever made. These were shows of prowess. We can do this. Look what we can do.
Much of what was promised came true. The machines got better. The networks got bigger. The scale of what could be produced, transported, calculated, and connected became unrecognizable inside two generations.
Alongside it, something else happened.
The same century that gave the world the Eiffel Tower also gave it the tenement. The ten-hour shift. The factory floor that ground workers down. Neighborhoods laid out for the convenience of production.
The velocity of what we could build outpaced the humanity of what it was like to live inside what we built. For many people, life did not improve. It became something to survive.
It seems to be a risk that follows every era of extraordinary capability: we become fluent in building and less fluent in inhabiting.
It’s not every day you think about Voltaire, but lately, I’ve been struck by how urgently his work argues for what we now call the Enlightenment: that inherited systems should answer to reason, and that human dignity should not be treated as optional. It makes me wonder if we are standing in a similar moment now—building powerful new systems, and needing a renewed insistence that they answer to the people who have to live inside them.
Candide, published in 1759, follows a young man through catastrophe after catastrophe while his tutor insists, each time, that they are living in “the best of all possible worlds.” The joke is cruel because the instinct is familiar: to explain suffering as part of a larger pattern no one can fully see yet, and to ask those living through it to wait for future understanding that might someday make it seem worthwhile.
Voltaire was part of a generation insisting on something both simple and radical: that our systems must answer to the humans inside them. That received authority deserves to be challenged. That dignity is not a favor granted from above. That what humans build owes something back to the humans who have to live within what is built.
We now call that insistence the Enlightenment, but it wasn’t a single moment. It was an argument carried forward—unfinished, contested, reclaimed again and again.
That argument never really ended. It simply reappears whenever societies gain new capabilities and have to decide what responsibility they demand.
The velocity of what we could build outpaced the humanity of what it was like to live inside what we built. For many people, life did not improve. It became something to survive.
Capability and consequence
This moment is another era of extraordinary velocity.
AI. Automation. Platforms. Decisions scaled at speeds no individual judgment can match. The capabilities are real. So is the temptation to celebrate them before asking what it will be like to live inside what they produce.
A colleague and I keep talking about a pattern we notice across our work:
Teams are not always ready to do the work. They might not be aligned on what problem they are solving—or for whom. Modernization can veer into an upgrade of technology rather than an improvement of human experience. Software can be bought (or built) and delivery teams assembled before these critical questions have been answered.
We build quickly toward solutions we’ve designed without the people who will experience them.
At some point—usually late, usually under deadline—someone asks a version of the questions we should have asked at the beginning:
Are we ready?
Ready to make this the new normal?
Ready to make this the experience a person like Maria will rely on?
Readiness is not only technical readiness. It is civic readiness. Human readiness. Ethical readiness. Operational readiness. The readiness to carry the consequences of what we’re building.
If readiness is the question, then the practical challenge becomes how organizations create the conditions to answer it early enough.
Related reading
Read The Policy Implementation Gap for a closer look at what happens when decisions, delivery, and lived experience fall out of alignment.
Enter design
One response is design—not as a step added at the end, but as a way of understanding people, asking better questions, and shaping decisions before they harden into systems.
Three ideas feel especially important here:
1. Design early, and with curiosity
Many organizations still bring research and design into the process downstream:
A usability test right before launch
Interviews meant to confirm a direction already chosen
Research used to reduce risk for a predetermined path
When questions arrive that late, they can unintentionally validate decisions already made rather than create space to reconsider them.
Earlier work creates room for curiosity:
What problem are we trying to solve?
For whom?
What assumptions are we making?
What have we not yet learned?
Asked early, these questions shape everything that follows.
2. Focus on people living inside the systems
Maria’s challenge is not simply a technology problem. It is an experience problem.
People do not encounter systems in isolated moments. They encounter them while caring for children, working jobs, managing uncertainty, and navigating the realities of everyday life.
Design asks organizations to focus attention there: on the people who occupy and live inside the systems being created.
Questions like:
Who are we building this for?
How will we make life more understandable, stable, or dignified?
What burdens are we unintentionally creating?
Who may be asked to do additional work to make this function?
3. Look across the whole system
Sometimes the answer is technology. Sometimes it’s policy. Sometimes it is governance, staffing, communication, or process.
Sometimes it is something much more simple: a clearer letter, a callback system that works, or an experience that better reflects the realities of people’s lives.
Looking across the full system matters because experiences rarely live inside a single silo. They emerge across policies, technologies, teams, and decisions.
The opportunity is not simply to build differently. It is to ask earlier, while the answers can still shape what comes next.
The readiness we owe
Somewhere in a meeting, decisions are still being made about timelines, systems, budgets, and capabilities. Somewhere else, someone like Maria is sitting at a kitchen table trying to navigate the consequences of those decisions.
The invitation, now, is to pause before we congratulate ourselves on what we can engineer and ask who we are building for—and what it would mean to understand their lives early enough for the answer to matter.
These questions do not slow the work. They change what the work is.
Because progress has never only been about what we can build. It is also about whether people can live with what we create.
And perhaps readiness is not simply about whether a system is ready to launch. Perhaps it is whether it serves someone like Maria, sitting at her kitchen table on a Tuesday night with greater clarity, dignity, and ease.
Let’s ask who we are building for and what it would mean to understand their lives early enough for the answer to matter.
Illustration by Summer 2026 intern, Gina Bae.
