The architecture, before anything gets built.
A program is not a pile of good courses. It is a sequence with a claim attached: by the end, people can do these things, and here is where each one was introduced, reinforced and assessed. This is the part that most libraries skip, and it is why they can't answer a simple coverage question three years in.
Five moves, every time
Whether it is one card or a whole program. The subject changes and the framework changes; the discipline does not.
Start from the performance gap
Not "what should we cover" but "what can people not do yet, and how do we know". The gap is evidenced from your incident data, audit findings, survey results or support tickets before a single objective gets written. Sometimes this step ends with us telling you the problem is not a training problem — which is cheaper to hear now than after the build.
Write one outcome, in changed behavior
One measurable statement of what someone will do differently. Everything downstream — the lessons, the assessment, the evaluation — is built to serve that statement, and anything that does not serve it gets cut, however interesting it is.
Map it to the framework that governs the work
Every objective tagged to a competency at the sub-competency level, in whatever framework your work answers to. Tagging at that grain is what makes coverage reportable: which capabilities your people are strong in, which ones nobody has touched all year, and where the next build should go.
Anchor every claim to a source
Content is verified against primary sources, not against a summary of one. References sit in the build file, dated and reviewable, so material has a defensible shelf life and a scheduled review rather than an indefinite one.
Evaluate for outcome, not satisfaction
The instrument asks whether the outcome was met, what the learner will change, and what will get in the way. Those answers are structured data, so evaluation feeds your next needs assessment instead of producing a star rating nobody acts on.
Every lesson maps to a competency
Not the course — the lesson. Tagging at that grain is the difference between a library you can report on and a pile of content you hope is covering the right things.
Most content libraries are tagged by topic, which tells you what a thing is about. We tag by competency, at the sub-competency level, which tells you what someone can do after it. That one change is what makes three questions answerable:
- Which capabilities is this program actually covering?
- Which ones has nobody touched all year?
- Where should the next build go — and what can we retire?
The framework is yours, not ours. A national academic set, a certification blueprint, a regulator's requirements, or your own role and capability model — the tagging layer takes any of them, and a piece of content can carry more than one at a time.
Worked example. Our own library is tagged to a ten-domain national competency framework, down to the sub-competency, which is what lets an individual see their own coverage and a program lead see where the holes are. The same architecture takes a different spine — a certification blueprint, an interprofessional set, or a client's own capability model — without redesigning the content underneath.
What you get, and where we can start
Take the whole thing, or come in at the stage where you are stuck.
Architecture
Before anything gets built.
- Needs assessment and gap evidence
- Program outcomes and course-level objectives
- Curriculum map — introduced, reinforced, assessed
- Sequencing, prerequisites and pathways
- Accreditation and self-study documentation
Build
Outline to packaged course, media included.
- Scripting, lessons and assessment
- Film, synthetic video and course art
- Workbooks, tools and worked examples
- Packaging and LMS handoff
Rescue and rebuild
A course that isn't landing, or a library gone stale.
- Teardown against the stated outcome
- Assessment and evaluation redesign
- Re-cut of existing media
- Review cycle and shelf-life plan
Delivery and measurement
Getting it in front of people, and knowing whether it worked.
- Packaging for your LMS, or hosted by us
- Completion and coverage reporting
- Outcome-based evaluation instruments
- Documentation for credit-bearing activity
On the subject matter. Our samples are healthcare, because that is where this practice has built most of its library. The architecture, the assessment design and the production pipeline are subject-agnostic — the same shells have been built against professional standards, certification blueprints and internal role frameworks. If your content is not clinical, none of it changes.
Tell us what your people can't do yet.
Bring the gap — an audit finding, an incident trend, a survey result — and we will tell you honestly whether learning is the right instrument and what it would take to build it.