Nandan Nilekani

Nandan Nilekani is one of the seven engineers who established Infosys in 1981. The company grew in a period when globally competitive software-services work from India was still being proven to customers. That required more than technical skill: it required an organization that could hire, train, coordinate, communicate, and deliver across distance. Nilekani later served as Infosys’s CEO before moving into public service, according to the company’s management profile.

The lesson for early founders is that capabilities compound. A first customer project can teach a team about process; a repeatable process can make the next project safer; and the organization can then take on work it could not have handled at the start. But compounding only helps when the company captures what it learns. Write down the workflow, surface mistakes, and make quality less dependent on one person’s memory.

From 2009 to 2014, Nilekani was the founding chairperson of India’s Unique Identification Authority (UIDAI), which led the Aadhaar identity programme. He later co-founded EkStep Foundation, a nonprofit focused on technology-enabled foundational literacy and numeracy. These roles differ sharply from selling a service to a private customer: public infrastructure touches people at national scale, and education systems involve children, teachers, communities, and institutions.

A large digital system can expand access and reduce friction, but scale also amplifies the consequences of design choices. Questions about inclusion, privacy, reliability, grievance processes, and accountability belong in the product conversation from the beginning. The history should not be told as if reach alone settles those questions. Nilekani’s path is useful precisely because it shows how a founder’s work can move between sectors where the affected people and obligations are different.

EkStep’s origin account describes a learning initiative intended to help children improve foundational literacy and numeracy through technology. Education is not simply a distribution challenge. A tool can reach a school and still fail to fit a teacher’s day, a child’s language, local connectivity, or the way progress is assessed. A responsible education venture must check whether the tool helps learning in the conditions where it will actually be used.

This is a useful warning against reusing a successful playbook without redesign. A team may carry hard-won knowledge from one company into a new setting, but the people affected, measures of success, and risks may all change. The founder’s job is not to insist that the old approach fits; it is to listen, test, and adapt the institution around the new problem.

When your project is meant to serve a broad public, describe not only how many people could use it but also who could be left out. Test with the people most affected, design a clear route for complaints, and measure outcomes rather than sign-ups alone. If the work touches identity, money, health, education, or essential services, explain privacy, safety, and oversight in plain language.

A founder’s previous success can be a source of skill, not proof that a new idea will work. Start the new chapter with fresh evidence. Define the user, context, smallest safe test, and the signals that would make you pause or change course. Systems earn trust not just by reaching people, but by remaining understandable and accountable to them.