Writing / Operating note

One page · four lines · one decision

What we looked at each week

This is the review, not a dashboard product. Four lines, then one change to the week’s plan. If a line has no owner, it is not a plan. The figures below are the public record, filled into the same four lines.

The four lines

Filled from the public record

$0.03cost per active user per year, after $2.15 per month
~2 wkcycle, from about four months
~10%rewrite remaining, from a full rewrite pass
Course, first sitting89%
Adoption on this line was practitioners through the course, partners live, and anything waiting on a missing owner. 30 paying partners. 30+ practitioners finished.
  1. Cost. Variable platform cost per active user, against the last figure.
  2. Cycle time. Days from scoped work to a release a person approved.
  3. Quality. Defects found in the build and screen checks before release, and support contacts that were the same question again.
  4. Adoption. Who is through the course, who is live, and what is waiting on an owner.

The decision at the bottom

The note ends with one change: stop, narrow, or staff. At NRTR this review sat with roadmap and money. At Sigil42 the same page covered sprint scope, release readiness, and whether an install was still worth keeping. At Anschutz the equivalent was which study was blocked, who had the next action, and which repeated ticket had already been written down as a procedure.

Blank form

LineThis weekOwner
Cost
Cycle time
Quality
Adoption
Change to the planStop, narrow, or staff