Lantern, a worked example · Record
MEAS-PREPARE-ADOPTION: Assignments scheduled a day or more ahead
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 6914e830beab · level L1 · scope examples/scheduling/**
Records › Measures › MEAS-PREPARE-ADOPTION
In the model: PRD-LANTERN › INT-PREPARE › OUT-PREPARE › MEAS-PREPARE-ADOPTION
The record
examples/scheduling/MEAS-PREPARE-ADOPTION.md · View the file on GitHub
| Field | Value |
|---|---|
| ID | MEAS-PREPARE-ADOPTION |
| Title | Assignments scheduled a day or more ahead |
| Type | measure |
| Status | draft |
| Owner | team-assessment |
| Visibility | internal |
| Audiences | engineering, product |
| Revision | 1 |
| Parent | OUT-PREPARE |
| Metric | assignments_scheduled_ahead |
| Direction | increase |
| Baseline | unknown |
| Target | 60% of assignments scheduled at least one day before they open |
| Window | 90 days after pilot-1 |
| Source | product-analytics |
| Format | spec 0.2 · profile intentset/measure/0.2 |
Method
Product analytics counts every assignment scheduled in the window and the share whose scheduled time was a day or more after the time it was created. A teacher who prepares in advance schedules ahead; one working at the last minute schedules for the same day. The baseline is unknown because nothing is scheduled ahead before the capability exists.
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
No other record links to this one.