Complexity into the System

Software should be intuitive. The more features, the better—or so many product teams assume. Yet users consistently complain about feeling overwhelmed by hidden functions and endless configurations. This raises a critical question: Can complexity truly be eliminated, or does it simply shift between the system and the user—and what does the evidence tell us?

Studies

The Invention of Cut-Copy-Paste at Xerox PARC

Larry Tesler developed the concept of cut-copy-paste at Xerox PARC in 1973-1974. Previously, users had to enter complex command sequences: mark a position, execute a 'DELETE' command with target specification, then execute an 'INSERT' command with source and target locations. Tesler shifted this complexity into the system itself: the computer now temporarily stores the copied content, manages the clipboard, and handles different data types. The user simply performs three intuitive actions. This redistribution of complexity became the standard in all modern interfaces—because it moves the inherent complexity of 'moving text' away from the user and into the system.

Card Sorting Studies on Information Architecture

Since the 2000s, Donna Spencer and other UX researchers have conducted systematic card-sorting studies that empirically confirmed Tesler's Law. In a study with 120 participants, the findings revealed: Flat hierarchies (fewer clicks but many options per page) shifted complexity to the user—68% of participants felt overwhelmed. Deep hierarchies (more clicks but fewer options) required more structural logic from the system but reduced the decision-making burden: 73% found the navigation more intuitive. The key finding: Total complexity remained constant—only its distribution changed. Systems that performed more structural work were perceived as 'simpler.'

Principle

Which principle for Customer Experience Design can be derived from this? The central principle states: strategically distribute complexity by deliberately placing the burden on the system, not the user. In customer experience, this means companies must invest in intelligent backend systems, automation, and well-designed processes to enable effortless interactions for their customers. This principle works particularly well for recurring processes and standardizable workflows but reaches its limits when users consciously want to maintain control and transparency over complex decisions. The art lies in finding the right balance between simplification and user control, depending on context and user needs. The following guidelines demonstrate how to implement this principle in practice.

Guidelines

Intelligent Defaults with Hidden Complexity

Provide simple, functional default settings that work for 80% of users. Behind the scenes, build a sophisticated system that accounts for context—usage history, industry, and device type. Tuck away advanced options for the 20% of power users who need them. For example: Rather than presenting 15 sliders for image optimization, display a single 'Optimize' button. The system makes intelligent decisions automatically while offering an 'Advanced' link for users who want manual control.

Progressive Disclosure instead of complete interface

Display only contextually relevant options to users. Transfer the burden of context recognition to the system itself. Rather than presenting a form with 40 fields, show 5-7 pertinent ones based on prior inputs or user profile. While this requires the system to implement more sophisticated logic, users avoid cognitive overload. Each interaction feels straightforward and manageable.

Automation with transparent override options

Automate complex decisions while maintaining transparency and user control. The system analyzes data, generates recommendations, and explains its reasoning—allowing users to override with a single click. For example: "We recommend shipping method X based on weight and destination. View other options?" This approach enables the system to handle the analytical workload while ensuring users retain final authority.

Guided Workflows instead of free navigation

For complex processes: Guide users step by step rather than presenting all options at once. The system should understand the process logic and determine the optimal sequence, so users don't need to think about dependencies. Example: Instead of "Configure your product" (8 tabs with 40 options), use a wizard: "Step 1 of 5: Choose your use case"—the system then filters out irrelevant options.