Showing posts with label tech support. Show all posts
Showing posts with label tech support. Show all posts

Thursday, 9 April 2020

Simple Remote Learning Fixes

Windows 98 is in the house!
I was asked what our spec-ed teachers can do to help students with IEPs who are struggling with technology at home.  This might not be the answer they expected, but here's 30 years of IT experience at work, and it follows the screensaver I always ran when I was a full time IT technician:  SIMPLIFY!

For many 'tech' is something out of their comfort zone which means you're battling a confidence issue as well as the tech problem.  For others, especially younger people who have been told they're digital natives who intuitively understand technology (which is hooey) you get the Dunning-Kruger Effect in full blossom and have have to back them out of the assumptions they jump into too quickly.


Here are the simple how-tos for tech support which will resolve the vast majority of technical problems you'll face in our bizarre new world of COVID19 bubble remote learning (you'll be building digital fluency in your users too!):


THE BASICS FOR TECH SUPPORTING REMOTE LEARNING




1. Have you tried turning it off and on again?  You'd be amazed how often that solves things.  There is a lot of data moving around in a computer and the person using it may very well have interrupted some of those processes.  Rebooting a computer lets it sort itself out and undo those interruptions.





2. SLOW DOWN! (it's a theme) Actually read the error - the computer is trying to tell you something, slow down and read and understand it. Many people tend to make assumptions and then start mashing buttons and messing with settings.  This makes it even harder to fix the probably simple issue that kicked this off.




3. Get good at searching online for a solution.  Don't paraphrase, put the specific message you're getting in the search and you'll get specific how-tos, you'll also get a sense of how common what's happened is.  Include details.  What operating system are you running?  Windows 10?  Windows 8?  Windows 7 even though it is no longer supported by Microsoft but your school board won't update?  Mac OSx?  ChromeOS?  What model of computer are you using - it's stamped on it somewhere.  Get details and use them in your online search. 






4.  Having said number 3, the internet is populated with idiots, so don't believe everything you read on the inter-webs - be critical!  Look for quality answers from a good source (it's NEVER Reddit - see the brilliant commentary on the right).
A Chrome answer from a Google page?  A Windows answer from a Microsoft page?  A Mac answer from an Apple page?  That's where you want to look - and then SLOW DOWN (theme, remember?) read and understand what they're saying.







5.  Make one change and test it.  As Charles from MASH once famously said, do one thing at a time, do it very well, and then move on.
Running off half cocked is what too many people do.  They end up making things worse by digging into settings and mashing buttons.  If it worked before, it's probably a single thing that changed.  Slow down, read and understand what's happening, isolate the problem, solve it - then reboot to let the computer sort itself out!




The technical side of things is only one part of the technical support equation.  Dealing with user psychology is the unspoken, secret side of the business.  User resilience plays a big part in why you're facing the many technical issues you've been tasked with solving.  It's a lack of confidence that prevents people from solving many of these issues themselves, not the technical complexity of the issue itself.  As my Dad once said, if a person built it, I can fix it.  Until we're facing alien technology, you got this.

If we can build confidence and encourage everyone to take on responsibility for using the tech, everything tends to work better, the user included.  Don't ignore the psychology - make a point of congratulating yourself or your user for resolving their own technical challenges - it helps bridge that confidence deficit.

6. BONUS:  it's usually something simpler than you think it is.  When I was looking at blade server failure that had just knocked over 600 employees off the network for no reason everyone else in the department wanted to dive into software settings.  I went and looked at the thing and realized it had been plugged in to the wrong breaker (plug), and it kept popping when over 400 connected at time.  Others wanted to get into settings, I checked to see if it was plugged in properly.

Mike Meyers has a similar story in his CompTIA A+ Study manual:  a colleague was bragging about how great his security firewalls were on a new server.  Mike bet him he could get into it and the guy took the bet.  Mike put on overalls, walked into the office saying he was there to do some maintenance and the receptionist waved him in.  He walked into the server room, unplugged it and walked out of the office with it under his arm.  The receptionist didn't notice because her internet was down (he'd just walked out with the thing that served it).


