> [!tldr] Accumulation of little solutions ends up being a problem. Observation across all domains: - There's a problem. You solve it by adding something. - There's a problem. You solve it by adding a 2nd thing. - There's a problem. You solve it by adding a 3rd thing. - ... - There's a problem. All thing things you've added are too much [[Overhead]]. The issue of accumulated addition without subtraction pops up all over the place. [[Minimalism]] is largely about avoiding this trap.[^1] [[Enterprise Architecture]] is largely about this. [[App Rationalization]] is all about this. > our bias drives us to add band-aid after band-aid, until the only choice is to destroy the whole system and start from scratch. > -- Steph Argo **Solutions:** - [[One In, One Out]] is a [[Minimal Stuff]]-flavored solution to this problem. - The same technique can be used to defend against calendar accumulation and process accumulation, though. - [[Make the Decision that Informs all Subsequent Decisions]] can help - e.g. "we use Apple products" can reign in proliferation. - This is where [[What is a Strategy|strategy]] comes into play. [[Architecture is about Picking the Problems You'll Solve]]. - [[Living with the problem can be the right solution]] - as in, don't solve the little problems to have those solutions accumulate **** # More ## Source - experience - Also just found this relevant post - https://stephango.com/remove [^1]: I just added this to "[[System Traps]]".