A wider lens on innovation
Innovation is usually described as a moment: a discovery, a launch, a new invention that arrives fully formed. The stories we tell about it tend to start with the breakthrough and skip what came before and after. But an idea becomes useful through a much less visible process. Someone understands a need. Someone else brings a skill. Another person builds the trust that lets them work together. Somebody maintains the result once the excitement fades. Progress takes shape in those connections.
Seen this way, innovation is less a single act of genius than a relationship between people, tools, institutions and places. The new device matters, but so do the training that makes it usable, the policy that decides who can access it, the budget that keeps it running and the community that decides whether to trust it. Remove any one of those and the idea can stall, however clever it is.
This journal begins with that wider lens. It is not a technology column, a policy newsletter or a sustainability blog. It is an attempt to follow ideas across the borders we usually draw between subjects, because that is where many of the most useful questions live.
Why thinking in silos holds progress back
Organisations divide work for good reasons. Specialisation builds depth, accountability and expertise. The trouble starts when the divisions we create for convenience begin to shape what we are able to see. A technology question can also be a question about access. A public-policy decision can change how a community learns. An environmental challenge can expose how an economy distributes risk. Treating each subject as a sealed room makes those relationships harder to notice.
Silos also shape incentives. A team measured on delivery speed may not be rewarded for the maintenance problems it creates for another team. A department responsible for one budget line may have little reason to care about costs that appear somewhere else. Each decision can be reasonable on its own terms and still produce a result nobody wanted.
None of this means that everyone should become a generalist. It means that someone needs to look at the space between the specialisms, and that the people working inside them need enough shared language to talk to one another when it matters.
Start with the people affected
A useful starting point is to ask who actually has the problem, how they describe it in their own words, and what they already do to manage it. People rarely wait passively for a solution. They improvise, adapt and build workarounds. Those workarounds are evidence: they show what matters to people and where existing systems fall short.
The answer to those questions may suggest a new tool. It may equally suggest a better process, a clearer conversation, a change in who is responsible for what, or the removal of an obstacle that nobody had thought to question. Starting with the people affected keeps those options open instead of committing early to the solution that is most exciting to build.
That approach requires listening before naming the solution. It also means bringing the people affected into the work early enough to change it. Participation has little value if every important decision has already been made, and people can usually tell when they are being consulted for appearances.
How connections create value
When different kinds of knowledge meet, something specific happens: assumptions become visible. An engineer explains a constraint that a designer had not considered. A teacher describes how a tool will actually be used in a crowded classroom. A community organiser points out who is missing from the conversation. Each perspective reveals the limits of the others, and the resulting idea is usually more realistic than any of them would have produced alone.
Those encounters are not always comfortable. Different disciplines value different kinds of evidence, move at different speeds and use the same words to mean different things. Working across them takes patience and a willingness to be the least informed person in the room. The reward is an idea that has already survived contact with the world it is meant to serve.
Connections also travel. A method that works in public health can inform how a city plans for heat. A habit from product design can improve how a nonprofit explains its work. Looking across disciplines makes it easier to borrow what already works instead of starting from nothing.
A practical map for connecting the dots
Interdisciplinary thinking can sound abstract, but it can start with a simple exercise. On one page, write down the need you are trying to address and who experiences it. Then list the people and organisations involved, the resources already available, the relationships that are missing and the assumptions that have not yet been tested.
The point is not to produce a perfect system diagram. It is to make the next useful conversation possible. A map like this often reveals that the most important missing element is not a technology at all, but a relationship: two groups that should be talking and are not, or a decision-maker who has never heard from the people the decision affects.
Three questions help keep the map honest. Who benefits if this works, and who carries the cost if it does not? What would we need to learn before committing further? And who is not yet in the conversation who should be?
What this journal will explore
Across technology, society, policy, environment, economy, health and education, the guiding question stays the same: what would make an idea useful, and for whom? Some pieces will be perspectives that argue for a way of seeing. Others will be field notes from everyday systems, essays that take a question further, and in-practice stories about people working together on something concrete.
The aim is not to have the final word on any subject. It is to ask better questions, show the trade-offs honestly and keep people in the picture. Progress rarely belongs to a single discipline. It belongs to the connections we are willing to build between them.
