“The next million users” is a phrase technology companies use to signal scale. But the people inside that number are not a single audience waiting for a lighter version of an existing product. They have different devices, languages, incomes, levels of digital confidence, and reasons to be cautious.
Building for broader access begins when teams stop treating those conditions as edge cases and start treating them as the environment.
Low bandwidth changes the product hierarchy
On an unreliable connection, speed is not a polish metric. It determines whether a task can be completed. Heavy imagery, repeated authentication, and unclear loading states spend a user’s time and data before value has been delivered.
Resilient products preserve progress, explain what is happening offline, and make the essential path lighter than everything around it.
Familiarity can be more useful than novelty
Design teams often reward originality, while users reward recognition. Familiar words, predictable navigation, and visible confirmation reduce the amount of new behaviour someone must learn at once.
Local context matters here. The right payment method, unit of value, example, or support channel can do more for adoption than a universal interface translated at the end.
Inclusion appears in operating decisions
A product is not inclusive because a campaign says everyone belongs. Inclusion shows up in supported devices, transparent pricing, accessible help, forgiving identity checks, and research that reaches beyond existing power users.
The work is less glamorous than a launch. It requires teams to notice who disappears from a funnel and to ask whether the user failed the product—or the product quietly excluded the user.
The next million users do not need to be impressed by the future. They need the product to work in the reality they already inhabit.
Back to all writing