Coaching with Mindsets in Mind - Big Takeaways for the Start of a New School Year

Big Takeaways for the Start of a New School Year

Well, the new school year has already gotten underway, but it seems that I am just now coming out of the fog and swirl of activity from the "boom" that marks the first day of classes.  With fall trips behind us, laptop rollouts and MAP testing done and dusted, and classes finally settling into a rhythm, it is time to reflect upon coaching from last year with an eye towards the future . . .

Here are my takeaways and thoughts/extensions for each:

• From my end of year coaching survey, I believe that you can have someone who is a capable or even advanced user/facilitator/integrator of technology in the classroom, who is still in a Fixed Mindset when it comes to educational technology.  They are using/integrating a number of technologies effectively in their classroom, but are very comfortable with what tools they employ and are not open to looking at or experimenting with new tools.  With the train analogy from an earlier post - they are in the lead car but are doing nothing to help move the train forward as a whole, or to lead those in the front of the middle car into the lead car.  They remain siloed and comfortable in what they are doing in their classroom.  Sidebar - this is where the train analogy starts to break down, as the cars represent where a teacher is on the ed tech scale of integration, rather than incorporating their mindset as well (which is perhaps, more important).  So what's the way forward?  Screening for mindset and nudging these types of faculty forward into a Growth mindset through conversations and exposure to new tools which can be specifically employed in their classroom/subject area/discipline can help to shift them into a more collaborative and open stance.  These faculty members might be shifted through an individual conversation or through a conversation with a peer or in their own Personal Learning Network (PLN).  Or perhaps the shift will occur through some "just in time" training that comes up, or through exposure to a new tool or idea during a PD workshop, conference or Speed-Geeking session.  It's hard to identify when or where a shift in mindset will occur with these folks, but seize the opportunity when it arises and turn these folks into teacher-leaders with ed tech.

• Again, from my end of year coaching survey, there are some faculty members who take a passive role when it comes to coaching.  Their stance is that they do not have time to consider new tools or to connect with other teachers in their discipline.  They expect everything to be brought to them for their consumption/consideration where they will passively decide whether it is something worth their time (usually not, or it will be "deferred" until a later time). These faculty members do not engage in the coaching process, are not very self-reflective and are therefore in a Fixed mindset.  They are notoriously hard to reach and to work with, as they would truly rather ignore you as a coach, then actually engage with you to improve teaching and learning.  These folks need to be nudged into a Growth Mindset to engage in the coaching process, which is hard to do.  If they are part of a team (teach a shared course, or are part of a grade level or subject team), then perhaps reaching this particular faculty member is best done through the team.  If their team decides to move forward with a new tool or approach, then they will have to follow along.  The toughest "nut to crack" is the stand-alone teacher who does their own thing and does not really belong to a team (they typically teach all stand-alone classes).  So how do you reach them?  By engaging them in conversation about their classes at every opportunity that presents itself, and by exposing them to new tools along the way.  The Walk-through/Check-ins that I regularly conduct also help with reaching these teachers, as it brings coaching and the conversation directly to them individually and personally.  All of these points of contact will help to nudge them forward, some faster than others of course.

• Working directly with a team of Growth Minded faculty has been very fulfilling professionally for me, as well as for members of the group/team.  This is what I do with the HS Tech Collective, which has grown out of what started as a decision making tech committee, into a collaborative think tank for professional sharing around educational technology.  It is not composed of the most technologically adept or switched on faculty.  The group composition changes each year (there is one only member who goes back to the first year committee, and another who has drifted in and out of the group over the years) and they self-nominate/apply to join the Collective.  The short application acts to screen for mindset, rather than looking at their tech skills or abilities.  By focusing on what people want to learn about and experiment with in their own classrooms, I look for people who are expressly not experts in a particular tool, but are Growth minded towards trying something new and different that they are interested in.  These faculty members have already reflected on their own teaching practice and have self-identified their own need or gap or problem of practice that they want to work on.  Bringing Growth Minded faculty members together around ed tech, to share, collaborate and simply converse with no meeting agenda is transformational for everyone involved, which in turn gets spread back to their departments or co-teachers of shared courses.  Working with and developing the Tech Collective each year has been a game-changer for me as a coach, and is influencing the overall culture of the school as it matures and spreads.  So my takeaway here is simple - keep the Tech Collective going, moving forward, developing and changing the school culture in positive ways.

