Description

A focused course, tailored for you

The Psychological Safety Risk Lead Operating Manual

Turn the psych-safety strategy deck into a measurable risk register, named owners, evidence trail, and quarterly review the trust and safety leadership will sign off.

Your strategy deck is approved. The risk register that backs it is still a working document, and the question coming back from review is always the same: who owns this control, what evidence is on file, and when was it last tested.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Psychological safety as a risk surface sits between integrity ops, legal, product policy, well-being research, and external regulators who are starting to ask the same questions a financial regulator asks of a credit risk function. The strategy work is the easy half. The hard half is the operating layer underneath: a register that names every psych-safety risk at a severity a reviewer can apply consistently, a control catalogue mapped to the integrity standards already in production, named owners on every line, evidence captured as a byproduct of normal work rather than a scramble before the quarterly review, and a review pack that lands on leadership desks in a format they can act on in a single meeting. Without that layer, the strategy deck reads as intent rather than a function that is running. The operating manual is the layer.

What you walk away with

A psychological safety risk register with severity rules a peer reviewer can apply without a meeting.
Control mappings against the integrity and well-being standards your platform already runs to.
Named control owners on every line of the register, with an escalation path that does not depend on you personally.
An evidence pipeline that captures artefacts as a byproduct of normal review work, not a quarterly scramble.
A quarterly review pack that fits one Trust and Safety leadership meeting and surfaces the decisions, not the metrics.

The 12 modules

Module 1. Scoping the psych-safety risk surface

Draw the line between psychological safety risk, well-being research, integrity enforcement, and product policy. Identify the surfaces your function owns and the surfaces where you are a contributing reviewer. Map upstream signal sources (user reports, integrity ops escalations, well-being study findings) and downstream stakeholders (product policy, legal, external regulators) so every register entry has a clear origin and a clear consumer.

Module 2. The risk taxonomy that survives review

Build a taxonomy at the granularity reviewers can apply consistently across thousands of decisions. Distinguish risks by surface, by user population, by harm vector, by reversibility. The output is a taxonomy that lets two reviewers classify the same incident the same way without consulting each other, which is the prerequisite for everything that follows.

Module 3. Severity rules that hold under audit

Move severity from a judgement call to a rule a reviewer applies. Define the inputs (population affected, reversibility, regulatory attention, prior incident history) and the rule set that maps them to a severity level. Document the edge cases so the rule set survives the third reviewer who joins the team and the external auditor who reads the rules for the first time.

Module 4. Control catalogue against integrity standards already running

Inventory the controls already operating in integrity ops, well-being research, product policy, and trust and safety operations. Map each register risk to controls that are already there before you propose new ones. This is the fastest path to a credible operating layer because most of the controls are already running, they are just not catalogued against psych-safety risks yet.

Module 5. Named owners and escalation paths

Every line on the register gets a named owner who can show evidence the control ran in the last review cycle. Build the escalation path that handles owner turnover, controls that fail their evidence test, and risks that need a second owner across teams. The output is a register that does not depend on any single person, including you, to remain credible.

Module 6. Evidence pipeline that captures from normal work

Design the evidence capture so it is a byproduct of work the team already does, not a separate task. Logs from integrity ops queues, sampled review decisions, dashboard snapshots taken on a schedule, well-being study artefacts filed against control lines. The pipeline runs on a calendar so evidence accumulates whether or not anyone is preparing for a review.

Module 7. Quarterly review pack format

Build the pack the Trust and Safety leadership reads in one meeting. Lead with the decisions you need from them, not the metrics. Surface the lines of the register that changed severity or owner. Show the controls that failed their evidence test and the remediation plan. Keep dashboards in an appendix, not the front matter. The format is the difference between a review that books a follow-up and one that closes the loop in the meeting.

Module 8. Cross-functional sign-off without rewriting the deck

Build the routine that brings legal, product policy, integrity ops, and well-being research to sign off on the register without each function asking you to rewrite the deck in their language. The technique is to bring each function in on the slices that touch their surface, not the whole register, and to record their sign-off line-by-line so the next quarter starts from a settled baseline.

Module 9. External regulator readiness for psych-safety surfaces

Treat the regulator-facing posture as a parallel artefact built off the same register. Cover the question categories regulators are starting to ask of large platforms about psychological harm: how you define the surface, how you prioritise, how you measure, how you remediate. The output is a regulator pack that aligns to the internal register rather than restating it differently.

