Schools Get an F: Our Kids and Tech

While I am loathe to admit it, I danced on a lighted dance floor. I did The Hustle. I was quite underage to be going to clubs, but that's what we did. Those were the times I grew up in.*

Why the confession?

Because while I was a girl--disco dancing under a mirrored ball--I got a better computer education than high-schoolers get today.

At my working-class public high school, I took a "computer" class. We had to learn a language and write a program. We called the computer on the special phone, put the telephone receiver in suction cups and typed the commands to run the program. If the program didn't work, we had to figure out why. Line by line. And when it worked, we had accomplished something and did a happy dance.

I used  the C:\ prompt on my first computer (at work). Not because I am geeky, but because that was all there was. We had to imagine what was behind the dir command, because directories were opened one at a time. There was no tree, like in Windows, so you had to abstract and remember the directory structure.

The very, very basic programming and directory commands that I learned introduced me to using computers. I've been lucky enough to work with nice, smart, truly geeky people to help develop my technical knowledge. But I had something to build on, a basic computer literacy.

My kids go to pretty good schools. Their computer classes include how to use Excel and Powerpoint. Kids don't need to learn how to use productivity software. They just use it. "Programming," when offered, is usually HTML markup. They don't use logic. No IF...THEN...ELSE statements. The teachers don't use computers and are reluctant (don't know how?) to use them in class. The teachers who teach technology are hockey coaches. Kids get lessons in net-etiquette but not in three tier architecture.

We think that "born digital" kids know technology, but many of them can only put together a tacky, over-animated, under-researched slideshow. We have web "programmers" with a knowledge of HTML which they have parlayed into a visual programming language, but without any understanding of databases and data structures, systems analysis, or resource management. And, we have leaders who run programs based on technology, but who disengage whenever tech is mentioned.

Kids use technology and computers from sunup to sundown, but they don't know how it works. And they need to. Whether or not they are computer scientists or technologists, everyone needs a basic technical literacy. We teach the basics of reading, the building blocks of math, the structure of writing, but no fundamentals of technology. This is a huge mistake.

Government depends on the effective deployment of technology to solve problems. We need to recruit people who can write effective RFPs, navigate technology issues, oversee technology and technologists, as well as be geeks. But, that means we need people with the right knowledge and skills in the pipeline.

Kids do need to learn that The Cloud consists of physical servers, that data quality is critical to good output, that the semantic web can help machines make sense out of information on a web page so information structure counts, that information stored across multiple datasets and servers can be combined and mined, and all this is at least as important as whether a train leaving Boston for New York will beat an earlier, slower train from Providence.

Teachers, principals, schools, Secretary Duncan, let's get back to the future and do some meaningful updating of our technology curricula.

Technology is the fourth "R"--reading, (w)riting, 'rithmetic, and rechnology (that last one only works when spoken like Scooby-Doo another relic of my past).

