Institutions & orgs

Your educator should not have to solve the same teaching problem twice

Your organisation’s teaching knowledge should not depend on who happens to be available, which folder someone remembers or whether a educator has time to read through another PDF.

Turn scattered materials and individual experience into shared teaching knowledge that people can find, use and build upon.

The goal is more than a central archive.

It is an institution that retains what its people learn and makes that knowledge useful in the next lesson.

Repeated preparation is an organisational problem

Consider three educators preparing to teach the same topic.

The first searches for a suitable explanation and creates a worked example.

The second finds a different source and builds a similar lesson.

The third has taught the topic many times and already knows the question that reveals the most common misunderstanding. But that knowledge remains in a private board or in the tutor’s memory.

Each person is doing legitimate teaching work. Yet the organisation is repeatedly investing in discoveries that could be shared.

The issue is not that every educator should teach identically.

It is that personalisation should begin with an informed starting point, not with everyone independently rebuilding the same foundation.

We built a PDF archive at EduQuant. Most of it went unused.

At EduQuant, our tutoring company, we created a shared PDF archive for our tutors.

The intention was straightforward. Collect useful material, make it available to everyone and give tutors a stronger starting point for their lessons.

In practice, most of the archive was rarely used. A tutor might rely on one familiar PDF while the other documents remained untouched.

The material was there. Reading through it was the problem.

To use an unfamiliar document, a tutor had to find it, open it, locate the relevant section, understand the surrounding explanation and decide whether it suited the student. Then they still had to turn that material into something they could teach.

Access to the archive did not remove that work.

Our experience changed the question we were asking.

Instead of asking, “How do we share more documents?”, we needed to ask:

How do we make the right part of our knowledge available when a tutor actually needs it?

Sharing a file is not the same as sharing expertise

An experienced educator may know which document contains the useful example, which pages can be ignored and what needs to be adapted.

A new educator sees a folder.

Research on organisational knowledge repositories has identified a similar problem. One study found that people who already had stronger access to organisational knowledge used the repository more frequently than people at the periphery. Making the repository available did not automatically make it equally useful to everyone. Knowing how to extract value from it mattered.

This research was not conducted in tutoring organisations, but it offers a useful explanation for our archive experience.

A document contains information. Applying it also requires context.

Who is it for? What should the learner already understand? Which problem does it address? What should the tutor do when the first explanation does not work?

A shared file rarely answers all of those questions.

Structure knowledge around teaching needs

Educators do not usually need “the whole PDF.”

They need a clear explanation of a particular concept, a suitable worked example or a question that helps them decide what to teach next.

An institutional teaching library should therefore make smaller components understandable and reusable.

For a topic such as quadratic functions, a useful component could include the learning objective, the intended level, a worked example, a common misconception and a suggested hint. It should also identify its source and explain any important limitations.

This preserves more than the finished material. It preserves the reasoning needed to use it.

Research on the transfer of best practices within organisations supports taking context seriously. A study of 122 transfers across eight companies found that major barriers included recipients lacking the background to absorb a practice and uncertainty about why the practice worked. Simply distributing the material was not enough.

For an institution, the practical lesson is to share the explanation behind the resource as well as the resource itself.

Make knowledge available where teaching happens

Even well-organised material can be difficult to use when finding it requires leaving the lesson, navigating another system and rebuilding the result.

The target should be a shorter path from teaching need to usable material.

When preparing a lesson, an educator should be able to find an appropriate explanation and bring it into the lesson.

When a participant struggles, the educator should be able to locate a relevant alternative example or hint.

When planning the next session, the educator should be able to build on what has already been taught.

EduBoard combines searchable PDF content and reusable lesson sections with shared organisational lesson libraries. These provide a foundation for connecting shared materials to the teaching workspace rather than maintaining them only in a separate archive.

Research in technical field work provides a relevant organisational analogy. A longitudinal study found that accessing documented knowledge during tasks was associated with fewer calls to technical support. Different kinds of knowledge were useful for different problem types. The setting was not education, but it illustrates why access at the moment of use deserves attention.

The objective is not merely better search.

It is making the result useful without asking the tutor to complete another round of interpretation and reconstruction.

Let one educator’s improvement become another educator’s starting point

A shared teaching workflow could look like this.

One educator creates an explanation.

Another uses it with a different learner and adds a clearer diagram.

A third identifies a recurring misunderstanding and proposes a diagnostic question.

An academic lead reviews the changes before the revised material becomes the recommended version.

The next educator begins with the combined contribution rather than the original draft.

This is how we think institutional knowledge should develop: through teaching, adaptation and review.

