This Week’s Blogs for Thought:
The Applification of the Enterprise: Part I
In early February of 2012, Halliburton, one of the world’s largest oilfield service companies, became the latest enterprise to abandon RIM’s BlackBerry. Halliburton’s new smartphone of choice: Apple’s iPhone.
Even two years ago, this would have been earth-shattering news. Companies of this size just didn’t buy Apple products. These days, however, announcements like these have almost become commonplace. That is, Halliburton is hardly alone in adopting the Apple’s iPhone throughout the company. In late 2011, Pfizer announced that it will purchase a rumored 37,000 iPads for its scientists and sales and manufacturing employees. In the same year, biotech giant Genentech announced that it had rolled out 30 company-specific apps in its own private app store.
How to Share Bad Project News
In the spirit of the holiday season, I just wanted to bring some levity to the blog. I’ll leave it to you as the reader to discern if there is any applicable value to you in how you communicate.
Email to the Divisional Vice President
Subject: Weekly Status Report on Project Thames
This was not a good week for the project.
23 of our nodes failed and we learned that there are limitations to how much the 3-node failover processes work. We’re still trying to figure out what we’re missing. Once we do, we’ll be in a better position to know when we can recover our data. Hopefully it doesn’t happen again. We also learned that the patch we were expecting from the vendor has been backburnered to 2013.
The Last Resort: Custom Fields
For many years, I worked implementing different enterprise systems for organizations of all sizes. At some point during the project (hopefully earlier than later), someone would discover that the core application had no place to store a potentially key field. Against that backdrop, the team and I had a few choices .