Build a decision-ready storefront backlog
Keep evidence, problems, proposed actions, owners, and decisions in one usable queue without turning every observation into a project.
Skip this if A short list controlled by one operator, where maintaining extra fields adds more work than clarity
Keep one storefront backlog that tells the next operator what was observed, why it matters, and what decision is due. It is not an “opportunity database,” and it is not a list of fixes pretending to be evidence.
The decision is whether a finding enters the queue, needs evidence, duplicates an existing problem, or should close.
The rest of this lesson is available once the Atlas is unlocked.