I was asked to work on a new project where I was to design and develop a resource website for a school district’s technology department. When I first agreed to take on the project I was unconcerned about what I was supposed to be doing. Resource website. Pffffttttttt. Even though I would consider myself to be far from a pro, I could build a simple website in my sleep. Not even an issue. Then my contact said these alarming words: You must build it in Sharepoint.
My response: I’m sorry, what now?
I have my fair share of technology background. I’ve been a teacher who heavily used tech, I was a technology integrator, then a technology director. One of my Master’s degrees is even in Information and Communications Technologies. I can work it or learn it with the best of them and I will push every button there is until I can figure it out. Usually.
If he had said Wix or Webs or WordPress or Google Sites we could have just kept moving, but he didn’t. He said Sharepoint. And laugh at me all you want, even though I appreciate Office 365, I’ve always been a Google girl. I didn’t even know at first that Sharepoint was a Microsoft thing. I literally had no idea what it was. When it comes to technology, I can’t remember the last time that I couldn’t even come up with a reference for something new. The only way I could describe my feelings was that of sheer terror.
I didn’t have the time for someone to teach me and I didn’t have a lot of extra time to learn. I was on my own with no direction and I was astounded at how much panic I felt. And like any good reflective professional, I started thinking about all the times I had asked teachers to learn something new that we didn’t have the time to properly train them on or they didn’t have the background knowledge to even begin to move forward. It made me cringe at how many times I had been a part of that process just because of my position. When I discuss the need for professional learning opportunities for educators, which I do often, I’ve always thought of it in terms of responsibility. As in it’s our responsibility as a district to provide educators with these opportunities otherwise we are asking them to do something we have never taught them to do. While this is true, what I was missing was the feeling of being behind and missing something. Of there being expectations that I didn’t know I could make. The emotions: fear, uncertainty, embarrassment, disconnection.
In order to move on, I had to remind myself of what I did know how to do. I knew how to Google. I knew how to find YouTube videos. I went to the Sharepoint site and began to click buttons. I have always believed that the only differences between people who learn technology easily and the ones who don’t are A) they are willing to push buttons knowing it won’t break and B) they rely on what they already know to get started.
It took me weeks to figure out Sharepoint to the extent that I needed to in order to finish the project, but when I was done I felt accomplished and proud of myself that I was able to create what they needed out of something new. It was a risk taking on a project on a platform I wasn’t familiar with. I recognized the possibility that I would need to admit to someone that I couldn’t do the job they asked me to do which added to my panic. If I claim to be a lifelong learner, I better be one. If I want to model growing in an area that I’m unfamiliar with, I better be willing to take risks. That feeling – the one of shock and nervousness and doubtfulness that I would be able to learn something – will not be forgotten anytime soon. I believe these kinds of experiences, when we notice them and do our due diligence to reflect, is what keeps us grounded and connected with others in our field. It generates empathy. It guides us and helps remind us how we want to treat others and provide a supportive environment so we don’t need to go to school feeling bad about ourselves because we just don’t know.