The Taming of the Inbox

I had a brief, yet celebrative moment yesterday; I zeroed out my inbox! Yes, for one fleeting and shining moment it was empty.

It’s a little disconcerting that by Monday morning, it will be regenerating, but such is life for the vast majority of us who are connected. Don’t lose hope, you can manage your inbox, but it takes a little effort. And there are huge benefits! Just that small, albeit temporary, victory is just one.

A recent study by the McKinsey Global Institute found that the average knowledge worker spends 28 percent of the workweek either writing, reading, or responding to email.  While you may not be technically classified a “knowledge worker” there is likely a high correlation to being an “imparting knowledge worker”; as in a teacher or administrator at a Charter School.

My favorite Charter School Administrator recently confessed to having something like 4,000 messages in her inbox. That’s a lot! Can you beat that record?

There are hundreds of excellent articles about this subject, so let’s approach it from an Information Architecture perspective. Like my father always said, “If you start with the right set of tools, the job is much easier”. Consider a couple of tools that should assist you in taming your inbox.

Start with an enterprise class mail system

The single most important step you can take to tame your inbox is to start using a real email solution. My recommendation for education has not changed in 10 years – Microsoft Exchange based email is the gold standard of email systems. It is now available as a free service from Microsoft as a Cloud Based (hosted service) and is called Office 365 for Education.

Hosted Exchange Email is the infrastructure an organization’s email runs on, the manner in which you connect to a hosted Exchange system is entirely up to you. You can use an internet browser, a desktop or laptop client such as Outlook (Mac or PC), an iOS device such as an iPad or iPhone, or any smart phone, or tablet.

Aside from Google mail, the alternatives are not even a close second. And privacy issues alone make me shudder in using Google mail, yes even the enterprise version of Google mail. Just because you are not getting advertising, does not mean your email is not being crawled for content.

I am especially puzzled when I come across schools that are using the “free” email that is included in their webhosting account. What an oxymoron that is! There is nothing free about dealing with the SPAM, the loss of messaging control, and the wide variety of compliance issues that accompany this choice of email systems.

A hosted Exchange email system is reliable, secure, compliant, feature rich, and it’s free. What are you waiting for?

Use Instant Messaging more for short or transitory conversations

Text messaging is quickly overcoming email as the mode of communicating in the digital world, but using it in education presents unique challenges. It is a little difficult to enforce a “sterile” learning environment, free from the disruptions of personal electronic devices (PED) if the teacher is constantly checking her own text messages on a PED in the classroom. 

A much better classroom solution is Lync 2010, another free education solution from Microsoft that is far superior to text messaging than what you find on your PED. Lync 2010 provides Instant Messaging (IM) on the desktop, your laptop, and your smartphone and there is a presence indicator for all of your communication. Don’t underestimate the importance of knowing the presence or availability of your intended recipient.

In addition to IM, Lync allows you to turn your texting into a full on video conference with just a click of the mouse. And you can connect with multiple individuals at the same time. And on top of all of that, you can share documents, transfer files, and even show others what you are viewing on your desktop.

In summary, by using Lync more and email less, you will reduce the endless stream of one liner emails that land in your inbox.

Implement a connected eRM/CRM system

The best improvement I have personally implemented in my inbox taming is Microsoft Dynamics CRM; we call it Education Resource Management or eRM for Charter Schools. I can sum up my experience in four short words – “Feel Free to Delete!”

Using eRM/CRM, allows you to associate an email with a contact, a company, a support case, a contract, an order, a meeting, a telephone call, or a dozen other items, and then DELETE it. The email is retained in the eRM/CRM system and you can now refer to it in context of the information it is associated with.

The most likely reason you keep all of those silly emails in the first place is just in case you might need to refer to it later. Fair enough; but while the search function in your email program is powerful, the association of emails with the people, processes, and things in your world is much more useful.

Not ready for an eRM/CRM system? A well thought out system of folders in your email system will be very helpful.

Utilize SharePoint for document collaboration

Ever notice how many emails can be generated over just one document? You send a document for input from an associate; they make a few changes, and then send it back. Next you send it off for approval, there are a few more changes and the document comes back. And finally you send it off for publication or printing and there are the confirmations and drafts and … well, you get the picture.

One of the most inbox clogging activities we observe is using email as a document collaboration platform. As the complexity and the connectedness of your organization grow, the multiplication effect is an inbox assault. At some point you may just have to call a meeting and sit down with all of those documents and team members to sort it out.

SharePoint changes the dynamics associated with collaborative effort and it will bring great happiness to your inbox. And if you have looked at SharePoint and find it a bit clunky, then you really have not looked closely enough.

If you use the synchronization tools in SharePoint and the network mapping tools in Windows that support SharePoint, you will find that getting a document onto your SharePoint document library is a simple as dragging and dropping or saving to a designated folder on your computer.

Oh, I almost forgot to mention – it’s also free and included in Office 365 for Education.

Summary

There are countless articles, even entire websites devoted to the techniques of managing email. And some of them are excellent. However, designing an efficient Information system will have more overall impact on your inbox than techniques.

