Work clarity
Which Numbers Can You Stop Checking Every Week?
Published by OneCell
Move an optional number out of your weekly check when it does not help answer the decision you are making there. Keep the figures and context that could change your next action. Preserve the underlying records and any required reporting: simplifying one review does not mean deleting its evidence.
Start with a review you already do. You do not need a new dashboard or a fixed quota of numbers. The useful change might be removing one field from one part of an existing report.
Name the decision before removing a number
“Review the numbers” leaves the purpose open. “Do we have evidence that another class is worth investigating?” gives you something to judge each number against.
Innovations for Poverty Action’s dashboard guidance, written for organizational monitoring, distinguishes a report from a view intended to guide a decision. A broad report can remain useful even when you need fewer fields for a particular operational check.
For each field you currently read, ask what you would do differently if it changed. If it supplies necessary context, such as a date or capacity, keep that context too. If you cannot name a use in this check, consider moving it to reference material rather than repeatedly reading it.
Work through one crowded weekly update
Consider Lina, a fictional class coordinator. She is checking whether an additional class is worth exploring. The current class has 40 places. Her update contains:
34 confirmed registrations: each allocates one place in this class, after cancellations have been accounted for.
0 waiting-list requests: nobody is currently recorded as requesting another date.
6 unconfirmed inquiries: messages that still need a response. These are not confirmed places or necessarily six different people.
1,200 registration-page views: views recorded over the previous seven days, not a count of people requesting a class.
The registration and waiting-list counts are checked as of Monday at 09:00. There are 40 − 34 = 6 places remaining. Those counts describe the current position; they do not predict who will attend or whether more people will ask.
Lina can keep a shorter capacity check: 34 confirmed out of 40; 6 places remaining; 0 requests for another date; checked Monday at 09:00. She keeps the six inquiries in the response queue she already uses, where they can receive an answer. She does not add them to the confirmed total.
She removes page views from this capacity check. The figure alone cannot establish a need for another class. She retains the original traffic report and any reporting commitments attached to it. This is a change to what she reads during this particular check, not a decision to erase traffic data.
Her immediate work is to respond to the inquiries and keep the actual registrations and requests current. The existing counts alone do not settle whether an additional class would be useful.
Change the action when the position changes
Now change the fictional case. By Thursday, all 40 places are confirmed and 12 distinct people have actively requested another date. Lina verifies that these are requests for an additional session, separate from the current bookings.
That gives her a reason to investigate an option. She checks teacher availability, a suitable room and possible dates, then asks whether the requesters could use the proposed date. Twelve requests are still not twelve confirmed bookings or approval to schedule a class.
The shorter review has kept the information that changes this next step. Checking it only once a week may now be too infrequent: Lina needs to review new bookings and requests as they arrive through the process she already uses. “Weekly” is a starting routine, not a rule that overrides the timing of the decision.
Bring a field back when the question changes
Suppose Lina later asks how people find the registration page. The traffic report she set aside becomes relevant again. She can examine the available source information alongside registrations, using clear periods and definitions. Page views alone still do not show how many people booked or why they chose the class.
The Department for Education’s service-performance guidance recommends combining measures with other evidence when making service decisions. In its government-service context, it also cautions against treating an activity measure as direct proof of success. A smaller operational check should leave room to investigate information outside it.
Remove one optional field from your next review
Write the question at the top. Use a decision you can act on, such as whether to investigate another session.
Keep the necessary inputs and context. Check definitions, dates and any missing information before interpreting a count.
Move one unrelated field out of this check. Retain its source and note what question would make it useful again.
Keep obligations visible. Leave contractual, regulatory, safety and other required monitoring with the people and processes responsible for it.
Choose when to look again. Use the next relevant change or deadline. Reconsider the omitted field when the question changes.
For Lina, that note can be a single line beside the existing update: “Page views remain in the traffic report; excluded here because this check is about available places and requests for another date.” She can explain what changed without maintaining a second reporting system.