It should not require every educator to write a separate report after every session. The contribution might be one improved example, a short contextual note or a clearer hint.

Nor should every change become institution-wide guidance automatically. The organisation needs to decide what is personal work, what is shared for discussion and what has been approved for wider use.

Reuse and quality control belong together.

Standardise the starting point, not every teaching decision

A shared library should support educator judgement, not replace it.

Two students may need different explanations of the same concept. One may need prerequisite practice. Another may need a more demanding application.

The institutional resource should help the educator make those choices.

That means preserving alternatives and context, not forcing every lesson into one script.

A useful shared explanation tells the educator what it is intended to achieve. A useful adaptation records why it was needed. A useful misconception note helps the educator recognise when another approach may be appropriate.

Consistency should mean that tutors can access the organisation’s knowledge and standards. It should not mean that every learner receives an identical lesson.

Build an asset that becomes more useful through use

An archive grows when someone uploads another file.

An institutional knowledge asset improves when someone makes the existing knowledge easier to find, clearer to understand or more useful to apply.

A lesson might contribute a more precise explanation.

An educator’s adaptation might reveal that a resource needs a different prerequisite.

An academic review might identify an outdated example.

A team discussion might connect a common misconception to a better diagnostic question.

When those improvements are captured and made reusable, later work can benefit from earlier work.

That is what we mean by a compounding teaching asset.

The value does not come from collecting the largest number of documents. It comes from accumulating relevant content, context, connections and reviewed improvements.

This is not automatic. Frequently used material is not necessarily the best material, and more recorded activity is not proof of better teaching. The organisation must continue to review what it preserves and recommends.

Your distinctive asset is the context around the content

A textbook available to other institutions is not, by itself, a unique advantage.

Neither is a collection of generic explanations.

What can become distinctive is the way your organisation connects its materials to its own teaching experience.

Which explanation do your tutors use for a particular level? What prior knowledge does it require? Which misunderstanding should they check for? What alternative example is available? How has the lesson changed after repeated use?

Those relationships describe how your institution teaches.

They can give a new tutor access to decisions that would otherwise have to be rediscovered. They can preserve useful expertise when a colleague changes roles or leaves. They can provide a common starting point without erasing individual teaching styles.

The asset is not merely a set of documents that nobody else has.

It is a structured record of your organisation’s teaching decisions, adaptations and reviewed knowledge. Another organisation cannot obtain that specific history simply by downloading the same textbook.

Keep institutional knowledge separate from the AI model

For institutions adopting AI, we recommend distinguishing between the knowledge they maintain and the model used to work with it.

The model provides capabilities such as generating language, summarising material and helping interpret a request.

The institutional knowledge provides the context: approved sources, curriculum mappings, explanations, examples, teaching guidance and revision history.

Retrieval augmented generation offers one technical way to combine these layers. The foundational research describes a system that combines knowledge stored in model parameters with information retrieved from an external collection. The external collection supplies material the model can use when generating a response.

For an educational institution, the strategic principle is:

Keep your teaching knowledge usable beyond any single AI model.

This does not mean separating the layers automatically creates portability or guarantees correct answers.

An institution should require usable exports, preserved source references, clear access controls and testing when models or retrieval systems change. Knowledge should remain understandable and maintainable outside an individual chat history.

The aim is to improve or replace the intelligence layer without having to reconstruct the institution’s accumulated teaching context.

Build the knowledge layer before expecting AI to understand your institution

Imagine asking an AI tool:

Prepare a lesson on quadratic functions for a student who understands factorisation but struggles to connect equations and graphs.

A general answer may provide a plausible lesson.

An institutionally informed answer should also be able to draw on the organisation’s preferred examples, curriculum requirements, known misconceptions and reviewed teaching materials.

That is the difference your knowledge layer should make.

However, those distinctions must first be recorded. An AI system cannot reliably apply teaching decisions that exist only in someone’s memory.

The work of identifying, structuring and reviewing institutional knowledge remains important. AI can help work with that knowledge, but it does not remove the need to decide what should count as an authoritative source.

Turn individual teaching work into institutional knowledge

A PDF archive answers a storage question:

Where should we put our materials?

A teaching knowledge system answers a working question:

How can the next educator benefit from what our organisation already knows?

That is the institution we want to help build.

One in which preparation does not repeatedly begin from nothing. One in which useful improvements travel beyond the person who made them. One in which teaching experience becomes accessible context for both people and AI.

Your educators should be able to build on each other’s work.

Your organisation should retain the knowledge it develops.

And every useful contribution should have a path into the next lesson.

Build your institution’s shared teaching knowledge with Eduboard.