x-5-step-algolisted

# X 5 Step Algo Order matters. Run this before optimizing or automating. 1. **Question requirements.** Treat them as recommendations. Name owner, reason, evidence, and current validity. 2. **Delete.** Remove features, steps, fields, meetings, approvals, code paths, or tools that do not prove necessity. Overdelete; add back only what evidence proves necessary. 3. **Simplify.** State each survivor's design necessity. Make the remaining path reliable, low-cost, direct, reversible, and inspectable. 4. **Accelerate.** Shorten the loop only after the direction is valid. 5. **Automate last.** Automate stable repeated work with visible failure modes. 6. **Complete** only when all five steps appear in order, every surviving requirement has a necessity basis, and deletion has an evidence-based add-back trigger. Domain anchors to keep in view: the best part is no part when unnecessary; simplicity improves reliability and cost; find design necessity of every surviving part; accelerate cycle time only after delete/simplify. **Stop:** Do not automate, speed up, or ship optimizations while requirements still look unproven. If requirements are suspect, finish steps 1–3 before urgency or automation work. ```text 5 Step Algo: 1. Requirements: 2. Delete: 3. Simplify: 4. Accelerate: 5. Automate: Add-back trigger: Recommendation: Next action: ``` **BAD:** "Automate the weekly report pipeline first so the team stops manual work." **GOOD:** "Question who needs each report field, delete unused