ISTE 2018 Takeaways

It's been over a month since ISTE 2018 ended and I left Chicago (and over two months since I posted here!) and I finally feel like I have been able to digest a small part of what happened there. For me, there were three major pillars to the value that ISTE provided. Every year I go, and this is my fourth year, I've enjoyed a big jump in my outlook, skills, abilities and connections, and this year was perhaps the biggest jump for me - though it's still quite a task to figure things. I'll do my best to simplify a complex few days. If I wrote everything that comes to mind, you'd be reading a novel, not a blog post.

He Tangata, He Tangata, He Tangata
There is a Māori saying, asking what the most important thing is and the answer is the people, not once, not twice, but three times. By far the most important part of ISTE is the people, and if it weren't for the people, there would be no point in me going.

One of the difficult things about being an educator and trying to do innovative things is that not everyone is on board. Many people don't have trust in you and often work against progress. It is at events such as ISTE where I find my tribe. These are the people that give me the energy to fight for what I believe is best for the learners in my care. These are the people that inspire me to be a better me. These are the people who make me question the things I do and the practices I preach. They give meaning not only to my career, but also to my life. The five days I spent at ISTE each year help me through the tough times in the other 360.

This was my first year at ISTE as an Innovator and I was lucky to connect with a group of other Innovators, especially the ones from Canada.

Oh Canada! Love the preparation for the final work of art. #GoogleEI pic.twitter.com/J2RUSNymVv

— Sandra Chow (@watnunu) June 24, 2018

This group of people were so inspiring to me and took me under their wing, making the week so much more special. I also had the opportunity to connect with some friends from NZ:

Representing @OrmPS and @OSC_Ormiston in Chicago #iste2018 @michaelteacher pic.twitter.com/Bsy55hKmHA

— Subash Chandar K (@elsubash) June 26, 2018

To make a long story short, I felt at home amongst the people in Chicago and that is so important when you're trying to do great things.

The New(ish) Tools
I've put tools in the middle of my three takeaways as it's probably the least important, but it's also the most practical. The two main themes I noticed this year througout the week were Geo Tools and AR and what better way to show them, but talking about Tour Creator, which is a combination of the two. If you've ever wanted to create your own Google Expedition, this is how you do it. It's super simple and in the week I had to try this with children, almost all of them completed a short tour and every child was super engaged - especially when we pulled out the Google Cardboard to have a look at them. There are loads of other Geo Tools that can be used (and I've seen them around for a while and every conference or summit always has a steady diet of session on the topic), including Tour Builder (not the same thing, though easily confused), MyMaps, Expeditions (now with AR!) and others.

The other tool that I saw a lot was VR, and specifically I looked at CoSpaces (and Merge Cube) a bit. It's quite easy to fall down a rabbit hole when you start looking at VR creation, so be careful. I also learned a little bit about Unity, which, when I tried it with year 5 and 6 children was a bit tricky - though the accessibility of tools like this is promising and is definitely something to think about if you've got older children.

One of the small things that I saw was that there is now a chrome extension that will allow you to add audio to Google Slides! It's aptly called Audio Player for Slides. Definitely worth checking it out if you've ever wanted to add audio to a slide deck.

I have also developed quite a nice appreciation for sketchnoting, especially after taking a quick lesson from a couple of my new Canadian friends. I'm not really one for taking notes, either written or sketched, but I personally find the sketches much easier to follow and more fun. So I'm going to do my best to get more people doing them so that I can have access to more sketch notes. I don't think its too difficult though. I just want to get a device that can do it all (it's funny the things you don't know about).

This is what @sylviaduckworth & @VirtualGiff showed me how to do! #GoogleEI #ISTE18 #ISTE2018 pic.twitter.com/rIJbBzyy2G

— Michael Davidson (@michaelteacher) June 23, 2018

Obviously there were more tools showcased (including a new Sphero, which I'm not sure if I'm even allowed to talk about here, but if you're going to get new Spheros, I'd wait a few months), but these were the biggest takeaways when it came to tools.

The Possibilities
ISTE fundamentally changed me this year. A byproduct of hanging out with a group of people who have done amazing things is that doing amazing things becomes the norm. When you hear people talk of writing their books, it becomes the normal thing to do. What I realized - and I mean really realized - is that there is practically no difference between myself and those people other than the fact that they've already done something really big.

How did this happen? Well, the Innovator program (and to a slightly lesser extent, the Trainer Program) has opened up many doors for me. I've probably been trying to go through more of them than I possibly could go through, but there was a convergence of a lot of these things at ISTE that made me feel empowered to do practically anything. The first was that I was given the opportunity to work at several booths in the Expo Hall and join in on other presentations. Spending time doing these things only helped further connections to others and plant a lot of seeds of ideas in my head. The Innovator Energizer, too was amazing. Just being in a room with so many inspiring people (and feeling Imposter Syndrome) was an amazing start, but then learning about Project Culture Shift (and joining in on the fun) was something else.

It was also a chance to start some conversations with people about collaborations, and things I've wanted to do for a while. But now those thing are starting to become a reality.

To put it simply: I've got plans. Lots of plans. Whether they come to fruition depends on how much time and effort I have and am willing to spend on them, and on getting others on board. Big things don't just happen on their own or by one person.

So here's to looking forward. Here's to new connections that haven't even been made yet. And here's to changing the world for better.

ISTE is an amazing experience for anyone, though I'm not sure if everyone takes advantage of its opportunities the way I have and will continue to do so. This is the start of something big. Watch this space for updates in the near and far future. But for now, my advice to anyone reading this: go to ISTE 2019. I'll see you there!

Book Review: Rosie Revere, Engineer

For a while I've been eying several books that would help support STEAM or Maker activities in the classroom. Rosie Revere, Engineer has been one that I've wanted to get for a while, so a few weeks ago, I ordered it off of The Book Depository. The story itself is a very nice tale of a shy girl who used to create a lot of creative and different inventions, but has been silenced because of the reaction of a family member. She learns later, from a family member that it's not about getting things perfect on the first go. This fits in perfectly with both the idea of Growth Mindset and the Design Thinking process.

There is a lot of potential for this book to lead into many different learning opportunities and ideas. It would be a great way to start a project where children build or create something.

But that's not all. There is also a companion book, Rosie Revere's Big Project Book for Bold Engineers, which gives an incredible amount of ideas to build upon the first book. You can find it at The Book Depository as well.

Though the book is primarily meant for individual children (it has many places for a child to draw or write) it can easily be adapted for a whole class to get them thinking in new and creative ways. As an adult, I was personally excited about the things in this book and potentially trying some of them on my own.

In the book there is a good deal of supporting information about engineers and engineering, as well as some advice about organizing your own "treasure" so that you can make your own inventions. There are also some step-by-step instructions to make a few different creative things (a small catapult and a solar oven).

The genius of this book does not end there though. There are also many real world challenges where the book asks readers to try to solve a specific problem in their own creative way. It also highlights the importance of "flops" and making mistakes.

At 94 pages this definitely is a recommended purchase for any classroom trying to bring out the creativity in children. It not only encourages children to build and invent things, but it gives them a few different methods and tons of inspiration.

There are a few other books in this series, so perhaps look for the reviews of those in the near future.

TED Talk: Adam Grant - The Surprising Habits of Original Thinkers

A long time ago I downloaded the TED Talks app on my tablet but in all the years it's been on there, I've not actually used it. The other day I opened it up, which caused it to start giving me some suggestions. I've watched a few of them in the past few days and here's one I feel is worth sharing.

It's all about what Adam Grant terms Originals - that is creative thinkers. He tells a story of how he missed an investment opportunity that would have paid off immensely for him because he didn't recognize that the ones who offered it to him were going to be successful.

A big part of the talk is how (moderate) procrastination can lead on to more creative responses. he says (and it's backed by his research) that if you put of completing a task it gives you more time to think and more time to come up with more ingenious solutions or responses. I found this to be very empowering as I do tend to be a person who procrastinates (and in fact, this blog post is a semi-procrastination from working on one of my Coding Across the Curriculum videos), but I also tend to come up with creative solutions. It's nice to see the connection between the two. It's also nice to be able to support those children who (again, moderately) procrastinate with their work - to give them time to think and mull over ideas. 

A second idea that he discusses is the idea that original people are full of doubt and fears. What is different however, is that the doubt is not self-doubt, but idea-doubt. That is, that original and creative people doubt that ideas will work, but don't give up on solving any problems. Many people doubt themselves so much that they don't even put ideas forward. This is not what originals do. He discussed the fact that you can (almost) predict the creativity of a person based on the internet browser they use (I'll let you watch the video to find out more on that though). The argument with that is not that your browser makes you creative, but the way you choose which browser you'll use reveals a lot about your mindset (so just changing browsers does nothing, I'm sorry to say to you Internet Explorer and Safari users - whoops, I just ruined the surprise).

The final point that he makes is that creative and original people produce a lot - and that a lot of it isn't their greatest. Most people who have done great and amazing things have got their because they tried many, many things. It is through those attempts that eventually they have discovered new and original ways of doing things. This ties into the whole idea that failure and mistakes help you grow (also doing an online course where this is being stressed - more on that when it's done).

Here's the talk below. It's definitely worth 15 minutes of your time. If you are one of the people he is describing then this can be very empowering. If you are not, then it can give you some insight into how you can be like that AND how you can recognize those people who are. 

Organizing an ILE (Part 3)

One of the challenges (or opportunities) that exists when teaching and working in a large space with many learners and many educators is that sometimes the children don't get to know all the other children. In a massive group, surprisingly enough, the same children tend to work with each other when given the choice.

As learning coaches, when we saw this we weren't too sure that this was the best for our learners. We wanted them to develop social skills that would enable them to work with anyone. We also wanted our learners to be able to reflect on their work, with someone who was a safe friend (or even a critical friend).

So we came up with the idea of having learning buddies. The idea was that whenever we had the whole group of them together, they would be sitting with their buddy. If we asked them to discuss anything, it would be with this buddy. So we made a list, which we started rotating every week and thought it would go smoothly. I guess by now I should know that nothing every goes smoothly. Some of our learners were doing as we asked and trying to have conversations with the correct buddy. But others were bringing their buddy with them and sitting next to their friend and talking to their friend. There was a lot of frustration.

Our initial thought was to put a forced seating plan in place so that they couldn't sit by their buddy. But cooler heads prevailed and we took advantage of a day when half of the learners were out testing to run a mini design thinking workshop. We identified the problem to the learners and we examined why this particular response was occurring.

The overall theme to the responses was that they didn't know their buddy and that they were more comfortable with their friends. Some of the buddies were goofing off so they wanted to make sure they talked to someone. We identified that the main problem was that they didn't have enough time to get to know there buddies. So we framed our How Might We question as:

How might we get to know our learning buddies better so that we talk to them and not our friends? (it may not have been exactly this wording).

From there were had the children do a crazy eights activity to come up with some possible solutions. Each child picked their favourite and pitched it to a partner. Each pair chose their favourite in that group and then pitched it to another pair. This continued until we had two ideas facing off against each other.

To be honest, all of the ideas were pretty good, but I liked both of the final two the best. The first was to have the buddies interview each other and the second was to have the play a game together. We combined both and changed the turnover rate between buddies. So every two weeks when they got a new buddy, there was a list of questions to ask each other AND we gave them a task to complete with the buddy. Those tasks were things such as: make a secret handshake, make something out of 10 lego pieces or design a logo for you and your buddy.

Things went a lot more smoothly after this. I can't say whether or not that was due to the fact that we did some interventions or the fact that the children were actually heard and empathized with (which is a big part of a design thinking approach). Either way, as the term went on, we as learning coaches did notice some interesting interactions and a growing sense of community amongst the learners. This effort was only a small part of our larger efforts but the idea itself AND the trouble shooting we did with the learners clearly has had some impact on the way our habitat runs.

Official Launch of The Monthly Maker

It is with great pleasure and after lots of last minute scrambling that I'm able to announce the release the first issue of The Monthly Maker. Due to an issue with gmail, I've moved distribution over to Google Groups for some subscribers today. Everyone should have received an email so if you didn't please check your spam or junk folders. There may be some emails in the coming days to add the remainder of the emails to the group for distribution. Apologies while I sort out the technical details (though admittedly the timing was great as I was able to get help from an actual Googler!)

You can access the newsletter below by clicking HERE.

Anyone who would like to receive future issues, you can subscribe HERE.

Feedback is always welcome.

Enjoy!

Stepping Out of My Comfort Zone

This past week, I attended the Whangarei EdTech Team Summit. After a few years of presenting (and having recently brought my learners to present at the Auckland Summit) I felt it was time to put my hand up for some new things. So when I got an email from the event organizer asking for someone to do an Ignite talk, I put my hand up and replied straight away. It was something I was starting to become keen on over the last few months. I had actually committed to doing one at Global Education Day during ISTE this coming June, so I thought this would be a good intro and first go at it.

Then, at the Summit, there was a call for presenters to do a Demo Slam. I'd never done one of those, so I thought I'd give that a go to. I was extremely nervous about both talks, but I managed to get up in front of everyone (how much harder could it be than a regular session) and do my best.

The first one up was the demo slam. You're meant to have 3 minutes, but I feel like I only used 1 of them. My demonstration was about how you can link Google Slides from one file to the next if you copy the pages. An interesting time saver if you track a lot of progress from learners and don't want to open 20 or 30 files at a time. It didn't win, but the one that did (from a wonderful new member of my digital tribe - Lindsay Wesner) hit right to the heart of a pain point for educators - marking.

I was pretty nervous and probably went through my demo too fast. That's what happens when you're nervous, I guess.

I didn't have much time to fret about that as I had to finish up my Ignite talk and slides. I spent a good amount of time practicing my pacing, and cutting out the unnecessary words.

The next morning I was pretty nervous for the talk, but I felt ready. I sat through the first two ignites and very quickly, it was my turn. We're all our own worst critics, so I was pretty hard on myself, but I also went about it with some perspective. So I'll start with the positive:

I think my message was good, and for the most part cohesive and what I said followed a logical path. I think that I adapted well when things weren't working properly (the slides weren't advancing as easily as I thought they would, and I had some initial trouble with hooking up my chromebook, though I'll attribute that to nerves).

There were, however, a few areas where I could improve upon. For starters, I felt as if I had my head buried in my tablet (which had my script on it). Normally when I talk, I wing it. Every time. I know the main points I want to say, but often ramble and go in an illogical way. An ignite talk is meant to be short and precise. So I made sure I did that. The problem was that I wanted to make sure I said everything as planned. And due to nerves and a lack of confidence, I had a hard time taking my eyes of my script.

That being said, I had at least two attendees give me some really positive verbal feedback. AND while reading, I kept on seeing a lot of twitter notices come up, which meant I was getting a lot of positive feedback online.

Have a view of what I said. Feel free to give me any more advice that I may have missed. It was a scary thing to do, but I'm glad I did it and I'm looking forward to doing it again in another capacity, somewhere.

Book Review: Code in Every Class

When I went to Sydney last year for the Innovator Academy, we were all given books. I was lucky enough to be given a book that related exactly to my project: Code in Every Class by Kevin Brookhouser and Ria Megnin. I only recently got around to reading it, which is unfortunate for me, as it has proven quite useful when it comes to wrapping my head around certain things.

The book aims to be a help to all educators, regardless of their skill level when it comes to coding and computational thinking. A beginning will take away a lot from it, but so, too, will an educator experienced in teaching these concepts.

The bulk of the first few chapters deals with the rationale behind teaching coding in class and how teaching coding to everyone is something that we must pursue - even if those learners will never code another line in their lives. The arguments and ideas set forth are extremely helpful in persuading those who would put barriers in front of those of us who want to teach coding.

The authors explain how coding can and should be integrated across the curriculum (hey, doesn't that sound familiar - at least I know I'm on the right track) and it gives a lot of foundation information that will help any beginning get a foothold. And what they don't give (or don't have time and space to give) can be found in the many links shared throughout the book.

The last section of the book has a large number of activities that can be done, ranging from beginning lessons to quite complicated ones. Again, there are many links shared so that the reader can get more information.

I would definitely recommend this book to any and all educators, even if you already are using coding (or more accurately, computational thinking) in your practice. It will help you spread the word and more likely than not, give you many ideas to begin or transform the way you teach coding in your classroom or with your learners.

It can be found on Book Depository and Amazon.