Why innovation depends on shared language, experimentation, and collaboration
Series: Sustainable Reality Reflections — Decisions in Emerging Technologies
Many organisations treat curiosity as a personal quality. In technical fields, it can be something far more practical than that.
As systems grow more complex, progress increasingly depends on people who can cross disciplines, ask unfamiliar questions, and build understanding between specialists who often use very different languages. Engineers, researchers, designers, and domain experts may all work toward the same goal while describing the problem in completely different terms.
Curiosity helps close that gap.
At Sustainable Reality, Perry Gibson explored that idea through examples spanning compilers, creative media, open-source communities, and experimental hardware. Together, they pointed to a broader truth: curiosity is not separate from technical work. It often helps make technical work possible.
Experimentation creates unexpected entry points
Innovation does not always begin with formal research programmes or carefully scoped product plans.
It often begins with smaller experiments that allow people to test ideas quickly, explore unfamiliar tools, or approach established problems from a different angle.
Creative side projects can serve this role particularly well. They lower the stakes, encourage iteration, and create room for learning that more formal environments sometimes suppress.
Examples from Perry’s work reflected that pattern. Projects involving poetry generation, music video creation, and unconventional hardware experiments may appear unrelated on the surface, yet each created opportunities to learn new tools, test assumptions, and collaborate across different domains.
Small experiments often open doors that larger initiatives overlook.
Innovation often happens between disciplines
Many important technical problems now sit between established fields rather than within them.
Modern AI systems, for example, rely on progress across hardware design, software engineering, mathematics, product thinking, and domain expertise. No single discipline owns the full challenge.
That creates a practical problem as much as a technical one. Specialists often optimise within their own area, but progress across boundaries depends on translation. Teams need ways to explain trade-offs, constraints, and possibilities to people with varying levels of expertise.
Shared language becomes valuable infrastructure. When teams can describe problems clearly across disciplines, collaboration accelerates; when they cannot, progress often slows despite strong individual talent.
Small projects often teach the most
Not every valuable project needs to become a product, a paper, or a large programme of work. Some of the most useful technical efforts are exploratory. They exist to answer questions, test boundaries, or understand how systems behave under unusual conditions.
Building a neural network compiler for older gaming hardware is a project Perry undertook as an opportunity to work within boundaries. The practical output may be niche, but the learning can be substantial. Work like this teaches constraint handling, systems thinking, tooling, debugging, and adaptation.
Projects like these also build confidence.
When people experiment outside standard pathways, they often discover that tools once reserved for large organisations or specialist labs are now accessible to smaller teams with enough persistence and curiosity.
Open tools are widening access to innovation
The conditions for experimentation have changed significantly. Open-source software, online communities, low-cost development tools, and accessible learning resources allow individuals and small teams to explore ideas that previously required much larger budgets or formal institutional support.
That shift matters.
Innovation no longer depends solely on large internal R&D functions. It can also emerge from distributed communities, independent builders, and cross-disciplinary teams willing to learn in public.
Advanced tools, including AI systems, may further accelerate this when used effectively. They can help people understand unfamiliar concepts, prototype quickly, and move into adjacent fields faster than before.
The underlying advantage, however, still comes from people who remain willing to ask questions and test ideas.
Curiosity as infrastructure
Technical organisations often invest heavily in hardware, software, and processes. These are essential foundations. Yet progress also depends on less visible assets: openness to questions, tolerance for experimentation, and cultures that reward learning across boundaries.
These qualities help organisations adapt when technologies shift, requirements change, or disciplines converge.
In that sense, curiosity is not a luxury. It is part of the infrastructure that supports innovation.
The teams best placed to navigate future complexity may not be those with the most resources alone. They may be those most willing to keep learning.
You can learn more about Perry’s work and projects by heading to our speaker’s page or watch a short clip below:
This essay forms part of the Sustainable Reality series on how decisions in complex technological environments shape progress.
You can see the first piece in our series, covering edge computing and circular heat design here.
Thanks to XKCD for their take on ‘average familiarity‘.