The 1 to 60 rule of product development

In aviation, the 1 to 60 rule states that if a pilot is off course by just one degree, they will miss their target by one mile for every 60 miles flown. Software development follows a similar trajectory. A single unnecessary option or a small deviation from the core user experience may seem insignificant in isolation. However, as these decisions compound over time, the product eventually misses its destination entirely.

Small deviations—like adding an edge-case setting or an extra button to the dashboard—lead to a product that is "off course." You may start with the intention of being helpful, but you end up with a "complexity monster" that confuses the very people it was designed to serve.

Identifying the complexity traps

Complexity rarely happens because of poor intentions; it happens because humans are naturally inclined to equate "more" with "better." Several common traps can nudge a product off course:

• The everything onboarding: Many products attempt to explain every feature through guided tours and tooltips. This often leads to a high drop-off rate. As noted in the discussion, one team found that only 30% of users completed a guided onboarding, while 70% got lost before they even started.
• The enterprise checkbox hell: Adding features simply to look "serious" or to match a competitor’s comparison chart creates a cluttered interface. Specialized software sometimes features toolbars with dozens of buttons that require a physical cheat sheet to navigate.
• The settings graveyard: Decisions that should be made by the developer are often offloaded to the user as "options." When you say yes to every customer request, you bury the core workflow under a mountain of settings.
• The "what if" paranoia: Teams often build for hypothetical scenarios or edge cases that rarely occur in the real world. This distracts from the needs of the 95% of users who only require the core functionality.

Strategies for radical simplicity

To maintain clarity and utility, digital marketing professionals and product leaders must prioritize outcomes over technical features.

1. Make decisions for your users

Instead of asking users to configure every detail, make the smart choice for them. For instance, an application might automatically block out travel time for meetings or set a default reminder window. As Patrick Enzinger observed, "We replaced complexity with clarity, instructions with examples, and choices with decisions." If a setting serves a purpose but hasn't caused a complaint in years, it might not need to be a setting at all.

2. Show, don't tell

Rather than using text-heavy tutorials, use the product to explain itself. Pre-filling new accounts with dummy data—such as sample invoices or appointments—allows users to see exactly how the tool functions in a real-world scenario. This "self-explaining" approach allows users to start being productive immediately rather than spending their first hour in a configuration menu.

3. Build for the 95%

It is a common mistake to optimize for the "power users" who represent only a small fraction of the user base. While these users are often the loudest, catering to their specific edge cases can alienate the majority of your customers. Success often comes from doing a few things exceptionally well rather than doing many things at a mediocre level.

The hidden cost of "more"

Feature creep feels like progress because it is easier to sell new capabilities than it is to sell a refined experience. However, the hidden costs of complexity are substantial:

• Longer learning curves: It takes users weeks instead of hours to become productive.
• Increased support burden: Support teams spend their time answering basic navigational questions rather than solving high-level problems.
• Lower adoption: Users often give up during onboarding because they are forced to make too many decisions before they have seen any value.

Evaluating your course

To determine if your product or process is veering off course, consider these three questions:

1. Can we make this decision for the user?
2. Does this help users accomplish their goal faster?
3. Would we rather explain this or show it?

Simplicity is not the absence of functionality; it is the presence of clarity. By focusing on the essential needs of the professional user and having the discipline to say no to "good" ideas that add friction, SaaS platforms can build tools that truly empower their clients to move faster and make better decisions.