Category Archives: Book Review

The New Polymath’s Ten Rules for Success

Vinnie Mirchandani‘s The New Polymath is a riveting read. It’s SuperFreakonomics for us technophiles. Because, for better or worse, The New Polymath (who can be thought of as a modern Leonardo da Vinci) must also be an IT guru … as it is information technology that is paving the way for a new generation of polymaths that have access to unprecedented levels of information across disciplines.

Rather than tell you that this fresh and inviting (Benjamin Fried, CIO Google) book is filled with incredible examples of passionate entrepreneurs (Marc Benioff, CEO salesforce.com), that I am inspired by this book (Maynard Webb, CEO LiveOps), or that Mirchandani is one of the few technology analysts to realize that technology doesn’t come in neat bundles anymore (Thomas H. Davenport, President’s Chair Babson College), I’m going to talk about The New Polymath’s ten rules for success which pop out at you if you read between the lines.

Why? One of the Polymath’s chronicled in Vinnie’s masterful manuscript is Brian Sommer, technology consultant extraordinaire of TechVentive and renowned ZDNet blogger, who asks “where are the 10 commandments for technology” as he struggles with the challenges of cyberethics that few dare to address. It’s a good question, and one that I believe we are not yet ready to answer. Which leads me to ask, “how do we get there”? Well, the first step is to obviously become learned, and successful, polymaths well equipped to ask, and debate, the question. To this end, we need a guide … a guide that, if you dig deep, is found within Vinnie’s terrific tome. To get you on your way, and to inspire you to (pre) order your own copy of The New Polymath, I give you:

The New Polymath’s Ten Starting Rules for Success

(because, in reality, there are more than ten … but these are the biggies).

  1. 1-1-1Adopt salesforce.com’s 1-1-1 model: 1 percent employee’s time; 1 percent equity; 1 percent product donation. A true Polymath operates in his community, not out of it, and makes a difference.
  2. 80 for 20Aim for solutions that deliver 80% of the value of previous solutions for only 20% of the price. A new Polymath is about true innovation, not overstated renovation.
  3. Invisible UIIf your product requires a manual, it’s not a product at all. A true Polymath produces solutions with UIs so seamless and so obvious that no manual is needed.
  4. TraceabilityEvery component can be traced back to the source … even if it’s software. (And if it is software, every data element can be traced back to the source.)
  5. Keep ScorePolymaths are responsible and drive for sustainability … to the point where they keep track of how well they are doing and how much better their inventions are compared with predecessor technology. If it’s not more environmentally friendly (and more cost effective, because true green keeps more green in your wallet), it’s not revolutionary.
  6. SemanticsIt’s the age of “big data”, and to make sense of it all, we need to find the data that is relevant to us.
  7. Decisions, Not DataBecause, in the end, the entire point of finding the semantically relevant data is to enable us to make better decisions than we could before.
  8. Adopt the “Shamrock” It’s Lucky for a ReasonA “shamrock” organization, as envisioned by Charles Handy, is one that encompasses “core management, a long-term but contractual talent pool, and a transient, flexible workforce”. We are in the age of networked person, who is used to working on the move, and tomorrow’s polymath’s will be flexible at the core.
  9. TiaSTechnology-is-a-Service. A Polymath moves beyond SaaS (Software-as-a-Service) and TaaS (Technology-as-a-Service) and embraces the concept that, like power and water, information technology must be delivered only as a service in the world of tomorrow. Just like the utilities deliver our power and water, tomorrow’s technology enterprises will deliver our apps, data, and information on-demand as that is what is needed for businesses to truly reach the next level of operations, as technology is not the core competency of most businesses that make use of it today.
  10. The Turing OathBrian Sommer notes that we need a Hippocratic Oath for technology, and I agree. We all need to agree to respect and uphold the privacy of our users and their data to the utmost above all else. And I’m calling that the Turing Oath, after Alan Turing who gave us the first test to determine whether a machine had reached intelligence (and, would thus, need to be instilled with ethics from the get go … and, hopefully, the the three laws of robotics.)