[* here's how I was saved. Not quite fodder for On dot-gov.]

On the Side: Sidewiki and SideKick

First, a side of Google. A few weeks back, Google introduced a new feature on it's Toolbar letting people comment on any web page. Called Sidewiki, people with Google accounts can comment on the entire content of a Web page or about specific portions of the page. They can also publish these comments to Twitter, Facebook and Blogger accounts.

Why is this important? Well, it's importance depends on it's popularity, but it frees comments from websites by opening all websites to comments--outside any comment, moderation or policy of a site.

People can have discussions around your site, rather than on it. Google wins by collecting information about pages and sites from humans rather than machines to grow their search algorithms. It's also another potential ad space--imagine an ad for Coke on the Pepsi homepage, Or ads from private sector employers in the same browser window as usajobs.gov.

For site owners, Google lets you claim your sites on Sidewiki. It's a good idea, too, since site owner comments appear first. You'll need a Google Webmaster Tools account. Many government sites are already using the Google Webmaster tools after the the Google Sitemaps push in dot-gov a few years back. Follow the steps here to claim your site. It took my team about ten minutes.

My second side is a side of the cloud you didn't want to see. People using T-Mobile's Sidekick smart phone lost all of their data supposedly safe "in the cloud."

A server meltdown over the weekend wiped out the master copies of personal data -- including address books, calendars, to-do lists and photos -- accumulated by users of T-Mobile's formerly popular Sidekick smartphone.

This computing calamity allows Sidekick owners only a faint hope of backing up the information currently on their devices, and none of recovering anything they'd trusted to online storage. And it leaves T-Mobile and the operator of the Sidekick's data service, a Microsoft subsidiary formerly known as Danger, Inc. -- oh, the irony! -- with some serious explaining to do.--Read more on WaPost.

Is this a setback for cloud computing? Well, it does put a damper on the cloud hype-machine. Importantly, the "cloud" in question was a single server--a single point of failure. To me, that doesn't sound like a cloud application but an application called "cloud computing."

For government, at the simplest it means to make sure you know what you are buying, understand redundancies and risks, and NEVER let your data get out of your control. A tough reminder, caveat emptor.

Hey dot-gov! Don't Believe Your Hype

Success! Popularity! Fans! Page views! I win! Seems everybody wants to be Internet-important. Not to bust anybody's bubble, but government success and engagement numbers benefit from some perspective.

For starters, Federal Computer Week listed the "Top Ten Agencies with The Most Facebook Fans." Tops is White House's Facebook page with (now) 375,000 fans. That's a respectable number that continues to grow. But for comparison, the Facebook page for Nutella--that chocolate hazelnut spread--has 3.3 million fans. Plus there are two other Nutella fan pages with 977,000 and 750,000 fans each.

NASA, government's popular space agency, is pulling closer to 10,000 fans of it's Facebook page. Pink Floyd--a band that released it's last album the day that Netscape was founded and who created one of the best rock albums of all time Dark Side of the Moon (released in 1973 the same year that NASA's space station Skylab was launched)--has 1.6 million fans. [See also Mark Drapeau's post on this topic.]

Second, there are the arguments I hear about the important power of government content and presence on the Internet. Overall, this is true. According to comScore data* all dot-gov traffic combined puts government among the top 10 online properties.

Looking closer at the numbers is more sobering. Because government sites are fragmented they are less trafficked than the aggregated numbers show.

For example, the online classified site craigslist.org has three-fifths (60%) the traffic of the entire government. Comparing the State Department--despite high traffic for passport and travel information, the sports-entertainment site ESPN has ten times more visitors. Commerce.gov--whose data includes hurricane and storm tracking from noaa.gov, weather.gov, time.gov--has less than one-sixth the traffic of the popular Weather Channel. And, the transaction heavy Social Security Administration has 10% of the visitors that Wal-Mart does.



Government websites and social media efforts exist in a broader ecosystem. Yes, let's celebrate success, but let's first define and refine what that means. The tough news? Looking at numbers without context can lead to believing that you are more important than you really are. The good news? The fact that you are less important than you think doesn't mean that you aren't important at all.

* The comScore data on government sites July 09 and regarding other media sites Aug 09.

When You Wish Upon The Cloud

Government cloud computing is being touted as the next new thing. Promises of cheaper costs and a reduced carbon footprint, along with consumer experience with the ease of free e-mail and document sharing via "the cloud" makes it a no-brainer. And, bonus, instead of using out-dated government computing structures, the commercial cloud promises innovation and flexibility.

It's not necessarily easy, though.

First, a reminder that cloud computing is real. There are physical servers in physical server farms. It's important to remember that The Cloud is made up of data centers running 24/7/365. There are racks and racks of blades, power supplies, spare parts, monitoring tools and data center staff. These servers and computing capacity are shared by The Cloud tenants. The Cloud is excess computing capacity from the likes of Amazon and Google. The Cloud is not frozen water crystals or fluffy cotton puffs. It's not magic. The Cloud is physical. Learn more about The Cloud here.

This is important because issues with cloud computing are real, too. And real is the backbone of my wish list for government cloud computing. I wish for

Analysis of the risks. Some security experts are very concerned about the security of cloud computing. Casey Coleman, CIO of the General Services Administration, said, "Something like 45 percent of the IT portfolio is ranked at a FISMA certification level of low. What that means is that those applications and that data are candidates for running on some sort of commercial or hybrid cloud service." [Read more from Coleman in Federal Computer Week.] So, what can securely be run in a cloud environment? What can't be? And no cheating on the analysis because the idea of the cloud makes you nervous. Be real.

Analysis of the costs. It makes intuitive sense that money can be saved by sharing computing resources, but the devil is always in the details. Consumers think that software and storage is free--Facebook, Gmail, Google Docs--but they pay by viewing advertisements. Will some applications and storage be on a commercial cloud? Will government data centers shut down? Will they connect and share computing power to become a gov-cloud? Will government share applications with commercial and retail tenants? What would it cost? What about software licensing? Cloud-wide software licensing agreements? Money is real, too.

Useful cloud services. I want to improve accessibility of content by having captioning, live captioning, and translation services on demand. I want a government-wide blogging platform like Blogger for Government. The Department of Defense is already doing this in the dot-mil domain--DoD Live, Army Live, Air Force Live, Coast Guard Live--using a common Wordpress install. I want to be able to transfer large files securely from agency to agency using a cloud FTP server. I want a platform solution for posting multimedia and conducting surveys. I want easy access to website analytics--and, better yet, a way to compare the traffic data across agencies. I want government-wide options for search, dialogue, white pages, email, relationship management, instant messaging. And, I want the service whether it's available on the GSA schedule or via another purchasing option. No reason to be parochial in The Cloud.

What I want from the government cloud. Quicker--like "just in time"--purchase and implementation of tools that are being used in government. Removing roadblocks and silos that make government function like hundreds or even thousands of governments instead of one. Each of these mini-governments have their own ways to buy, their own ideas of security, their own interpretations of the Privacy Act of 1974, their own cookie policies, their own implementations of accessibility guidelines, and their individual risk tolerances. This makes sense for individual agencies who know their particular niches, but it makes no sense to the people--businesses, NGOs, staff, citizens--who need a simple answer and a single conduit to find it. Last, and not the least, I want citizens to control their own identities and to manage their relationship with government not on a per-agency basis but in a system that recognizes that they are whole people. This would make a real difference in the way government does business.

Now, keeping it real, what are YOUR wishes for the government cloud?

Searching for My Inner Craig

Topic One at the big Government 2.0 Summit here in Washington last week was "What is Gov 2.0, and how do we get there?"

This isn't a new question. Twenty-seven months after HHS launched the first Cabinet-level public discussion via a blog, we are still trying to define both the destination and the journey.

My own embrace of a new, open, transparent, participatory and collaborative era of government is shackled by the fact that I am an implementer. I don't get to sit on the sidelines and make smack-talk. I have to figure out how to make this work operationally, legally, and effectively for a federal agency. And, I would be a big, fat liar if I didn't admit that it is harder than it looks and more than a little scary [insert your favorite "not safe for work" link here].

This is where my unknowing mentor Craig comes in. Craig, the man who put the Craig in Craigslist, has been successfully herding cats--by not trying to herd them--on the humongous, world-wide online classified ad site and community he founded in 1995. He's also an active advocate of improving government services.

I've been studying Craig's zen-like approach to service and communities as a model to help me with Gov 2.0. In searching for my inner-Craig I've begun to identify some "truths" to help in actualizing open, transparent, participatory and collaborative government.

Truth 1 Trust. Craig says, "Most people are trustworthy and good and want to treat other people like they want to be treated." While this seems easy, in a bureaucratic, conservative command and control organization--like the government--it's easy to get stuck on the word "most." Since not everyone is a good guy, risk-averse organizations develop structures and policies to treat all comers as if they were "bad." Michele Weslander Quaid, CTO for the Office of the Director of National Intelligence, said that ODNI hired a risk manager to help make decisions based on risk/reward. By identifying potential risks and the chance the event will occur, government can develop policies that make sense. Working from fact, not fear, lets us trust people to do the right thing--even when it's something we didn't expect--and get out of their way.

Truth 2 Patience. Government social media and transparency efforts are in their infancy. We need to take the time to build out a process. It won't happen overnight. Craigslist grew organically in the Bay Area for years. There were trials and lessons learned to apply to new cities as it gradually expanded over a decade. This isn't to say that we need to slow down efforts, but that there will be successes and failures. We need to learn from both. It's like a three act play. After the heady first act of new blogs, video sharing and wikis, we are now in the long second act where the heroes are tested and do battle, make mistakes and learn how this works. We are still a ways from the climax and dénouement of Act III. We can't rush the story.

Truth 3 Customer service is public service. It's easier to have all the answers than to spend time listening to your audience. It's also not a successful strategy. For government, our audience--our customers--are the American people. We don't make government for the sake of government. We make government on behalf of, and in service of the people. So, its up to us to get out of our cubbies, our jargon, and our assumptions and get out of the way of the information and services people need. Behind Craigslist is the philosophy that people are basically good and their needs fairly simple (see trust above) so a minimal structure led by user needs will let people work things out by themselves. Government should not direct the user, the user directs the government to meet their needs.

Danielle Blumenthal is getting at this in her recent blog post.

Silence is not the answer. Jargon is not the answer. Long sentences and self promotion are not the answer. Let's stop talking to ourselves in a haze of groupthink and fear and start having real conversations about who the customer is (the public) what they want and need to hear (the truth) and how we need to say it so that they really get the message (any method of communication that works).--More from Branding and Social Media.

Knowing the truths is not the same as truly incorporating the truths. I am not all the way there, but I have a path. And I am working on it.

Thanks Master Craig, from Grasshopper Gwynne.

[For more on Craig, check out his blog or the recent Wired Magazine feature on him. ]

Pulling the Plug on Underperforming IT Projects

The Department of Veterans Affairs pulled the plug on 45 problem IT projects, pending further evaluation to see if they should continue.

In preparing data for the so-called IT Dashboard, a site that offers a window into the complex and costly process of procuring government IT services, VA officials discovered problems with some of the agency's IT projects. For example, while sifting through the data, VA Secretary Eric K. Shinseki and CIO Roger Baker learned that a scheduling project was running 17 months behind schedule, Kundra said.

Shinseki and Baker announced on Friday that they temporarily stopped development of 45 projects that are either behind schedule or over budget to determine if they should be canceled or salvaged.--Read more on NextGov.

The IT Dashboard allows users to learn more about information technology projects, like the VA's Health Data Repository, a $28 million project that is way behind schedule.



In addition to cost and schedule information, you can easily learn the purpose of the project and review other official documentation. And, very importantly, you can provide your thoughts to the CIO on specific projects.

This project is a tough one for agency CIO's. They are required to very publicly report and evaluate their projects. Many of them are responsible for projects that they didn't approve and in some cases went sour before their arrival. But it's important to begin to get an honest handle on IT projects and expenditures. And it's even more important to do something about them.<

Bravo to the VA, and bravo for this new transparency resource.