
The Kids Designing the Global Future
A kid building an app quickly discovers that code is only part of the work. Someone has to understand the people using it, decide what it should do, give it a form, and keep it running. The project crosses professional boundaries long before its maker has chosen a profession.
The same happens with a garment, a publication, or a community. Learning follows the demands of something that needs to exist. A missing skill becomes a reason to study, ask for help, or work with someone who knows more.
Institutions struggle to recognize this kind of education when they look only for a completed credential or a familiar job title. Leaving school proves nothing on its own. Neither does remaining within it. The work deserves to be examined for what its maker understands and what they can actually contribute.
Learning through a problem
A project brings knowledge into relation. Someone building a small digital product may need to understand software, visual hierarchy, payment systems, customer behavior, and the language used to explain the offer. The problem supplies a reason to move between those subjects.
That movement can produce a useful form of judgment. A decision that appears efficient within one field may create a difficulty elsewhere. Learning through the whole project makes those consequences harder to ignore.
It also has limitations. Immediate problem-solving can leave gaps in foundational knowledge, and an apparently successful result can conceal a misunderstanding. A self-directed practitioner needs ways to discover those gaps rather than assuming that delivery proves complete competence.
The strongest version of the method combines practical iteration with study and informed criticism. A working prototype gives the learner something specific to examine. A more experienced collaborator can explain where it is fragile, what has been misunderstood, and which principles would make the next version stronger.
Community as a place of evaluation
Online communities and informal professional networks can make work available to people who would not otherwise encounter it. They can supply feedback, collaborators, and opportunities that are difficult to obtain through a conventional application.
But a community’s approval is not automatically a reliable measure of quality. Familiarity, charisma, and shared taste can shape what receives attention.
A network that claims to have abolished gatekeeping may simply have made its gates less explicit.
Useful communities can explain their judgments. They should be able to recognize contribution, offer criticism without humiliation, and make room for someone whose work does not yet fit the dominant style. The point is to give people a route into serious practice, rather than to replace one status system with another.
Contribution should also be understood broadly. Maintaining a tool, documenting a process, helping someone resolve a difficult problem, and carrying a project through unglamorous stages all sustain the conditions in which visible work can happen. A healthy network recognizes those activities alongside the compelling final image.
Adaptation with a foundation
The ability to learn a new tool quickly is useful. It becomes more valuable when supported by principles that remain intelligible across tools. Composition, evidence, incentives, material constraints, and the responsibilities attached to a decision do not disappear when the software changes.
Deep knowledge remains essential to that foundation. The difficulty arises when a specialty becomes a reason to ignore consequences beyond its boundary, or when an institution assumes that the categories of yesterday fully describe the problems of today.
A multidisciplinary practitioner does not need to replace the specialist. Their contribution may be to recognize when a specialist is needed, formulate a question that permits useful collaboration, and understand enough of the answer to carry its implications into the rest of the project.
Adaptability then becomes a disciplined relationship to uncertainty. A person can change direction without pretending that every new possibility is equally credible. They can retain what has been learned while revising the assumptions that no longer hold.
From a product to its conditions
A project can reveal that the visible object is only one part of the work required. A tool may depend on a service around it. A creative initiative may need a commissioning structure. A community may need rules, maintenance, and ways to resolve conflict before it can continue beyond its founders’ enthusiasm.
Thinking in systems means learning to see those conditions. The term should make responsibilities more concrete. It should identify who does the work, how information moves, what happens when something fails, and which relationships need to endure.
For the young practitioner, this widens the range of meaningful contributions. A person may begin as a designer and discover that the project needs them to organize a team or develop a new process. That discovery can become the beginning of a practice, provided they take the additional responsibility seriously.
What institutions could do
Schools and employers could examine work in ways that make its reasoning visible. A portfolio should allow someone to explain the question, the constraints, the decisions, and what changed after testing. This provides a stronger account of ability than either a credential alone or a polished collection of outcomes.
They could also support supervised projects across disciplines, provide access to experienced practitioners, and recognize the maintenance and documentation that make collaboration possible. Informal learning becomes more useful when it can meet institutional resources without losing the initiative that produced it.
These practitioners are already doing work that crosses the boundaries institutions use to evaluate them. Their contribution will depend on the depth they acquire, the relationships they sustain, and the responsibilities they are prepared to accept. Those are qualities worth creating room for.
Abel Paul George ·
