Over the past two decades, I've had the good fortune to visit hundreds and hundreds of schools across all six continents to learn about how they are using new technologies -- and hope to use them in the future. (Maybe some day I'll visit the Antarctic school that was connected to the Internet by Chile's pioneering Enlaces program and I'll be able to claim I've done this on *all* continents!)
From Korea to Costa Rica, Sri Lanka to Syria, Lesotho to Laos, Papua New Guinea to Puerto Rico: School visits in over 50 countries have run the gamut, from observing the shared use of quite old graphing calculators and lectures at the blackboard describing how to navigate Microsoft Windows (even though there was a nary a PC to be found in the building) to marvelling at technology-rich classrooms filled students and teachers doing things with hardware and software that I couldn't have dreamed of doing when I was a student myself, many years ago.
I have visited schools in prosperous countries in peacetime and in very poor countries emerging from conflict (and in some cases, still technically at war). I learned firsthand about technology use in schools in Iceland when that country was labelled the world's 'most developed' and in schools in Haiti, the poorest country in the western Hemisphere, after that country suffered its devastating earthquake.
In pretty much all cases and contexts, investments in 'technology' were meant to be deliberately forward-looking (if not always necessarily that 'strategic' or well-planned), to some extent symbols (often explicit ones) of progress and optimism about the future, no matter the education system, from the most 'high performing' to the most dysfunctional.
Because I've had lots of comparative experiences visiting schools in 'other places' around the world, I am sometimes asked to provide an 'international perspective' on what is happening within a set of schools in a given country, part of a larger effort to benchmark what is being done and planned against norms in other countries. It can be a pretty cool gig at times (although the travel can be rather punishing). I am always learning, and the dynamism and determination of students, teachers, principals and education officials whom I observe and chat with quite often leaves me inspired and (re-)energized.
Since I have been doing this for so long, I sometimes help 'train' people (at ministries of education, at NGOs) who are assuming leadership positions in educational technology initiatives on how to develop their own "carpenter's eye" -- the ability to make quick assessments and judgments about what they are seeing in ways those less experienced in the field may struggle to do.
What's a 'carpenter's eye'?
A carpenter can often quickly judge whether an angle is truly 90 degrees, or that a wrong tool was used for a particular job, or make educated guesses about why one material was employed instead of another, or that something is destined to break. Such judgments may not always be accurate, and may be informed by various biases, but they are often qualitatively different than those of people less skilled and experienced with woodworking, who may not notice such things -- and who in fact may not care about them, nor understand why they might be important.
In my personal experience working with new technologies in the education sector, many of these folks have come from 'technical backgrounds' and typically direct their gaze toward, and ask the majority of their questions about, the technology itself. Often times the end goal of such investigations is meant to build an accurate inventory the equipment that is available in a school, rather to trying to learn about how the equipment itself is being used (and not used), why this might be the case, and how people feel about this. Fair enough: We all have different bosses, different ideas about what is important, and different incentives for doing whatever it is we may do. I don't mean to deny the importance of surveying what technologies are currently available in schools. But in my experience, visiting a school to learn about the technology it has and only focusing on that technology (what processor a device has, which operating system it runs, how much memory is available) represents a real lost opportunity to learn about and gain insight into many more things at the same time.
In case it might be of use to anyone else, I have assembled a quick list of some of the things that I often ask about and consider, usually automatically and unconsciously, when I visit a school to learn about how information and communication technologies (ICTs) are being used (and not used) for a variety of purposes. It's by no means comprehensive, and of course every context is different, but I find that these are often the types of things that I ask about and look for (in addition, of course, to the more general educational and demographic stuff that would be common areas of inquiry related to most school visits, and the hyper-specific stuff that might be the reason I am visiting one school in particular).
I have cobbled this list together from a much larger, slightly unruly 'master' list of questions that I maintain, which draws on notes and emails I have shared with people over almost two decades of school visits, working with hundreds of people, many of whom had little prior experience in visiting schools to assess what was happening with technology. Sometimes -- if not often -- sharing these sorts of questions is meant as much to spark discussion and debate within a team about what might be important (and what isn't so important), and how to go about finding this out, as it is to suggest actual questions that should be posed. Every context is different.