Takeaways from a Short Jaunt to HEL and back

A few weeks ago, I jumped on the opportunity to go to Helsinki to attend a workshop on Collaboration and Peer Observation with expert Fran Prolman.  The one-day workshop was being held at the International School of Helsinki (their entire faculty was attending) and sponsored by CEESA (which made it free for me to attend, thank you very much!).  We had a small crew from Warsaw there, and there were other teachers from Krakow and Riga as well.

Did you know . . . HEL is art deco?

My school brought in Fran this past fall, to work with our faculty on team building and protocols for having those "difficult conversations".  Having worked with Fran before, I knew that this would be something worth going to.  I really like Fran's straight-ahead, tell-it-like-it-is style of presenting, and how she encourages everyone to engage in professional conversations . . . even when they are difficult ones to have.  As I was going to HEL, I had a few "burning questions" (sorry, own intended ;-) in mind for Fran to answer about what I have been doing as a Tech Coach with conducting regular Tech Walkthroughs.

As we progressed through the workshop and got into the meat of Peer Observations, I began to wonder about how my Walkthroughs fit in with the model that she was presenting.  To help build a culture of collaboration in a school, having the trust and shared goals in place first, for Peer Observations to take place, are a given.  Peer Observations should be initiated by the observee (yeah, I know this is not actually a word but I am going to use it anyway), and they should direct the observer on the areas/topics they want data and feedback on, and the observations are typically longer or even over a period of time.

Storm clouds in HEL

So how do Walkthroughs fit in?  That was my new "burning question" that immediately sprang to mind, which Fran answered for me.  She told me that my tech walkthroughs were perfectly fine to do, and serve a different purpose than the more formal peer observations.  Although the observees are not initiating the walkthrough and are not directing what I am observing, they do know in advance why I am there and what I am looking at (technology integration in the HS).  Because the faculty know this in advance and expect me to regularly drop by their class at random times for a few minutes, my Tech Walkthroughs are productive and useful.  They have a clear purpose and understood parameters, the most important of which is that I am visiting their classroom in a non-evaluative role.  And when the walkthrough turns into a check-in with the teacher (because there is no class), then it is still time well spent through making connections with faculty, building currency, and bringing coaching/support directly to them.

Once I had confirmed with Fran that conducting regular walkthroughs as a tech coach was a good practice, I then pressed on with my original "burning questions" - Should I encourage other faculty to come along on walkthroughs in order to see other people's classes in action?  When I observe something in a class where I could suggest a change of approach/delivery/tools, should I give that unsolicited feedback to the teacher?

Yes, it does snow in HEL!  And they do like the colour red!

For the first question, I have been trying to get other faculty members to come with me on a walkthrough but I have not had anyone take me up on it.  Fran set me straight on this though - this will not work as anyone's class that we walked into will change the dynamic of the walkthrough.  In essence, the observee knows why I am there and what I am observing, but they don't know what someone else will focus on or what their goals for being there are.  This is where the Peer Observation model comes into play, where the observee directs the observer in what jot look for, collect data and give feedback on.  Fran cut quickly to the root of why I shouldn't do this and why it wouldn't be productive, so I will no longer suggest or pursue doing this and I now know why.

For my second question, it is something that I have been wondering about - giving unsolicited feedback or suggestions to a teacher about something observed in their lesson.  Fran's basic direction here is "don't do it".  Again, relating back to the Peer Observation model, the observee needs to choose what they want to learn about in their class, and direct the observer in what data to collect and what they want feedback on.  Giving unsolicited feedback can be perilous - Fran's advice here was to tread lightly or not at all.  If you really have to provide some feedback on what you observed in someone's classroom, then you must guide the teacher to think about and reflect upon what you observed.  Do not judge, do not evaluate, do not interrogate, do not ask "why" and do not make suggestions on what to do to "correct" the issue.  All you can do is gently/collegially/professionally guide the teacher to reflect on what happened and to come to their own conclusions about what the problems & solutions might be.  Or just don't say anything at all . . . after all, as a Tech Coach I am not there to evaluate, but to support and coach.

These are my personal takeaways (there were more, but more specific to my school rather than for my role) from a short, one-day focused workshop with Fran Prolman.  Each of these items has a direct impact on my daily coaching practice and how I work with my faculty - that's a big win in my books!  It's a great feeling coming home from a conference experience with your "burning questions" extinguished, and with practical advice which you can implement immediately . . . well worth the trip to HEL and back.

Going on Walkabout - A TechXcursion in your own School

Classroom walkthroughs are a popular and current tool for administrators to gauge what is going on in their school, but I have found walkthroughs to be a simple alternative to observational meetings as a Tech Coach.  I have divided up the HS into four different areas or zones, and I am intending on conducting a Walkthrough/Check-in of each area about once a week.  I have always been interested in getting into more of the HS classrooms on a regular basis, other than when I am meeting with a teacher, perhaps observing their class on their request, co-teaching a class, or delivering some kind of tech-related lesson to students.  Getting into HS classes can be especially challenging due to the usual reasons of time (many teachers equate a classroom visit to an unwanted disruption, or they go the other way to "put on a special tech show" for that one class), compartmentalization in the HS (a few teachers have a "closed-door" policy and do not want to be disturbed, ever), and fear of observation (some teachers perceive classroom visits as part of the teacher evaluation process).

I have only done a few of these walkabouts to date, but I think I have cracked the nut - finally!  I am branding my school walkabouts as Walkthrough/Check-ins to make them informal, short, strictly observational if there is a lesson going on, and teacher focussed if they are in a prep period or if they can stop and talk for a minute while I am there.  By making this less about the observation of their class (and the use/integration of technology in their lesson) and more about checking-in with them for how things are going (with the use/integration of technology in their classes), I am seeing an openness and appreciation that I have not seen before.

The "closed-door" teacher became much more welcoming and open when I was simply checking-in with them, rather than observing them.  The simple act of going to them to see how things are going seemed to validate that whatever level the integration and use of technology in their class is currently at, that it's alright.  I was coming to see them, to see how I can make things better, how I can help them "just in time" with something that they are working on, or tease out that niggling problem or question which they have never bothered to ask before or have forgotten about.  To me, a short check-in visit in a teacher's own space really helped to build currency between us.

Early days in our HS 1:1 program

For the "do not disturb" and the "am I being evaluated?" teachers, the unscheduled, informal and brief nature of the Walkthrough/Check-in has served to relieve the anxiety of the more formal (and lengthy) classroom observation.  I got a more realistic view into what is going on in their classroom with technology, had a chance to talk with students about what they are doing, and took the opportunity (if it presented itself) to check-in with the teacher on how things are going.  I find that the informal nature of the walkthrough, combined with the teacher-centric focus of the check-in, has helped to reduce "evaluation anxiety".  A good friend and mentor once told me that what I am best at (as a tech person) is "keeping it real".  I think the Walkthrough/Check-in model does just that, and gets rid of the anxiety and facade of classroom observations.

By conducting a short walkthrough of a section of the school, I can cover 1/4 of the HS faculty in 30-60 minutes.  I take notes along the way, and typically find a number of issues/problems/questions to further investigate, follow-up with and hopefully resolve.  Walkthrough-Check-ins also allow me to talk with students and see firsthand how technology is being used to enhance their learning.  I frequently hear about projects that particular teachers are doing with particular grades or classes.  But what about the other classes?  What about when their class is not working on a big or special project?  How is technology enhancing teaching and learning during those times?  What about the class or the teacher that I do not typically hear about?  What is happening in their class?  If I can conduct these Walkthrough/Check-ins on a regular basis over the school year, I will hopefully get some concrete answers to these questions.

Have you ever thought about doing walkthroughs?  Maybe you should!  If you are already going on walkabout, then how has it helped with being a tech coach or integrator?