We often praise organisations for values like integrity, customer centricity, ethics, accessibility, inclusion, and governance. But values only matter if the systems behind them make those values visible in practice. The real question is not whether organisations say the right things, but whether their processes, products, and decisions are designed to deliver them.
This question has occupied my thinking for some time. As someone who has navigated systems as an IT professional, a customer, an autistic mother, a person living with a disability, and someone whose circumstances have changed significantly over time, I have become increasingly interested in the relationship between organisational values and organisational design. Not simply whether organisations have values, but whether their systems make those values real.
Take financial services as one example. Many financial products are designed to comply with regulatory frameworks and ethical standards. Compliance is essential. But is compliance alone sufficient? If the goal is to preserve financial wellbeing, how should organisations respond when a customer’s circumstances change dramatically? If the goal is to preserve dignity and cognitive ease, what responsibility do organisations have to reduce unnecessary burden, particularly for customers living with disabilities, neurodivergence, or other differences?
These are not abstract questions. They are design questions. And they should be asked more often, across teams, disciplines, and leadership tables.
Every organisation creates assumptions about its customers: how quickly they can complete forms, how easily they understand communication, how much time they have, how many times they are willing or able to repeat their story, how confidently they can navigate complex processes. But what happens when those assumptions do not reflect reality? What happens when the system is built for the ideal customer rather than the actual one?
When that happens, the burden shifts from the system to the individual. The customer adapts. The patient adapts. The employee adapts. The parent adapts. The neurodivergent person adapts. Until adaptation itself becomes the product.
As someone trained in Information Technology, I find myself viewing lived experience through the lens of systems analysis. Every point of frustration represents a point of friction. Every repeated explanation signals a process failure. Every workaround reveals a design assumption. These are not isolated complaints. They are data.
We celebrate digital transformation as progress.
But progress for whom?
Technology has made our lives faster, more efficient and more connected.
Yet in our pursuit of convenience, I wonder whether we have unintentionally designed out the very people who need our systems the most.
The elderly who struggle to navigate apps and online portals.
The autistic adult overwhelmed by multiple authentication steps and inconsistent communication.
The person living with a disability trying to complete inaccessible forms.
The customer who has lost a job, a loved one, or their health and simply doesn’t have the capacity to navigate another complex process.
Technology is not the problem.
The question is whether we have confused digitalisation with accessibility.
A process can be completely digital and still be completely inaccessible.
Perhaps the measure of innovation is not how quickly a process can be completed, but whether the most vulnerable person can move through it with dignity.
So what would it look like if we treated them that way? What if organisations invited people with lived experience into the design process earlier, not just after something has gone wrong? What if we asked customers where the system creates confusion, delay, shame, or exhaustion? What if we measured not only completion rates, but recovery time, emotional load, and the number of times someone has to ask for help?
Perhaps this is where we have an opportunity to evolve. Rather than only viewing lived experience as something to celebrate during awareness campaigns, perhaps we should begin recognising it as one of the richest sources of organisational intelligence available. People who have navigated systems over months or years often understand those systems in ways that performance dashboards cannot reveal. Their experiences identify not only what happened, but why.
So how do we bring those insights into the room? How do we design feedback loops that capture the reality of vulnerable journeys? How do we ensure that the people most affected by system design are not only heard, but actually shape the design?
This is particularly relevant for organisations that publicly commit themselves to ethical leadership, human-centred design, accessibility, inclusion, or faith-based principles. The true measure of those commitments may not be found in policy documents or marketing campaigns. It may be found in the experience of the customer whose circumstances unexpectedly change, the employee returning after illness, the disabled client navigating support, the family facing financial hardship, the person trying to understand a process that was never designed with them in mind.
So who is actually making these decisions? Who is asking whether the system works for the people most likely to struggle with it? Who is checking whether the journey is dignified, understandable, and humane? Who is measuring whether the organisation’s values are visible in the moments that matter most?
The takeaway is simple: values are not real until vulnerable people can feel them in the way an organisation behaves, decides, and responds. If that is true, then perhaps the next question is not whether we have the right values, but whether our systems are built to express them.
Can we audit the vulnerable journeys? Can we track the friction? Can we measure the recovery time? Can we listen to the people who have had to work hardest to be served?
If your systems only work well for the easiest customers, then your values are not yet embedded. They are aspirational.
I do not pretend to have all the answers. But I do wonder how much of my energy I am scattering for something where systems can only exist if there is a profit. And I do believe these are questions worth asking.
And I would invite leaders, designers, policymakers, and practitioners to ask them now, before another vulnerable customer is forced to prove, once again, that your values are easier to declare than to experience.
Perhaps this is where the next generation of ethical leadership begins: not with certainty, but with better questions about how our systems are designed, who they serve, and who they still leave behind.