How a learning institution was built from a Google Site, a LinkedIn licence, and the people already in the room.
Begin reading↓Learning in a start-up is rarely anyone's priority. There is always something more urgent.
The organisation had exceptional talent: engineers, product managers, and business professionals drawn from some of the best companies in the world. What it did not have was shared context. Web3 was new territory. Trading was new territory. The industry had no established learning playbook.
No one, regardless of how accomplished, arrived knowing the product, the instruments, or the domain. The ask that came in was simple: set up learning. The work that followed was not.
No budget for new platforms. No content subscriptions. The design had to start with what existed.
What existed was a LinkedIn Learning licence, a Google Workspace, and an organisation full of people who knew things no external vendor could teach.
These were the materials. The constraint produced a clarity that open budgets rarely do. Instead of evaluating platforms or commissioning content, the question became:
What does this organisation already have, and how do we make it move?
The answer was not external. It was already in the room.
One drew on internal expertise. One built a home for it.
The design produced two parallel tracks, each addressing a different layer of the problem. Together they became the institution.
The first track drew on what the organisation already had: people who understood blockchain deeply. Engineers, product leads, trading specialists who had been in Web3 before it had a name. They became the faculty.
Topics were curated weekly. Speakers prepared their sessions, built their materials, and presented to the full organisation. Sessions were interactive. Attendance was consistent, with participation rates sustained across the series.
The content was specific, current, and impossible to buy: real practitioners explaining real systems, and the mechanics of trading, to the people building alongside them. The Speaker Series gave the organisation something no external curriculum could.
The second track required a home for content. Without an LMS, a Google Site was built within the organisation's existing infrastructure: structured, navigable, and organised by level of domain expertise required.
Web3, blockchain, and trading content was tiered. What engineers needed to understand at depth, other functions needed to understand at breadth. The library was built to reflect that distinction. Open-source material, YouTube, whitepapers, books, and curated LinkedIn Learning paths were organised and housed in one place. As the series grew, internal experts began recommending additions. The library expanded continuously.
When the onboarding programme was redesigned, the Academy became its backbone. A Web3 Essentials learning path was made mandatory in the first month. A 70% pass mark on the associated assessment was required before completion. Those who did not pass returned to the path and retook it.
The Google Site had a name. It was branded deliberately, launched with a campaign, and communicated as an institution. It became the Academy.
Domain knowledge was only part of what the Academy carried.
Behavioural learning paths were built and housed alongside domain content: structured programmes anchored to the competency framework, mandatory for all employees. Security and compliance training was mandated and tracked separately.
Speaker Series recordings sat in the Academy too. Every session became a permanent resource. Nothing was lost.
A shared learning institution built on existing infrastructure, at no additional budget.
A fully remote organisation of 200 people, distributed across 73 cities, had a shared learning institution within months of one being commissioned.
The Academy reduced time-to-productivity for new joiners. It created a common language around the product, the domain, and the mechanics of trading. It gave internal experts a platform and an audience.
It made mandatory learning achievable without a dedicated system. It ran on what was already there. It cost nothing additional to stand up.
And it was built because the budget said no, and the design had to find another way.
The organisations most resistant to investing in capability building are often the ones that need it most. New industries, new technology, and new contexts do not come with inherited knowledge. Someone has to build the infrastructure that carries understanding from the people who have it to the people who need it.
Constraint does not prevent that work. Sometimes it is what makes the design honest.