7. SUPER BONUS!!!  PUSH YOUR UPDATES!  If you're on Windows type in update in the search bar and it'll walk you through them - being out of date can stop your machine from working properly, especially in our interconnected techosystem (see what I did there?).  Being out of date also opens you up to all sorts of cybersecurity headaches.  If you're on an Apple product, the process is similarChromebooks need updating love too, don't forget it!



There is nothing magical about digital technology, or any technology really.  Our inability to manage it usually comes down to either a confidence problem around a lack of familiarity or an over falsity of confidence based on a lack of genuine expertise.

When you're trying to get students connected during an emergency situation don't over-complicate things and look for the easiest fix first.  I've seen 'experts' diving into Chrome settings and spending an hour messing with things and still coming up short.  The IT tech in me always wonders why they don't spend five minutes uninstalling and reinstalling it.  The point isn't to show off your prowess (though I'm not sure that wandering through settings randomly trying things for an hour would do that), it's to make things work.

In short, be humble, be helpful and be solutions focused which includes addressing where your user is in terms of psychology.  That'll get 99% of your technical challenges sorted in our bizarre #COVID19 remote learning bubbles.  For the other 1%, that's why we have IT departments.



Thursday, 19 January 2012

Part 1: Magical Technologists

"Any sufficiently advanced technology is indistinguishable from magic."
Arthur C. Clarke


I'm reading Kurzweil's The Singularity is Near, and in the opening he compares computer programs to Harry Potter's magical spells.  It seemed spurious when I read it, but now I'm wondering how it looks from other eyes.

I'm the go-to tech guy at school, and I dig the position.  I've joked before about how people need to sacrifice a chicken (or just wave a rubber one over the computer) if they want something to work, but now the metaphor is resolving a bit more.

Today our soon to retire head of guidance came in all worked up because he couldn't take a document and put it in his powerpoint.  He was using and old, hobbled, board laptop with an ancient copy of, well, everything on it; it was state of the art in 2002 when he got it.

I copied his (wordpad!) file onto a USB key, opened it on my competent, not-board computer (it actually uses Windows 7 instead of XP - the ONLY OS of choice for our board) and MS Office instead of Wordperfect.  I opened the DOC in Office (which just works, unlike Wordperfect on the board laptop) and then screen grabbed the guidance material he wanted into two jpegs.  I then copied them onto the USB and moved them back over to his sad, old laptop.  In moments I had one of the jpegs filling a slide on his powerpoint.  After I did the first one, I got him to do the second one.  He was happy, it all worked, and he even had some idea of how to put jpegs into powerpoint too.

Looking at the order of operations above, it looks pedantic and pretty this/then/that to me, but many people reading it would get lost in the acronyms or the logical sequence of it.  It assumes an understanding of what works with what and how to bypass difficulties around software not cooperating, among other things.

From another point of view, it might look like I pulled out my own, newer, better wand (laptop), and made some arcane gestures (trackpad), spoke some gobbledigook (tech-talk) and dropped a regent into the spell (the USB key).  and made what seemed impossible possible.  Without comfort level, experience and equipment, it looks like I made something happen out of nothing.

The councilor with him said I was the secret technical mystic they turned to when things just didn't work.

I try to be transparent with what I'm doing, and explain it to people as I'm doing it, but I see their eyes glaze over when I use the first acronym and then they just sit there with a happy smile on their face as the issue gets resolved.  I'd like for everyone to be able to cast their own spells, but I fear many would rather just applaud the magician.

Which takes me back to Harry again.  There's a scene where Dumbledore escapes from the evil Ministry in spectacular fashion.  He could have just disappeared, but he doesn't, he does it with a flourish.  Kingsly the auror says afterwards, "Dumbledore may be a criminal, but you've got to admit, he has style!"

If you're going to be a tech-magician, and if you're reading this you probably already are, then don't cast your spells flat, be like Dumbledore, have some style!