Context-Blind Design
Context-blind design is the primary obstacle Prahalad identified to serving the bottom of the pyramid, and it is the design pathology that defines the current generation of AI tools. The products that fail at the bottom of the pyramid are not products that lack capability — the capability is real. They are products whose capability is embedded in assumptions about infrastructure, economics, behavior, and language that do not hold in the environments where the bottom of the pyramid actually lives. The designers do not choose to ignore context; they do not see it. Their own context is the water they swim in, and water, to fish, is invisible.
In the AI Story
The current generation of AI coding tools embodies a specific set of Silicon Valley context assumptions. The workflow assumption: tools assume continuous, uninterrupted sessions that the developer in Lagos cannot maintain through rolling power cuts and unreliable mobile data. The economic assumption: tools assume experimentation costs are negligible, while a hundred-dollar monthly subscription represents a meaningful fraction of average Nigerian monthly income. The linguistic assumption: tools perform measurably better on English-language rhetorical patterns, imposing a conformity that narrows the thinking the tools can amplify.
The knowledge-ecosystem assumption: tools assume access to Stack Overflow, GitHub communities, YouTube tutorials, and local meetups designed for Silicon Valley workflows — forcing non-Western developers to continuously translate between accessible resources and operational context. The market-infrastructure assumption: even if a product is built, app stores, payment platforms, and customer support systems are designed for developed-world markets.
The consequences are systematic exclusion. The democratization narrative — AI tools put unprecedented capability in the hands of anyone with an internet connection — describes a formal availability that masks practical inaccessibility. The capability is technically available; the conditions under which it can be captured are not.
Prahalad's corrective was co-creation — involving users in the design process from the earliest stages, locating design teams in the markets they serve, building feedback loops that capture actual usage. Applied to AI tools, co-creation would produce fundamentally different products: designed for intermittent connectivity, flexible pricing, multilingual interaction, integration with local market infrastructure.
Origin
The concept emerges from Prahalad's consulting work with multinationals attempting to enter Indian and African markets in the 1990s and 2000s, where he repeatedly observed capable products fail not because of deficient technology but because of unchallenged design assumptions.
Key Ideas
Invisible assumptions. Designers cannot see their own context because it is the water they swim in.
Capability works, deployment fails. The technology is real; the fit is absent.
Blame redirected to market. Failures get attributed to the market rather than the design.
Five specific assumptions. Workflow, economic, linguistic, knowledge-ecosystem, and market-infrastructure assumptions each exclude BoP users.
Co-creation corrective. Designing with, not for, the context produces products that actually deploy.
Appears in the Orange Pill Cycle
Further reading
- Prahalad, C. K. & Hart, Stuart L. The Fortune at the Bottom of the Pyramid (strategy+business, 2002).
- Norman, Don. The Design of Everyday Things (Basic Books, 1988).
- Suchman, Lucy. Plans and Situated Actions (Cambridge, 1987).