LEAF Academy: Where research becomes capability.
Emerging technology creates little value when knowledge remains concentrated in a few specialists. Organizations need a shared language for understanding what is changing and practical experience applying it to their own work.
LEAF Academy turns the research, technologies and systems we work with across Advisory and Labs into tailored learning programs that help leaders and teams understand them, use them and build lasting internal capability.
- AI literacy
- Emerging technology
- Hands-on practice
- Upskill & reskill
Why Academy
Technology adoption is a people problem too.
Organizations can buy software, commission prototypes and approve technology strategies without developing the internal capability required to use them well.
When only a few specialists understand a technology, decisions become slower, expectations become unrealistic and adoption remains dependent on external support.
Academy closes that gap by turning technical and strategic knowledge into a language teams can share and into practices they can apply inside their own work.
The Academy path
From frontier knowledge to something a team can use.
Research becomes language. Language becomes practice. Practice becomes adoption.
Understand
Frontier research
01/ Research
Start from what is actually changing
Academy draws on the same research, technology scouting and engineering work that informs LEAF Advisory and Labs, helping separate durable developments from short-lived noise.
- Papers
- Signals
- Engineering work
Try
Shared language
02/ Language
Give the organization a shared vocabulary
People do not need the same technical depth, but they do need enough common language to discuss capabilities, limitations, risks and decisions without talking past one another.
- Concepts
- Terms
- Boundaries
Apply
Practice
03/ Practice
Put concepts into people's hands
Workshops and exercises move the discussion from explanation to use: working with relevant tools, workflows, examples and decisions rather than remaining at slide level.
- Tools
- Workflows
- Exercises
Adopt
Organizational capability
04/ Adoption
Connect learning to actual work
The aim, agreed when the program is designed, is for participants to leave with something they can apply: for example a revised workflow, a better-informed decision, a practical deliverable or a clearer operating practice.
- Teams
- Decisions
- Practices
Each program decides how far along this path it needs to go, and for whom.
What we cover
Different organizations need different kinds of capability.
Four capability areas, combined and adapted around the organization. They are areas of competence, not four fixed courses.
AI Literacy & Strategy
Build the language required to understand what modern AI can and cannot do, where it may affect the organization and how to reason about adoption, risk and investment.
Emerging Technology
Develop practical foundations in technologies that may reshape products, operations and markets before they become everyday business infrastructure.
Hands-on Adoption
Move from concepts to direct use through workshops built around relevant tools, workflows and organizational problems.
Reskill & Upskill
Design longer learning paths around the capabilities an organization wants to build internally rather than offering the same curriculum to every team.
No fixed syllabus, no public course catalogue: content, depth and format are designed for each organization.
The same technology, different depth
A leader and an engineer should not receive the same program.
Audience-design patterns, not packaged courses: the same technology is taught at the depth each role actually needs.
Decide
Leadership & decision makers
Strategic language, capability boundaries, adoption choices, risk, governance and the questions leaders should ask before committing resources.
Focus
- Capability boundaries
- Risk & governance
- Investment questions
Use
Business & operational teams
Practical understanding of how technology affects daily work, where it can assist existing processes and what responsible use looks like.
Focus
- Daily workflows
- Assisted processes
- Responsible use
Build & operate
Technical teams
Deeper implementation concepts, architectures, evaluation, integration and operating practices relevant to the technology being adopted.
Focus
- Architectures
- Evaluation
- Integration & operations
Align
Cross-functional groups
Shared sessions that allow business, technical and leadership roles to establish a common vocabulary before working on the same initiative.
Focus
- Common vocabulary
- Shared initiative
- Aligned decisions
Shared language
Adoption slows down when every team means something different by “AI”.
Terms such as agent, model, automation, RAG, AI readiness or on-premises AI can mean very different things depending on who is speaking.
Academy creates enough shared technical language for business, leadership and engineering teams to discuss the same technology without requiring everyone to become a specialist.
The objective is not vocabulary for its own sake. It is better decisions and more productive collaboration.
Format follows the goal
From focused workshops to structured learning programs.
Scope can range from a focused workshop to a multi-session program. Duration is defined by the learning objective and the participating team.
Workshops
Focused sessions around a defined technology, challenge or team objective.
Tailored courses
Structured learning designed around the organization's maturity, roles and technology priorities.
Onboarding & enablement
Training connected to a tool, system or capability being introduced into the organization.
Upskilling / reskilling programs
Multi-session paths for building deeper capability over time.
Practical information
- Language
- English or Italian, with bilingual sessions where that is useful for the participating team.
- Delivery
- Defined around the program and the participating team.
- Group
- Format and facilitation are adapted to the size and composition of the group.
- Duration
- Set by the learning objective, from a single focused session to a multi-session path.
- Completion
- Structured programs can include a certificate of completion, which is not a formal professional accreditation.
Designed around the organization
Start from the people, tools and decisions that already exist.
Every program is designed before it is delivered, in five steps.
01/ Understand
Define who needs to learn what
Identify participants, current maturity, strategic objectives and the decisions or activities the program should support.
02/ Contextualize
Replace generic examples with relevant ones
Adapt concepts, terminology and exercises to the organization's sector, systems, constraints and current initiatives.
03/ Practice
Move from explanation to direct use
Give participants structured opportunities to apply the concepts rather than treating attendance as the outcome.
04/ Apply
Connect learning to real work
Where appropriate, exercises can be built around actual workflows, tools, documents or decisions from the organization.
05/ Review
Look at what changed
Evaluate practical outputs, understanding and adoption signals appropriate to the program instead of relying only on attendance.
From explanation to practice
Understanding a technology is different from using it.
A presentation can explain what a model, agent or emerging technology is. It does not show whether a team knows when to use it, when not to use it or how it changes the work around it.
Academy programs therefore create opportunities to work with concrete examples, tools and decisions wherever the subject allows it.
The objective is not activity for its own sake. Practice should reveal where understanding is strong, where assumptions break and what the organization needs to clarify before broader adoption.
Taught from the work
The material comes from the same world we advise on and build in.
Academy is connected to the technology work carried out across LEAF. Advisory explores how emerging technologies affect organizations and decisions. Labs prototypes, engineers and validates systems. Academy turns those lessons into capability for the people who need to use, evaluate or operate them.
That connection helps keep training grounded in how technology behaves outside the classroom rather than separating education from implementation.
Research connection
Close enough to research to see what is coming. Practical enough to teach what matters.
LEAF was founded by university lecturers and researchers who build products: its founders combine university teaching and research with engineering and product development.
Academy brings that intersection into organizational learning: frontier concepts are interpreted through the requirements of real systems, teams and businesses.
LEAF is not a university. Academy programs are not university-accredited and do not award academic credits.
Real tools when they help
Learning can connect to the technology teams will actually use.
Where it improves the learning objective, Academy programs can be connected to technologies and systems relevant to the organization rather than relying only on generic classroom examples.
That may include tools built within LEAF Labs or the same classes of AI systems, enterprise architectures and emerging technologies explored through Advisory and Labs.
Academy is broader than product training: a LEAF Labs technology is used only when it serves the learning objective.
Explore LEAF Labs| Generic example | Relevant to the organization |
|---|---|
| Sample dataset | Documents or data the team works with, where appropriate |
| Demo tool | Tools and systems the team will use |
| Hypothetical scenario | An actual workflow or decision |
Measure more than attendance
A completed session is not the same as capability.
Participation tells you that someone attended. It does not tell you whether they can apply the material.
Depending on the program, evidence of learning can come from exercises, practical deliverables, changed workflows, demonstrated use of a tool, scenario analysis or other outputs agreed before the program starts.
Attendance
Tells you who was there.
- Sessions attended
- Hours completed
- Certificate of completion
Evidence of capability
Shows what people can now do.
- Exercise results
- Practical deliverables
- Changed workflows
- Demonstrated tool use
- Scenario analysis
- Outputs agreed upfront
The measurement approach should follow the learning objective rather than forcing every program into the same test.
Capability progression
Not everyone needs to reach the same depth.
Different programs target different endpoints. A leadership literacy program may aim for understanding; a technical enablement program may aim for operational capability.
Awareness
Knows the technology exists and why it matters.
Understanding
Can explain how it works, what it can do and where it stops.
Practice
Has used it in guided exercises with relevant examples.
Application
Applies it to real work, with support.
Operational capability
Uses, evaluates and maintains it as part of normal operations.
An explanatory learning progression, not a validated maturity model. Each program agrees its target endpoint.
AI literacy
Enough technical understanding to make better decisions.
Often the broadest entry point to Academy: the language leaders and teams need to reason about AI without becoming specialists.
Models
What modern AI systems do, how outputs are produced and why capabilities differ across model classes.
Use cases
Distinguish problems that benefit from AI from those better solved with conventional software or process change.
Limitations
Understand probabilistic behavior, incomplete information, evaluation and why fluent output is not evidence of correctness.
Data & privacy
Reason about what information enters a system, where it is processed and which organizational policies apply.
Governance
Understand ownership, human review and the controls needed when AI influences decisions or workflows.
Adoption
Identify how roles and processes change when new tools enter real work.
Data, privacy and governance are treated as organizational reasoning, not as legal or compliance advice.
Emerging technology
Understand a technology before it becomes an urgent decision.
Academy is not limited to whichever AI tool is currently receiving attention. LEAF works across emerging technologies, and training can help organizations establish the foundations required to assess what is changing before adoption becomes urgent.
Areas LEAF works in
- Talk with Your SystemsEnterprise RAG & AI Assistants
- AI AutomationAI Agents & Workflow Automation
- Confidential AIPrivate & On-Premises AI
- AI on the EdgeEdge AI Engineering
- Synthetic DataTraining Data Generation
- Industrial IoTConnected Sensing & IIoT
- AEO / GEO / AI SEOAnswer & Generative Engine Optimization
Examples from LEAF's current work. Programs are defined around the organization's priorities.
Who Academy is for
Organizations that want capability to remain inside the organization.
Academy is designed for organizations building internal understanding around AI and emerging technologies, whether the immediate need is leadership literacy, hands-on adoption, technical depth or broader reskilling.
Leadership teams
Building the shared language to set direction, weigh risk and decide where technology deserves investment.
Business functions
Understanding how a technology affects their processes and how to use it responsibly in daily work.
Technical teams
Going deeper into the architectures, evaluation and operating practices of the technology being adopted.
Cross-functional transformation teams
Aligning business, technical and leadership roles before they work on the same initiative.
Organizations following an Advisory or Labs engagement
Preparing the people who will evaluate, use or maintain what the engagement produced.
One cycle
Understand it. Build it. Make it usable by the organization.
Advisory, Labs and Academy form one cycle, but not a mandatory sequence.
From strategy to internal capability
A recommendation creates more value when the team understands what comes next.
An Advisory engagement may identify a technology, operating model or opportunity. Academy can translate that strategic work into the knowledge required by the people who will evaluate, use or govern it.
Explore LEAF AdvisoryFrom system to adoption
A working system still needs people who know how to work with it.
A Labs project can introduce a new tool, AI system or technical capability. Academy can support the teams who will use, supervise or maintain it by connecting training directly to the resulting system.
Explore LEAF LabsWhat training does not solve on its own
Capability needs more than attendance.
Academy builds the human capability required to adopt technology well. It does not replace the strategic, technical and organizational work surrounding that adoption.
- A workshop does not replace a technology strategy.
- Training cannot compensate for unclear ownership or poor operating processes.
- Knowing how a technology works does not make every use case appropriate.
- AI literacy does not eliminate model error or technical risk.
- Tool training becomes obsolete if people learn buttons rather than underlying principles.
- Not every role needs the same technical depth.
- A certificate of completion is not proof of business adoption.
- Adoption requires time, incentives, processes and leadership in addition to training.
- Formal regulatory or professional accreditation is separate from ordinary Academy participation unless explicitly stated.
- Learning outcomes should be evaluated against the objectives defined for the program.
What should your team be able to do differently?
Tell us what technology your organization is trying to understand, adopt or operate, who needs to build the capability and what should change after the program. We can design the learning path around those objectives.