Last July 20 we celebrated the 45th anniversary of Apollo 11's giant leap for mankind. I remember watching Neil Armstrong's and Buzz Aldrin's historic moonwalk on a black and white TV in a motel in Alamogordo, N.M. I was 12 and had grown up watching launches and splashdowns of the Mercury, Gemini, and Apollo missions. Dinner conversations included my dad explaining the fire and door failure that killed the Apollo 1 astronauts and my mom explaining how returning capsules had to enter the atmosphere at just the right angle or they would burn up or bounce off into space. On April 11, 1970, Mrs. Reams' language arts class was interrupted by an announcement that the Apollo 13 astronauts had safely returned. After Apollo 17, astronaut Harrison Schmidt, one of the last two humans to walk on the moon, returned to his hometown, Silver City, N. M. and spoke to high school students about the mission. Silver City is my hometown, too. I was in the audience.
In October 1, 2013 HealthCare.gov launched. We all remember what happened next.
In The Key to Successful Tech Management: Learning to Metabolize Failure, Clay Shirky ties the success and failure of those (and other) massive, technology based, federal projects to the practices followed by their creators. He emphasizes that his is not a political piece evaluating the merits of the programs.
Shirky's observations about going to the moon and launching HealthCare.gov offer a means to judge the implementation of the Common Core.
Now, I know the Common Core is not a federal project. But it is certainly a massive technology-based project of nation-wide significance that includes federal incentives, government bureaucracies, commercial interests, a divided public and profession, and the media spotlight. So, I think it's fair to critique how states roll out the CCSS using Shirky's standards.
I've rewritten Shirky's main concerns as yes/no questions that can be asked about any state's roll out.
- Is there a mechanism to rapidly report significant problems?
- Will the state's Common Core technology be slick or frustrating?
- Is the state's roll out a reasonable combination of features, quality, and deadlines?
- Do competing imperatives of broad scope with reduced timelines threaten the roll-out?
- Does the state's request for proposal for assessments allow small vendors to compete fairly with large vendors?
- Has the state made sure that the talent necessary for implementation is being deployed appropriately?
- Shirky argues that overly meticulous planning eliminates flexibility too soon.The biggest challenge is not eliminating uncertainty but adapting to it. Is the state generating detailed standards and timelines too far in advance?
- Is the state practicing "Agile Development" and "Test-driven Development"- the processes of dividing a project into small, testable chunks, with progress continually monitored and plans continually updated?
- Is the state avoiding a single, fixed plan to be delivered long down the road?
- Does implementation test the state's assumptions and produce new information that can inform planning?
- Is the state avoiding the embarrassment of unsupported claims?
- All new work involves failures and failures can be useful learning opportunities. Will failure be penalized?
- Are penalties in place for opacity and information hoarding?
I'm moving from being a cautious supporter of the Common Core to being a conditional supporter. I'm watching and using Shirky's criteria to evaluate how well the standards are implemented in my state (Arizona). I have no doubts that success or failure will be traced back to the process of how well the state rolled out the Common Core.
For more on the Common Core, see:
- The Common Core Debate: I'd Rather Be Well Than Right
- From, "Arggghhhhhh!" to "Awesome!"
- Common Core Math Instruction, Managing a Tripolar System
- My Teacher Leader Manifesto