There’s a parallel between how enterprise software is structured and office structure.

Consider a typical office building. The front desk is welcoming, possibly over-designed with marble floors and fresh flowers. It is meant to impress visitors. As you go deeper you’ll find work floors that are functional, optimized and maybe some plants to keep things human. Then the back-office areas: IT rooms and storage closets which are purely utilitarian

Enterprise software mirrors this almost perfectly.

The onboarding flow is the reception area. It is carefully crafted, user-tested, disproportionately polished. We pour resources into those first screens because first impressions matter. The core functionality is the work floor, designed for efficiency and repeated use. The admin panel is the basement server room, powerful but rarely given the same attention.

This reflects several biases. We design based on perceived importance and frequency. What’s used most often gets the most attention. But power users working in admin areas daily get interfaces that feel like afterthoughts.

The metaphor served its purpose. It gave us mental models for organizing complexity.
But software doesn’t need a front desk separated from the workspace. The admin panel doesn’t have to be a windowless back office. We inherited spatial constraints for a medium that has none.