Skip to content

Lantern, a worked example · Record

OUT-PREPARE: Reduce assignment preparation friction

An invented example

This Atlas is drawn from the records of an invented product, so it can be published to show what the Atlas shows. A team's own Atlas may contain internal and restricted records and stays inside the organization. The files are authoritative; these pages are a derived view of them.

Snapshot: commit unknown · graph hash 3b31c362b352 · level L1 · scope examples/scheduling/**

Records › Outcomes › OUT-PREPARE

In the model: PRD-LANTERN › INT-PREPARE › OUT-PREPARE

The record

examples/scheduling/OUT-PREPARE.md · View the file on GitHub

Field Value
ID OUT-PREPARE
Title Reduce assignment preparation friction
Type outcome
Status draft
Owner team-assessment
Visibility internal
Audiences engineering, product
Revision 1
Parent INT-PREPARE
Format spec 0.2 · profile intentset/outcome/0.2

Measure

Success is judged two ways: teachers spend less time preparing an assignment, read by an observed task study, and more assignments are scheduled ahead of the day they open, read from product analytics. Each has a measure record under this outcome with its metric, baseline, target, window and source; both are read 90 days after the pilot.

Everything below is derived: the Atlas reads it from this record and the others, and none of it is written in the file.

Linked from other records

The links other records write to this one, read the other way (Core §5).