Start with an enterprise level (not a consumer grade) email system. Embrace an IM or text messaging system that is integrated in your organization. Connect your email with the people, processes, and things you deal with inside a business management system. And use SharePoint for document collaboration, sharing, and versioning.

Good luck mastering your inbox; it makes for a much more enjoyable weekend.

Help Desk Perspectives

A recent experience over the use of a help desk caused me to revisit the subject, with a little more insight. It went something like this:

After completing a major upgrade at a small (25-30 users) organization, we were anxious to get feedback about improved performance and user experience. So I instructed the office manager to provide a list of issues which would help us to quickly identify individual PC’s that might be having problems.

And this was not a casual effort without communication infrastructure. The manager had direct access to me via Instant Messaging, with presence, using Lync 2010, email, and my cell phone. We conversed about other matters routinely, in fact on a frequent basis I asked about any upgrade issues specifically and the response was “thumbs up”.

Unaware to both of us was a collection of little slips of paper, post it notes, and torn off pieces of yellow note pad pages accumulating on the bulletin board next to the refrigerator in the break room. Neither I nor the office manager had the slightest idea that a major problem was causing a significant slowdown for a large number of users.

That experience did not end well, but reinforced an important lesson about how not to manage your help desk. For a review about the benefits of a help desk, please see my earlier post here.

How you identify, communicate, prioritize, assign, and account for technical support issues makes all the difference in the world with respect to how well technology works in your school. And there are a large number of help desk systems available for you to choose from. Here are the features that I would look for in a help desk system:

Universal Communication Medium

Help desk issues need an agreed upon standard communication protocol organization wide. The most practical is email, but only if you have a robust email system that provides you synchronized messaging anywhere on any device.

Email is accountable, easily distributed, actionable within automated ticketing systems, and universally used in most schools. Little post it notes (or big ones) probably won’t meet this standard, and have you no (eco-green) shame.

Filtering and Consolidation Mechanism

With the capacity to easily fire off an email to help@yourschool.com, any help desk solution will quickly be overcome with redundant and sometimes ridiculously simple support requests (computer unplugged, network cable disconnected, etc.). So there needs to be a way of collecting daily support requests in some sort of queue, in order to quickly evaluate and act upon requests.

If fifteen teachers report that a crucial website is being blocked by your content filter (for example), then it is entirely counterproductive to think about creating fifteen support requests, or even creating a single trouble ticket for that matter. In the span of time required to create a trouble ticket, you could easily log-in to the firewall and resolve the issue. Then happily delete all fifteen emails reporting the issue!

The most common mistake in designing a help-desk system is the requirement to create a support request (case, incident, ticket, or whatever you choose to call it) for each and every issue. Where a simple notification and action request exists, most ongoing support requests can be resolved as a matter of course.

This is especially true when you are fortunate to have daily onsite technical support resources.

Escalation Process

Any technical problem can be solved with sufficient resources, co-ordination of effort, documentation of actions taken and proposed, and feedback. But, complex or persistent issues may require escalation to a more experienced team member, or an outside vendor. This is not something you can do effectively with a post-it note, or even a three ring binder.

The capacity to resolve complex support requests requires documentation that is available to all parties involved. This includes desktop support technicians, network engineers, software vendors, and most importantly – the end user.

At a minimum, the documentation should include date and time stamps, priority, resolution status, technician assignment, and notes for those involved documenting steps taken and subsequent actions required. An enormously helpful feature would be automation and integration with your internal communication systems, this will facilitate status updates, expected resolution timeframes, and resource requests.

Knowledge Base and Performance Metrics

The accumulation of knowledge about your infrastructure is an important by-product of a well-designed help-desk. Issues that repeat infrequently can be more easily resolved by referring to case notes of a previous support request. Knowledge bases can also be made available to your end users and encourage more self-support in their daily activities.

Performance metrics really speak to the effectiveness of your technical support staff. The most equitable way to measure the effectiveness of your technical support team is through the reporting that comes from the very system they use to resolve your technical support issues. If one of your technicians routinely resolves a significantly larger number of support cases (or queues) in a specified period of time, you might want to consider giving him a promotion!

Summary

Getting frustrated about the difficulty in using a help desk is understandable if it is too cumbersome, complex, and available to only a few individuals. But don’t give up, the benefits of a rational help desk are significant and worth the investment of your time and resources. It can pay big dividends.

Find a simple and reliable communication method (we recommend email) that can be used by anyone having a support request.  Incorporate a practical filtering and issue consolidation process that helps you assess priorities, gauge relative impact (many or few users), and provides a working list for your support staff. Then develop a time or severity based escalation process that formalizes support requests and starts the documentation to resolve and account for more serious issues. And finally, look more long-term at the reports coming from your help desk to assess the effectiveness of your support staff and technical support organization.

And if you really just can’t give up your yellow post it notes, do your support team a favor. Place them in a prominent position and don’t scold them when they miss the support request posted to the bulletin board in the break room next to the refrigerator they never use!

Let us know if you would like to explore ideas about how you can improve your help desk experience.