Focused on the services and applications development space. Have authored most of the posts for the Next Big Thing blog (www.hp.com/go/tnbt) and try to regularly participate in #CIOChats. Recently retired from HP.
Actually, most of the docs I saw this summer were empathetic, but there were several snafus when information had to physically shared. Surveys have shown that empathetic docs who apologize when things go wrong get sued less. And I do believe there was geneuine compassion on the part of several docs.
I did find that as much of the information did automatically flow between docs in different facilities (5). One doc in particular was religious are sharing information and there about nine docs involved. She was the only one to use e-mail with me where they don't get compensated. Her place in the pantheon of my favorite physicians is secure. She even called me once to see how I was doing....an above and beyond physican.
In looking back, the flow of information went reasonably well despite a couple of horrendous mistakes, the sting of which has worn off....
"Outside-in" is another way to describe loosely-coupled web-based computing where technology more closely mirrors the business. Maybe computing isn't the right word, but information flow does not quite cut it, either. Author Eric Openshaw offers up a decent example to explain what he's talking about and four steps about how to get "Outside-In."
Here's an excerpt: "The answer lies in re-envisioning your architecture, not as an enterprise-wide monolith but as interrelated systems and data sets, encapsulated for external consumption."
It needed to be said yet again, but open source software is the way to go, says this new white paper "Open for Businesss." Open systems have reach a point of maturity where they are ready to handle mission critical applications. Migration to open source also requires rationalizing of current proprietary (legacy) systems.
I have one 40-something physican who types into a notebook during 90% of the appointment and makes almost no eye contact. I find it distracting and borderline rude. I applaud that he's using technology and not wracking up bills using a transcription service or a scribe. But someone needs to tell this guy to type less and pay more attention to the patient. It's like the notebook has the appointment, not the patient.
For a while now there is constant conversation that the traditional drivers are obsolete. Do you think that is true or are we just looking at the problem differently. IT organizations have gotten into the habit of striving for:
Last week I was interacting with a number of technologists where we were discussing the need for organizations to be more agile and the implications this may have on an organization’s architecture efforts in general and enterprise architecture in particular.
The same pressures shifting the needs of the business are present where business and technology meet and should affect the creation and use of architecture work products. Much can be learned from what’s happening in the agile development space, and applied to architecture:
Since the first of the year, I’ve been giving a presentation on embracing technical trends for organizations – what strategists need to think about to address the needs of their organizations. At the end of the material, I include a summary of takeaway points. Since I haven’t posted anything to this site for a while, I thought I’d share them and see what kind of reaction develops:
This week I was working on a presentation for the ISSIP Service Futures SIG titled: Service Futures and Drivers of Change. Part of the presentation included a discussion of megatrends – the industry independent trends that will shape our lives in the future and their effect on business decision making.
Last month, I attended the MIT CIO Symposium focused on the transformational CIO. At the event I ran into John Dodge (of this site). John said I hadn’t posted much recently so I thought I’d pass along a brief summary of the panels I attended: