Somebody changed something, and nobody wrote it down
It is rarely sabotage and almost never a deploy. It is a price, a setting, a flag, a republished page, changed by someone who was right to change it and had no reason to announce it. Here is how to find what it was, and why the record you needed never existed in the first place.
Something is behaving differently, and everyone is certain they did not touch it. That sentence is usually true and almost never means nothing changed. It means nothing was deployed, which is a far smaller claim, because most of what can alter production never goes near a deploy.
Why nobody told you
The instinct is to look for carelessness. It is almost never that. The changes that are hardest to find share a specific profile:
- They were legitimate. A founder testing a price, an ops hire correcting a tax rule, support issuing a coupon, a marketer fixing a typo on the pricing page. Everyone did their job.
- They took fifteen seconds. Nobody writes a changelog entry for something that took fifteen seconds, and no process asks them to.
- They happened outside engineering. The person who made the change is often not in the channel where the incident is later discussed, so they never hear the question that their change answers.
- Some of them had no person at all. An app that auto-updated overnight, a vendor changing their own platform. There is nobody to ask, which is why these take longest.
Where to look, in the order that finds it fastest
Deploys last, deliberately. They are the best recorded changes you make, which is exactly why they are rarely the mystery.
- Billing and pricing. A price, a coupon, a trial length, a tax setting, a webhook endpoint. Highest stakes, editable in a dashboard, immediate effect on real money. Stripe keeps a thorough record of this; it is just organised per object rather than as a timeline.
- Feature flags. A flag exists to change behaviour without a deploy, so it is the single most likely non-deploy cause and the easiest to forget. Check the actual current percentage, not the one you remember.
- The CMS or storefront. A republished page, a changed offer, a removed button, a theme edit. Often attributed to a person, in a tool engineering never opens.
- Apps and integrations that update themselves. Nobody installed anything. It updated on its own schedule. Because there is no human actor, this will not appear in any log you search by person.
- The platform underneath you. We counted: Shopify shipped a change on 55% of last year’s working days, touching checkout or payments every two days. “Nobody changed anything” is a statement about your team. It was never a statement about your stack.
- Then deploys. By now you have usually found it.
Two questions that shorten the search
When exactly did the behaviour change? Not the day, the hour if you can get it. Almost every investigation collapses once you can name a six hour window, because the list of things that changed in six hours is short enough to read.
Who is affected? One country points at shipping, tax, currency or payment availability. One device or browser points at a front-end or theme change. One traffic source points upstream, outside your stack entirely. Everyone, evenly, points back at billing, flags or the platform.
Making the next one take ten minutes
The fix is not more discipline, it is a record that does not depend on discipline. One list, in time order, of every production-affecting change across every tool, that anyone can read without permissions to five admin panels. Once that exists the investigation stops being archaeology and becomes a lookup: what changed in the six hours before the number moved?
You can start it by hand today, in a channel or a shared document, and it genuinely works. Be warned that it usually dies within about a month, for the same reason the change was never announced in the first place: the effort falls on the people with the least reason to make it.
Where Rearview fits
Rearview builds that record automatically. Changes from Stripe, your CMS, your feature flags, your storefront and your deploys land on one timeline, and anyone on the team can ask it in plain English rather than needing an account in every tool.
Related reading: when a conversion rate drops and nothing changed, tracking feature flag changes, and tracking Stripe pricing changes.
Never wonder “what changed?” again.
Rearviewputs every production change on one timeline, so anyone on the team can ask. Join the waitlist and we'll let you know when it's ready.
Get early access →