The Quote Board Conundrum

I keep a 4×8 sheet of whiteboard on my office wall. Always have. Sometimes I use it as a low-tech auxiliary memory sometimes when things hit a level of complexity that throws my brain into gridlock. Other times I diagram projects, fill it with post it notes so I can see how things fit together (or don’t), or draw pictures so I’m sure I understand what someone is telling me (or vice versa).

Over the years, though, I have used it primarily as a central repository of things people say, noteworthy quotes made memorable by keen insight, egregious absurdity, or just plain funny stuff. An old favorite came from a former Director: “The meeting is relatively mandatory.” Another from a principal, asked what school policy was when kids were chronically late because of disorganized  parents: “We don’t think it’s a good idea.” From NAIS Pat Bassett: “The single greatest impediment to change in independent schools is our cultural attachment to consensus.”Most of the quotes came from real people I know, and there was a certain quality of board-worthiness associated with whatever went up there.

Lately, I haven’t put many quotes up and the board is strangely empty. As a typical human, of course, my first impulse is to blame other people for saying fewer interesting things. Lord knows that seems to be true of pretty much any of the talking heads we experience in the mass media.

On the other hand, you have to be listening for the serendipitous moments when the best quotes are uttered. I think I figured out that during this year, the busiest and most pressure-packed in many years, I have likely spent too much time in my office and not enough out and about in the community, engaging in the informal conversations that are fertile ground for board-worthy comments.  I never thought of my board as a barometer of my visibility within the Schools, but now that I have, it should be a good reminder to show my face more often.

Insisting, Part Two: Close the Loop

A couple of posts ago, I began to consider what elements of our daily IT practice I insist on (I also said I don’t insist on very much because insisting all the time is tiresome for the insistees, which I know is not really a word).

But I did write a bit about why I insist that all tech purchases and donations channeled through my office. I also asked other IT leaders what they insist on, but didn’t hear from anyone. Maybe I should insist that they respond.

Another of the small set of practices I insist upon is that people I work with close “open loops” on tasks or projects in progress. Nothing snarls communication in a high-performing, fast-paced work group more than lack of status information, whether it is a help desk ticket, a delegated task, or action step in a project plan. When loops are left open, the results are wasted time, confusion, faulty assumptions, and looking disorganized to your user base–all undesirable outcomes. It saps team morale, too.

All it takes is a quick e-mail, text message, note in a project portal, help desk ticket, IM, phone call — just a half minute to say the project or task is complete or not complete, and any contextual information I need to know. Short and sweet — but your to-do list grows unmanageable if you never close those open loops.

The Best Account Exec Ever

Two weeks ago, Jack, the best account exec I’ve encountered in 14 years as an IT Director, told me he was leaving his company, bad news indeed. He came to see my team and me last week and took us out for one last business lunch like many we’ve enjoyed over the years.

He was quick to say that he’d called us first with the news of his decision because we were his favorite customers–not his biggest customers by any means, just the ones he felt closest to and fondest of. That meant a lot to me. I’ve worked hard to manage all my school’s technology vendor relationships going back to my earliest days in this position.

Jack’s departure prompted me to think about what made him such a good account exec.  What makes a strong vendor/client relationship? What do both parties need to bring to the table to make the relationship work?

In short, it’s all about mutual trust and the steps you both take to earn it.

From the customer side of things, vendors earn my trust when they:

>>>  take the time to learn about my school, my IT team, and how the team’s goals fit into the school’s big picture

>>>  make certain we are both clear on what we expect from each other

>>>  deliver at least what is promised (and often more) on time and on budget

>>>  take responsibility for delays, missteps, or problems with products or services they sell, and act quickly and effectively to put them right

>>>  advocate for our needs with their higher-ups when necessary

>>>  bring us creative, worthwhile options we hadn’t thought of to achieve our goals

>>>  are well-organized and efficient in following up on action steps  — getting the little things right

>>>  get back to me in a reasonable amount of time when I contact them

>>>  are able to hear and give constructive feedback on the working relationship we have

>>>  deliver a quality product or service at a fair price (which may or may not be different from the lowest price–in general, I think you get what you pay for)

>>>  are respectful of my time

These are the qualities that made Jack such a valued partner in our work here at my school. We will miss him and wish him all the best in his next endeavor, whatever it turns out to be.

To make vendor relationships work from our end, we need to:

>>>  be clear about specs/features and our goals/expectations when acquiring any given product or service

