Archive for July, 2009

Health 2.0 Challenge: Managing User-generated content (UGC) in the regulated environment

Health 2.0 Challenge: Managing User-generated content (UGC) in the regulated environment

Update: Over the past 90 days, I have been hearing more and more about Health 2.0 — the use of Web 2.0, Gov 2.0 and Enterprise 2.0 technologies to help improve medicine and health care. In response of I have updated my post outlining the major HHS and FDA regulations any Health 2.0 service provider will have to navigate to deliver a regulatory-compliant solution…

What I Took Away From the Inaugural Open Government & Innovations (OGI) Conference

What I Took Away From the Inaugural Open Government & Innovations (OGI) Conference

This week was the first Open Government & Innovations (OGI) conference in Washington, DC. What was special about this was that it combined the Obama Administration’s push for Transparency & Open Governance with the momentum to adopt “All Things 2.0.” It was a great conference. However I came away with some second-level observations that highlight some execution challenges we will all face to us Gov 2.0 effectively to help address our larges public policy problems…

What Joe Shea, Program Manager of NASA’s Apollo Program, Taught Me

What Joe Shea, Program Manager of NASA’s Apollo Program, Taught Me

Today is the 40th Anniversary of the Apollo 11 Moon Landing. As such, I thought it would be appropriate to reflect on what Joe Shea taught me at MIT about designing large-scale systems and managing their successful “launch”…

Article III for Good Architecture: Extensibility (a.k.a. How I Used Polymorphism to Convert a Lead-Gen Project into a Service that Generated Over $1Bn of Value Across Multiple Lines of Business)

Article III for Good Architecture: Extensibility (a.k.a. How I Used Polymorphism to Convert a Lead-Gen Project into a Service that Generated Over $1Bn of Value Across Multiple Lines of Business)

We have all heard the mantra, “write once, re-use everywhere,” to describe the concept of creating technology that can ubiquitously to create value in many places. However, publishing APIs alone will not achieve this. To be ubiquitous, you must incorporate the principle of Extensibility into every aspect of design, development and operation. Here is how I have defined this as a guiding architecture principle and applied it to create over $1 Bn of value…

Article II for Good Architecture: Isolation of Logic By Application Area (Where I Break with Many COTS Vendors)

Article II for Good Architecture: Isolation of Logic By Application Area (Where I Break with Many COTS Vendors)

Correct isolation of logic in your applications can enable them to “turn on a dime,” rapidly adapting to changing business rules and requirements. Placing logic in the wrong places can lead to spaghetti, long test cycles or (even worse) complete breakage of your data model. This is why “Isolation of Logic by Type” is an architecture principle I live by–even if many of my vendors do not…

Article I for Good Architecture: Modularity and Encapsulation (And How I Would Use This to Make Money via Facebook)

Article I for Good Architecture: Modularity and Encapsulation (And How I Would Use This to Make Money via Facebook)

Use of modularity and encapsulation if one of the most powerful approaches to scaling architecture (your ability to built it, your cost to operate it–AND the value you can obtain from it). Those enterprises who incorporate this into the DNA of their technology create “killer networks” that can used to generate enormous value…

© 2009-2011 Exsecutus Blog. All rights reserved.