Thought leader series: 5 pointers for breaking into the elderly demographic

The over-60s demographic controls roughly half of all consumer spending in the UK, and most digital products treat them as an afterthought. Not out of malice, but because the teams designing those products are rarely in their sixties, rarely test with people in their sixties, and carry assumptions about that age group that are decades out of date. The result is a quiet, systemic exclusion built into the texture of the product itself: type too small to read comfortably, flows that assume confidence with gesture-based navigation, and onboarding that front-loads so much information that a new user simply closes the app.

The over-60s demographic controls roughly half of all consumer spending, yet most digital products treat them as an afterthought.

We worked on a gifting product that had to serve a genuinely wide range of users: tech-savvy parents building wishlists, children receiving gifts, and grandparents contributing to those pots on birthdays and holidays. The older contributors were the group the product stood to lose most easily. To make sure it worked for all of them, we ran focus groups across different ages and demographics. What those sessions made clear is that the problem with reaching older users stems from design assumptions. The same interface that feels obvious to a 28-year-old product manager can feel genuinely hostile to someone who did not grow up with smartphones, and that gap is entirely fixable.

What follows are five honest pointers for any brand or product team trying to do this properly, drawn from real design work, real focus groups, and the patterns that keep appearing when we get it right.

Why Most Digital Experiences Quietly Exclude Older Users

Exclusion rarely looks deliberate. It tends to arrive through a series of small decisions, each of which seemed reasonable at the time. A designer chooses a typeface they find clean and modern. A developer sets a default touch target size that passes accessibility checks but is barely adequate in practice. A product manager decides the onboarding flow should surface all key features within the first session, because retention data suggests users who activate more features in week one are less likely to churn. None of these decisions were made with the intent to exclude anyone. And yet, together, they produce a product that a significant portion of potential users cannot comfortably operate.

The research behind this is consistent. Knowledge, competence, and perception, encompassing education, trust in the provider, privacy concerns, and health literacy, appeared in 68% of articles reviewed in a mapping review of factors influencing older adults' intention to use digital technology (PMC, 2023). That is the dominant category, above cost, above accessibility, above usability in isolation. Older users are primarily blocked by feelings of incompetence, distrust of the product, and confusion about what they are being asked to do and why.

Designing for this group means designing for those specific barriers. That is a different problem from making a button larger, though larger buttons help too.

The Assumptions Worth Dropping First

The most productive thing a product team can do before designing for older users is list what they currently assume about them, and then check each assumption against the people themselves. Several assumptions come up repeatedly, and almost all of them turn out to be wrong in at least partial ways.

They are not homogeneous

A 62-year-old who has worked in tech for twenty years and a 78-year-old who bought their first smartphone eighteen months ago are both "older users" in the typical product brief, and they are not the same person. Grouping them is as crude as grouping all users under 40. Health status, digital history, living situation, and confidence all vary enormously within the demographic. The mapping review we cited earlier found that demographics and health status appeared as influencing factors in 63% of reviewed articles, meaning the differences within the group matter as much as the fact of being in the group at all.

They are not resistant to technology

Older users are often willing, even keen, to engage with digital products. The barrier is usually an interface that does not extend them the patience or clarity they need to get started, combined with a real cost to making mistakes, financial, social, or emotional. Designing out those costs, and making early errors obviously recoverable, removes the resistance far more reliably than simplifying the product down to a version that feels condescending.

Drop the assumption that older users need a special, stripped-back product. They usually need a better-designed version of the same one.

Trust Is the Actual Conversion Metric for This Demographic

Conversion for older users tends to follow a different pattern than for younger ones. Younger users often try something quickly, decide whether they like it, and either stay or leave. Older users tend to evaluate trust before they try. They are asking themselves whether this product, and the company behind it, is the kind of thing they can rely on before they commit any personal information, payment details, or significant time to it. If the product has not earned that trust, they do not explore further.

We saw this pattern clearly on the healthcare product we built for African markets. Users were arriving in an emotionally heightened state, often anxious, and the design had to work hard to calm that state before asking anything of them. We chose a dark UI with green undertones, green for its associations with calm, safety, and medical support, and deliberately avoided anything clinical or sterile. The language throughout was simplified and stripped of jargon. Every decision was made to reduce anxiety, not amplify it, and to signal clearly that the product was there to support the user rather than process them.

Older users evaluate trust before they try, and if the product hasn't earned it, they don't explore further.

The same logic applies in wellness, beauty, or any lifestyle category. An older user arriving at a skincare brand's app for the first time is making a trust assessment before they interact with a single feature. Cluttered interfaces, aggressive upsell prompts, unclear data practices, and language that talks down to them all fail that assessment before the product has had a chance to demonstrate its value.

Place trust signals, plain-English privacy notes, visible customer support, and honest language about what the product does, within the first two screens of the experience, before you ask for anything.

Designing for Emotional State, Not Just Age

Age is a proxy, and a rough one. What actually governs how a person responds to a digital product is their emotional state at the moment they arrive. This is as true for a 70-year-old as it is for anyone else, and in several contexts relevant to older users, health management, financial decisions, new living situations, that emotional state is often anxious or overwhelmed rather than curious and engaged.

On the financial application we worked on, the product was information-heavy and functionally designed, and the team initially assumed that clarity of data was the primary design goal. What we found was that people experience real anxiety around their finances, and that surfacing dense information into that anxiety made the product harder to use, not easier. The solution was to use education as an emotional intervention: framing what the user was about to see, explaining where they were within the product, and giving them enough context to feel oriented before asking them to process anything complex. That shift transformed the product from a functional tool into something that felt genuinely supportive.

Match information density to emotional readiness

The same principle applies in any wellness or health-adjacent product aimed at older users. There is often internal pressure to front-load results and data, to show the science quickly and demonstrate credibility. But a user who arrives anxious about their health is not ready to process a chart. They need to feel safe first. Emotional framing before information density is the sequence that works, and reversing it produces the opposite of the intended effect.

Before each key screen, ask what emotional state the user is likely to arrive in. Design the screen to address that state before it asks them to do anything.

Information at the Right Moment, Not All at Once

Progressive disclosure is a well-understood design principle, but it is routinely abandoned in practice, particularly at onboarding. The assumption is that users want to understand everything the product offers as quickly as possible, so showing it all at once feels helpful. For older users, and for most users, in high-stakes or unfamiliar situations, it does the opposite.

We built a concierge app for residents moving into a new block of flats. The standard approach in that product category is to surface the full directory of building information immediately: recycling locations, fire procedures, local area guides, maintenance request flows, all of it at once. We made the deliberate decision not to do that. We recognised that someone who has just moved home is in an emotionally variable and often overwhelmed state. Some users had just bought their first property; others were moving after a separation. Neither group was in a mental state that was receptive to a large volume of information on day one.

So we drip-fed notifications over time, matching content to when users would actually need it. Recycling information arrived a couple of days after move-in. Local area recommendations came through the first weekend. Emergency procedures were surfaced once users had settled into the app rather than the moment they opened it. The experience felt human rather than bureaucratic, and the difference in how people responded to it was noticeable.

Map your notification and onboarding sequence to the user's likely life timeline, not to your product's feature list. What do they need on day one, day three, and week two? Those are three different answers.

Community and Human Connection as Product Features

Qualitative interviews consistently find that participants cite friends, family, and connection as the things that make them most happy in life, as discussed in Springer's work on app development for recovery contexts (2022). That finding is not surprising, but it has real consequences for how products aimed at older users should be designed. Connection is a primary motivator for this demographic.

On the concierge app project, we ran focus groups with two very different groups: high-net-worth individuals who were the target users, and people from social housing who would never be customers. We brought in the social housing group because they had something we were trying to build into the product: a genuine sense of community and neighbourliness that was typically absent in high-rise developments where residents rarely knew each other. What those sessions showed was that meaningful, deeper conversations between residents were what built community, not information systems or digital directories.

That insight reshaped the product. Rather than automating away human interaction, we designed the app to handle the transactional and mundane, maintenance requests, recycling locations, fire drill procedures, and free up space for the social. We added personalisation features so residents could see their neighbours' interests and get a sense of the concierge as a person. Community emerged when people accumulated shared, personal knowledge about one another. The product's job was to surface opportunities for that, not to replace it.

When to Step Back from Self-Service

Self-service is usually positioned as a win for everyone: lower support costs for the business, faster resolution for the user. For older users, it can be neither. The assumption that every user wants to resolve everything themselves, at any time of day, without speaking to a person, does not hold across all demographics. Older users, particularly for higher-stakes tasks, often prefer the reassurance of a human interaction, and a product that makes that genuinely difficult is one they will stop using.

Design the escape route as carefully as the flow

The practical answer is not to remove self-service, but to make the human option visible and accessible at every point where the user might want it. A phone number that takes four taps to find is functionally not available to someone who is anxious and confused. A live chat that requires account login before it will connect is a barrier at exactly the moment the user most needs help. The design of those access points deserves as much attention as the design of the self-service flows themselves.

For lifestyle brands in particular, fitness, wellness, home, travel, the human touchpoint is also a brand expression. An older user who gets through to someone knowledgeable and warm has had a brand experience, not just a support interaction. That is worth designing for deliberately rather than treating it as a cost centre to be minimised.

Testing With the Audience, Not About Them

Product decisions about older users are regularly made by people who are not older users, using data generated by people who are not older users, tested on panels that skew heavily toward the team's own demographic. The result is a product shaped by assumptions rather than observation. The fix is to involve older users in the research process directly and early, not as a validation step at the end but as a source of genuine insight throughout.

On the gifting product we worked on, a platform that let parents and children save together toward presents and experiences, with grandparents and family members able to contribute to the pots, we ran focus groups across multiple age groups and demographics. The older contributors were not just tested on the interface. They were part of shaping what the product needed to do. That is a different kind of involvement, and it produces different outcomes.

Ask how it feels, not just whether it works

When we propose design changes to clients, the most immediate validation often comes simply from asking: we have changed this, how does that feel to you? That question works because every person in the room is a user of something, and emotional responses to design are accessible without expertise. The same approach works in user research with older audiences. Functional usability testing tells you whether someone completed a task. Asking how it felt tells you whether they would want to do it again.

The research question is not "can they use it?" A better question is "do they want to?" Those are rarely the same answer, and the gap between them is where the real design work sits.

Conclusion

Breaking into the over-60s demographic is less about specialist design and more about honest design. The failures that exclude older users, information overload, absent trust signals, hidden human support, interfaces that assume digital fluency, are failures that compromise the experience for everyone. Fixing them for older users tends to improve the product across the board.

The five things worth holding onto from all of this are reasonably direct. Drop the assumptions and test them against real people. Build trust before you ask for anything. Design for the emotional state the user actually arrives in, not the one you wish they had. Sequence information to match the user's readiness rather than your product roadmap. And make human connection a feature rather than a cost.

None of this requires a separate product track or a special older-user edition of your app. It requires designing with more care and more curiosity about who is actually on the other side of the screen.

If you are working on a product that needs to serve a wider age range than your current experience covers, let's talk about your audience.

Frequently Asked Questions