Design principles to Increase Technology Self-efficacy for Older Australians with Mild Cognitive Impairment (MCI) and Older Carers

As the global population ages, technology is increasingly vital for supporting independent living among older adults, particularly those with mild cognitive impairment (MCI). However, there is a significant gap in understanding what motivates these individuals to adopt and continue using technology. This study explored the experiences of older Australians with MCI and their carers through semi-structured interviews. The researchers analyzed these experiences using the Protection Motivation Theory (PMT) to understand how users assess threats to their independence and how they select coping strategies.

The findings reveal that while older adults with MCI are motivated to use technology to maintain autonomy and quality of life, they face significant psychological barriers. Constant technological change—such as software updates, interface modifications, and new feature releases—is a major disabler. These changes create stress, anxiety, and confusion, which in turn lower the user's perceived IT literacy and self-efficacy. Because these users rely on structure, routine, and predictability to manage their cognitive symptoms, frequent changes disrupt their established habits and discourage sustained use.

To address these challenges, the authors propose two high-level design principles grounded in Albert Bandura’s four sources of self-efficacy (performance accomplishment, vicarious experience, verbal persuasion, and psychological state):

1. Design to support and maximize feelings of self-efficacy: This involves creating intuitive, consistent, and personalized interfaces that enable successful task completion and provide clear feedback.
2. Implement technology change to minimize or eliminate negative impacts: This focuses on maintaining status quo where possible, providing advance notice of changes, and ensuring that updates do not disrupt the user's established routines or cognitive load.

These principles are accompanied by detailed guidelines, such as using multimodal feedback, avoiding complex branching instructions, and ensuring that interfaces remain predictable even as software evolves.