The interface decides who a product is actually for.
The plainest version of what I argue, why it is a decision rather than a style, and why it carries more weight at India's scale than almost anywhere else.
Design is decision architecture
Design is the practice of deciding, in advance and on purpose, which people a product will work for. The interface is where that decision becomes visible and where it takes effect. Most problems people call design problems are really business, inclusion, or trust problems wearing a design costume.
Every screen sets conditions of entry
A screen is never neutral. It assumes a connection speed, a language, a screen size, and a level of practice with phones. Anyone who meets those assumptions gets in. Anyone who does not is quietly turned away, and no one on the team ever sees it happen, because the people who fail to complete a flow do not file complaints. They leave. That is the decision I mean. It gets made whether or not anybody intends to make it.
Why this is a decision and not a style
If a form needs fast internet, confident English and many taps in a row, it has decided that people without those do not matter enough to design for. That is not a harsh reading of it. It is the literal outcome. The reason it does not feel like a decision is that nobody sat in a room and chose it. It arrived by default, one reasonable-sounding requirement at a time, and defaults are decisions that nobody signed.
At India's scale the maths stops being abstract
In most markets an interface decision costs a business some conversion. Here it does not affect a few users. It includes or excludes millions of people, many of them on old phones, weak networks, and their first year of using the internet at all. When a public service is involved, the person who cannot get through the form does not lose a purchase. They lose access to something they are owed.
How to tell whether it is happening to you
You do not need to be a designer to check. Ask who the last five decisions on your product were convenient for. If the answer is the team, the roadmap, or the org chart, the interface has already chosen its users and it did not choose them for their benefit. The most reliable place to look is the error state, because that is the screen nobody rehearses and the one where a person decides whether to trust you or give up.
Where I learned this
From doing both ends of it. Consumer work at super app scale teaches momentum, because if the flow loses people the business quietly loses money. National public-sector work teaches inclusion, because if the flow loses people a citizen loses a service. Very few designers have done both, and the two jobs correct each other. One keeps you honest about speed and desire. The other keeps you honest about who counts.
The obvious objection
Someone always says that you cannot build for everyone, and they are right. You cannot. The argument is not that every product must serve every person. It is that the choice should be made deliberately, by someone who knows they are making it, instead of arriving by accident through a stack of small technical conveniences. Deciding to exclude is a legitimate business call. Excluding without noticing is not a call at all.