Approval flows should follow the risk, not the org chart
Not every action deserves the same approval. A read-only lookup risks nothing. A routine update risks a little. A consequential action risks a lot. Approval flows should follow the risk, not the org chart. Which action in your product is over-approved, and which one is under-approved.
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.