The goal of starting up the NASA Ames CIO blog here last week was to share some exciting projects our team here at Ames is working on and to encourage dialogue and participation. Based on all the feedback and comments, we’re off to a tremendous start! Thank you for all of the constructive feedback and comments on the first posts, both here and on the other sites where this blog is syndicated. Rather than responding to each of these comments individually, let me respond to some of the overall themes and elaborate on a few things that were mentioned in the introductory post.
Openness and Innovation – We vs. I
You probably sensed a lot of “passion” in my first post, and this is exactly what makes NASA so cool. It’s what we all share for what we are doing here at NASA — it’s what brought me here and why this is a great time to be at NASA, at Ames and in Silicon Valley and to be part of this incredible team of people. There has been a lot of discussion about the role of the team (We) versus the role of the individual (I) and what a Blog is, and how it relates to Center and Agency policy. Perspectives shared on a personal blogs by a public officials raise many questions for bureaucracies designed for consensus-based decision making and diffused responsibility. When a public official says something on a blog, does this reflect public policy, or the opinion of the public official? This topic deserves much more time and space, but others have been thinking about the issues presented by blogging, including David Wyld at the IBM Center for The Business of Government at SLU, who recently published The Blogging Revolution: Government in the Age of Web 2.0. What I will add to the conversation today is that one individual in an any large organization will not accomplish anything significant. Teams can make significant things happen.
Standing On the Shoulders of Giants
I consider myself incredibly fortunate to have the opportunity to contribute to NASA. For me to even be able to talk about a personal vision for NASA’s future on the web would not have been possible without the passion and dedication of several generations of my colleagues, both here at NASA Ames and at our other NASA centers around the country. I’d like to acknowledge a couple comments from my colleagues. One was from Brian Dunbar, NASA’s Web Manager in Washington D.C. Another was from George Alger, who managed the people that now comprise most of the IT organization at Ames. Both have dedicated their careers to NASA and have built great teams and solid infrastructures. Brian and his team brought www.nasa.gov from this to this since 2003. George and his team built a solid infrastructure at Ames that was ahead of its time (in fact, the logical zoned network architecture George built at Ames five years ago is the “to be” state for the rest of the Agency over the next five years). The comments from George, who retired last year, and from Brian at NASA Headquarters remind me of how fortunate we are at NASA to have a culture that welcomes new ideas and diversity. I can assure you that Pete Worden and the leadership here at Ames have fostered this environment.
Collaboration with Microsoft and Concerns about Open Standards
While much of NASA’s data is technically available to the public, in many cases it’s far less accessible than it could be. Making NASA content accessible in platforms like Microsoft World Wide Telescope and Google Earth make content far more accessible to a much greater audience of people. It should be noted that all of the data will be accessible through open, public APIs, and in both of these examples Microsoft and Google have reimbursed NASA for the time and resources spent translating and hosting the data for their platforms.
Closing Thoughts
To be clear: the primary purpose of this blog is to share information, ideas and have a conversation that will lead to better and more informed decisions as we forge ahead into this new era of government in the age of web 2.0. In its charter, the Space Act of 1958, NASA is required to make its data available to the public to the greatest extent possible.
Openness and Innovation – We vs. I
You probably sensed a lot of “passion” in my first post, and this is exactly what makes NASA so cool. It’s what we all share for what we are doing here at NASA — it’s what brought me here and why this is a great time to be at NASA, at Ames and in Silicon Valley and to be part of this incredible team of people. There has been a lot of discussion about the role of the team (We) versus the role of the individual (I) and what a Blog is, and how it relates to Center and Agency policy. Perspectives shared on a personal blogs by a public officials raise many questions for bureaucracies designed for consensus-based decision making and diffused responsibility. When a public official says something on a blog, does this reflect public policy, or the opinion of the public official? This topic deserves much more time and space, but others have been thinking about the issues presented by blogging, including David Wyld at the IBM Center for The Business of Government at SLU, who recently published The Blogging Revolution: Government in the Age of Web 2.0. What I will add to the conversation today is that one individual in an any large organization will not accomplish anything significant. Teams can make significant things happen.
Standing On the Shoulders of Giants
I consider myself incredibly fortunate to have the opportunity to contribute to NASA. For me to even be able to talk about a personal vision for NASA’s future on the web would not have been possible without the passion and dedication of several generations of my colleagues, both here at NASA Ames and at our other NASA centers around the country. I’d like to acknowledge a couple comments from my colleagues. One was from Brian Dunbar, NASA’s Web Manager in Washington D.C. Another was from George Alger, who managed the people that now comprise most of the IT organization at Ames. Both have dedicated their careers to NASA and have built great teams and solid infrastructures. Brian and his team brought www.nasa.gov from this to this since 2003. George and his team built a solid infrastructure at Ames that was ahead of its time (in fact, the logical zoned network architecture George built at Ames five years ago is the “to be” state for the rest of the Agency over the next five years). The comments from George, who retired last year, and from Brian at NASA Headquarters remind me of how fortunate we are at NASA to have a culture that welcomes new ideas and diversity. I can assure you that Pete Worden and the leadership here at Ames have fostered this environment.
Collaboration with Microsoft and Concerns about Open Standards
While much of NASA’s data is technically available to the public, in many cases it’s far less accessible than it could be. Making NASA content accessible in platforms like Microsoft World Wide Telescope and Google Earth make content far more accessible to a much greater audience of people. It should be noted that all of the data will be accessible through open, public APIs, and in both of these examples Microsoft and Google have reimbursed NASA for the time and resources spent translating and hosting the data for their platforms.
Closing Thoughts
To be clear: the primary purpose of this blog is to share information, ideas and have a conversation that will lead to better and more informed decisions as we forge ahead into this new era of government in the age of web 2.0. In its charter, the Space Act of 1958, NASA is required to make its data available to the public to the greatest extent possible.
The last paragraph of the introductory post said… “If you are interested in following this blog…” however, I am not looking for followers, but to create an opportunity for those interested in having a conversation about NASA’s future to share their ideas. So, please continue your feedback and your ideas on how to improve NASA’s web presence and let’s make this is an ongoing conversation about NASA’s future on the web.
Thanks Chris for venturing out into these frothy unchartered waters. In the past, government has been a faceless bureacracy. The social media revolution is changing that. You are a pioneer, one of the many at NASA who have forged new uncomfortable paths for the way we do business in government. Our job is to manage risks, rather than be be risk averse; therefore, we may stumble on a rock or two along the way. But, at least we’re moving forward rather than standing safely still. I appreciate your eagerness and passion. Your blog sparked a passionate debate inside and outside NASA. The conversation stretches us far more than silence. I look forward to more debate and more forward movement. Glad you’re part of the incredible team called NASA!
😀
http://www.usa.gov/Topics/Reference_Shelf/News/blog.shtml
on subject of individuals contributions (personal opinion) vs statement of public policy, how about this: If a federal worker (Civil servant or contractor) wishes to express her/his thoughts on something related to what they know from their work, then, subject to usual disclosure parameters, they can do so. However, if they are speaking as a representative of their Agency and represent Agency policy, then their byline can be tagged with the logo of the Agency. That way the reader knows the difference. I know that as civil servant I didn’t give up my right to freedom of speech, but the recipient of any of my musings has the right to know if I am speaking on behalf of my employer or not. So even though my email address reveals my employer, note there is no logo next to my name.
For Chris Kemp,
Chris, congrats on the launch of Nebula. It will be interesting to see how the idea of integrated cloud computing relates to historically siloed departments and projects. On a related thread, I also applaud your call for “conversation” as well. The topology of computing “fabrics” is changing at a dizzying pace, and I hope that the use of hybrid, heterogeneous compute clusters can provide NASA value as a part of that cloud implementation, especially in massively parallel computation fabrics.
I also hope that NASA Ames can avoid the pitfall of the NIH syndrome – Not Invented Here. There is a vibrant community of innovation in developing applications for modeling, simulating and visualizing dynamically evolving, large-scale, complex systems, and I hope you will allow members of this community to help NASA push forward toward its objectives my considering these technologies.
Ken
IT IS IMPORTANT TO ME TO HAVE GOOD NEW SCIENCE INFORMATION AVAILABLE RIGHT AWAY. THANKS FOR POST THIS AND I WAITING FOR NEXT POST.