Software Abandonment: Why Users Discard Digital Tools the Same Way They Abandon Architectural Space

How the science of app abandonment explains the failure of BIM projects, engineering collaboration platforms, and perhaps certain urban spaces themselves

Out of every hundred people who download a new app on their phones, only four remain active users a full year later. This is not a rough estimate but a finding confirmed across multiple studies on the mobile app lifecycle—and it is a figure that should concern anyone designing a digital tool today, whether a shopping app, a Building Information Modeling (BIM) management platform, or a smart application for managing movement within a city. Architects and urban planners, who now operate within an ever-expanding ecosystem of software—from three-dimensional design tools to contractor collaboration platforms to citizen-facing “smart city” applications—face the same dilemma confronting any digital product: why do people form a relationship with a tool, only to abandon it suddenly? The answer, as revealed by a body of research spanning information science and human-computer interaction, is far from simple. It is a cumulative outcome of factors that intersect with everything architects already understand well: fit with genuine need, ease of use, fatigue, and the alternatives available in the marketplace.

When the Tool Fails to Meet a Real Need

The deepest problem driving any user—whether an architectural designer or an ordinary citizen—to abandon a digital tool is that it simply does not solve a real problem they have. Researcher Richard Nickerson noted decades ago that many interactive systems are built in response to needs that exist only in the developer’s mind, not in the target user’s actual reality, and so they sit unused despite their apparent sophistication. More troubling still, involving users themselves in the design process does not guarantee a solution, because a system may be built to the user’s literal “specifications” while missing the essence of their actual problem. This observation closely parallels what architects encounter when they design a building or public plaza based on superficial surveys that never touch the genuine needs of the local community—leaving the plaza abandoned despite its designed “beauty.”

At the institutional level, a study by researchers Furneaux and Wade examining large organizations found that the single most important factor driving companies to replace their information systems is “capability shortfall”—the system’s inability to keep pace with evolving organizational needs. In a related vein, a field study conducted in Africa by researcher Okonkwo and colleagues found that poor functional performance of an app was among the strongest predictors of abandonment. The lesson here is clear for any engineering firm developing or procuring a digital platform: a tool that fails to update in step with shifting project needs is destined for abandonment, however polished it may have been at launch.

Poor Performance and the Collapse of Trust

The second category of abandonment reasons concerns a purely practical matter: does the tool actually function as intended? The classic complaints Nickerson documented—slow response times, system downtime, work sessions interrupted in ways that destroy user confidence—remain powerfully present in the current digital era, though they have taken on new forms. In mobile applications, a study by researcher Vagrani and colleagues points to memory and battery drain, along with incompatibility with available network infrastructure, as factors leading directly to frustration and then deletion. The absence of technical support, weak documentation, or even a service provider’s declining commitment to supporting an aging system—as Furneaux and Wade demonstrated in the organizational context—accelerates the decision to replace it.

This should be read carefully by any entity developing BIM systems or construction management platforms: a system that crashes during a critical coordination session between an architect and a structural engineer does not merely lose a moment of work—it forfeits long-term strategic trust, much as a building whose mechanical systems repeatedly fail loses its users’ confidence in it as a dependable space.

The “More Is Better” Trap: When Complexity Becomes a Burden

One of the more striking paradoxes in this body of research is that adding more features does not retain users—it can actively drive them away. Researchers describe this phenomenon as “feature overload”: the number of functions available on a platform effectively exceeds what the user needs, producing fatigue and dissatisfaction that push toward discontinued use, as demonstrated in a study by researcher Zhang and colleagues on social media platforms. In the mobile context, Vagrani points to resource consumption—processing time, battery, storage space—as the most frequently cited reason for deleting apps, and in Africa, applications are rejected outright if they consume too much of a phone’s memory.

Remarkably, complexity also intersects with how users choose a tool in the first place. An analytical study of Firefox browser extension data, conducted by researchers Zhao, Tian, and Xue, found that users who gravitate toward downloading complex applications simply because they rank highly in app store rankings are more likely to discontinue using them later—a phenomenon of “herd imitation” that afflicts consumers before it even afflicts real estate developers who mimic prevailing design “trends” without scrutinizing their fit for their actual site or users.

