Journal · 10 min · Helen Marlowe
Instrumentation reviews before you ship
Screenshots of a staging dashboard are not a review. A review is a conversation with engineering that produces a punch-list: what will fire, what will be null, and what you are willing to live without. In the Product Telemetry Studio this is week five. You can steal the hour-long version immediately.
The hour
Bring the ticket, the event list, and one person who can change the code. Walk the user path once. For each event, ask four things: when it fires, what identity it carries, which properties can be missing, and whether a second platform will name it differently. Write the answers in the ticket, not in a side document that will rot.
If a property is “nice to have,” delete it from the release. Nice-to-have properties become null-filled charts that train the organisation to ignore missingness.
Refuse a few things
Refuse events that fire on render and on click for the same action. Refuse user ids that change when the app is backgrounded. Refuse a funnel that includes a step the user cannot fail because the UI skips it. These refusals feel petty until you try to explain a 98% conversion rate to a sceptical CFO.
After the hour
You should have a list of no more than eight items, each with an owner. If you have twenty, you did not prioritise; you transcribed anxiety. Ship with the eight. File the rest as a follow-up with a date, not as a “phase two” that never arrives.
Typical turnaround when Appvertexhub marks a review for a Circle Retainer is twelve days, because we wait for a build we can actually open. A review of a Figma file is a conversation about intent, not telemetry.