>>>  review contracts and service agreements carefully and resolving any matters of concern before signing them

>>>  pay them on time for services rendered

>>>  provide them with any important contextual information they may need to fully meet our needs

>>>  provide constructive feedback as needed, and promptly share concerns or kudos

>>>   be appropriately patient when things don’t go as planned, and be direct, assertive, and professional if and when appropriate patience becomes exhausted

>>>  respond in a timely way when they contact us

The best relationships between customers and vendors are always about something more than just buying and selling equipment or services. The “value add” (a popular term I don’t much care for) starts rising when the trusting relationship you’ve set out to build makes both parties better at what they do.

Reflections on the Year in Technology: Seismic Disruption

It’s often been said that change is the only constant in life. That is certainly the case in technology, where the unrelenting pace of change can sometimes blur the distinctions between the evolutionary and the revolutionary. In reflecting on the past year, it struck me that more than any others in recent memory, 2011 was indeed revolutionary in the K-12 technology arena.

I started thinking about this after a conversation last winter with a colleague from a west coast independent school. This fellow is well-known for incorporating technology into creative, innovative, and pedagogically sophisticated projects with students. Along with a third colleague, we were celebrating a successful workshop we’d presented earlier in the day at NAIS.

In the course of our conversation, he said that he was really anxious about the year ahead. I asked him why, since he was rarely anxious about his craft. “I have always been able to figure out what was coming and how I should respond to it, as an educator and an IT leader, ” he said, “but I have no idea what the next year will bring. Things are changing so fast that for the first time in my career, I simply don’t know what to do.” For someone of his skill and stature to say that really got my attention.

That thought stayed with me for the rest of the year as I watched the former version of the technology marketplace blow itself to smithereens and scatter debris all over the place. The proliferation of powerful, user-friendly handheld devices, the various operating systems on which they run, the tens of thousands of apps that exploded on to the scene, the panoply of choices for streaming multimedia content, the emergence of e-books, competition for your “cloud computing” dollars among Google, Microsoft, Apple, and hundred of other hosted services — it was a year of seismic disruption unlike any in the fourteen years I’ve been in this position.

The bad news is that technology is going to be very messy for a long time to come, not only for consumers, but for institutions who have to make decisions about where they need to go and how they are going to get there. Any technology decision one makes these days spawns as many questions as it answers.

The good news is that many of these developments will, in time, empower learners in ways we couldn’t have imagined a couple of years ago. It’ll take time, patience, good communication, an appetite for judicious risk, and a willingness to be uncomfortable as we pick our way through difficult terrain — a tough assignment, to be sure, but one I’m looking forward to.

Happy New Year, everyone!

Dear IT Leader: What Do You Insist On?

I’m always wary of people in schools who are fond of insisting. I’m not one of them. If you insist all the time, people get tone-deaf to it.  Tech leaders have to be especially careful about what they insist on, since managing a variety of fairly serious risks is part of the territory. That can lead to an awful lot of insisting if we’re not judicious about it (this is starting to sound like the first in a brief series of Things I Insist On–we’ll see if that pans out).

I do insist that all tech purchases and proposed donations be cleared through my office.

There are at least four good reasons to do this :

1) To protect school stakeholders and the school’s interests in legal matters, including all the stuff nobody but me and the CFO ever reads: vendor contracts, Terms of Service, Privacy Policies, data security practices for offsite vendors, licensing agreements, and so on.

2)  To determine support implications for my team, which there nearly always are. It’s also helpful to store copies of license codes, vendor contact info, renewal dates, licensing agreements, and other such data in a central repository for those times when it gets away from the departments and offices who buy it.

3)  To have a reasonable shot at having the data needed to work on Total Cost of Ownership and Value On Investment calculations.

4) To maintain overall coherence with the school’s technology  direction.

This last piece is probably most important. As people tire of hearing me say, IT leaders are often one of only three or four people in any school who work with absolutely everyone. Departments and offices are not in a good position to know what all the others are doing or grasp interdependencies among school subgroups. We are. We need to use our unique position to ensure that people acting with an appropriate degree of autonomy don’t tie anyone else’s shoelaces together.

The Business Office here has become very cooperative in alerting me to tech purchases coming through its paper trail. The Computer Science Department also communicates well about purchases they need to make and broader purchases they are prepared to support with their software budget. And I still reserve the right to refuse support services for items acquired outside the prescribed process. I can’t say I’ve ever done that, but I have come close.

