11 parts · 2 checkpoints · 2 free / 9 member parts →
Four rows in an example weekly dashboard
TrekCup sells tumblers and PetNest sells pet supplies. These four classroom rows show what was observed, where the evidence comes from, and what the owner should check next. A weekly ops dashboard is these four, read weekly.
Practice
TrekCup: orders and delivery questions
- Observation
- UK TC-20OZ-OLIVE £42→£39; orders 46→58 and delivery-topic questions 3→11 in matching seven-day windows.
- Source and scope
- Shopify paid orders and manually classified support wording; UK, the same SKU (stock keeping unit), matching weekly windows.
- Assessment and next action
- Sample 3 questions and 3 orders. Collect evidence if the path is unknown, observe if promises agree, or assess one correction for a specific conflict.
- Owner
- Market and support leads, with one named person following up.
- Review and stop condition
- At Wednesday 11:00, inspect matching orders, questions, and customer paths; record the result and stop condition.
PetNest: page usability
- Observation
- Page event counts from three reads with one tool: 58, 54, 57, median 57. Keep orders 39→40 separate. When the count swings, check cache, sampling, consent filtering, and load timing.
- Source and scope
- Recorded tool, metric unit, device, URL, theme version, network, and time; check that conditions are comparable.
- Assessment and next action
- Repeat matching observations and check reviews, add to cart, cart, and events. Investigate one candidate script in a theme copy if needed.
- Owner
- Theme lead, involving the event owner when needed.
- Review and stop condition
- Set the next matching check time; reverse the latest candidate change and preserve evidence if functions break.
PetNest: two Flow exceptions
- Observation
- PN-1043 has empty tracking; PN-1044 has near-duplicate writes. Investigate them separately.
- Source and scope
- Each order timeline, run log, field, and receiving record; note the store time zone.
- Assessment and next action
- Inspect source, mapping, trigger, and writers. Check one action in a named small sample and verify the receiving result.
- Owner
- Automation lead; fulfillment or support owners inspect facts in their systems.
- Review and stop condition
- Set a check before the next run; stop writes and escalate if writes duplicate or business facts are affected.
One order: reconciliation across systems
- Observation
- Shopify, GA4, or ads readings differ, or a purchase event is missing.
- Source and scope
- The order’s payment, refund, market, and currency; each report’s event definition, window, and transaction identifier.
- Assessment and next action
- Record values and missing points; distinguish measurement, processing, mapping, display, or unknown. Do not change orders to align totals.
- Owner
- Operations or finance checks business records; analytics or media owners explain measurement.
- Review and stop condition
- Review according to report processing and business risk; involve the business owner first if payment or fulfillment is affected.
From release record to weekly judgment
Which signal comes first this week?
Self-check not answered
After release, check what happened during the week
Bring your change record if you completed the release-control lesson, or start here independently. TrekCup is the example tumbler store and PetNest is the example pet-supplies store. All figures in this lesson are classroom examples.
Practice
- Signal
- TC-20OZ-OLIVE moved from £42 to £39 in UK market; order growth and delivery questions rose together.
- Scope
- Compare only UK, the same weekly window, paid orders, and support records grouped by delivery promise.
- Responsible person
- Market and support leads check the records together. Involve the checkout or fulfillment owner when the problem affects their work.
- Signal
- Same device, product page, and theme version; orders move from 39 to 40.
- Scope
- Use only the recorded device, URL, theme version, time, and key product-page interactions.
- Responsible person
- Theme lead; add script or event lead only when that surface is actually involved.
- Signal
- In the classroom example, PN-1043 was paid at 11:04 and had a fulfillment update at 11:06. PN-1044 has records at 14:22:03, 14:22:11, 14:22:16, and 14:22:19.
- Scope
- Inspect the order or customer record, Flow run, workflows or apps that may write the field, and the system that received the result.
- Responsible person
- Automation lead, with fulfillment or support owners checking the records they manage.
- Signal
- System totals differ, or a paid order has no corresponding event or record in one system.
- Scope
- Same order ID, paid time, market/currency, report window, and written event definition.
- Responsible person
- Operations or finance checks the order record; analytics or media owners explain events and reports.
Series start
Member practice follows
The weekly row, signal closure, three-week case, and board dictionary live in the member workspace.
Pro · Parts 3-11 · 9 parts
Members: full exercises and records
This part includes
- A weekly row traces to real orders
- Reconcile before judging a signal
- Platform docs only calibrate scope
Pro $20 / monthYearly $16 / month
Choose a plan, sign in with your email or Google account, and complete payment. You'll have instant access to all member benefits.
- Unlock every premium lesson
- Advanced tools and member resources
- Member-requested courses and ongoing updates
- Pro community and priority support
Checking your membership…
What's the difference between monthly and yearly?
Yearly plans save you 20% with annual payment. Monthly plans offer more flexibility for short-term needs.
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
FAQ
- What is the difference between a weekly ops dashboard and a KPI dashboard?
A KPI dashboard shows order, traffic, or support counts. A weekly ops dashboard also explains how each number is counted, what it is compared against, what the next action is, who owns it, and when it gets reviewed.
- Why inspect delivery questions when orders are growing?
More paid orders do not establish that the customer experience is working well. TrekCup’s UK orders rise from 46 to 58 while delivery questions rise from 3 to 11, so the question rate moves from 6.5% to 19%; order growth hides the experience problem, which is why both readings belong side by side.
- When does a page reading deserve a place in weekly review?
When it can change an action and you can name the tool, metric unit, page, device, theme version, network, and time window.