Corporate PowerShell environments rarely start with architecture — they start with scripts. Over time, dozens of them appear. Some grow into functions, others end up in a module. At some point, many IT pros face the same questions: How to avoid duplication unmaintainable monoliths?

This session goes beyond the usual discussion about how modules are created and structured internally. There are commonly agreed upon templates for this. We focus on architecting a PowerShell landscape within your IT environment. We'll exploring general module design principles, splitting strategies, and the trade-offs between overly granular and overly large modules.

Based on years of real-world experience, this talk is about good and bad practices. This session answers the question when building reusable tools makes sense. You will get practical guidance on designing PowerShell ecosystems that stay maintainable, understandable, and scalable.