I’m always amazed when I encounter schools with leaky procurement practices who then expect IT staff to support anything and everything that comes in.  Ultimately, students pay the price for the chaos this creates — which sounds like a natural segue into the next installment in this series.

Are there things as an IT leader that you insist on? I’d be curious to hear some.

Don’t Go Like That!

Patient: “Doctor, it hurts when I go like that.”

Doctor: “Don’t go like that.”

– Henny Youngman

After taking part in yet another disappointing online discussion of iPads, I find myself dispirited by the constant emphasis some teachers and tech folks place on “going like that.”

The iPad wasn’t designed to be a substitute laptop. Printing and word processing on the device are not the same as on your laptop. They both involve some pain on the iPad because the device wasn’t designed to do things we’ve always done. Using it well means thinking and behaving differently with a whole world of tools that a laptop doesn’t have.

We already have a lot of devices that were designed for word processing and printing that do those things much better. Insisting that the iPad needs to do those things well, or whining that they don’t, is “going like that.”

Don’t go like that. Forget about printing from your iPad. Use Evernote (or any of a number of other solutions) to store the stuff you have to write on the iPad. Use Pages to create documents and email them to yourself so you can print them from another device. But don’t try to format a term paper on it, and stop bemoaning its limitations for doing the same old same old.

Instead, push yourself to see what you can do with this device that you cannot do with your laptop or desktop. If you need help with that, put a few apps on the device that a young kid might like, give the device to her,  and see what she does. She’ll point you in the right direction.

Are IT Leaders Change Addicts?

In an earlier post, I wondered if IT leaders might be a self-selected group of “change addicts,” professionally restless, attitudinally positioned to engage with change, naturally curious, and at ease with being in a constant state of transition in daily work.

After much thought, I’ve concluded there is some substance to the claim. I’ve met lots of school IT leaders while presenting at and attending conferences and regional meetings, teaming with them on consulting engagements, and participating in online communities. As we get better acquainted, my personal and professional histories seem freakishly congruent with theirs in many ways. It’s a small sample size, but it’s come up too often to ignore.

My family moved often as I grew up. Until college, I never attended any school for more than two consecutive years. After grad school, I taught Kindergarten for two years in a public school and was laid off. At Lab, I started as a third grade teacher for a few years, and then requested a move back to Kindergarten. Four years later, I left Lab to pursue other options in psychology, social work, student teaching supervision, and textbook writing. I returned to Lab three years after that to teach fourth grade, and four years later, moved into the position I currently have.

I’ve stayed in this job for thirteen years now, the longest I have ever held the same position. Though the title hasn’t changed, the job most certainly has; as the school’s needs have evolved, what the school needs me to be and do gets reinvented regularly. I can identify at least four distinct evolutions during this span that could easily be viewed as entirely new jobs, but without a title change.

Many of my IT leader peers report similar career paths to and within their current positions. Watching them move in and out of different phases of their careers can be wonderfully entertaining (and sometimes instructive), whether reinventing themselves where they are or moving on to other ventures.

For the sake of argument, let’s say this admitted generalization holds water. So what?

For one thing, keeping this notion in mind adds potentially helpful perspective to conversations about change management in schools. It may be that this self-selected group is so inured to change that they assume others share their appetite for it. No doubt, this assumption will apply to some stakeholders, but likely not for many. The resulting clash of perspectives, if we are not aware of it, can create friction between IT leaders and some stakeholders that diverts attention from a proper focus on what students need to how comfortable adults are, or are not, with change. That’s not usually a good thing, at least not for students.

It may also help those responsible for hiring and supervising IT leaders. Candidates for IT leadership positions who have not demonstrated a healthy appetite for change may not fare as well in IT leadership as those who have. Please note that I said “healthy” appetite for change; a change glutton is probably not want you want, either, since change for the sake of change is as perilous to good schooling as no change at all. Supervisors may indeed have to help build consensus around what healthy change looks like in their school.

What is your experience? Do you find that IT leaders are naturally attracted to change, or does their work simply require them to accommodate it? How does your school respond to change generally, and particularly with respect to technology?

One of Those Nutty Days

Every once in a while, a day comes along that is so filled with seemingly random bits and pieces that you realize what a strange job managing IT can be. Today was one of those days. Here’s a pretty thorough recounting of what I handled today:

- making time for a new standing meeting for administrators I’ll need to attend

- making time to discuss with University legal counsel how we will handle copyright infringement notices involving members of the Lab community

