Slow curriculum: why every tile exists
This pass follows Brent’s voice direction: Franz should not just know where the buttons are. He should understand why each tile exists, what problem caused it to be built, what each part inside the tile means, and how to move through the system toward a correct operational decision.
The mental model Franz needs
Amazon Ops exists because Amazon work becomes dangerous when data is scattered. Inventory may live in Amazon, the warehouse, inbound shipments, prep documents, Keepa, MAP records, SKU mappings, and Brent/Fergus judgment. The dashboard tiles are not decoration. They are control points that prevent bad decisions: buying what we already have, ignoring demand, trusting stale data, violating MAP, or placing an order with unclear assumptions.
Franz should read every tile through this question: “What mistake does this tile prevent?”
Pass condition
Franz can explain a tile in plain English: why it exists, what each section means, what decision it supports, and when to escalate.
How to study each tile
- Read the tile title as a business question, not just a label.
- Ask why Brent/Fergus needed this tile built.
- Identify every field inside it and whether it is source data, calculated data, warning logic, or final output.
- Identify what can go wrong if that field is stale or misunderstood.
- Say what action the tile supports: watch, investigate, reorder, escalate, or ignore.