Amazon's Weekly Business Review: what finance teams should copy, and what they shouldn't
I spent 2018 to 2022 in operations finance at Amazon, on the fulfillment and transportation side. Most of what made the reporting work is public. The weekly business review, input metrics, written narratives, and the annual planning cycle are described in Working Backwards by Colin Bryar and Bill Carr, and AWS has written publicly about its correction-of-error reviews.
So nothing here depends on anything internal. It’s what I’d bring to another finance team, and what I’d leave behind.
What’s worth copying
Report why the number moved
The habit I value most is that every number comes with a bridge. Plan to actual, last week to this week, broken into what moved it: volume, rate, mix, one-time items. A lot of finance reporting stops at the number and a variance percentage. With the bridge, an operator knows where to look.
Manage the inputs
Output metrics are results like cost per unit, revenue, and margin. Nobody can move them directly. Input metrics are the things a team controls that drive those results. Working Backwards describes the WBR as focused on controllable inputs, with the outputs following from them. For a finance team, that means pairing each outcome with the few drivers an operator can actually change, and reviewing those every week.
One definition, one owner
Reviews work when nobody argues about the denominator. Each metric has one definition and one owner, and it shows the same value everywhere it appears. When a definition changes, someone decided that on purpose. Plenty of teams lose review time reconciling whose report is right before they get to what the number means.
Split fixed and variable
Cost per unit only tells you something if fixed and variable costs are separated. Otherwise a volume drop looks like bad performance, and a volume spike can hide a real problem. Holding a manager to what they control starts with that split.
Write it down
Amazon uses written narratives in place of slide decks for a lot of its senior meetings. A real miss gets a correction-of-error write-up covering what happened, the root cause (found by asking why until you hit it), and what changes so it doesn’t happen again. The write-up outlasts the meeting. A verbal explanation in a review is usually gone by the next week.
Same format every week
Same deck, same order, every week, exceptions first. When something is off, the owner brings a cause and a date. With a fixed format, people read for what changed instead of relearning where everything is.
What I’d leave at Amazon
To be fair to Amazon, the parts below fit Amazon. A network that size needs a lot of metrics and a heavy planning calendar, and the intensity of the reviews is part of how it holds a very large organization to one standard. The trouble comes from copying them into a company that isn’t built the same way.
Metric sprawl
An Amazon review can cover a lot of metrics because the people in the room are trained to read them. Hand the same volume to a team that hasn’t done this and nobody reads it. Start with a short list tied to decisions the team actually makes, and add metrics once the definitions hold.
Too many planning cycles
Amazon runs an annual operating plan in the fall and updates it in January, known as OP1 and OP2. Most companies need one annual plan and a regular reforecast. Adding cycles without the people to run them leaves the forecast half-updated most of the time.
The pressure without the mechanisms
Amazon’s reviews have a public reputation for being demanding. That rigor holds up there because the mechanisms underneath are strong: clean data, clear owners, written follow-ups. Bring over the intensity without those and you mostly get defensiveness, and people managing the metric instead of the operation. I’d bring the mechanisms and let the tone match the company.
Where to start
The first half of this list works at a company of any size, and none of it needs Amazon’s systems. Pick the few numbers that matter, agree on one definition for each, give each one an owner, and add a bridge to every review. The rest can come once those hold.