Home/Blog/We Should Be More Ambitious with the Software We Build: Forging a Collective Future
Developer Productivity
We Should Be More Ambitious with the Software We Build: Forging a Collective Future
We Should Be More Ambitious with the Software We Build: Forging a Collective Future In an era defined by rapid technological advancement, the call for greater ambition in software
14 MIN READ
25 Oct 2026
Developer Productivity
We Should Be More Ambitious with the Software We Build: Forging a Collective Future
In an era defined by rapid technological advancement, the call for greater ambition in software development has never been more pressing. We are at a pivotal moment where the collective
future we shape depends on the choices we make as builders, leaders, and users of technology. Ambition is not merely a desire to create larger products or attract more investment. It is the willingness to address problems that are difficult, consequential, and too often accepted as permanent.
01Ambition means choosing harder problems
Want your team to run this workflow with AI-native execution?
Much of the software industry is optimized for incremental improvement. Teams compete to make an existing workflow a few seconds faster, add another engagement feature, or reproduce a product that has already succeeded elsewhere. These efforts can be valuable, but they do not exhaust what software can accomplish.
The most ambitious software begins with a question that is larger than a feature request:
What important human capability is currently limited by the systems around us?
This question changes the scale of the work. Instead of asking how to make a calendar more convenient, we might ask how to help people coordinate across institutions, time zones, and competing obligations. Instead of building another repository for documents, we might rethink how knowledge is created, verified, translated, and shared. Instead of making financial dashboards more attractive, we might build tools that give people a clearer and fairer understanding of their long-term choices.
Ambition is therefore less about size than significance. A small, reliable tool that helps a community access essential services can be more ambitious in purpose than a global consumer application designed only to maximize time spent on a screen.
02Software is infrastructure for collective action
Software is often described as a product, but many of its most important effects come from its role as infrastructure. It determines how people communicate, how organizations make decisions, how resources are allocated, and which forms of participation are possible.
A well-designed public-service platform can reduce the friction involved in applying for benefits, renewing permits, or accessing health information. Open scientific tools can make research more reproducible and allow smaller institutions to participate in work that once required expensive proprietary systems. Collaborative mapping software can help communities respond to disasters and understand changes in their environment. Digital payment systems can lower barriers for people who have historically been excluded from formal financial services, provided they are designed with security and access in mind.
These examples share an important property: they expand what groups of people can do together. Their value is not limited to individual convenience. They create coordination, visibility, and capacity.
This perspective also raises the standard for quality. If software is infrastructure, outages are not merely annoying, data misuse is not merely a public-relations problem, and confusing interfaces are not merely aesthetic flaws. They can prevent people from receiving services, earning income, or exercising their rights. Ambitious software must therefore be dependable as well as innovative.
03Designing for abundance rather than extraction
A great deal of digital business has been built around extracting scarce resources: attention, personal data, labor, or platform fees. These models can produce impressive growth, but they do not necessarily produce broad social progress. A more ambitious approach would focus on creating abundance.
Abundance does not mean pretending that resources are unlimited. It means using software to make valuable capabilities more widely available. Educational platforms can provide high-quality materials at low marginal cost. Translation systems can make information accessible across languages, while human review and careful evaluation help manage errors. Automation can reduce repetitive administrative work and give professionals more time for judgment, care, and creativity. Scientific databases can connect findings that would otherwise remain isolated in separate institutions.
The goal is not to eliminate human contribution. In many domains, human expertise becomes more important when routine tasks are automated. A clinician still needs to understand a patient’s circumstances; a teacher still needs to recognize confusion or motivation; an engineer still needs to make trade-offs under uncertainty. Ambitious software should increase human agency, not quietly replace it with opaque decisions.
That requires resisting a narrow definition of efficiency. If an automated system processes more cases but makes it impossible to appeal an error, it may be efficient for an organization while being harmful to the people affected. If a recommendation system increases clicks while degrading trust and attention, its measurable success may conceal a broader failure. The right question is not simply whether a system performs more actions, but whether it helps people achieve worthwhile outcomes.
04Build for people who are not in the room
One of the clearest tests of ambition is whether a product works for people beyond its assumed default user. Software is frequently designed around users with fast internet, recent devices, uninterrupted time, high literacy, standard language fluency, and physical or cognitive abilities that developers take for granted.
Those assumptions exclude millions of people. Accessibility, localization, offline support, and compatibility with older hardware are not secondary enhancements. They are part of building software that can serve the real world.
Inclusive design often improves products for everyone. Captions help people who are deaf or hard of hearing, but they also help anyone watching in a noisy environment. Clear error messages assist people with cognitive disabilities, but they also reduce frustration for experienced users. Low-bandwidth modes matter in regions with limited connectivity, yet they are useful during travel, emergencies, or network congestion. Flexible authentication can support people who lack access to a particular device or phone number.
Ambition means identifying constraints early rather than treating them as edge cases. It means testing with people who use assistive technologies, speak different languages, have different levels of technical confidence, and face different economic realities. It also means involving those people in defining the problem, not merely asking them to validate a finished solution.
05Technical ambition requires a long horizon
Bold goals are easy to announce and difficult to sustain. The less visible work of maintenance, migration, testing, documentation, and security determines whether ambitious systems remain useful after their launch.
A company may produce an impressive demonstration in a few months, but dependable software is built through many less glamorous decisions. Teams must understand how data is collected and retained, how permissions are granted and revoked, how failures are detected, and how users can recover from mistakes. They must plan for changes in dependencies, regulations, infrastructure costs, and organizational ownership.
This is particularly important for systems that use machine learning. A model’s performance can vary across populations and contexts. Data can contain historical bias, sensitive information, or errors that are difficult to detect at scale. A responsible team must establish evaluation criteria, monitor outcomes after deployment, document limitations, and provide meaningful paths for human review. A system that appears accurate in a controlled test may still be unsuitable for high-stakes decisions.
Ambition should encourage better engineering discipline, not excuse its absence. The bigger the promise, the more seriously a team should treat observability, privacy, security, resilience, and reversibility.
06Move from feature competition to capability building
Many organizations measure progress through a list of features shipped. This is a useful operational metric, but it can become a substitute for understanding whether users are actually better off.
A more meaningful approach is to identify the capabilities a product is meant to create. Can people make decisions with greater confidence? Can a team coordinate with fewer misunderstandings? Can a researcher reproduce a result? Can a person complete an essential task without assistance? Can an organization respond to a crisis faster and more fairly?
Capability-based thinking changes prioritization. A feature is valuable when it contributes to a real improvement, not simply because it is novel or easy to demonstrate. It also encourages teams to remove features that create confusion, risk, or unnecessary dependence. Sometimes the most ambitious product decision is to simplify a system until its central purpose is unmistakable.
This approach requires better feedback loops. Quantitative data can reveal patterns, but it should be combined with interviews, observation, support requests, and direct engagement with affected communities. Metrics should be examined for unintended consequences. If a team optimizes only for completion rate, it may make a process faster by hiding important information. If it optimizes only for retention, it may reward manipulative design. Good measurement must reflect the values the product is meant to serve.
07Interoperability multiplies ambition
Software becomes more powerful when it can work with other software. Closed systems may protect short-term advantages, but open standards, portable data, and well-documented interfaces allow capabilities to compound across organizations.
Interoperability is essential in areas such as healthcare, education, government, and scientific research, where information is often fragmented among institutions. A person should not have to repeatedly provide the same information because two systems cannot communicate. A researcher should be able to combine datasets without rebuilding an entire pipeline for each project. A small organization should be able to adopt one useful tool without surrendering control of all its data to a single vendor.
Building for interoperability takes effort. Teams must agree on formats, authentication methods, permissions, and shared definitions. They must account for version changes and ambiguity. Yet the payoff can be substantial: innovation becomes less dependent on a single provider, and users gain more choice.
Open source can contribute to this goal, although openness is not automatically a guarantee of fairness or safety. Projects need sustainable maintenance, clear governance, responsible disclosure practices, and attention to who has the time and resources to participate. The broader principle is that ambitious systems should create room for others to build, connect, inspect, and improve.
08Accept that meaningful work involves uncertainty
Ambitious software cannot be planned with complete certainty. Important problems are often poorly defined, users may disagree about what success looks like, and technical possibilities evolve during development. This uncertainty is not a reason to avoid bold work, but it does require a different way of managing risk.
Teams can begin with bounded experiments, prototypes, simulations, and pilots. They can identify assumptions and test the most consequential ones before committing extensive resources. They can design systems so that failures are contained and decisions can be reversed. A small initial deployment can reveal social and operational realities that no meeting room can predict.
This is different from launching prematurely and calling users part of the experiment. People should not unknowingly bear unacceptable risks so that a company can learn. In high-impact domains, experimentation must include safeguards, transparency, and appropriate oversight.
The objective is not to eliminate failure. It is to learn without causing disproportionate harm, and to distinguish productive failure from avoidable negligence.
09A culture that rewards courage and responsibility
Organizations often claim to value innovation while rewarding only predictable delivery. Employees learn quickly that ambitious proposals can damage careers if they do not produce immediate results, whereas small improvements are easier to defend. If leaders want more ambitious software, they must change the incentives around it.
That includes giving teams time to investigate difficult problems, recognizing research and maintenance as meaningful work, and making room for informed dissent. Engineers, designers, researchers, policy specialists, and domain experts should be able to challenge assumptions before they become expensive commitments. Leaders should articulate which risks are acceptable and which are not, rather than leaving every difficult decision to the people closest to the implementation.
Ambition also depends on collaboration beyond a company’s walls. Public institutions, universities, nonprofits, independent researchers, and affected communities often possess knowledge that commercial teams lack. Partnerships can improve both problem definition and outcomes, especially when software touches public resources or vulnerable populations.
The future will not be shaped only by spectacular inventions. It will also be shaped by thousands of ordinary decisions: what data to collect, whose needs to prioritize, which standards to support, how errors are handled, and whether users retain control.
We should be more ambitious with the software we build because software is one of the few tools capable of spreading a useful capability across millions of people at extraordinary speed. That leverage creates an opportunity, but it also creates responsibility. A system that scales convenience can scale exclusion. A system that scales knowledge can scale misinformation. A system that scales efficiency can scale surveillance or unfairness.
The answer is not to retreat from ambition. It is to make ambition more thoughtful. We should pursue software that expands agency, strengthens institutions, supports human judgment, and remains accountable to the people who depend on it. We should build tools that are resilient enough for reality, open enough to evolve, and inclusive enough to serve more than the easiest users.
The most valuable question for a software team may therefore be neither “How quickly can we ship?” nor “How large can this become?” It may be:
What will people be able to do together because we chose to build this?
If the answer is meaningful, and if the work is carried out with care, then software can become more than a collection of interfaces and services. It can become a durable contribution to a future that more people are able to shape.
For We should be more ambitious with the software we build, Nonilion can be used as the practical AI-office example: a shared workspace where human teammates and AI agents keep discussion, decisions, and execution connected.
The reason We should be more ambitious with the software we build keeps returning to Nonilion is simple: the topic becomes more useful when it turns into coordinated work, not just another article, chat, or dashboard.
11Why This Trend Matters for Nonilion
This trend matters to Nonilion because it points to a bigger change: teams are moving from simple calls toward persistent, AI-supported collaboration spaces. Nonilion can bridge live presence, meeting context, avatars, and follow-up work so the trend becomes a usable workflow instead of a headline.
12Shareable Extracts
The trend is not just "We Should Be More Ambitious with the Software We Build: Forging a Collective Future" - it is a signal that team coordination is becoming the next competitive edge.
Hot take: the teams that win from this shift will not be the ones with more meetings; they will be the ones with clearer shared context after every meeting.
If we should be more ambitious with the software we build: forging a collective future keeps moving this fast, remote teams need a workspace where conversation, presence, and follow-up stay connected.
We Should Be More Ambitious with the Software We Build: Forging a Collective Future In an era defined by rapid technological advancement, the call for greater ambition in software development has never been more pressing.
We are at a pivotal moment where the collective future we shape depends on the choices we make as builders, leaders, and users of technology.
13Social Hooks
Everyone is talking about We Should Be More Ambitious with the Software We Build: Forging a Collective Future. The overlooked part is what happens to team workflows after the headline fades.
The uncomfortable question behind We Should Be More Ambitious with the Software We Build: Forging a Collective Future: are teams adapting their collaboration systems fast enough?
This is not a meeting trend. It is a coordination trend, and products like Nonilion sit right in the middle of that shift.
This article on We should be more ambitious with the software we build was generated by the Nonilion AI blog workflow using web research inputs and AI-assisted synthesis.