I strongly encourage you to read Vinnie’s groundbreaking debut into the world of publishing (other than his prolific blogging over the years over on Deal Architect and New Florence. New Renaissance.) and do what it takes to become The New Polymath. The world of tomorrow needs you, and in fact, so does the world of today. If, like the polymaths chronicled in this book and Nathan Myhrvold (who was the cloth the new polymaths chronicled in the book were cut from), I encourage you to join the Humanitarian Technology Challenge. The world needs you!

Share This on Linked In

The New How, A Book Review

Nilofer Merchant’s The New How: Creating Business Solutions through Collaborative Strategy is a great book for those that truly want to collaborate but also need a framework for collaboration along with some practical advice on how to actually get down to the business of collaboration. A veteran of strategic thinking and innovation in the business context, Nilofer goes beyond simple academic frameworks and packs each chapter with examples and real-life situations that illustrate her points.

Furthermore, while the book does introduce some new terminology that, for the most part, is unnecessary, it’s pretty much limited to:

  • The New How
    which is Nilofer’s way of saying that siloed businesses can no longer survive and that they have to embrace more collaborative ways of working together,
  • The Air Sandwich
    which is Nilofer’s way of referring to the void that exists between the executive suite and the trenches in an average large organization, filled by middle management who are supposed to be bridging the gap but who, usually, only widen it with their inability to truly understand both the corporate strategy and shop floor details that they are not part of on a daily basis,
  • Murderboarding
    which is Nilofer’s process of using a razor-sharp tool to slice away at fuzzy thinking and kill off good ideas to let the great ideas thrive, and
  • Chief of Answers
    which is Nilofer’s characterization of the current, doomed, organizational model where one person is responsible for driving all strategy.

Furthermore, while most of the book is focussed on Nilofer’s QuEST (Question, Envision, Select, and Take ownership) process for the collaborative creation of strategy, Nilofer also realizes that collaboration requires more than just a process. Thus, the first part of the book spends a couple of chapters on how to “be” a collaborator — which requires us, at a minimum, to listen and understand, and the last part of the book focusses on the bigger picture and provides us with the “glue” necessary to mesh the people with the process in a way that can produce real results.

But what makes the book great is that even if you tossed the framework, every chapter is filled with practical, down-to-earth advice, on how to become a true collaborator and real-world examples of not only how to apply the concepts, but what might happen if you don’t. For example, Nilofer starts the book by describing one of her own experiences where she was in charge of revenues for the Americas in a large multi-national software company. She described how, one day, the VP dropped by to explain how the company had decided to diversify their product line six-fold within the coming eighteen months — with no input at all from the trenches or even (senior) middle management — based solely on the results of a market exploration which convinced senior management it was “the right idea”. Somehow, sales and marketing would generate demand while new products were developed in parallel. The CEO said “We Must”, the (senior) VPs said “We Will”, and everyone charged forward on the vision, and edict, handed down from on high.

The results were, as we would now expect, predictable. A few months into the new revenue cycle, Nilofer received a call from the lead product manager for the new suite. It started off with “We have a problem here. You know the lead product? Yeah, the one that’s supposed to net us most of this year’s revenue? We’re not going to be able to ship it with all the features we originally planned.” Meetings and chaos resulted, with the typical end-result where the product was shipped on the planned release date, knowing full well it wouldn’t live up to the expectations marketing had created. And it didn’t sell well. Revenues were weak. Customers that bought were unhappy. The team was demoralized and the corporate culture took a nosedive. Several talented staff members resigned. And it took a while for the company to recover.

And it was all preventable. Had the strategy not been created in a vacuum in the senior executive suite, but collaboratively with the front-lines who could have provided feedback on what could be done, and when, chances are that a simpler vision could have been successfully delivered to greater profits than the unmaintainable grand vision that was decided on the simple basis of a market-study with no cross-company input.

After all, as Nilofer points out in the Introduction, there’s not much difference between strategy success and strategy failure. The formula for both is summarized as:
good intent + good idea + talented direction + hard work + "magic black box".

The difference is that in a successful strategy, the “magic black box”, or the details of a successful execution are worked out before the strategy is adopted and launched. Strategy fails when the keys to making a strategy operational cross-functionally are not uncovered soon enough. This happens when a company jumps from “grand vision” to “execution” without sufficient exploration and planning, not because the idea is bad, or the direction is off, or the people aren’t talented and hard-working enough. And that’s why Nilofer wrote the book, to try and help people understand how to replace the “magic black box” with a “successful execution strategy” so that you can be a winner every time. (Because winning today is not enough, you have to win tomorrow, and smart companies go for a series of smaller wins rather than betting the farm on one big win.)

