It occurs to me that the practice of [[Enterprise Architecture]] shares certain fundamental elements with the practice of [[Minimalism]]. > [!NOTE] Addition By Subtraction > - applies to both things In both cases you're: - avoiding [[Simplicity|Complexity]] - seeking to have **fewer non-valuable things** to manage and maintain. - investing highly in those few things that **are worth** investing highly in - reusing what you have rather than simply getting something new for the sake of new things - simply _knowing_ what is important and worth investing in and being able to discern it from the rest It feels like practices from minimalism could be useful in the EA space: - **[[One In, One Out]]** - if you onboard a new tool, mandate that some other tool be end-of-lifed - **[[Packing Party 📦]]** - a watered down approach, you could simply _shut off_ any APIs, reports, wiki pages, or tables that you think might not be getting used - and leave a stub saying "if you used this resource, let us know"... then turn on those things that end up getting used. After ~6 to 12 months, if nobody's used it, fully archive/remove the thing. ...and if you're anal enough practices from EA could be useful in your minimalist lifestyle: - Create [[Business Capability Models]] for what you like doing in your life, ensure you're investing in those things appropriately and _not_ investing in other things that don't deserve it - Create [[Principles Index|Principles]] ala the [[CSVLOD]] model **** # More ## Source - self