I met with Darren Ash, the CIO of the Nuclear Regulatory Commission, today as well as Jeffrey Main who is driving much of the effort to improve the NRC's website over the coming months and years.
We were talking about all of the great things made possible by Web 2.0: Information sharing, collaboration, improved integration of systems, etc., but CIO Ash made the point that whatever NRC puts in place needs to anticipate "whatever comes next."
In one of the best displays I've seen of a CIO vision aligning with his team, Jeffrey chimed in and said that their plan is to modularize the key services they offer. They want best-in-class content management, Web metrics, customer surveys, and-- if we have made the case effectively for GovDelivery-- Email & Digital Subscription Management. Jeffrey was very clear that modularization for them means two things:
1) NRC wants systems to talk with each other particularly on the reporting front so they can track results easily across their entire suite of Web tools / systems
2) NRC will use different systems (including hosted, Software as a Service platforms) provided they are best-in-class and work nicely together. If a particular module underperforms or is no longer necessary in the future, they will swap it out for something new because they own the data and content and can move to a new platform at anytime.
I find this approach very compelling for the following reasons:
-Encourages NRC to think about scalable strategies for ensuring systems work together
-Leaves the door open for using more modern, innovative, and cost-effective SaaS solutions that government sometimes avoids to its detriment
-Keeps the service providers honest and focused on continuous improvement and results
-Avoids NRC getting too embedded with a single service provider
I believe we will be hearing more about this type of approach and that modularization will become the goal of many Web teams.
We were talking about all of the great things made possible by Web 2.0: Information sharing, collaboration, improved integration of systems, etc., but CIO Ash made the point that whatever NRC puts in place needs to anticipate "whatever comes next."
In one of the best displays I've seen of a CIO vision aligning with his team, Jeffrey chimed in and said that their plan is to modularize the key services they offer. They want best-in-class content management, Web metrics, customer surveys, and-- if we have made the case effectively for GovDelivery-- Email & Digital Subscription Management. Jeffrey was very clear that modularization for them means two things:
1) NRC wants systems to talk with each other particularly on the reporting front so they can track results easily across their entire suite of Web tools / systems
2) NRC will use different systems (including hosted, Software as a Service platforms) provided they are best-in-class and work nicely together. If a particular module underperforms or is no longer necessary in the future, they will swap it out for something new because they own the data and content and can move to a new platform at anytime.
I find this approach very compelling for the following reasons:
-Encourages NRC to think about scalable strategies for ensuring systems work together
-Leaves the door open for using more modern, innovative, and cost-effective SaaS solutions that government sometimes avoids to its detriment
-Keeps the service providers honest and focused on continuous improvement and results
-Avoids NRC getting too embedded with a single service provider
I believe we will be hearing more about this type of approach and that modularization will become the goal of many Web teams.
Leave a comment