- revisiting my earlier research on  dimensions and locations of proposed multifunction devices in our enormous renovation and expansion project for a meeting called today for tomorrow morning

- learning (with some dismay) that Apple has suddenly discontinued the MacBook, the laptop model we most often buy, and then deciding whether or not to purchase 160 of them 5 months earlier than I had planned

- questioning added project management and hardware/supply fees on an audiovisual system quote from an a/v vendor

- with support staff, researching options for a physical security device for new iMacs

- drafting a never-before-needed message to be delivered remotely to unauthorized users of Lab School assets

- completing a draft of a comprehensive series of informational pages on school technology operations for a new parent portion of the IS web site

-  vetting Terms of Use and Privacy Policy for 2 online service providers

- managing Quia user accounts

- reviewing a new University social networking policy now in force and assessing its congruence with  an existing draft of a similar Lab-specific policy

- writing the annual tech letter to parents and updating student tech contracts and AUP summaries

I’d planned only about half of these activities, and I suppose I could have deferred or delegated some of the ones that came up during the course of the day–but I didn’t, and just allowed the day to unfold in its own way. I still got a lot done before I realized how many different aspects of my work popped up during a single day.

Don’t get me wrong: I know tons of people in lots of jobs are ridiculously busier than I will ever be, and face daily pressures I can’t imagine. I’m not trying to lump myself in with surgeons, police officers, executive chefs, soldiers, iron workers, or commodities brokers. I doubt whether I could face those kinds of daily schedules and pressures and still stay sane.

The only reason to share something like this is to help demystify what school IT leaders might be called upon to do in the course of day, figuring that those of you inclined to read a blog about managing IT in K-12 schools may find it of some interest. I’d be happy to hear from others in the field about  nutty days you  have had.

Anyone? Bueller? Anyone?

The New Normal, Part 3 of 3

Let’s finish up the New Normal series today. This series revisits my portion of a panel presentation at the NAIS conference this year.

Feel free to revisit Parts 1 and 2 archived on this blog to bring you back up to speed.

Today, I’ll focus on school leaders and their role in the new normal of educational technology.  Defining “leader” in broad terms is good practice here, since in most schools, leaders pop up in all kinds of places. My operational definition of a school leader is anyone who has the qualities and skills it takes to rally others around an idea and impel constructive action that ultimately benefits students.  You don’t need an office or a title to be a leader, but you have to be a leader to bring about change. Whomever your leaders are, and wherever you find them, here is the first of two key things they must do differently in the new normal:

Savvy leaders at all levels in the new normal must view and manage institutional attention as an even more precious resource than time. To accomplish school technology goals, or even put a school in position to create technology goals, there must be appropriate attention given to it.

Lack of time is often cited as an obstacle to progress in realizing the potential of technology for learning. I agree that this can often be the case, but more often the real problem is that schools do not manage institutional attention as well as they could.  You can recover time by managing attention more carefully. When institutional attention is scattered, time becomes more of a  problem than it would otherwise be.

Most schools I know try to wrestle far too many initiatives to the ground at the same time to do a capable job of managing all of them, despite the talent and sincerity they bring to each task.  Accreditation reviews, diversity initiatives, scheduling committees, “green” efforts, capital campaigns,  dealing with learning differences….so many of these kinds of large scale projects are running concurrently, it is no wonder technology is so often an afterthought.

Dealing with the new normal in ed tech will require a level of discipline and focus to meet the challenges ahead with purpose and intention. Schools that continue to crowbar, duct tape, and hot glue technology on to a lumbering caravan of competing efforts will find themselves outsmarted and outperformed in surprising ways by competitors who choose depth over breadth when making decisions about strategic initiatives. These school leaders are prepared to take some flak about what they are not doing so they can excel at what they are, and are not shy about saying that some initiatives are more important than others. They also do their homework about what their school’s particular strengths are and design their strategic plans to achieve goals unique to them, because they know it is the best way to stand out in an increasingly competitive independent school market.

Finally, schools who come out ahead in the new normal are those who lean into the discomfort that change brings with it. IT leaders are used to change, or had better be if they expect to keep their jobs (in fact, I believe we are a self-selected group of change addicts, but that is another post). We live in that twilight zone between that which rarely changes (human nature, institutions, school curricula) and that which changes daily (technology). It’s OK with us that what we knew yesterday may or may not help us today.  CIO magazine put it best in 2005: “IT leaders are change agents; transition is our stable state.”

