Heckel’s law is a principle that states how users will tolerate complex interfaces if the product offers high value. UX (user experience) designers must balance usability with functionality to ensure user satisfaction and be careful to prevent unnecessary complexity in the UIs (user interfaces) they create.
“The quality of the user interface of an appliance is relatively unimportant in determining its adoption by users if the perceived value of the appliance is high.”
— Heckel’s Law (cited by Technical Consultant, Nigel Derrett)
Explore how to balance simplicity with complexity in this video, featuring some fascinating insights from Morgane Peng: Designer, speaker, mentor, and writer who serves as Director and Head of Design at Societe Generale CIB:
Paul Heckel, a software designer active since the 1960s, authored The Elements of Friendly Software Design in 1984. This book laid the groundwork for user-friendly software with its emphasis on clarity, consistency, and designs that align with how people think. For no small reason, then, Heckel’s work continues to influence UX and UI practices far into the twenty-first century. Designs may have become more sophisticated, but the core principle that they need to communicate effectively with—and match the mental models and expectations of—users with real-world needs remains constant, and it will continue to do so as long as brands offer products to users.
While Heckel himself didn’t coin a formal “law,” the term Heckel’s Law later appeared in a 2004 academic paper by Nigel Derrett. Derrett drew on Heckel’s ideas to explore how users engage with complex systems—focusing on the bassoon, a notoriously difficult musical instrument. Despite its intricate design and steep learning curve, the bassoon remains a favorite among musicians because it offers exceptional expressive power. They tolerate its tricky nature and hard-to-access mastery because, to them, it’s worth the bother (time, effort, and maybe even tears). Derrett concluded that the usability of a product’s interface might not be the primary factor in its adoption if users perceive the product’s value to be high. So, if people want or need something badly enough, they’ll typically put up with flaws—within reason—and adapt to it.
For UX and UI designers, Heckel’s law provides a useful lens for thinking about the trade-offs between usability and functionality—or simplicity and utility—in whatever they design. It shows that while intuitive interfaces are ideal, they’re not always necessary for user adoption—especially when the product offers substantial or unique value. If users can achieve some meaningful end which they couldn’t with a “lesser” item, the product they’ve chosen to invest their time and effort in has high-value features—and they’ll be more forgiving of a complex interface. While Derrett’s study of the bassoon presents an intriguing angle—an “analogue” item—consider some examples of interfaces that illustrate Heckel’s law:
Linux Operating Systems
Distributions like Arch Linux or Debian often call for manual configuration and terminal commands, and they appeal to advanced users and system administrators. They’re not quite so beginner-friendly, but power users love them for the control, customization, and performance they offer.
Microsoft Excel (Advanced Use)
While basic spreadsheets are easy to use, Excel’s advanced features—like pivot tables, nested formulas, VBA scripting, and Power Query—call for significant learning. Nonetheless, professionals in finance, engineering, and analytics rely on Excel because of its powerful capabilities. Even when alternatives exist, the ecosystem and depth of Excel keep it entrenched as a desirable asset and mainstay of the business world.
SAP ERP Systems
SAP is one of the world’s most widely used enterprise systems and figures significantly in resource planning. It’s known for being difficult to use and navigate, but its strategic value, customizability, and ability to support complex business processes make it indispensable. Organizations invest in training because the payoff is worth it; the system’s value is high and indispensable.
SAP S/4HANA Cloud represents the culmination of many years of innovation and refinement.
© SAP, Fair Use
For a helpful way to grasp why Heckel’s law is important, consider how it sits alongside other important laws for designers to know—and apply—such as:
Hick’s law: The more options users have, the longer it takes them to pick one.
Fitts’ law: Larger and closer targets are easier to reach and select than smaller and farther-away ones.
KISS (Keep It Simple, Stupid or Keep It Simple and Straightforward or Keep It Short and Simple): The easier something is to understand and use, the more likely it is that users will adopt and engage with it.
What makes Heckel’s law particularly valuable for designers is how to understand the limits of tolerance that users will—or will be able to—have. If the interface hinders the user’s ability to access the product’s value, there’s a chance they’ll become frustrated and abandon it. In the commercial world where people often have countless alternatives and can dismiss products quickly and easily, this can be a major problem for a brand that doesn’t appreciate this “balance.” However, what about areas where “high value” or “unique use” are life-or-death matters? Consider two scenarios where a user interface must not hinder the users’ ability to access the “value” of a product (the device a user must use):
1. Aviation Systems
Airline pilots go through rigorous training, including in simulators, before they ever take control of a real cockpit. Aircraft systems are intentionally complex—and need to be with so much at stake—designed with redundant controls and fail-safes to ensure safety under any circumstance. The lives of passengers, crew, and people on the ground (in a potential accident zone) depend on that intricately strung system of safety nets, and the pilot’s and co-pilot’s expertise and judgment are vital. Here, the value is control, precision, and trust in critical situations; with so much skill and so many back-up systems guarding them, passengers can focus on other things, like their destination.
Takeoffs and landings particularly demand immense judgment—and levels of control.
© Rafael Cosquiere, Pexels
2. Nuclear Control Rooms
With great power, there must come great control—perhaps no setting can illustrate that more than nuclear power stations. Seven years before the notorious Chernobyl incident, another disastrous chain of events unfurled and would haunt the American nuclear power industry for decades. The Three Mile Island incident in 1979 remains a tragic case study in interface design gone wrong. There, a combination of equipment failure, unclear indicators, and human error led to a partial meltdown. Well-trained, competent operators misread the system, not realizing a stuck valve was causing the core to overheat. When systems are this complex, users must have the power to make the right decision at the right time—hence why UX design is mission-critical in contexts like these.
Explore vital points about UX design and more—including the Three Mile Island disaster—with Don Norman: Father of User Experience design, author of the legendary book “The Design of Everyday Things”, and co-founder of the Nielsen Norman Group, in this video:
Jerome Bruner by Poughkeepsie Day School (CC BY-NC-SA 2.0)
https://www.flickr.com/photos/poughkeepsiedayschool/10277703145
Three Mile Island by Nuclear Regulatory Commission (CC BY 2.0)
https://www.flickr.com/photos/nrcgov/17674734289
TMI-2 Control Room in 1979 by Nuclear Regulatory Commission (CC BY-NC-ND 2.0)
https://www.flickr.com/photos/nrcgov/7447591424
Stevens, Stanley Smith by Mark D. Fairchild
Fairchild M.D. (2016) Stevens, Stanley Smith. In: Luo M.R. (eds) Encyclopedia of Color Science and Technology. Springer, New York, NY. https://doi.org/10.1007/978-1-4419-8071-7_314
This is a photograph of B.F. Skinner. by Msanders nti (CC-BY-SA-4.0)
https://commons.wikimedia.org/wiki/File:B.F._Skinner.jpg
EDSAC by Copyright Department of Computer Science and Technology, University of Cambridge. Reproduced by permission.
https://commons.wikimedia.org/wiki/File:EDSAC_(12).jpg
Two pieces of ENIAC currently on display in the Moore School of Engineering and Applied Science, in room 100 of the Moore building. Photo courtesy of the curator, released under GNU license along with 3 other images in an email to me.
Copyright 2005 Paul W Shaffer, University of Pennsylvania. by TexasDex (CC-BY-SA-3.0-migrated)
https://commons.wikimedia.org/wiki/File:ENIAC_Penn1.jpg
Biblioteca de la UCSD by Belis@rio (CC BY-SA 2.0)
https://www.flickr.com/photos/belisario/2700271091/
This is an image of a place or building that is listed on the National Register of Historic Places in the United States of America. Its reference number is 78002444. by Bestbudbrian (CC-BY-SA-4.0)
https://commons.wikimedia.org/wiki/File:North_facade_of_College_Hall,_Penn_Campus.jpg
Atkinson Hall at the University of California, San Diego, housing the Qualcomm Institute—the UC San Diego division of the California Institute for Telecommunications and Information Technology (Calit2) by TritonsRising (CC-BY-SA-4.0)
https://commons.wikimedia.org/wiki/File:Qualcomm_Institute.jpgProfessional tools like Adobe Photoshop illustrate Heckel’s law in everyday tech. It’s feature-rich but complex—and still, creatives around the world invest time and effort into learning it because they believe nothing else offers the same level of control and creativity. On the flip side, a clunky photo app with a confusing interface but limited functionality is likely to get deleted within minutes, even after just a glance at the UI. Value must justify effort.
For UX designers, this means that while it’s essential to strive for intuitive and user-friendly interfaces, it’s just as important to make sure that the product delivers substantial value to its users. When users recognize the benefits they gain from a product, they may be more willing to overcome usability challenges and put up with minor “inconveniences” to become proficient with it. Even so, designers should aim to minimize these challenges to enhance the overall user experience—there’s no room for complexity for complexity’s sake; empathy becomes a powerful keyword in this light.
Explore why empathy must figure in design from the outset, so users feel the product and brand truly caters to them, in this video:
To effectively apply Heckel’s law in UX design, follow these guidelines:
Conduct user research and do it well, so you can collect insights into user needs, preferences, mental models, and pain points—through surveys, interviews, and observations. Pick quantitative and qualitative research methods that you can apply well—and appropriately—to users in your target audience. Build strong foundations from solid insights you get from research methods into users—who these people are, what they face regarding problems or obstacles to what they want to do, and the wide range of concerns and pressures they have to deal with in their everyday lives. Interpret your findings well—and you’ll have a rich tapestry of minute details that can show you accurate pictures of where you may need to go with a digital solution or service.
Get valuable insights about the difference between qualitative and quantitative research, both essential ways to learn about users, as William Hudson, User Experience Strategist and Founder of Syntagm Ltd, explains:
Create user personas to guide your design decisions towards better outcomes for your product, your brand, and the users who should come to trust it as a go-to name. Personas are fictitious representations of real users; when you develop detailed profiles representing different user types, you can proceed more confidently on firmer foundations of what users are really like—and how they’ll use (and appreciate) your potential design solution.
Watch as William Hudson explains why design without personas falls short:
Identify essential features for users—which features are most valuable to them in their contexts of use—and focus on optimizing these elements for them.
Simplify user flows to smooth the way for users. Design intuitive pathways for them to accomplish primary tasks efficiently—learn how they expect to be able to move across a journey with your product and brand and get what they need or want to do done.
Hide complexity and reveal advanced options as needed: When you present basic features upfront and reveal advanced options only when users actually want or need them, you lower the potential for overwhelm; too much too soon can put many users off.
Use tooltips and help guides to keep users from becoming confused or frustrated. When you provide contextual assistance to help users navigate complex features, they’ll value that in-the-moment help and trust your brand more as one that understands them and has their interests at heart.
Learn how to leverage progressive disclosure in this video:
Use consistent design patterns and familiar UI elements to reduce the learning curve—well-chosen design patterns can help users get up to speed without any moments of confusion souring their experience. Help users recognize rather than recall cues to speed them on their way to their goals.
Explore how to employ UI design patterns to help your interfaces reach users so they enjoy seamless user experiences with your product and brand.
Include interactive tutorials to lessen the risk of overwhelming users. Offer guided walkthroughs to help them understand how to use the product effectively and without confusion. You can shed light on the complex features they’ll need in a natural way, so they can take the right actions at the right times without breaking the seamless experience between themselves and your product. It only takes a moment of hesitation for users to start doubting (and distrusting) your product, so keep them on board and prevent that.
Include a strong visual hierarchy and use design elements well—including color, size, and spacing—to guide users’ attention to important features; design in line with how their eyes will actually encounter what you intend to present for them.
Give users fast access to what they want to see—design for reading patterns like the F- and Z-patterns.
© Interaction Design Foundation, CC BY-SA 4.0
Use responsive design so the interface adapts seamlessly across different devices and screen sizes—“flowing” from screen to screen in a way that preserves your brand image and matches their expectations and needs whatever the device.
Watch Frank Spillers explain responsive design and its benefits:
Cater to user preferences to help make it a “preferred” product for them. Let users customize the interface to suit their workflow and preferences; they’ll want to do this especially when the functionality divides between what new users and experienced ones find most useful. Follow your research findings to see what power users would prefer, while novices can enjoy a simpler seamless experience—all within the same product.
Use modular design to keep design needs straightforward. Design components that are rearrangeable or modifiable according to what user needs tell you.
Conduct usability testing well and establish any issues that arise—and keep an open mind without bias. Observe users as they interact with the product and identify areas of confusion or difficulty; their actions will often teach you more than their words can. Approach them with a humble mindset and beware of the Hawthorne effect; they may act unnaturally if they feel “watched” and end up distorting how usable your product actually is.
Use analytics tools so you can track user interactions to spot which features they use most and any places they run into difficulties.
Apply performance metrics to get the figures out in the open. Measure task completion rates, error rates, and user satisfaction to assess usability and gauge your product’s effectiveness.
Discover what analytics can do for you as William Hudson reveals key benefits and more in this video:
Author: Stewart Cheifet. Appearance time: 0:22 - 0:24. Copyright license and terms: CC / Fair Use. Modified: Yes. Link: https://archive.org/details/CC1218greatestgames
Employ iterative design and keep making adjustments according to what users tell you—through their actions as well as words—through testing. When you continuously refine the interface based on user feedback and testing results—and keep going until tests reveal that you’ve smoothed out the kinks—you can craft the most effective digital solution.
Provide documentation to show you understand your users’ needs, prevent their confusion, and stay ahead of the game. When you give users comprehensive guides and FAQs to help them understand complex features so they can use them as they need or want to, you increase the chances that they’ll enjoy seamless experiences.
Nurture community support and prove your brand cares about its users and the impacts of using its product. Foster user communities where individuals can share tips and solutions; apart from anything else, it will take pressure off your brand’s technical support line—although it’s vital to identify and minimize potential problems in the first place.
Future-proof your interfaces so any products you design can enjoy long “shelf lives.” Design interfaces that can accommodate additional features without compromising usability—your product may last for many years to come, so provide for changes without the need for major overhauls.
Create modular architecture to reduce the need for extensive overhauls, too. Develop a flexible system that permits easy updates and enhancements, and your digital solution should be able to keep helping users long into the future.
The bassoon example might imply one of the reasons some people prefer “difficult” things is that they are complex—and some designers might infer that users can find harder-to-use interfaces “cool” or a status symbol. After all, to outside eyes, developers often seem to dwell in a niche where skillset can lend itself to a type of “culture.”
With its complex key system, double reed, and other peculiarities, the bassoon is notoriously hard to play.
© Alexander Zvir, Pexels
However, remember that users are people—human beings who come from many backgrounds, encounter products in various contexts, and often don’t have the luxury of taking time to learn the intricacies of a product or service. For example, a stressed person who needs to purchase airline tickets in a hurry will appreciate being able to do so with minimum “detours” to find information or functionality. While Heckel’s law acknowledges that users may accept complex interfaces for high-value products, always strive to minimize unnecessary complexity. Designers who overcomplicate interfaces can cause user frustration, decreased productivity, and potential abandonment of the product.
Another vital point is that designers need to consider accessibility and ensure that individuals with varying abilities can indeed use interfaces. Accessible design essentials include keyboard navigation, screen reader compatibility, and sufficient color contrast—and many users with disabilities also use assistive technology to access and enjoy digital products.
Discover vital aspects of design in this video about accessibility:
Overall, user-friendliness needs to figure in design, however specialized the target audience may be. Extensive training and vocational know-how can’t overwrite the primary need of people who encounter interfaces to reach for controls and get something done, quickly. Heckel’s law deserves its place in the toolbox of UX design for that reason.
Heckel’s law teaches that complexity isn’t always the enemy—so long as it leads to meaningful value. However, that doesn’t give designers a free pass to ignore usability—the idea is to earn users’ time and trust, not waste it. Designers who understand how users think, feel, and behave—especially under pressure—can build products that are powerful, purposeful, and truly people-centered as well as desirable. Heckel’s law belongs in every designer’s toolbox—not to justify complexity, but to help designers recognize when it’s worth it. After all, if a product is to stand high above others in the marketplace, the people who take the trouble to reach its “summit” must feel rewarded for the effort to get there.
Discover valuable points about users and design in our article Negative Emotional Responses.
Want to know more about personas and how to use them effectively? Personas and User Research: Design Products and Services People Need and Want will show you how to gather meaningful user insights, avoid bias, and build research-backed personas that help you design intuitive, relevant products. You’ll walk away with practical skills and a certificate that demonstrates your expertise in user research and persona creation.
Explore additional insights in the Made in Tandem article Emotional Design: How to Create Products People Will Love.
Find further details and tips in UX Designer Shaily Goel’s article, Heckel’s Law.
Heckel's law, derived from Paul Heckel's work, states that users will tolerate a complex interface if the product offers sufficiently high value. This principle matters a great deal in digital product design because it serves as a reminder that usability is not always about simplicity—it's about perceived benefit.
For example, take powerful tools like Adobe Photoshop, Figma, or Blender. These applications have steep learning curves and dense interfaces, but professionals continue to use them because the value they provide far outweighs the complexity. Users are willing to invest time and effort learning such tools if they believe the outcomes will be worth it.
This law emphasizes an essential trade-off: The more valuable your product is to users, the more complexity they're willing to tolerate. So, in digital product design, the goal isn't always to eliminate complexity, but rather to justify it with powerful capabilities or significant user benefits.
However, designers still must manage that complexity thoughtfully—using onboarding, progressive disclosure, and expert-friendly workflows—to ensure that value is discoverable and achievable.
Find out how to employ UI (user interface) design patterns to help your interfaces reach users so they enjoy seamless user experiences with your product and brand.
“Heckel's law says people will put up with a complicated interface if the product gives them something really valuable in return.”
Think of tools like Photoshop or Excel. They're not simple, but people keep using them because they are powerful. The key idea is that value makes complexity acceptable.
So, when designers follow Heckel's law, they don't always try to make everything super simple. Rather, they make sure that the effort it takes to learn the interface is worth it. The product has to offer clear, meaningful benefits—like saving time, unlocking creativity, or helping someone do something they couldn't do before.
The real challenge is that designers still need to make sure that the value is easy to find and access. That's why things like onboarding, tooltips, or well-designed workflows matter. Complexity is all right—as long as the payoff is big enough, or the gain in “no pain, no gain” has to be well worth the proverbial “pain.”
You might think of it like using a fancy espresso machine. It can be a little confusing, at first; however, once you learn it, you can make café-quality coffee at home. That's Heckel's law; the value justifies the learning curve, and the reward can speak for itself.
Learn about how to “get” people who don't get design in this video from Morgane Peng: Designer, speaker, mentor, and writer who serves as Director and Head of Design at Societe Generale CIB:
Heckel's law states that users will tolerate a complex interface if the product offers high value. It focuses on the trade-off between usability and perceived benefit. So, users are more willing to deal with complexity or a learning curve if they believe the outcome is worth it. Think of advanced tools like Photoshop or Figma; they're not easy to use at first, but people accept that because the capabilities are so powerful.
By contrast:
Fitts' law is about motor movement: it predicts how long it takes to move to a target based on its size and distance. It helps designers decide how big buttons should be and where to place them for efficiency.
Hick's law is about decision-making time: the more options users have, the longer it takes them to choose. Designers use it to reduce clutter and simplify user choices.
So, while Fitts' and Hick's laws are focused on optimizing physical or cognitive efficiency, Heckel's law is about value perception. It doesn't demand simplicity—it says complexity is acceptable if the product delivers clear, meaningful rewards.
Pick up tips and insights into how to make users' journeys even better in the article Hick's Law: Making the choice easier for users.
Heckel's law concerns how users are willing to tolerate complex interfaces when they believe the product delivers enough value. This insight directly ties in with user motivation: when people feel a tool is powerful or essential to achieving their goals, they're more focused, patient, and determined—even if the interface isn't simple at first.
In these cases, motivation drives sustained attention, especially during the initial learning curve. For example, users of Photoshop, Excel, or Blender are often motivated by professional or creative goals. That high perceived value encourages them to explore, learn, and master the complexity.
When designers apply Heckel's law, they don't necessarily aim to remove complexity—they work to ensure that the value is obvious and accessible early. Smart onboarding, clear benefit communication, and progressive feature exposure help users feel that the effort they invest is worthwhile.
So, Heckel's Law doesn't say, “make it easy”; it says, “make it worth it.” And when something is worth it, users stay engaged—even when it's hard.
Enjoy our Master Class Conceptual Models: A Guide to Intuitive Design with Jeff Johnson, Assistant Professor, Computer Science Department, University of San Francisco.
Heckel's law suggests that users will tolerate a complex interface if the product offers them enough value. That means when designing a rich or feature-dense product—like a professional tool, analytics dashboard, or creative suite—you don't always have to oversimplify the UI. Instead, focus on helping users discover the most valuable parts of the product quickly and clearly.
For navigation or layout prioritization:
Surface the high-value actions early: Prioritize features that deliver immediate or essential value. For example, in a design tool, that might mean emphasizing “Create New Project” or “Upload File”—the actions that move users toward their goal.
Use visual hierarchy to reinforce that value: Make high-utility elements more prominent through size, color, placement, or contrast. This encourages exploration where it matters most.
Accept some complexity—but guide it: If your product contains advanced capabilities, group and reveal them logically (e.g., tabs, dropdowns, or progressive disclosure). Users who see value will dig deeper—as long as the interface helps them find what matters.
Include scaffolding where appropriate: Even in complex systems, users shouldn't feel lost. Labels, icons, tooltips, or brief onboarding can help bring the product's value to the surface without dumbing it down.
For instance, tools like Notion, Figma, or DaVinci Resolve have layered interfaces, but users stay engaged because the layout helps them quickly see how those layers lead to powerful results. Don't hide complexity—just make the reward worth the effort.
Discover how to get your interface's visual hierarchy to not only match what users expect to see but also delight them in a seamless experience.
Heckel's law suggests that users will tolerate a complex interface if the product offers high enough value. This principle is especially relevant for power users, who often seek out advanced functionality and are motivated by depth, flexibility, and efficiency—even if it means navigating a steeper learning curve.
To apply Heckel's law for power users:
Don't oversimplify things. Power users are willing to handle complexity as long as it enables them to work faster, automate tasks, or access advanced features.
Provide customizable interfaces, keyboard shortcuts, and power panels that expose depth rather than hide it.
Allow experienced users to bypass onboarding and tutorials—but not because they demand simplicity, rather because they're already motivated to dive deeper into valuable workflows.
Surface high-leverage functionality (like batch actions, scripting, version control) that might intimidate beginners but delight expert users who value capability over ease.
Think of products like Figma, Notion, or Blender; they offer clean starting points, but power users stick around (and thrive) because the interface scales with their needs. These tools may be complex, but the value is obvious and worth the effort.
Heckel's law doesn't tell you to reduce friction—it tells you to make the friction worth it.
Enjoy our Master Class User Journey Mapping for Better UX with Kelly Jura, Vice-President, Brand & User Experience at ScreenPal and come away with a wealth of insights about users, their experiences, their expectations, and more.
Heckel's law suggests that users will tolerate a complex interface if the product offers sufficient value. In mobile design, where screen space is limited and user attention is fragmented, this principle highlights an important balance: complexity isn't inherently bad—it's only a problem if users don't see what's in it for them.
Mobile products that solve meaningful problems or offer high utility—like banking apps, creative tools, or health trackers—can afford to include more layers or sophisticated interactions, as long as the benefit is clear. Power and depth can coexist with small screens—if the user understands the reward.
So, in mobile design:
Expose core value quickly. The faster a user sees how the app improves their life or solves a task, the more patient they'll be with its complexity.
Use progressive disclosure: Start simple, but let users dig deeper when they're ready. This supports both casual and committed users.
Design for motivated workflows: if a task matters—like booking a flight, creating content, or managing money—users are willing to learn more steps, provided each one feels purposeful.
Provide scaffolding, not simplification: brief onboarding, visual feedback, and contextual help can support complex flows without stripping away functionality.
Apps like Notion, Adobe Lightroom Mobile, or mobile trading platforms often have deep capabilities and layered navigation. They succeed not by hiding complexity, but by making the value of that complexity visible and worth the user's effort.
Remember, clarity of benefit beats simplicity of layout.
Watch how to reveal a wealth of insight into user behaviors and needs from task analysis—particularly useful for mobile design—with Frank Spillers: Service Designer, Founder and CEO of Experience Dynamics.
Heckel's law is about how users will accept complexity if the product delivers enough value. So, when testing alignment with this principle, the goal is not to see if users succeed immediately—it's to see whether they're willing to keep going despite friction because they recognize the product's usefulness.
To test for alignment with Heckel's law:
Assess perceived value during usability testing. Ask participants: "Was this worth the effort?" or "Do you feel this tool helps you accomplish something important?"
Observe persistence in the face of difficulty. If users struggle but remain engaged or express curiosity, that can be a sign that the value justifies the complexity.
Measure task completion over time, not just initial success. Heckel's Law supports a learning curve—as long as users feel their effort is rewarded.
Use think-aloud protocols to listen for value signals (e.g., "This is tricky, but I can see how useful it will be once I get it.")
Combine behavioral metrics (like retries, return usage, time spent learning) with attitudinal data (satisfaction, intent to continue).
Tools like UserTesting, Lookback, or Optimal Workshop can help you capture both the struggle and the motivation behind continued use.
Remember: under Heckel's law, a design doesn't need to be frictionless; it needs to be worth it.
Take our course Conducting Usability Testing for a wealth of insights and more into the world of testing to find the best designs.
Designers ignore Heckel's law not by making interfaces complex, but by failing to justify that complexity.
Here are common design mistakes that violate Heckel's law:
1. Hiding valuable functionality to maintain surface-level simplicity
Some designers over-prioritize minimalism and strip away advanced features—or bury them—thinking users can't handle complexity. However, if those features offer value, users would engage with them.
2. Failing to show the value early
If users don't quickly understand why the product is worth learning, they may abandon it—no matter how powerful it is. They won't miss what they couldn't sense the value of.
3. Using shallow onboarding instead of guiding users to depth
Overly basic walkthroughs may explain simple tasks but don't help users see the full capability of the product. Power users, especially, may feel underserved—even patronized—and leave.
4. Overemphasis on short-term ease over long-term power
Designers sometimes optimize for early success metrics (e.g., first-click usability) and avoid exposing rich tools that users will grow into.
Examples of good alignment include apps like Figma, Notion, DaVinci Resolve, or Airtable—they may look simple at first, but offer deep, complex functionality that users tolerate and even seek out because of the value they unlock.
Ignoring Heckel's law doesn't mean making things too complex—it means failing to make complexity feel worth it. This is why user research is particularly important, and tools like personas—fictitious representations of real users—help a great deal.
Want to know more about personas and how to use them effectively? Personas and User Research: Design Products and Services People Need and Want will show you how to gather meaningful user insights, avoid bias, and build research-backed personas that help you design intuitive, relevant products. You'll walk away with practical skills and a certificate that demonstrates your expertise in user research and persona creation.
Derrett, N. (2004). Heckel's law: Conclusions from the user interface design of a music appliance—the bassoon. Personal and Ubiquitous Computing, 8(4), 208–212.
In this article, Nigel Derrett explores the user interface of the bassoon, a complex musical instrument, to challenge conventional assumptions in user interface design. He introduces "Heckel's Law"—proposing that the quality of a user interface is not the primary determinant of an appliance's adoption. Despite the bassoon's intricate and inconsistent interface, musicians invest significant time mastering it, suggesting that factors beyond interface design—such as the instrument's expressive capabilities and cultural significance—play crucial roles in user engagement. This perspective invites UX designers to consider broader contextual elements influencing user adoption and satisfaction.
Remember, the more you learn about design, the more you make yourself valuable.
Improve your UX / UI Design skills and grow your career! Join IxDF now!
You earned your gift with a perfect score! Let us send it to you.
We've emailed your gift to name@email.com.
Improve your UX / UI Design skills and grow your career! Join IxDF now!
Here's the entire UX literature on Heckel’s Law by the Interaction Design Foundation, collated in one place:
We believe in Open Access and the democratization of knowledge. Unfortunately, world-class educational materials such as this page are normally hidden behind paywalls or in expensive textbooks.
If you want this to change, , link to us, or join us to help us democratize design knowledge!
.jpg){kind=link}
