When John Chambers arrived at Cisco in 1991, the company had about 400 employees and no desk waiting for him. His office was inside a closet, with a telephone switching system behind it. Then a customer had a problem, and Chambers went looking for the customer-service department. He found two or three people and an inflatable penguin. The internet's future had an unusually modest reception committee.
Chambers told this story years later with the advantage of knowing how it ended. Yet the useful detail is the smallness of the beginning. A company could have capable engineers, a product customers wanted and an enthusiasm for helping them, while still lacking a dependable way to deliver. He had walked into the gap between a promising invention and a business that could keep its promises.
That gap has occupied much of his working life. At Cisco, he helped turn networking equipment into an enterprise sold and supported around the world. At JC2 Ventures, he coaches founders facing their own versions of the closet. At Nile, where he is a co-founder and board member, he has returned to networking with a proposition that asks customers to buy a managed service. Starting over, in his case, involves an impressive amount of familiar territory.
“You don’t learn very much when you speak.”
John Chambers
Before the internet, a salesman
Chambers was born in Cleveland in 1949 and grew up in West Virginia, spending his early years in Ravenswood and Charleston. He earned business and law degrees at West Virginia University, followed by an MBA at Indiana University. The legal qualification did not lead to a legal career. In 1976, he joined IBM in sales, beginning a professional education conducted across the table from customers.
Wang Laboratories came next. He sold computers in Asia, rose through management and developed a friendship with founder An Wang. It was an education in the power of a technology company, followed by an education in its vulnerability. Wang's difficulties helped make Chambers attentive to an uncomfortable possibility: a business can keep doing the things that made it successful while the market finds something else to want.
At Cisco, he would return repeatedly to market transitions. The phrase sounds suitable for a conference slide, but its meaning is quite practical. Customers change what they buy. Technologies alter what is possible. A leader has to decide when to put money and people behind the next demand, even while the existing business still pays the bills. Chambers had already worked inside companies where that problem was difficult to solve.
Buying time, one company at a time
Cisco appointed him CEO in January 1995. The appointment followed four years of expanding responsibilities under John Morgridge, who had brought him in with the expectation that he might eventually run the company. Chambers inherited an expanding business and a question of timing. Networking was moving beyond the router. Customers needed a wider range of equipment, and developing everything internally would take time they might not give Cisco.
Acquisitions supplied one answer. By April 1997, Cisco had bought 14 companies since late 1993. Its approach combined the acquired teams and technology with Cisco's sales, manufacturing and distribution. The appeal was speed: a smaller company might already have solved a problem that Cisco's customers wanted addressed. An acquisition could bring that work into reach without waiting for a development cycle to finish.
The arithmetic is memorable. During his Cisco tenure, Chambers participated in 180 acquisitions. The judgment behind them interests him just as much. Describing his rules in 2019, he put cultural compatibility and trust near the top. He said he had abandoned two major deals at an advanced stage after losing confidence in the other company's leader. A promising spreadsheet could not repair a doubtful relationship.
He also insisted on checking with customers and explaining the implications to employees. People hearing about a transaction naturally wonder what it means for their own work. A chief executive may be thinking about a new market; an employee may be thinking about Monday. Chambers's acquisition method had to account for both calendars.
Same company. Different scale.
The price of having been there
The scale of Cisco's growth can make the years between its beginnings and Chambers's departure look deceptively smooth. They included the internet boom and the dot-com collapse. Cisco briefly became the world's most valuable company in March 2000. Its shares subsequently fell more than 80 percent. Chambers later recalled the crash as the worst period of his career. Experience came with a bill.
He handed the CEO role to Chuck Robbins in July 2015, remained executive chairman and left the board in December 2017. Chairman emeritus became his honorary title. These are distinct stages of leaving a company: giving up the operating job, helping the successor, then stepping away from the board. After more than a quarter-century at Cisco, he had to choose what kind of work would follow.
His advice about difficult periods is unusually procedural for someone so associated with big technological predictions. In a 2023 conversation, he described separating problems caused by the market from problems a company had caused itself, adjusting spending to reality and communicating regularly. He paired ambitious positioning with financial restraint. A downturn, in this telling, demands more than a stirring speech. Somebody still has to check the cash.
A new network, with old colleagues
JC2 Ventures launched in January 2018. Chambers made coaching central to the firm, investing his experience alongside capital. Its approach includes regular calls with portfolio CEOs, introductions to customers and partners, and work on hiring, culture and growth. The professional identity changed from running one large company to helping several smaller ones learn to run themselves.
Nile gives that second career a particularly personal plot. Chambers and Pankaj Patel, Cisco's former chief development officer, were named as co-founders when Nile emerged publicly in September 2022. Patel is its CEO. Chambers sits on the board. They were returning to the industry in which they had spent years building products, with a service aimed at the operational burdens those products can leave behind.
Nile's proposition is wired and wireless networking delivered as a service, with monitoring and automation built into the offering. Its company account emphasizes reducing complexity and incorporating security into the network. The customer is being asked to think about the experience of operating a network as well as the equipment inside it. For Chambers, it is a chance to apply his argument about transitions to a field he knows closely.
There is a certain comedy in a long career bringing you back to the original problem with a different purchase order. In 2009, he described networking as plumbing, an occupation he embraced. He wanted Cisco to move further into advising businesses about what that plumbing could make possible. Nile's service model revisits the practical question underneath: how much networking work should a customer have to perform?
The fishing trip has an agenda
Chambers's version of mentoring sometimes requires travel to Alaska. In a 2018 interview, he described taking startup CEOs fishing alongside a dozen seasoned business friends, including people with Cisco experience. Seven days together allowed them to develop relationships and learn from one another. The setting supplied something a tightly scheduled introduction rarely can: enough time for a conversation to become candid.
The choice is revealing without requiring any mythology about leadership and trout. He enjoys fishing. He also wants founders to have access to people who have already worked through the decisions ahead of them. Put the two together and the offsite becomes both a personal pleasure and an extension of his working method. Even away from the office, he is arranging useful introductions.
His son, John J. Chambers, is part of the JC2 Ventures team, working on growth. Other colleagues include Yvette Kanouff and Patel. The surrounding network contains family, former coworkers, entrepreneurs and business leaders. Chambers's second act depends on these relationships becoming useful to somebody besides Chambers. A contact book earns its keep when another person can make the call.
“I always believe you deal with the world the way it is, not the way you wish it was.”
John Chambers · 2009
A startup state, and another conversation
West Virginia remains part of that ambition. In November 2018, he committed financial support and time to West Virginia University's startup work. The business school was renamed the John Chambers College of Business and Economics. His commitment included support for the Startup Engine, a philanthropic venture-capital fund and a Center for Artificial Intelligence Management. He also pledged five percent of his time to the university.
The phrase he used was a “startup state.” It locates entrepreneurship in a place where he grew up, rather than leaving it as an abstraction from Silicon Valley. His proposal required the university, businesses and public institutions to work together. A namesake college is a visible monument. The harder ambition is to help create conditions in which somebody else's company can begin.
His connections extend well beyond his home state. He chairs the US-India Strategic Partnership Forum and has served as a global ambassador for French Tech. In February 2026, USISPF announced an AI task force led by Chambers. The work applies his interest in technology adoption to institutions and countries, where education, business relationships and government decisions all affect what a new company can do.
He also keeps asking questions in public. His book, Connecting the Dots, written with Diane Brady, appeared in 2018. His Chambers Talks podcast extends the conversation to other executives. A July 2026 episode with Amazon grocery and Whole Foods leader Jason Buechel explored listening to customers, culture and making time to learn. After all the routers, acquisitions and board meetings, he is still interested in how another person does the job.
That is a fitting place to leave him: with another question to ask, another founder to coach and a networking company making a fresh attempt at an old complication. The penguin belongs to Cisco's early history. The problem Chambers found beside it remains a useful one. Someone has made a product people want. Now the company has to learn how to look after them.