Separate domain complexity from interface complexity
Technical terminology, dependencies, and edge cases may be unavoidable. Repeated controls, unclear hierarchy, and fragmented navigation are not. Start by removing complexity the interface created itself.
Organize around questions
Users rarely arrive thinking about modules. They arrive with questions: what changed, what needs attention, or what should I do next? Structure information and actions around those questions before exposing system architecture.
Reveal power through context
Progressive disclosure works when advanced options appear at a predictable point in the task. Hiding everything behind generic menus creates mystery, not simplicity. Preserve the context users need to understand consequences.