Approach
Many systems are built to manage people from the outside.
They measure behaviour, automate decisions, optimise attention, reduce friction, and try to make human life more predictable. Some of this is useful. But when systems are designed only around efficiency, engagement, or control, they can weaken the very capacities people need most: judgment, attention, trust, resilience, and agency.
Living Fabric Research begins from another premise.
The purpose of a system is to help people become more capable of meeting life.
A good system should not quietly train dependence. It should not replace the difficult human work of thinking, choosing, relating, repairing, or growing. It should create the conditions in which that work becomes more possible.
The next generation of tools and systems should be judged not by how much human effort they remove, but by what human capabilities they strengthen.
Research areas
Our work is organised around five areas of research. Each begins with a practical question.
Relationship clarity
How can two people understand each other well enough to choose each other, or before distance becomes damage?
Many relationships weaken not because people stop caring, but because they lose the ability to say what they mean, hear what the other person means, or repair what has gone wrong. The caring remains. The language for it disappears.
We study how trust, misunderstanding, conflict, silence, and emotional distance develop between people, how people come to know and name what they need from one another, and design tools that help them clarify what they are experiencing, understand one another more accurately, and return to the relationship with greater honesty and care.
Decision support
How can people make difficult decisions without surrendering the decision to a system?
People often mistake relief for clarity. A decision that reduces anxiety in the moment is not always the right decision, but under pressure, the two can feel identical. That pressure takes many forms: emotional weight, family expectation, limited information, fear of choosing wrongly.
We study how people narrow their options, avoid uncertainty, defer to others, or lose sight of what actually matters to them. Our work in this area focuses on tools that help people slow down, examine the decision honestly, and choose with greater agency.
Emotional recovery
How can people move through difficulty without being left alone or made dependent?
People often need support during periods of anxiety, grief, conflict, transition, or loss of direction. But support can fail in two ways: it can be absent when needed, or it can take over the work a person needs to do for themselves. Either failure weakens the person’s ability to recover on their own terms.
We study the conditions that help people stay grounded, name what they are carrying, recognise patterns, and recover steadiness over time. The tools we design here support reflection and emotional movement without pretending to replace therapy, friendship, family, or community.
Developmental environments
What kinds of systems help people grow without pushing them toward a breaking point?
People develop inside environments: homes, schools, communities, workplaces, institutions, and digital systems. These environments shape what people believe is possible, how they handle pressure, and whether they can become more capable over time. What people believe about themselves is not easily undone.
We study how environments either strengthen or weaken attention, clarity, judgment, resilience, and belonging. We design systems that help people grow without reducing them to performance, productivity, ranking, or compliance.
Environmental systems
What would it take for the large systems a society depends on to work well for the people inside them?
This is the widest of our areas, and it holds several problems rather than one. How a city processes what it throws away, and what it would take to empty a landfill that has been filling for decades, is a question of cost, method, and consequence. Why people maintain some shared systems and quietly damage others is a question about people.
We study these systems as they are used: what they cost to run, where they fail, how people behave toward them, and what would make caring for one worth doing rather than merely required. Waste is the example closest to hand, what processing it costs, what emptying a landfill would take, and whether returning it properly can be made to pay the person who does it. The same questions reach infrastructure, public services, and the arrangements a place has settled into over time.
How we work
We work from human situations, not from technologies looking for use.
We begin by sitting with a problem as it actually appears in someone’s life, not as a category or a use case, but as a real difficulty with real pressure around it. From there we ask: what is getting in the way? Is it lack of information, lack of trust, emotional overload, poor timing, social pressure, institutional design, the absence of the right kind of support, or something else?
We then design and test an appropriate form of support: sometimes a tool, sometimes a method, process, programme or intervention. A scaffold supports when needed and then steps back as capability returns or begins to grow.
Study the situation
We look closely at the real context in which the difficulty appears: who is involved, what pressure they are under, what support exists, and where the system fails them.
Define the capability
We identify the specific capability that needs strengthening. This may be the ability to name what one feels, understand another person, stay grounded under pressure, see more than one path, or make a decision with care.
Design the scaffold
We build a tool or method that supports that capability. The design must keep the person active, not passive.
Test in practice
We test whether the scaffold improves the human situation it was designed for. The measure is not attention, engagement, or time spent. The measure is whether people become more capable of doing what matters.
Refine, publish, or stop
If the work shows promise, we improve it and decide whether it should become a product, research note, method, or prototype. If it does not strengthen capability, we stop or change direction.
We accept long time horizons. Some questions may become products quickly. Others may remain research directions for years. We do not treat speed as proof of importance.
A system is worth building only if it strengthens human capability without weakening human agency.
Outputs
We will share research as the work develops: notes, technical reports, prototypes, field observations, essays, talks, and publications.
Some questions will become formal papers. Others may become methods, product principles, design studies, or discontinued lines of inquiry.
Each piece of work will make clear what question it addresses, what was tested or observed, and what we learned from it.
Research outputs will be published here as projects develop.