Who is Nandan Nilekani?
Nandan Nilekani cofounded EkStep Foundation with Rohini Nilekani and Shankar Maruwada. The initiative concerns digital infrastructure and learning. It extends the founder lens beyond a conventional company to the design of systems that other organisations can use and build upon.
- Founder profiled
- Nandan Nilekani
- Company or institution
- EkStep
- Reading lens
- Public infrastructure
Source starting point: EkStep: cofounders and community ↗. Full sources and context appear below.
A venture can be designed to help other people build. EkStep names Nandan Nilekani, Rohini Nilekani and Shankar Maruwada as its cofounders. The foundation describes its work through connections among society, markets and governance, with technology serving a broader ambition for participation and progress.
A wider unit of design
When many organisations must contribute to an outcome, the product is only part of the problem. People need ways to work together, adapt ideas to their own setting and carry knowledge between institutions. EkStep’s stated approach invites attention to those relationships rather than treating technology as a complete intervention by itself.
Reuse requires room for difference
Something built for many users or organisations must accommodate variation without becoming impossible to understand. Shared components can reduce duplicated work, while local participants bring knowledge of the people they serve. Finding that balance is an organisational challenge as much as a technical one.
The founder lens
Our interpretation of this chapter in Nilekani’s work is to ask what becomes possible when another team can build on what yours has created. That question changes the measure of success. The useful outcome may include capabilities and connections beyond the founding organisation, even when their contribution is harder to capture in a single company metric.
Design for participation beyond the original team
A tool intended for many organisations has to make sense outside the setting in which it was created. Documentation, understandable responsibilities and room for adaptation become part of the proposition. A founder can study participation by following a new organisation’s first attempt to use the work. Which assumptions are unexplained? Where is permission or assistance required? Shared infrastructure can reduce duplicated effort, but it does not remove the need for local knowledge or a sustainable operating arrangement. The useful question is what others can accomplish independently because the foundation exists. That keeps the story grounded in actual capability rather than treating a platform announcement as an outcome in itself.
The decision and its trade-offs
Infrastructure creates a different relationship with users from a standalone application. The immediate adopter may be an institution or a developer, while the intended beneficiary is someone further along the chain. The design task is to make participation understandable and useful without assuming that every participant has the same resources, incentives or technical capacity.
How to investigate the operating model
Draw the chain from a shared component to an organisation using it and finally to a learner’s experience. At each step, identify who maintains the connection and how failures are reported. Interoperability needs practical documentation and support, not only a common specification. The usefulness of infrastructure becomes visible in what others can reliably do with it.
Evidence and context
EkStep is a foundation, and its model should not be evaluated as though it were simply another venture-backed software startup. Reach, adoption and educational outcomes require distinct evidence.
Put the idea to work
Use these questions to investigate the idea in your own context.
- Describe the task another organisation should be able to complete.
- Test the first-use journey without assistance from the original team.
- Identify what must remain common and what can adapt locally.
A closer look
How does enabling other builders differ from selling one product?
The intended outcome depends partly on what other organisations do with the shared work. The founder therefore needs to consider adoption, documentation and institutional relationships alongside the technology itself. EkStep provides a setting for examining those choices.
What should a founder investigate in the EkStep story?
Look for usable implementations, clear responsibilities and evidence of the final experience. A widely available building block does not by itself prove impact.
Sources & editorial note
This profile draws on the public sources below. Company and founder accounts describe their own perspective. Our analysis, questions and takeaway are editorial interpretation. This is not an original interview or a sponsored feature.
See our editorial standards or request a correction. For a useful comparison, read Rakesh Verma: the MapmyIndia founder story. Explore the founder topic guides for connected reading paths.


