I saw an article aimed at authors and publishers on how to handle critical reviews. And I chuckled to myself "I could have written that myself"
I took most heat for the first volume of SAP Nation - mostly from SAP fans and partners. It was actually a generous history of SAP as it grew from small German vendor to global powerhouse. What I drew attention to was its poor handling of partners and the massive costs and project failures in the ecosystem. Five years later, I can say with some pride that it had a significant impact. The strategies I highlighted in the book like ring fencing with cloud, two-tier ERP and third party maintenance have gone mainstream. Also, in writing volume 3.0 I saw customers have become cautious in their use of large SIs, they are minimizing change as they move to S/4 etc. That to me is gratifying. I was talking to the customer audience and many of them have benefited from the book.
I was criticized for not being alarmist enough with Silicon Collar. The book came out when prominent Oxford profs and Gartner analysts were screaming about catastrophic job losses from automation. Mine was a tone of optimism - automation makes us safer, smarter, speedier workers. Machines typically impact repetitive tasks not complete jobs. Automation takes time to mature, it is not cheap. History has proved me right so far. Very few job losses from machines. We are pushing back dates for autonomous vehicles, for payback from machine learning. Two disappointments from the book- I had hoped SIs and outsourcers would automate their own operations - but they are mostly sticking to labor intensive models. The other was software vendors would reshape processes to reflect growing drones and telematics in logistics, sensors, 3D printing and wearables on the shop floor, robotics everywhere but it may take a wave of greenfield vendors to come along to do that.
I am starting to hear criticism I am "too nice" to SAP in the latest, volume 3.0 of SAP Nation. I am actually pretty tough on SAP in a number of chapters. What I do point out is how little its competition has evolved in the last 5 years. So many missed opportunities. Some of the criticism is coming from them for highlighting their performance. To me, again, that is background noise. The book gave me a chance to highlight 200+ pages of case studies talking about a slew of new SAP products. Hopefully, the customer audience benefits from that and sees that this is not "your Dad's SAP". And the competitors realize the clock is reset and they can show much more progress by the time I start to write volume 4.0 in the series.
I tend to be a tough critic myself. The New Polymath was one of my best reviewed books and it was gratifying to get a number of comments about people wanting to expand their own skillsets. What I had hoped in addition was it would spur Polymath organizations like the GE Global Research Center I described in the book "Conversations in the cafeteria, in the hallways, and at the 40 - room lodge attached to the center effortlessly drift from pathology to holography, from one “ aha ” to another. The Global Research ethos is “ Innovation occurs at the intersection of disciplines. ” So, put chemists, mathematicians, engineers of all stripes, and biologists in close proximity and who knows where the conversations will lead."
The New Technology Elite was about smart products (analog products made digital with software, sensors and satellite support) and covered design, IP issues, the application of Moore's Law, a need to plan multiple releases, product documentation and training and a number of other dimensions. I see so many smart products launched in the last decade which could have used that advice. You wonder, for example, how things would have worked out if Boeing had provided better documentation and training around the MCAS software and the Angle of Attack sensor on the 737 MAX.
I write books to stay in touch with practitioners - my case study heavy style makes me reach out to over a hundred for each book. They provide me the reality checks and validations for the themes of each book. They also provide fodder for our advisory work. The ultimate compliments and criticism also comes from them, not from social media. Nothing is more pleasant than a note from a client which says "thank you from saving us from a $50 million mistake" or "you forced us to consider couple more scenarios we had not factored"
Having said all that, I happily sign my books, and enjoy presenting on themes from my books especially to audiences on campuses. See you at an event soon.
Comments
The joys of book reviews
I saw an article aimed at authors and publishers on how to handle critical reviews. And I chuckled to myself "I could have written that myself"
I took most heat for the first volume of SAP Nation - mostly from SAP fans and partners. It was actually a generous history of SAP as it grew from small German vendor to global powerhouse. What I drew attention to was its poor handling of partners and the massive costs and project failures in the ecosystem. Five years later, I can say with some pride that it had a significant impact. The strategies I highlighted in the book like ring fencing with cloud, two-tier ERP and third party maintenance have gone mainstream. Also, in writing volume 3.0 I saw customers have become cautious in their use of large SIs, they are minimizing change as they move to S/4 etc. That to me is gratifying. I was talking to the customer audience and many of them have benefited from the book.
I was criticized for not being alarmist enough with Silicon Collar. The book came out when prominent Oxford profs and Gartner analysts were screaming about catastrophic job losses from automation. Mine was a tone of optimism - automation makes us safer, smarter, speedier workers. Machines typically impact repetitive tasks not complete jobs. Automation takes time to mature, it is not cheap. History has proved me right so far. Very few job losses from machines. We are pushing back dates for autonomous vehicles, for payback from machine learning. Two disappointments from the book- I had hoped SIs and outsourcers would automate their own operations - but they are mostly sticking to labor intensive models. The other was software vendors would reshape processes to reflect growing drones and telematics in logistics, sensors, 3D printing and wearables on the shop floor, robotics everywhere but it may take a wave of greenfield vendors to come along to do that.
I am starting to hear criticism I am "too nice" to SAP in the latest, volume 3.0 of SAP Nation. I am actually pretty tough on SAP in a number of chapters. What I do point out is how little its competition has evolved in the last 5 years. So many missed opportunities. Some of the criticism is coming from them for highlighting their performance. To me, again, that is background noise. The book gave me a chance to highlight 200+ pages of case studies talking about a slew of new SAP products. Hopefully, the customer audience benefits from that and sees that this is not "your Dad's SAP". And the competitors realize the clock is reset and they can show much more progress by the time I start to write volume 4.0 in the series.
I tend to be a tough critic myself. The New Polymath was one of my best reviewed books and it was gratifying to get a number of comments about people wanting to expand their own skillsets. What I had hoped in addition was it would spur Polymath organizations like the GE Global Research Center I described in the book "Conversations in the cafeteria, in the hallways, and at the 40 - room lodge attached to the center effortlessly drift from pathology to holography, from one “ aha ” to another. The Global Research ethos is “ Innovation occurs at the intersection of disciplines. ” So, put chemists, mathematicians, engineers of all stripes, and biologists in close proximity and who knows where the conversations will lead."
The New Technology Elite was about smart products (analog products made digital with software, sensors and satellite support) and covered design, IP issues, the application of Moore's Law, a need to plan multiple releases, product documentation and training and a number of other dimensions. I see so many smart products launched in the last decade which could have used that advice. You wonder, for example, how things would have worked out if Boeing had provided better documentation and training around the MCAS software and the Angle of Attack sensor on the 737 MAX.
I write books to stay in touch with practitioners - my case study heavy style makes me reach out to over a hundred for each book. They provide me the reality checks and validations for the themes of each book. They also provide fodder for our advisory work. The ultimate compliments and criticism also comes from them, not from social media. Nothing is more pleasant than a note from a client which says "thank you from saving us from a $50 million mistake" or "you forced us to consider couple more scenarios we had not factored"
Having said all that, I happily sign my books, and enjoy presenting on themes from my books especially to audiences on campuses. See you at an event soon.
The joys of book reviews
I saw an article aimed at authors and publishers on how to handle critical reviews. And I chuckled to myself "I could have written that myself"
I took most heat for the first volume of SAP Nation - mostly from SAP fans and partners. It was actually a generous history of SAP as it grew from small German vendor to global powerhouse. What I drew attention to was its poor handling of partners and the massive costs and project failures in the ecosystem. Five years later, I can say with some pride that it had a significant impact. The strategies I highlighted in the book like ring fencing with cloud, two-tier ERP and third party maintenance have gone mainstream. Also, in writing volume 3.0 I saw customers have become cautious in their use of large SIs, they are minimizing change as they move to S/4 etc. That to me is gratifying. I was talking to the customer audience and many of them have benefited from the book.
I was criticized for not being alarmist enough with Silicon Collar. The book came out when prominent Oxford profs and Gartner analysts were screaming about catastrophic job losses from automation. Mine was a tone of optimism - automation makes us safer, smarter, speedier workers. Machines typically impact repetitive tasks not complete jobs. Automation takes time to mature, it is not cheap. History has proved me right so far. Very few job losses from machines. We are pushing back dates for autonomous vehicles, for payback from machine learning. Two disappointments from the book- I had hoped SIs and outsourcers would automate their own operations - but they are mostly sticking to labor intensive models. The other was software vendors would reshape processes to reflect growing drones and telematics in logistics, sensors, 3D printing and wearables on the shop floor, robotics everywhere but it may take a wave of greenfield vendors to come along to do that.
I am starting to hear criticism I am "too nice" to SAP in the latest, volume 3.0 of SAP Nation. I am actually pretty tough on SAP in a number of chapters. What I do point out is how little its competition has evolved in the last 5 years. So many missed opportunities. Some of the criticism is coming from them for highlighting their performance. To me, again, that is background noise. The book gave me a chance to highlight 200+ pages of case studies talking about a slew of new SAP products. Hopefully, the customer audience benefits from that and sees that this is not "your Dad's SAP". And the competitors realize the clock is reset and they can show much more progress by the time I start to write volume 4.0 in the series.
I tend to be a tough critic myself. The New Polymath was one of my best reviewed books and it was gratifying to get a number of comments about people wanting to expand their own skillsets. What I had hoped in addition was it would spur Polymath organizations like the GE Global Research Center I described in the book "Conversations in the cafeteria, in the hallways, and at the 40 - room lodge attached to the center effortlessly drift from pathology to holography, from one “ aha ” to another. The Global Research ethos is “ Innovation occurs at the intersection of disciplines. ” So, put chemists, mathematicians, engineers of all stripes, and biologists in close proximity and who knows where the conversations will lead."
The New Technology Elite was about smart products (analog products made digital with software, sensors and satellite support) and covered design, IP issues, the application of Moore's Law, a need to plan multiple releases, product documentation and training and a number of other dimensions. I see so many smart products launched in the last decade which could have used that advice. You wonder, for example, how things would have worked out if Boeing had provided better documentation and training around the MCAS software and the Angle of Attack sensor on the 737 MAX.
I write books to stay in touch with practitioners - my case study heavy style makes me reach out to over a hundred for each book. They provide me the reality checks and validations for the themes of each book. They also provide fodder for our advisory work. The ultimate compliments and criticism also comes from them, not from social media. Nothing is more pleasant than a note from a client which says "thank you from saving us from a $50 million mistake" or "you forced us to consider couple more scenarios we had not factored"
Having said all that, I happily sign my books, and enjoy presenting on themes from my books especially to audiences on campuses. See you at an event soon.
April 18, 2019 in Industry Commentary, SAP Nation, the book | Permalink