Why New York Isn't Ready For The Common Core [PhilanthropyNY] - The Jose Vilson

Why New York Isn’t Ready For The Common Core [PhilanthropyNY]

by Jose Vilson on December 17, 2013

in Jose

bittenapple

I was recently asked to write for the Education Funders Research Initiative, a collective of education funders and researchers from around New York City, and their first question was, “Is New York City ready for Common Core implementation?” Of course, I saw plenty of problems with this statement:

Right now, however, I don’t see how New York City, much less our state, can meet or exceed the expectations laid out for us as a result of the Core nor get students “college and career ready.” Academic standards are only as effective as the organizational standards we hold for our system, and currently, we still have far too many structural issues. For one, curriculum publishers still work under the auspices of the previous way of thinking about instruction: “If we slap a sticker on our textbooks and say they’re Common Core, districts will pick it up and they won’t know any better.” Developing coherent curriculum is far more than just following the textbook. Teachers have to develop their own materials to accompany and bolster any textbook, new and old.

Click here to read more. Comment. Share. Thanks!

Mr. Vilson

photo c/o

{ 1 comment… read it below or add one }

Joanna Boyd Best December 18, 2013 at 2:58 am

I like the article because you focus on the actual nuts and bolts of working with the standards in application. Calmly, you point out the areas for improvement needed if we are going to make it work and you find value in the goals of the standards, the integrity of teachers for knowing not to just grab anything that commercially boasts of CCSS alignment, and you do not get hung up on how the standards came about (you leave politics out, which is refreshing).
I hope your recommendations are considered and used.
Thank you for being a rational voice for how to move forward.

Reply

Leave a Comment

Previous post:

Next post: