Friday, April 27, 2012

Is Disruptive Innovation Compatible with Education?

Yesterday, I had an opportunity to listen to Ray McNulty, the president of the International Center for Leadership in Education, commonly known as Daggett's organization.  We spent a lot of time discussing innovations in education, and especially how those innovations affect the work of organizations as they define and refine their #rti process.   This was our capstone meeting for the IRIS/RTI pilot project in Iowa.

***
McNulty spoke last year, and was the first person to introduce me to John Hattie's book, Visible Learning, which was a meta-analysis of research into education efforts with a large effect size.  Grant Wiggins also highlighted this research on  best practices in a recent post, and Hattie's latest book is Visible Learning for Teachers, which tries to highlight ways to implement these ideas in the classroom.   Ray reminded us that socio-economic status and home environment were not on the list, in spite of our assumptions and misconceptions to the contrary.  That gave me food for thought immediately on helping all students achieve.

Then, we discussed turnaround schools, including the successful literacy initiative at Brockton High school.   Not surprisingly, McNulty pointed out the need for a systemic change, which led to this insight:

If you could get teachers in your school to do only 3 things well and consistently, what would you ask of them? 


How simple is that?  Three things, done by all on a staff, perhaps proposed by different cohorts of stakeholders who came to consensus.  They need large effect sizes, and perhaps are the things that @jasonglassia referenced in a tweet earlier today.  That's the job of the system.  CHOOSE WISELY.

***
But then, Ray pulled a rabbit out of his hat.  I felt like he was channeling Steve Jobs as he described his 'one last thing'.  Here it is:   In order for us to move to the next level, we must value innovators, and realize that innovation is what we must accomplish, rather teachers who produce deliverables.

Deliverables are lessons, lectures, papers and tests.  They include presentations, discussions with the board, and newsletter posts. They are important.  They form the backbone of our system, but they do not encourage the types of questions that promote innovation.  In education, we have traditionally valued deliverables over innovation, so entrepreneurial ideas and educational outliers are often discouraged or pushed out.


Five points to consider (Ray's McNulty's statements in brown, followed by my questions):


  • Innovators practice associational thinking.  
    • When was the last time your staff members connected to other disciplines, businesses, and countries?  
    • Does your staff look for global change, or stay focused on their own buildings?
    • Do staff members have charge of their own networking and PD, or is the role of your administration to design and control such experiences?
  • Innovators have the ability to experiment. 
    • When was the last time your staff got to try something just to see IF it worked? 
    • Is there a  'fail-forward' reflection policy to innovation? 
    • Does your system adopt 'programs' or 'best-practices', and how is stakeholder input maximized?
    • How are experiments in the system communicated with your other stakeholders?
  • Innovators have the ability to observe from an outside vantage point.
    • Does your system look at other successful systems to see opportunities and potential pitfalls?
    • Have you encouraged your staff to visit other successful systems to see different points of view?
    • Do you value staff comments and questions, or squelch them?
  • Innovators have the ability to question.
    • Does your staff include questioners? 
    • Is there a systemic process to encourage questioning?
    • Do staff feel safe in asking questions or making observations?
    • Are questioners of value, or are they 'loose cannons' to be marginalized?
    • How does questioning move from the stakeholder to the administrative level?
  • Innovation doesn't occur in an entire system; it grows in unexpected pockets, with an administration that then builds capacity.
    • What innovation pockets exist in your system?
    • Does your system allow for disruptive innovations?
    • Are staff members who passionately and effectively pursue an unexpected innovation rewarded?
    • Are system structures formed to encourage innovations to be shared and mentor others?

I find myself, after working in quite a few systems, reflecting on how very hard it is for a CEO or system expert to welcome disruptive innovation.   After all, the expert has large amounts of training and theory in setting vision, developing budget, and setting goals for the management of their organization and employees.   They make reasonable statements like, "We should  consider that next year," or "We've always done that and it's worked alright," or "I didn't expect you to do that."   Such comments work well for loyalists who want to produce deliverables and work within the company framework.  Our industrial model is built on such leadership.

But that is EXACTLY the problem with innovators.  They are intrinsically self-motivated, and driven by passion rather than a company vision that operates on a 3-5 year time frame.  They will do things without being asked, and often succeed at possibilities that are remote.  They are frustrating because they want new challenges and challenge traditional structures of top-down leadership, and they offer advice that is unsolicited.

How do we balance the needs of the system, which places its focus on stability and deliverables, with that of transformative learning, which encourages the value of innovation?  It is tough.  Excellence is not mandated, it is coaxed, like a fragile flower, out of soil that has been well-prepared and watered.


Sunday, March 25, 2012

If They're Succeeding Why Do I Feel Bad?

Tomorrow morning is quarter grading period time.   All information must be posted by 8:30 am so it can go out to parents, and interested students.  I always find myself waiting until the last night to enter in those final grades, reluctant to finalize the process we've attempted in the last 9 weeks with a grade.  My rationale?  In the end, most of your grade will be represented by that little 'dash' that forms the spaces between the moment you were born and the moment you moved on beyond this life.

I hate grading. Honestly, I don't let kids go on until they show me competence in an area.  They must, for example, be able to show me mastery of vectors in more than one way, explaining the concept using scaling of golf courses, personal discussion, and Google forms.   And they must do a great deal of personal reflection on their tasks, which I grade for understanding.  The projects are the main part of the grade, and the assessments at the end are to make certain that they have been successful.  If they have not been successful, I pull them out, and reteach, and let them retake the test.. That means that I pull them out DURING my class, usually, and then work one-on-one with them.  And then I give them the score they earn on the retest.  Then I give them an alternative way to make up the project work, which includes setting up the lab, for example, at home and then bringing in their data, or their edible race car, or whatever it is.

So if I fast-forward to the end of the semester, I have kids who 'normally' get Cs and Ds but who have worked hard for me and have scored As and Bs.  And if they retested and 'got it', so what if I don't have low scores? But when I post grades, that nagging self-doubt of argument works like this:

"Is learning about trying to weed out the As from the lower levels, or is it about checking to see for their understandings?  Am I giving out As because I believe in their competence?  What does an A mean, anyway?"


The content I teach kids is deep and focused on the essential concepts found in the Iowa Core.   The ideas I want my kids to have are based first in relevancy, grounded in project-based learning, and evidenced through daily work, collaboration, and honest dialogue.  It should be designed to help kids to think about their thinking as well as helping them to succeed.

If what I am doing is right, most kids SHOULD be succeeding at an A level, at least in a definition where A translates from competency.  I should be reveling in the idea that my kids know what is expected, I work with them to get it, and I check for their understanding.  But not many people do it this way. Perhaps that bothers me most of all.

And that question haunts me:   Am I doing it right?