It is increasingly uncontroversial to suggest that traditional educational institutions no longer satisfy 21st century needs. This sentiment has been prevalent in the tech community for years, but is gradually seeping into mainstream conversations around the world.
One of the key problems with the existing education system is the gap between what schools and universities teach, and what industry needs people to understand. This is a contributing factor to what is commonly known as the 'skills gap'. It is most evident in 'frontier' technology domains, which are defined by dynamic skillsets due to constantly moving goalposts.
Given that digital technology has been the dominant 'frontier' for the past ~20 years (and therefore one of the most dynamic), it is the area in which the chasm between education and industry is most acutely felt, though by no means the only one. While it is inherently difficult to accurately quantify this, data points suggest that 87% of employers currently have a skills gap or expect one within the next 5 years, there is only weak correlation between educational and job performance while only ~40% of college graduates work in jobs that typically require a degree. Qualitatively speaking, many tech companies no longer require employees to have a degree. More anecdotally, most people working in technology can describe their own experiences of the mismatch between their education and their employment.
Having paid attention to web3 for a little while now, I think it may have something to offer in this context. Web3 (both technologically and culturally) changes a fundamental assumption of traditional educational institutions, that 'learners' are not capable of producing work that is valued by the market. Instead, web3 assumes that 'learners' are capable of producing real, valuable work as part of the process of learning. In doing so, it may provide a new primitive which enables education and industry to be brought into dynamic alignment, resulting in a faster and more consistent supply of talent with up-to-date industry skills, even in frontier domains.
I want to use this piece to explore this idea in the following main sections:
So, before we talk about web3, why is this important in the first place?
Realistically, employers need some way to distinguish between potential hires who do not yet have extensive working experience. Similarly, students need some way to bootstrap a reputation before they have had the opportunity to gain real working experience. Latter-stage education (~late high school through university), then, should act as an intermediary which fulfils two functions:
Traditional educational institutions have evolved a monopoly around solving these problems; built around the assumption that students aren't capable of producing work that is valued by the market while they are still learning. Courses are ostensibly developed to focus on building the skills that will be required to produce valuable work in the future.
However, in making this assumption, it creates a series of entangled problems that disconnect the work done while 'learning' from the work done while 'working'. Ultimately, this creates a 'gap' (or, at least, a 'lag') between the skills that are needed in industry and the skills that are being taught in schools and universities. This often leads to wasted time and money for graduates, while also reducing the number of skilled workers available to employers.
Let's dig into some of the reasons why this happens.
In the traditional educational experience, the nature of the work is highly theoretical. It is generally about understanding concepts rather than applying them in context. On an average computer science degree course, for example, the focus is largely on the theory of topics like data structures, programming languages, computer architecture and novel computing concepts. While understanding of the theory is at the foundation of becoming a great software engineer, tackling theory in isolation largely divorces the ideas from the real-world context which makes them meaningful. The transition from computer science student to professional software engineer is therefore marked by an entirely new learning curve, including things like working in a shared codebase, deploying in a production environment and working with real users. The theoretical concepts are still highly relevant, of course, but the characteristic that is ultimately valuable is the ability to apply these ideas to build software that solves real problems in the world.
Given the focus on understanding concepts, traditional credentials have evolved to prove theoretical understanding. Good scores in exams and assignments are signals of strong engagement with and understanding of the course material, and so a degree exists to prove a student's understanding of theory in a given domain. Unfortunately, understanding of theory does not imply practical ability. Practical ability can only be built through experience.
Instead, I suspect that the actual value of (most) university degrees to employers is closer to a 'conscientiousness test'; a proof that students are willing and able to apply themselves to achieve some kind of long-term goal. If this is true, then it suggests that despite spending at least three years in higher education, the majority of the skills that are required to be successful in a professional organisation must instead be learned after already getting a degree. Of course, universities do not solely exist for the purpose of getting a job, but it is certainly a key reason.
With a focus on theory, traditional educational institutions cannot perform well as an intermediary, because theory in isolation is not what is ultimately valuable to employers.
Developing courses is a costly and time-intensive process. In order to put a university course together, it requires a well thought out curriculum, staff to teach it, (often) physical space for lectures, course materials, exams and, of course, students. The burden for online courses is usually lower, but the time for new courses to evolve is still usually on the order of months to years. Unfortunately, this timeline is exacerbated by bureaucracy. While it might only take a few months to develop the course once started, it can take significantly longer to realise the need and come to a decision to begin development.
In the case of fast-moving industries, like technology, new skills can arise and become in-demand very quickly. For those familiar with web3, this is very topical. For example, writing smart contracts in Solidity (and now Rust) has become a massively in-demand skill despite relatively little supply. Similarly, the evolution of DAOs has also seen community management evolve as a key skillset.
Unfortunately, by the time that a traditional course covering any of these topics has been developed, it may well be out of date. For example, it might be the case that Solana becomes the dominant blockchain ecosystem, leaving more smart contract written in Rust than Solidity, or that STARKs become the dominant scaling solution, leaving platforms written in Cairo. There might be a new platform that comes to dominate community aggregation other than Discord. These developments would necessarily change the content of the course, and render an older version out of date. Developments like this are the nature of any fast-moving industry, and must be accounted for in any solution looking to adequately match employer demand for novel skillsets. Universities are surely aware of this fact, which may even act as a disincentive to maintain pace with industry developments due to the additional cost of maintenance.
So, for structural and logistical reasons, it is very difficult for traditional education to keep pace with the needs of industry, which creates space between current industry needs and what education can provide.
The gap in education is relatively well established, so partial solutions already exist in the form of trade schools (like Bloom), apprenticeships (like Multiverse), online courses (like Udacity) and a long tail of other online options. These are all good options, but there is a need for a more systematic approach capable of responding to a broad range of dynamic industry needs. It’s here that I think web3 has something to offer.
The current wave of web3 is seeing DAOs move into the mainstream. For anyone not familiar, DAOs enable people and funds to organise on the internet in pursuit of a shared goal. While DAOs are still in their very early days, they are moving fast and moving mountains - for example, ConstitutionDAO raised >$40 million to buy a rare copy of the US constitution, KrauseHauseDAO has raised >$4 million on their way to buying an NBA team and Praxis Society is bringing people together to build a new city. While it is tempting to ask what DAOs are ‘for’, it's truer to say that DAOs are not ‘for’ anything, and are rather an organisational primitive that can be used for practically any purpose, including areas that we would typically attribute to companies.
DAOs are organisations composed of values-aligned communities. While there is usually a team of core contributors, the ultimate goal of DAOs is to enable rapid self-organisation of decentralised, economically-empowered internet communities. Over the long term, DAOs’ potential as an organisational technology is correlated to their ability to embrace and exploit a level of complexity that traditional organisations cannot handle.
In the DAO model, contributors are often not 'hired' through a traditional hiring process. Instead, contributors are freely able to join and progressively earn the right to take on more work and influence the direction of the DAO, through successive proofs of contribution. So, instead of handpicking individuals to join, DAOs create a selection pressure for those who are most aligned with the DAO’s goals to arise organically through contribution. This is a unique strength, because DAOs can benefit from a wider talent base (who may be missed by traditional company requirements) and better long-term incentive alignment.
For DAOs to be successful, then, one key characteristic is creating mechanisms that enable new participants to begin meaningfully contributing. To leverage DAOs’ unique strengths, these mechanisms are likely to diverge significantly from traditional hiring processes, though require solving similar problems:
These are challenging problems to solve, but prior art can provide clues. One of the most successful proto-DAOs is Wikipedia. Wikipedia has evolved mechanisms that solve each of these problems while largely achieving the 'autonomous' nature that DAOs currently lack:
The key aspect that enables Wikipedia to scale coordination across large numbers of open-source contributors is the aggressive modularisation of contributions, which can arise both bottom-up and top-down. Bottom-up contributions occur from someone visiting a page, noticing a problem and making an edit, such that Wikipedia benefits from contributions that could not have been predicted by existing contributors. Top-down contributions arise from an internal task board which represents work that has been identified as needing to be done; so Wikipedia creates simple on-ramps for people who want to get involved more systematically.
A similar pattern of modularisation can be found in almost all other successful open-source collaborations. Michael Nielsen, always way ahead of the game, identifies and explores this in detail in his wonderful book - “Reinventing Discovery”.
DAOs are a different beast, though. Mechanisms are necessarily more complex because there are many more types of contributions, and incentives are more explicit. DAOs are also as much about vibe alignment as goal alignment.
Despite this, efforts to modularise are evolving, notably bounties and grant programs, and will continue to expand. We can look at bounties as a 'top-down' strategy for contributions (work that has already been identified as needing to be done), and grants as a 'bottom-up' strategy (incentivising contributions that arise from the community and can't be predicted up-front). Both of these mechanisms represent incremental, modular units of real work that are valuable to a DAO, but, critically, can also act as clear on-ramps that enable new members to begin meaningfully contributing without necessarily having prior experience in the DAO.
So, what's the link here with education? Well, contribution mechanisms like these are still in their infancy, and don't yet work efficiently. However, if we extrapolate their growth into the future, I think there is a possibility that they can represent a new primitive for coordinating education.
In order to walk with me through the next sections, I'd like to present some assumptions up front. Of course, these are not assured, but they do appear to extrapolate some developing trends:
With these assumptions in hand, we can begin to explore one aspect of the potential for web3 in the education systems of the future.
Earlier on, I stated that one of the core assumptions of traditional education is that learners are not capable of producing market-valued work while they are still 'learning'. Through a series of entangled problems, this creates a coordination problem between education and industry which results in a skills gap. With the set of ideas outlined in the previous section, it creates a mechanism in which there is a new assumption. Web3-native organisations (DAOs) enable people to produce valuable work regardless of whether they are learning or an established professional. Instead of having to spend years acquiring a university credential before earning the right to start contributing valuable work to the market, 'learners' can learn by doing real work for real organisations working in frontier domains.
I suspect that novel contribution mechanisms (like bounties and grants) can represent a primitive for new kinds of education businesses, able to build supportive scaffolding around a dynamic landscape of modular work. These businesses will be able to understand the goals of individuals, and build experiences that orchestrate open-source work to achieve those goals. In doing so, they will perform the role of universities by taking on the metacognitive burden of traditional courses, but will be entirely internet-native and responsive to market needs.
This represents some significant changes from the university model from the point of view of the learner.
There are significant benefits of this model from the point of view of the learner. However, the greater potential of this model arises by zooming out to the system level.
Let's project ourselves a few years into the future and imagine that this model is operating at significant scale. Let's say that there are millions of DAOs, large and small, spread across all industries throughout the world. This isn't so farfetched, given that there are 10.75 million companies in the US alone and DAOs are significantly easier to start than companies. Let's also imagine that over this time, DAOs (and their tools) have become really good at modularising their work and efficiently coordinating large numbers of contributors.
Now, each DAO is producing hundreds or thousands of modular units of work every week which are available to open communities. We also assume that DAOs are tackling every conceivable kind of work, and so these modules are an accurate representation of their current needs. We now have a very large number of open-source work tasks that can be taken on by learners and professionals alike.
Where universities have traditionally between intermediaries between industry and 'learners', there are now direct on-ramps to acquiring expertise in frontier domains. Most excitingly, this may create the potential for 'education' to adapt in perfect synchrony with industry, because the new structural components of education are also incremental units of work for frontier organisations. This ability can come without any additional 'cost' to the system, since the modularisation of work by DAOs is critical to their function and not expressly in the name of 'education'.
As a quick thought experiment, let's imagine that a majority of large DAOs for whom it is relevant decide that STARKs are the future of blockchain scaling. As a result, they decide to rewrite their existing smart contracts in Cairo. In order to make this happen fast, each DAO decides to split this work out into individual tasks (for ease, let's imagine each task is one rewritten smart contract) and offer them out to the ecosystem. This creates a large amount of demand for Cairo developers in a short space of time, and given that Cairo is a new skill which is relatively scarce (and the need to rewrite the contracts is urgent), the price that DAOs are willing to pay is relatively high. In response, there is now a strong pressure for developers to learn Cairo (assumed here to be a new skill with zero established experts, and is a skill that requires significant time investment to learn).
Currently, the most visible signal for this demand is job postings, which in turn act as a signal for individuals and educational organisations looking to provide in-demand skillsets. However, along Coasean lines, this comes with high transaction costs for each party:
By reducing the functional unit from a full-time position down to a task while creating a direct relationship between organisations and learners, we can reach a new equilibrium which supports the needs of each party. For individuals, tasks enable acquisition of expertise while reducing the risk of committing to full-time positions before understanding long-term interest. For organisations, urgent requirements can be filled faster while real contributions act as a higher-fidelity signal of long-term vibe alignment (which can convert to longer-term positions if desired). For educational businesses, it is easier to quantify the demand of new skillsets and build experiences that effectively teach them.
Ultimately, this mechanism may enable education and industry to co-evolve as needs change more quickly than has been possible before.
The goal of this piece has been to discuss the potential of web3 to better align education and industry in the pursuit of progress. To summarise the key points:
Do you have thoughts on this topic? I’d love to hear from you! Please do reach out - you can find me here.