One-Point Lesson (OPL): The Single-Page Standard for Fast Training

A one-point lesson (OPL) is a single-page visual training document that teaches one specific skill, standard, or piece of knowledge in five to ten minutes. Born inside Total Productive Maintenance programs, the OPL replaces thick manuals and hallway tribal knowledge with a focused, sketch-heavy sheet that an operator or technician can absorb at the machine. The point is speed and retention: one topic, one page, one short session. When you scale OPLs across a plant, you build a library of small, precise lessons that turn scattered know-how into a repeatable standard.

What a one-point lesson actually is

An OPL is deliberately narrow. Instead of documenting an entire changeover procedure, an OPL covers a single decisive point: how to read one gauge, why one bolt torque matters, or the correct sequence for one cleaning step. That constraint is the whole idea. A person can teach it, learn it, and be checked on it in minutes, which is why OPLs are a backbone of autonomous maintenance where operators take on basic care of their own equipment.

Good OPLs lean on visuals: annotated photos, arrows, before-and-after sketches, and short bullet captions rather than paragraphs. The rule of thumb is that roughly seventy percent of the page should be image and thirty percent text. Each sheet carries a title, the author, a date, a revision number, and a place for trainees to sign once they have been shown and can demonstrate the point.

The three types of OPL

OPLs come in three recognized categories, and knowing which one you are writing keeps the content honest.

• Basic knowledge OPL. Teaches a fundamental that everyone in the role must know: how a component works, what a warning symbol means, the correct lubrication point, or how to interpret a pressure reading. These fill knowledge gaps and form the largest share of most libraries.
• Problem case OPL. Captures a specific failure that occurred and the fix, so the lesson is not relearned the hard way. It documents the symptom, the root cause, and the corrective action, and it pairs naturally with structured methods like 8D problem solving and A3 problem solving.
• Improvement OPL. Shares a kaizen or a better method that a team developed, such as a jig that halves a setup, so a good idea spreads instead of dying on one line. These are the connective tissue of a healthy PDCA cycle.

A worked example: cutting setup errors on Line 3

A packaging line runs a filler that jams whenever the guide rail is set even slightly wide. Over one quarter the team logs 18 jams, each costing about 12 minutes of downtime, so 216 minutes lost, roughly 3.6 hours of production. Investigation traces every jam to operators eyeballing the rail instead of using the reference mark.

The team writes a basic knowledge OPL: a single photo of the guide rail with an arrow to the engraved reference line, three caption lines, and a note that the correct gap is 42 mm. Training takes 7 minutes per operator across 9 operators, about 63 minutes of total effort. In the following quarter jams drop to 3, saving 15 jams times 12 minutes, or 180 minutes recovered. Against 63 minutes invested, the payback lands inside the first week, and the recurring saving compounds every quarter. That same signal shows up in your overall equipment effectiveness as a cleaner availability figure and a lower scrap rate.

How to write one that sticks

A tight OPL follows a predictable rhythm, which is why teams can produce dozens without a template committee.

1. Pick exactly one point. If you need the word "and," split it into two OPLs.
2. Lead with an image. Photograph the real machine, then annotate directly on it.
3. Write captions, not prose. Short imperative lines: "Align to the mark," "Torque to 25 Nm."
4. State the why. One line on the consequence of getting it wrong drives retention.
5. Add verification. A sign-off box turns "shown" into "confirmed competent."
6. Date and version it. An OPL that outlives the current machine setup is worse than none.

Keep OPLs close to the standards they support. They are a natural companion to a control plan and to the visual discipline of the seven quality tools, giving a shop-floor face to documentation that otherwise lives in a binder.

Attaching OPLs to assets and work orders

An OPL only earns its keep if the right person finds it at the right moment. A sheet buried in a shared drive is invisible; a sheet linked to the exact pump a technician just opened is training on demand. The modern practice is to attach OPLs to two anchors:

• To the asset. Every machine record carries its relevant basic and problem-case OPLs, so anyone assigned to that asset sees its known failure modes and care points first.
• To the work order. When a preventive or corrective job is raised, the matching OPL rides along with it, so the standard is in hand before the wrench turns. This is how OPLs plug into a CMMS and shift a plant from reactive toward proactive maintenance.

When OPLs live where the work happens, you also shorten the ramp for new hires and reduce the odds that a solved problem returns, which quietly protects both MTBF and MTTR.

Where Fabrico fits

Fabrico is the real-time data foundation that gives OPLs a home and a trigger. Its field-ready CMMS lets you store documents against each asset and each work order, so the relevant one-point lesson travels with the job to the technician on the floor. Because Fabrico also delivers real-time OEE and production monitoring, and can watch machines with computer vision even where there is no PLC, you can see which assets generate the most stops and write problem-case OPLs where they will pay back fastest. Fabrico is EU-built with EU data residency, so that training and asset history stay inside your compliance perimeter. You can see the maintenance side in the CMMS solution overview and the monitoring side in the MES and OEE solution overview.

Frequently Asked Questions

How is an OPL different from a standard operating procedure?

An SOP documents an entire process end to end and can run many pages. An OPL isolates a single point within or around that process and fits on one sheet built for a five to ten minute session. They are complementary: SOPs define the full workflow, while OPLs reinforce the specific steps people most often get wrong or need to learn quickly.

How long should a one-point lesson take to deliver?

Aim for five to ten minutes of active teaching, including a quick demonstration and a check that the trainee can perform the point. If a lesson consistently runs longer, it is covering more than one point and should be split so each sheet stays fast to teach and easy to verify.

Who should write OPLs?

The people closest to the work: operators, technicians, and line leaders. Frontline authorship is what makes problem-case and improvement OPLs valuable, because the knowledge comes straight from the person who lived the failure or found the better method. A simple review step keeps the content accurate before it enters the shared library.

Ready to attach one-point lessons to the assets and work orders where they belong, backed by real-time production data? Book a Fabrico demo and see how a live CMMS turns scattered know-how into a standard your floor actually uses.