And while I’m not going to get into the nitty gritty details and give it all away, since this is another book I believe you should carefully read cover-to-cover (I did), I am going to give you some examples of the practical, down-to-earth advice that the book is crammed with.

  • Even bright, talented, and motivated people cannot jointly create effective strategies until the fundamental enablers of collaboration are in place.
    Some people have to be guided, and, more importantly, the organization has to foster a culture of collaboration. If the corporate culture is “I own my domain, you own yours” and every manager is always trying to one-up the manager down the hall for greater recognition from the CEO, collaboration is not going to happen.
  • Setting direction is an art and a practice.
    Just like strategy is a noun and a verb. You have to have a vision not only of a goal, but of a realistic execution strategy to get to the goal.
  • The hallmark of thorny strategy problems is that they involve contradiction – that is, they contain a set of conflicting goals or imperatives that create a tension that defies objective resolution.
    And there’s rarely just one right answer. To find the answer, you’ll have to take on tough debates, uncover tacit issues, and work with your “foes” to developer a deeper understanding of the issue that will allow everyone to collectively reach a solution that everyone can live with, get behind, and execute on. Furthermore, by acknowledging and addressing those tensions as we develop ideas rather than smoothing things over, we’ll end up with an even stronger, more viable set of options. It’s one of those pay-me-now or pay-me-later choices.
  • It often happens that our Achilles heel as leaders is attempting to come up with the answers and solve the tough problems by ourselves.
    Even a genius doesn’t know everything, and a true genius admits it.
  • In the long run, what truly matters is not what each of us knows today, but out ability to continue expanding the aperture of what each of us can see and understand tomorrow.
    That’s pretty much the reason Sourcing Innovation exists!
  • Powerpoint slides are just another form of air in the sandwich.
    Powerpoint slides capture high-level ideas, not understanding. For a corporate strategy to be successfully executed, everyone in the organization has to understand it, not just 1 in 20 individuals (which is the number of individuals who understand corporate strategy in your typical organization today). You don’t want to be in the situation where you were looking for a strategy, but only found a PowerPoint.

Share This on Linked In

Beyond the Beaker, A Book Review

Paul Patterson’s Beyond the Beaker, a book on How to Achieve Successful Market Adoption for Emerging Technologies, is a book that belongs on every innovator’s bookshelf. Whereas there are a lots of books on how to innovate, and even a fair number on how to take your product to market, there are very few that overview all of the relevant issues that need to be addressed and managed, fewer still that address both the innovator and corporate perspectives, even fewer still that illuminate the roadmap with real case studies, and next to none that uses successes and failures to help you understand the criticality of getting even the seemingly mundane choices right.

As Paul Patterson notes in the preface, the true, Real Life, events, which frequently go undocumented, are more often the critical events of success. For example, its 4 am and your phone rings. The person on the line is upset, screaming vulgarities because someone in the collaboration violated international trade laws. It’s your job to repair the situation.

For example, sometimes the most important aspect of the product is the seemingly mundane service guarantee. Here in North America, we expect our products to work and manufacturers to replace them if they don’t. We also reward companies who have faith in their products and provide satisfaction guarantees in addition to basic “works as advertised” guarantees. These companies do so knowing that, since we want to do the right thing, we won’t abuse the guarantee. However, do the right thing is culturally defined. Whereas some cultures will pride themselves on only using a guarantee if they are truly unsatisfied or the product doesn’t work, others will pride themselves on finding innovative ways to use the guarantee because their culture prizes cunning in business more than personal restraint. As Paul Patterson notes with this quote from Gan Chee Eng, Vice President of Amway China Company Limited, the Amway Guarantee almost put them out of business in China on the first day:

“I tried to explain to corporate that their guarantee will not work in China, but they insisted. People would have a wagon in the parking lot with a small barrel in it, come into the shop and purchase a 1 litter container of L.O.C.TM, walk out to their wagon, dump the container into the small barrel, walk back inside, and say, ‘I’m not satisfied, you replace’. Honouring the guarantee almost put us out of business on the first day. We closed for two weeks and re-opened with a new guarantee, which limited customer satisfaction to providing one replacement, which meant we effectively sold two for the price of one.”
– Gan Chee Eng

