Skip to main content

Connecting the Dots. Book by John Chambers.

Here's what I remember from John Chambers' impressive 2014 keynote at Cisco Live. Not all of his predictions have come true. IoT/IoE has a long way to go to become a multi-trillion dollar industry. Cisco didn't turn out to be like IBM, HP or Dell, but much better than all of them. What I remember the most is what happened after the speech. As the crowd was leaving, I saw a group congregating near the stage. They were are all surrounding John Chambers. He was in no hurry to go anywhere. People were talking to him, taking selfies with him. Some complained about partnerships, others about products. To all the complaints, he gave his card and said, "Call me". Not, call support, bizdev, or someone else. Just, "Call me". That was impressive.
Connecting the dots packs powerful advice for all of us in the technology industry bookended by the stories of West Virginia, IBM, Wang labs, and JC2 ventures. Since I just finished completed listening to the audio book, here are the things I remember.
  1. John reviewed and followed up on critical customer situations every day for the 20 years.
  2. Meeting the customers often, listen to their complaints, needs and feedback. That can guide your acquisition and strategy. Many of the acquisitions were guided the customer needs and suggestions.
  3. It's time for a change if your company isn't listening to customer complaints. He quit IBM when his boss wasn't listening to customer complaints.
  4. Quite a good chapter on acquisitions -- Cisco acquired about 180 companies. Only acquire if you have a vision for what you're going to with the product and PEOPLE from that company. A Merger of equals never work.
  5. Cisco is not about the switches or routers, it's "Changing the Way We Live, Work, Play and Learn".
  6. Look forward. Think tomorrow, not yesterday.
  7. Re-invent yourself every few years.
  8. Startups have to make the impossible possible, unimaginable a reality. Not just rip & replace.
  9. Cybersecurity is a problem. Big problem. For everyone.
  10. Embrace, drive and create change.
  11. The world is flat. Really flat, maybe tilting away from the US.
  12. Digitization has just begun.
  13. Even with all the advice, recommendations you get, leadership is a lonely place.
  14. Sometimes, you can be too early for a market (Wang for PC) and consequently, back-off when its time really comes. Timing is important and tricky.
  15. Leaders without foresight will create a big downfall.
  16. It's important to be human. He shared his own challenge with dyslexia when he saw a girl having difficulty to speak in front of the class.
  17. Use play books and checklists for everything. Strategy, sales, acquisitions.
  18. And he voted for Hillary Clinton.


I recommend you read/listen to the whole book and get your own insights.

Comments

Post a Comment

Popular posts from this blog

MongoDB to Couchbase for Developers: Part 2: Database Objects

    MongoDB developers and DBAs work with physical clusters, machines, instances, storage systems, disks, etc. All MongoDB users, developers, and their applications work with logical entities: databases, collections, documents, fields, shards, users, data types.  There are a lot of similarities with Couchbase since both are document (JSON) oriented databases.  Let’s compare and contrast the two with respect to database objects.  Here’s the first part of this series comparing the architecture.   MongoDB Organization A full list of MongoDB schema objects is listed here and here . A database instance can have many databases; A database can have many collections; Each collection can have many indexes.  Each collection can be sharded based into multiple chunks on multiple nodes of a cluster using hash-sharding strategy or index sharding strategy.  The MongoDB indexes are local to their data.  Therefore, the indexes use the same strategy as ...
4 comments
Read more

Swami Vivekananda: The Monk That Nobody Sent to Chicago

  There’s a saying in Chicago: “We don’t want nobody that nobody sent.” This was the cold reception Swami Vivekananda faced when he arrived in the windy city in July 1893, determined to attend the World Parliament of Religions that September. He belonged to no organization, carried no letter of recommendation, his countrymen were nobody, and represented an alien religion to the Western world. As the days passed, his hope of attending the parliament dwindled. With money running out and the odds stacked against him, he left the Windy City and went to Boston, praying for a glimmer of opportunity.  Swamiji came to America to share India’s most profound gift: the wisdom of the Hindu sages, preserved through centuries of oral tradition and embodied by its monks. This was 1893, not 1993—India was under the British grip, its resources drained, and its spirit subdued. Swamiji’s mission was not just a cultural exchange; it was a bold step toward envisioning a future where India could re...
Post a Comment
Read more

Why Should Databases Go Natural?

From search to CRM, applications are adopting natural language and intuitive interactions. Should databases follow? This article provides a strategic perspective. Amid the many technological evolutions in software and hardware (CISC/RISC, Internet, Cloud, and AI), one technology has endured:  Relational Database Systems   (RDBMS), aka SQL databases. For over 50 years, RDBMS has survived and thrived, overcoming many challenges. It has evolved and adopted beneficial features from emerging technologies like object-relational databases and now competes robustly with   NoSQL databases .  Today, RDBMS dominates the market, with four of the top five databases and seven of the top ten being relational. RDBMS has smartly borrowed ideas, like JSON support, from NoSQL, while NoSQL has also borrowed from RDBMS. NoSQL no longer rejects SQL. From a user perspective, all modern databases have SQL-inspired query language and a set of APIs. All applications manage the respective data...
Post a Comment
Read more