How to record what you've learned, how verification works, and when to use measurements.
An Update is a piece of evidence attached to a Model item. It can be an observation, a metric you noticed, customer feedback, an experiment result, a document, research, or feedback from a meeting.
The point of an Update is not to repeat the plan. It’s to record something concrete that helps you judge whether a Goal, Constraint or Move is real, changing, or worth revisiting.
A useful Update says what was actually observed in plain language.
Good examples include:
That kind of evidence is more valuable than simply restating intention, such as “we’re still working on this”.
Each Update can carry a verification status, so people know how much weight to put on it:
You can also note where the evidence came from and when it was observed.
Separately from narrative Updates, a Model item can also carry one tracked measurement.
This is the quantified number you want to watch over time, with a clear target. You can also add:
You then add fresh readings over time so the trend becomes visible.
The difference is simple:
You will often want both. The measurement tells you whether the number is moving. The Updates explain what may be causing that movement, what people are seeing, and why the result matters.
Ask AJ
“Log this customer feedback as an Update against that Constraint.”
“Set a measurement for this Move and record today’s reading.”
Read next: Viewing a summary
Related: Working with Moves · Updating the model