Sometimes the most important aspect of the product is the education around the importance of the product. For example, the success of Hindustan Lever Limited (HLL), the largest soap and detergent manufacturer in India, and its Lifebuoy soap (reformulation) came down to educating the populace on the importance of using soap. A market analysis by HLL found that many consumers were not using soap when washing because they believed that soap did not provide any additional value. So HLL developed an educational program that “visual clean is NOT safe clean” which included a germ-glow demonstration targeted at school children ages 5 to 13 and their parents. This program which did not advocate HLL or Lifebuoy but simply soap usage, ultimately led to a sales increase of 30%. The branding around the educational content was enough.

And sometimes the most important aspect of the product is the insight into potential usage. For example, consider the classic Post-It Note. In 1968, Spence Silver at 3M developed a super-weak glue that could stick to objects, and be easily peeled off, while searching for a new super-strong glue formula. For five years, he hyped the product internally, showing samples in spray-can and tack-less bulletin boards, but it never took off. Then he noticed Art Fry using pieces of the tack-less bulletin board tiles to mark pages in his hymnals and he came up with the idea for a better bookmark. Then he realized that the product wasn’t really a better bookmark at all, but a better note. And while there were technical challenges in perfecting the formula so the glue stayed on the note and not the object the note was stuck to when the note was removed and in developing appropriate coating equipment for paper (which was an imprecise substrate), the biggest hurdle was coming up with the right application for the technology. The second biggest was the right marketing campaign as the product, which was the company’s Outstanding New Product in 1981, did not take off with the first launch attempt in 1977, but the second in 1980.

The second thing I really like about the book is that it’s not your usual pop-culture business book that uses 200 pages to expound upon a simple (although usually very important) idea that could be summarized in 20 pages but is instead a jam-packed tome of information which would make a good textbook. As a result, this is a book that will end up on your bookshelf when you are done reading it and not the goodwill donation pile because you will want to read some parts of it more than once and keep it for reference.

Not only does it tackle strategic marketing, business development, financial concerns, legal considerations, organizational management, and corporate perspectives as well as the identification and evaluation of emerging technologies and technology development, but it addresses each from multiple viewpoints. For example, with respect to strategic marketing, it addresses SWOT (Strengths, Weaknesses, Opportunities, & Threats), macro and micro approaches, Porter’s Five Forces (Rivalry, Threat of Substitutes, Buyer Power, Supplier Power, and Barriers to Entry), Boston Consulting Group Market Evolution (Fragmented, Specialization, Volume, Stalemante), market and sector attractiveness, competitive advantage, value proposition, application and value chain analysis, other market drivers, and risk management. It addresses business development from a multitude of perspectives that include strategy, cultural, pitch, promotion, and communication. And it covers the five phase evaluation of emerging technologies (feasibility, value research, quick test market, action plan creation, and implementation) because the easiest thing about innovation is, well, innovation itself. The real challenges often lie in getting the innovation to market.

Finally, I really like the inclusion of a chapter on the corporate perspective. If you identify an emerging technology that you want to bring to market, you have to understand how your potential financiers think if you are going to be successful. Financiers typically invest in a portfolio of opportunities to mitigate their risks and increase the odds that they will see a return on their investment. As defined by Copper et. al in Portfolio Management for New Products:

Portfolio management for new products is a dynamic decision process wherein the list of active new products and R&D projects is constantly revised. In this process, new projects are evaluated, selected and prioritized. Existing projects may be accelerated, killed, or deprioritized and resources allocated and reallocated to the active projects. The portfolio decision process is characterized by uncertain and changing information, dynamic opportunities, multiple goals and strategic considerations, interdependence among projects, and multiple decision makers and locations.

This indicates that decisions about whether or not to invest in your product will not be made in a vacuum and will be made with respect to the rest of the portfolio. That means that you will need to insure that you continually address each of the critical success factors of portfolio management (strategic alignment, competitive advantage, market attractiveness, leverage of core competencies, technical feasibility, and financial rewards) if you wish to get funding and maintain it.

All in all, a great book and a great reference.

Share This on Linked In