But not everyone in schools has made peace with such rapid change. The leaders’ job is to win enough trust from people to get them into that twilight zone with us  long enough for them to see what’s in there. Once people do that,  and they learn to tolerate, and then embrace,  the discomfort they feel, they begin to see opportunities where others see only problems. They start to develop the kind of resilience it takes to thrive in such a dynamic space, a space very much like that in which our students will grow up and make a life.

What we absolutely cannot do is be complacent. I often hear people in independent schools say, “Our enrollment remains strong, our students get into the best colleges….what’s broken that needs to be fixed? Why change?” This is no doubt a familiar refrain to many of you.

Most of our schools have achieved the success they have because at some point in their evolution, they took a bold step others would not or could not. As we look at the global redefinition of learning in the digital age, and the seismic cultural shifts we see in the way students access information,  there are profound opportunities for our schools to step forward once again to do something only they can do.  The new normal rewards  judicious risk and punishes complacency. There is no better time to lean into our discomfort and see what we can learn about ourselves and our students as we do.

A Word About Vacations

I owe you all one more post about the New Normal in ed tech, but since I just returned from an excellent week in Arizona watching Cactus League baseball (Go, White Sox!) and seeing the Grand Canyon, I thought I’d take a moment to comment on vacations–and the frequent lack thereof for school technology staff.

12-month technology staffers are among the most vacation-averse employees in any school. The 24x7x365 nature of the work makes one day seem very much like the next, even in schools, where the summer months are often the most busy for IT staff.

But it’s in everyone’s long term best interests to make sure technology staffers take the time they accrue. Burnout doesn’t have to happen in IT and turnover is expensive and disruptive. Well-rested, well-rounded IT employees are far more productive and effective; when we lose the “edge” we need to cope with the fast-paced, demanding IT environment, we really have to fight to get it back if there’s no time off on the horizon.

Unfortunately, schools often fail to recognize the burden they place on IT employees. Though lots of IT folks love their jobs, it’s more often that burden than their love of the job that keeps them from taking the vacation time they’ve earned.

Before most IT workers will feel comfortable taking a “real” vacation, not a “fauxcation.” two structural pieces need to be in place so they don’t compromise their time off by worrying about things imploding while they are away.

The first prerequisite is an appropriate level of human/skill set redundancy. There has to be someone else available to perform critical functions while the employee is away. You may find it appropriate to train up a tech-savvy staffer from another department to do a few basic things, rent some help from an outside vendor, or rethink job descriptions for current IT staffers to build in more of this redundant capability. This third approach is how I’ve handled most of it here, and while we are not redundant as I would like in a couple of areas, we are pretty well set in most of them.

The other prerequisite is an enlightened viewpoint from the IT workers’s superiors (I am fortunate to have this situation here at Lab). Pretty much every IT position has new duties added in the course of a year, but schools often don’t take steps to identify and address the resultant “mission creep.” Long hours of overtime for overburdened employees quietly become the norm. A long weekend here and there is not a substitute for a vacation that de-stresses and recharges the batteries enough so that the employee has  enough energy left for living life outside school, too. Supervisors need to keep track of IT employee accruals and ensure they take the time they’ve earned. Banking many weeks of untaken time should not be permitted, tacitly or otherwise.

Higher-ups can also support their IT leader’s efforts to set a reasonable expectation for service levels. The number of truly critical operations in any school is not nearly as high as it is in, say, a corporate business environment, despite what some users may believe. Identifying those operations that truly are critical will help guide the organization in providing redundant staff capabilities. You may even want to go as far as creating and sharing a Help Desk Service Level Agreement to help clarify support practices.

My favorite example of unreasonable support expectations is the Christmas morning I got a call at home from a teacher who’d made her holiday airline reservations using her school e-mail account and was having trouble accessing them. She saw nothing inappropriate in expecting me to step away from my family’s Christmas celebration to troubleshoot a personal situation in which the school’s resources should never have been involved in the first place.

So, then, if you supervise IT staff, check on their vacation accruals and work with them to make sure they are taking what they’re entitled to, and that what they are entitled to is clearly spelled out. Let them know you expect and support their taking vacation time. If you are one of the people in a school who receives services from IT staff, be aware that not every request you make can or should be handled with the same priority level. Be reasonable in the requests you make and understand that IT staff does not slow down in the summer; the rhythm of the school year is distinctly different for all 12-month employees, who probably do not have a vacation schedule similar to yours.