Academy
Our teaching approach
Case-based management system training that develops practitioner skill and professional judgement in situations an organisation actually meets
A management system, not just documents
It is how an organisation assigns responsibility, controls risk, creates records, learns from performance and improves over time. So we teach it the way it is actually operated: inside situations, not clause by clause.
Overview
A requirement becomes a situation you can act in
Our training modules connect management-system concepts with realistic organisational situations, so a reader sees what a requirement actually turns into: who governs it, what it exposes the organisation to, which controls carry it, what proves it is working, how it survives change, and who decides.
Those six questions are the capability domains the curriculum is organised by, and they hold across disciplines and standards: for example, analysing risk works much the same way in an information security system as in a quality one.
Our training approach is built on explaining each concept, demonstrating it in realistic situations, and building the required skills up until they hold in real, often messy ones.
Case organisation
A fictional organisation that behaves like a real one
Participants work through management system situations where standards, roles, risks, controls, evidence and decisions come together in one organisation.
Northstar Integrated Services AG
Northstar is a Zurich-headquartered group providing digital operations platforms and managed services to regulated organisations across Europe. It is fictional, and deliberately so: it lets us show weak processes, awkward supplier arrangements and unhelpful evidence without exposing a client. Exercises run on it rather than on a fresh example each week, so what you decide in one module is what the next one finds.
What the organisation keeps
The records a real one keeps: organisation and people, risks, objectives, policies and documents, findings and reviews, third parties, processes. Exercises open them at the point in the company history the module has reached.
It has a history
The organisation has a timeline and modules enter it at different points, so a structure can be studied before it broke as well as after.
It crosses borders
A Swiss parent and an acquired operating business that kept its own legal identity, which is where the interesting failures live: group instruments rolled out operationally and never put in force by the subsidiary itself.
Nothing is summarised
Registers, policies, audit findings and supplier records to interpret where they would really sit, not a tidy summary of them.
What a module trains
The questions a practitioner asks without being prompted
Our modules are designed around practical reflexes rather than around a list of topics. A practical reflex is what a practitioner asks and does without being prompted, under pressure: whether an owner can actually act, whether an exposure is being accepted or merely tolerated, whether the criteria in use can carry the decisions they are asked to carry, and then the move that follows from the answer. Topics can be listed after a course; reflexes show up in the next register review, the next escalation and the next acceptance signature.
Three practical reflexes, taken from the curriculum:
- Real ownership and escalation
- Test whether a named owner actually holds the authority and the resources to act, keep risk, control and treatment ownership apart, and recognise when an exposure needs escalating as a decision request rather than another status update.
- Residual exposure and explicit acceptance
- See where exposure is being carried rather than treated, accept that an organisation may run exposure deliberately to pursue its objectives, and insist that such acceptance is named, dated, reasoned and signed instead of arriving by inertia.
- Risk criteria and acceptance authority
- Design impact, likelihood and acceptance criteria proportionate to the organisation's size and decision needs, with named acceptance authority, escalation thresholds and a review cadence, and recognise the defects that make a framework unusable: scales that cannot be compared across units, criteria without decision consequence, and rules copied from elsewhere that nobody applies consistently.
For our learners the outcome is practical reflexes: skills that transfer into their daily work. Rather than learning clauses and technical terms, or applying a template without judgement, they are prepared to make a system effective in real organisational work and to keep it that way.
Inside a module
You practise on realistic, messy situations
Our training modules follow the case organisation's own timeline, so situations reach you in the order the company actually met them. Each situation runs through the six steps below, and the same call comes back often enough to become a reflex.
01
Situation
Something has happened
A moment at the case organisation, or one from your own work, before it has been named as a problem of any particular kind.
02
Concepts
What the standards require
The requirements and terminology that govern the situation, taught before the exercise that needs them.
03
Evidence
What the organisation has
Registers, the org chart, findings and review records, incomplete and occasionally contradictory, as in practice.
04
Work
Exercise to train your reflexes
Capability broken down into reflexes that cannot be split further, drilled first and then combined into longer sequences.
05
Feedback
Every answer comes back explained
An answer comes back with the distinction it turns on. Written work is graded against named criteria with a stated pass mark.
06
Take-home
What goes back to work with you
A set of tools and templates you encountered during the module, ready to adapt to your own organisation.
FAQ
Good to know
Is the case organisation based on a real client?
No. It is written from scratch, and the failures in it are the ordinary ones: a standard adopted verbatim years late and still not fitting, an access exception agreed by e-mail with no expiry, a supplier operating a control with nobody named on our side of it.
Why one case organisation instead of separate examples?
Because learning becomes cumulative. Returning to a familiar organisation means you recognise the people, posts, processes and registers immediately and can spend your attention on the new concept. It also means the disciplines meet inside one organisation, so a decision taken for one is what the next one has to live with.
Why is the training built around practical reflexes?
Because clause knowledge alone does not survive contact with a real Tuesday morning. What practitioners use is a reflex: whether an owner can act, whether an exposure is accepted or merely tolerated, whether the criteria can carry the decisions, and the move that follows. That transfers between standards and roles in a way clause recall does not.
How is a reflex developed during a module?
By meeting the same reflex repeatedly: introduced where the concept is taught and practised in the exercises, with the guidance thinning out as it goes. Some reflexes recur across modules too, so a second module deepens what the first one started, in whatever order you take them.
Does the method work for self-paced learners?
Yes, by design. The written module is complete in itself: everything a live session would cover is in the reading, and every exercise can be worked from it. Videos of the trainer are recorded for parts of it as a second channel, so you can hear a point argued as well as read it.
How are reflexes assessed fairly?
Every graded exercise has named criteria, fixed points and a pass threshold, and you get a per-item score with the reasoning behind it. Where more than one answer is defensible, what is graded is the quality of the reasoning rather than the choice, so you are not marked down for reaching a different conclusion, only for reaching it badly.
Where to start
See the method in a module
A module page sets out what the module trains, the case organisation it runs on, and how the work is graded.
Browse the catalogueWhere it leads
Modules stack into role-based tracks. A track adds what a single module cannot: a capstone engagement and a final examination, ending in a credential issued without expiry.
In your organisation
Bring this approach in-house: the modules run privately, on your dates, with your context in the examples.