The Psychological Load: Guilt, Exhaustion, and Regret

Software abandonment is not merely a cold, rational decision—it is charged with complex psychological dynamics. Drawing on expectation-disconfirmation theory, a user forms certain expectations before and during use of a tool; when performance falls short of those expectations, a “negative disconfirmation” results, generating dissatisfaction that leads directly to intention to discontinue, as Zhang and colleagues’ study demonstrated. On the other hand, high satisfaction and reinforced habit remain the two strongest factors preventing withdrawal, according to a study by researcher Turel on Facebook users.

Deeper still is what a study by researcher Fu and colleagues reveals, applying a “stressor-strain-outcome” framework to social platforms: three types of overload—information overload (excess content), feature overload (excess updates and functions), and social overload (excess demands from contacts)—combine to produce what is termed “digital exhaustion,” which drives users to scale back, suspend, or completely stop using a platform. Notably, feature overload specifically amplifies the effect of the other two types—meaning that excessive updates and notifications do not merely tire the user with a single feature, but disrupt every interaction they have with the system.

In “addictive” systems that create strong habits—such as social media platforms—Turel adds another dimension: withdrawal is also driven by feelings of guilt over excessive use, and by the user’s confidence in their actual ability to quit. Paradoxically, strong habit reduces the desire to withdraw on one hand, while simultaneously generating addiction-like symptoms that produce guilt, which weakens the user’s confidence in their ability to abandon the tool—what the researcher terms a “double-edged sword.” Meanwhile, Zhao and colleagues’ study on browser extensions adds the dimension of post-adoption regret: those who adopt a tool because it is “most popular” rather than because it best fits their needs later experience regret that drives them to abandon it—a direct lesson for anyone designing marketing campaigns for real estate projects or architectural products based on “trend” rather than actual fit.

Easier Alternatives and the Critical Mass Problem

In a world crowded with alternatives and where the cost of trial keeps shrinking, “replacement”—not technical failure alone—becomes a primary driver of abandonment. A study by researchers Salo and Makkonen on mobile app switching documented a striking behavior: users actually trial between two and fifteen alternative applications simultaneously before settling on one, benefiting from low search and installation costs, the ease of app-store recommendations, and their weak commitment to a “faceless” service provider. This explains why no digital architectural platform—whether an engineering collaboration tool or a facilities management app—can rely on the user’s “default loyalty”; the alternative is only a few clicks away.

There is another category of abandonment tied to what Nickerson calls the “critical mass problem”: tools whose value depends on collective use fail if the group as a whole does not adopt them. In personal information management, Jones and colleagues document this precisely: when one member of a work team invests effort in a shared system while the rest of the team ignores it, they come to feel they are “throwing effort into a void” and stop. This mirrors exactly the reality of collaborative BIM platforms in engineering firms: a platform’s success hinges on adoption by every party—architect, structural engineer, contractor—not on one enthusiastic party surrounded by indifferent others.

Why Users Don’t Abandon: The Hidden Forces of Inertia

The flip side of this phenomenon is critically important: most “abandoned” apps are never actually deleted at all. A study by researchers Park, Eun, and Lee reveals that users hesitate to delete unused applications due to time-related, financial (coupons, points, mileage), mental, and emotional burdens, in addition to concerns about privacy and stored information. Habit, satisfaction, retained personal data, the cost of relearning, and even social pressure (one’s social circle using the same app)—all of these are inertial forces that keep a user tethered to a tool they may not actually like, as both Turel and Salo demonstrate. Some service providers even exploit these mechanisms deliberately, through personalization and data retention, to reduce churn rates.

This carries a precise lesson for anyone measuring the “success” of a digital tool—or even an urban space—by its continued use alone: persistence is not necessarily evidence of satisfaction; it may simply be evidence of inertia. And when barriers to leaving are removed—easier data export, simpler account deletion—abandonment accelerates the moment users have sufficient motivation.

The Practical Takeaway for Anyone Designing a Tool or a Used Space