Module 10. Incident response and post-incident control updates

Standardise the post-incident loop so every incident produces a register update, a control update, and an evidence artefact. Distinguish learning-only incidents from severity-shifting ones. Build the rule that decides when a single incident moves a control from green to amber. Without this loop the register goes stale and the strategy deck stops matching the operating reality.

Module 11. Metrics that the leadership will actually use

Strip the dashboard down to the handful of metrics that drive a decision. Coverage of named owners. Evidence freshness by control. Severity drift across the quarter. Time from incident to control update. Resist the urge to publish a wall of metrics that nobody acts on. The goal is two screens that a leader scans before walking into the review meeting and knows where the function stands.

Module 12. Running the function as a discipline, not a project

Move the function from a quarterly heroics cycle to a calendar-driven discipline. Standing reviews. Pre-committed evidence cycles. A clear escalation path that does not need your personal involvement. The closing module covers the operating cadence that lets you take leave without the register going stale and lets the function survive the next reorganisation without losing the controls it has already established.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

You inherited the strategy deck and need to build the operating layer underneath it before the next leadership review.

Trust and Safety leadership is asking for a single quarterly pack rather than the current scatter of dashboards.

External regulator attention on psychological harm at large platforms is rising and the function needs a credible posture.

A reorganisation is on the horizon and the function needs to survive without its current lead in the seat.

What you get with this course

Twelve written modules with worked examples drawn from large-platform psych-safety functions.
Risk register template with the severity rules and field schema pre-built.
Control catalogue mapping format against common integrity and well-being standards.
Quarterly review pack template tuned to a single Trust and Safety leadership meeting.
Regulator-facing posture artefact built from the same register.
The hand-built implementation playbook delivered against your actual surface mix and review cycle.

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours: learning environment account provisioned and the implementation playbook delivered alongside it.

Week one: register template populated against your actual surface mix.

Week two: control catalogue mapped against the integrity standards already running.

Week three: evidence pipeline scheduled and named owners on every register line.

Week four: first quarterly review pack assembled in the new format, ready for leadership.

Before and after

Before

Strategy deck approved, register treated as a working document, controls owned in scattered places, evidence assembled in a scramble before each review, leadership review packs that vary in shape every quarter.

After

Register with severity rules a reviewer applies without a meeting, every line owned by a named person, evidence captured as a byproduct of normal work, a quarterly pack that lands one meeting before the review and drives decisions in the room.

What happens if you do not address this

The strategy deck remains intent rather than a running function. Reviews keep producing the same gap question. A single incident or a single regulator inquiry exposes the gap between the deck and the operating reality, and the rebuild happens under pressure rather than on a chosen calendar.

Who it is for

Strategy and risk leads inside large platform companies who own a psychological safety, well-being, or integrity risk surface and report into Trust and Safety or a Chief Compliance Officer. Comfortable with the strategy work, the gap is the operating layer underneath: register, controls, owners, evidence, quarterly review pack.

Who this is NOT for. Researchers who are studying psychological safety as an academic topic. Product managers who own a single feature rather than a risk surface. Generalist GRC analysts without a psych-safety remit. The operating manual assumes the strategy is already approved and the task is building the function that runs underneath it.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Six to ten hours across the twelve modules to read and apply. Roughly four weeks elapsed to stand up the register, control catalogue, evidence pipeline, and first quarterly pack against your actual surface.

Why $199 is the right number

A generic GRC course teaches enterprise risk management at a level of abstraction that does not match psychological safety as a risk surface inside a large platform. A consultancy engagement produces a deck rather than an operating function. The operating manual is built for one role: the strategy and risk lead who needs the layer underneath the deck and is doing the build personally.

FAQ

Is this aligned to a specific compliance standard?

The control catalogue module maps against the integrity and well-being standards your platform already runs to, rather than introducing a new external standard. Most large platforms run a mix of internal integrity standards plus regulator-facing artefacts. The course assumes you bring the standard list, the modules show how to map controls against it.

Does this cover the external regulator angle?

Module nine treats the regulator-facing posture as a parallel artefact built off the same register. The point is that the regulator pack and the internal register stay aligned rather than diverging into separate maintenance burdens.

What happens after the course?

The implementation playbook is hand-built against your actual surface mix and review cycle and delivered alongside course access. The course teaches the method, the playbook applies it to your specific function.

Refund policy?

Thirty-day money-back if the course does not deliver what is described.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.