In Part 1 of this article, I discussed the information management needs for my training practice. Now I will turn to the first major component of the system – managing correspondence and applying OneNote® to the task.
With vary rare exceptions all correspondence for my training practice is electronic – email. So the primary purpose of the system is organizing and managing email. At the same time, the system needs to allow for possible correspondence in other formats, particularly telephone calls and text messages.
In Part 1 of this article, I referred to the system’s “prime directives”
- ease of storage
- ease of retrieval
The system is intended to manage information
- received from, and sent to, other people
- about training workshops and people attending.
Dealing with training workshops and the people who attend the workshops suggests a general structure (or categories) for organizing the information:
- Information Requests
Given that most of the information I am dealing with comes in the form of e-mail, it is fair to ask why go beyond my email client, Outlook®? After all, Outlook does offer custom folder, and fairly extensive search tools. Couldn’t you organize all the information in Outlook and avoid transferring information to and from another tool?
The answer is, of course, “Yes …. but….”
As good as Outlook’s folder management and search tools are, I found they weren’t quite the tool I was looking for. For one thing, my emails deal with more than just training-related information. As my training practice grew, it became increasingly time-consuming to track down all the emails related to, say, a specific workshop or a specific sponsor.
Some years ago, I discovered OneNote® and had been using it to store and manage much of the information that comes my way on a daily basis. For example, I uses a variety of computer applications. I use a OneNote notebook to keep track of the license information for these applications.
So I began thinking about using OneNote to manage my training practice information. Communication between Outlook and OneNote is relatively easy; versions of Office since 2010 or so have included an Outlook command to send the current item to OneNote. The same versions include a ‘printer’ which means you can create a OneNote entry for just about anything simply by printing the item and selecting “Send to OneNote” as the printer.
Setting it up in OneNote
The OneNote features I will be discussing here specifically refer to OneNote 2016 running on a Windows 10 desktop computer. The organization of OneNote notebooks is relatively simple.
A OneNote can have one or more sections. Each section can have one or more pages. For my purposes, the most useful structural feature of notebooks is section groups. It is this feature the is at the heart of my filing system.
When you first create a OneNote notebook, it has one section with one page in it. In my training notebook I will use that section as a table of contents for the entire notebook. To identify the section and its purpose, I have renamed it ‘Notebook Contents.’
I should mention at this point that I use the Onetastic add-in TOC in Current Notebook macro to automate this part of the notebook. The table of contents supports the ease of retrieval prime directive. The Notebook Contents section contains a single page, ‘Table of Contents,’ generated by the Table of Contents macro. When I add new content to the notebook, I use the macro to generate a new Table of Contents page and delete its predecessor.
The notebook has a second ‘top-level’ section named, ‘Information Requests.’ This section contains one page for each training information request I receive. I use another Onetastic macro, TOC in Current Section, to generate a Table of Contents list of current requests in the section.
The meat and potatoes of the notebook is a section group I have called Sponsors. Each sponsor is represented by its own section group with an index section, and one section group for each training year. Each training year has one section for correspondence to and from this specific sponsor during the year and a section group for workshops. Finally the Workshops section group has individual sections for each workshop.
One possibility I considered was to have two section groups for workshops, pending and completed but I decided to simply use colour coding to make the distinction.
Believe me this system is far more complicated to write or read about, so here is a chart outlining everything:
Notice that the contents are blue and underlined? Each entry in the generated table of contents is a hyperlink to the section listed. That makes it easy to get to any particular section or page.
How it Works on a Daily Basis
Here’s how the workflow goes.
I receive an email from Mary Smith asking for general information. After reading her email in Outlook, I click the Send To OneNote command and choose the Training Notebook Information Requests section as the destination.
Now, let’s skip ahead in time a bit to when Mary books a training date. Since I don’t yet have a section for the company that will be sponsoring the training, I create new section in the Sponsors section group for DEF Inc. At this point I name the section that OneNote automatically added to the DEF section group for 2016, name its first section Correspondence and create a Workshops section group.
In the Workshops section group, I name the first section Workshops and create a new section named for the Workshop that Mary has booked.
Now, if all of that sounds time consuming, it really isn’t. All it takes is a couple of minutes.
Since I’d like to keep all correspondence related to a particular sponsor together, at this point I will move Mary’s information request to the new correspondence section for this year for the sponsor. OneNote make it easy to relocate pages ‘on the fly.’
I should also note that, while the Onetastic TOC macros are a great tool, this system does require some manual work for some of the sub-indexes. Once again, OneNote makes creating links to specific pages pretty much child’s play.
So that is my correspondence management in a nutshell, albeit a somewhat large nutshell. Part 3 of this article will discuss the building data management component of my system.