A coherent set of lessons can be drawn from this diverse body of research. First, genuine alignment with the user’s actual task must be ensured, and capability gaps must be continuously addressed, because users focus more on what a tool lacks than on what it provides. Second, complexity must be kept in check; excessive features and frequent updates generate fatigue that outweighs any added benefit. Third, performance, reliability, security, and visible user support remain non-negotiable conditions for any platform’s survival. Fourth, expectations must be managed honestly, because adoption driven by hype or rankings produces subsequent regret that leads to abandonment. Fifth, design must ensure visibility (so the user does not forget the tool exists), integration with the rest of their toolkit, scalability, and a clear return on investment that justifies the learning effort. Finally, user retention is not won at the moment of initial adoption alone—it is won or lost anew with every update, every support interaction, and every new alternative that appears in the market.

Ultimately, a user abandons a tool when its perceived value fails to justify the effort required to engage with it—whether due to poor performance, excessive complexity, fatigue, apprehension, disappointment, or simply because an easier, better, and more socially favored alternative has appeared on the horizon. Abandonment is rarely attributable to a single cause; it is the outcome of an interaction between product quality, ease of use, the psychological strain it produces, the surrounding social dynamics, and the alternatives available in the market.

✦ ArchUp Editorial Insight

The “critical mass problem” governing collaborative BIM adoption is not a technology failure but a labor and liability structure failure. Architects, structural engineers, and contractors operate under different fee arrangements, different insurance exposures, and different incentives for early data-sharing—so a platform requiring simultaneous full participation is asking parties with misaligned risk positions to absorb coordination costs unevenly. The contractor who inputs construction sequencing data early exposes themselves to claims before payment terms reward that transparency; the structural engineer who front-loads model detail carries liability the architect does not share. What results is not abandonment but asymmetric participation: partial models, withheld data, and duplicated drawings maintained outside the shared system. The fragmented coordination later blamed on “poor collaboration culture” is in fact the predictable output of procurement and liability frameworks that never restructured contractual risk to match the technical demand for simultaneous, complete data input.

References

Turel, Ofir. “Quitting the Use of a Habituated Hedonic Information System: A Theoretical Model and Empirical Examination of Facebook Users.” European Journal of Information Systems, 2015.

Zhao, Xiao, Jun Tian, and Lin Xue. “Herd Imitation and Software Adoption: A Re-Examination Based on Post-Adoption Software Discontinuance.” Journal of Management Information Systems, 2020.

Nickerson, Raymond S. “Why Interactive Computer Systems Are Sometimes Not Used by People Who Might Benefit from Them.” International Journal of Man-Machine Studies, 1981.

Jones, Elizabeth, Harley Bruce, Predrag Klasnja, and William Jones. “I Give Up! Five Factors That Contribute to the Abandonment of Information Management Strategies.” Proceedings of the American Society for Information Science and Technology, 2008.

Okonkwo, Chukwuemeka W., Magda Huisman, and Ethan Taylor. “Factors Influencing Africa’s Rejection and Discontinuation of Mobile Application Use.” African Journal of Science, Technology and Innovation Development, 2021.

Vagrani, Ankita, Neeraj Kumar, and P. V. Ilavarasan. “Decline in the Mobile Application Lifecycle.” Procedia Computer Science, 2017.

Salo, Markus, and Mikko Makkonen. “Why Do Users Switch Mobile Applications? Trial Behavior as an Antecedent of Switching Behavior.” Communications of the Association for Information Systems, 2018.

Park, Hyunjin, Jieun Eun, and Jinyoung Lee. “Why Do Smartphone Users Hesitate to Delete Unused Apps?” Proceedings of the 20th International Conference on Human-Computer Interaction with Mobile Devices and Services, 2018.

Zhang, Shuang, Li Zhao, Yi Lu, and Jian Yang. “Are You Tired of Socializing? An Empirical Interpretation of Discontinuous Usage Behavior in Social Networking Services.” Information & Management, 2016.

Fu, Shihui, Hui Li, Yi Liu, Henri Pirkkalainen, and Markus Salo. “Social Media Overload, Exhaustion, and Discontinued Use: Examining the Effects of Information Overload, Feature Overload, and Social Overload.” Information Processing & Management, 2020.

Furneaux, Brenda, and Michael Wade. “Exploring Discontinuance Intentions of Information Systems at the Organizational Level.” MIS Quarterly, 2011.