Published: 11 July 2016
If it’s not obvious from my prior posts on this subject, I’m a fan of Microsoft OneNote. I think it’s a fantastic tool for business analysts, but it definitely has its quarks and limitations.
This post will explore OneNote’s various search functions and discuss two ways you can structure your OneNote content to take advantage of its strengths while working around its limitations. Specifically, using one notebook per project or effort; and defining a reusable folder structure that enables you to best leverage OneNote’s searching and tagging functions.
The reasoning behind both of these recommendations has to do with limitations of the OneNote search and tag functions, and the fact that these functions are spread out across multiple access points within OneNote. For example, the Search function (via the Search box) will let you limit the search results by the following criteria (in OneNote 2010 and 2013, which are the versions I have access to):
Find by Author search (which is accessed only via special button under the History tab) will only let you limit the search by:
Recent Edits function (also on the History tab) will initially let you narrow your results by all of the following options:
And once you have selected a time period, the list of
Recent Edits can be further narrowed by selecting from among the following options:
Lastly, there is the
Find Tags function (discussed in the “Using OneNote Tags” article on this blog). In that function, you can choose to limit the results by selecting from all of the following options:
So depending on what type of content you are looking for, you may be limited by different search capabilities within OneNote. And this is on top of fact that OneNote will not let you combine search terms (no ‘AND’ in text or tag search) or combine search terms with other parameters (e.g. search for all instances of ‘Marketing’ in notes that have been updated in the last 7 days).
Given this current set of limitations, how can you structure your OneNote content best?
The first way to work around these limitations are to store all of the notes for a given project or effort within their own dedicated OneNote folder. And part of the reason for this is to remember that OneNote stores each Notebook as its own discreet file.
By keeping each set of notes on a specific project (or effort, training, process initiative, or whatever else makes sense to you), you can:
All Notebooksoptions. This means it is very simple to limit all of your searches to the current project folder if you change the default search option from ‘All Notebooks’ to ‘This Notebook’
For me, this is the central idea around which I organize my OneNote content. When I was taking classes, I organized the folders by semester with each class its own section. At work I have a separate folder per project, with other folders dedicated to training and other ongoing topics. It also has the benefit of enabling the next concept.
If you agree with the idea of using a single OneNote folder per project, the next step is to structure the sections in your project folder in such a way as to best support the search functions described above. By putting some thought and effort into this, it makes it MUCH, MUCH, MUCH easier to find specific notes from an elicitation session, or a meeting, or a task activity. Or to find just the information you added recently for a specific purpose.
And once you have thought through and defined a generic structure for your project folders that works for you (or even several different ones), they are easy to save and use as ‘templates’ to get every project off to a quick start.
I am going to go through the re-usable project folder I ended up creating for myself below. It includes both pre-defined sections and pre-defined pages that may already have template just waiting for me to fill it in (to be discussed in a later post). It’s important to realize that I may not use all of these for every project or effort, but by defining the template up front I can start with the maximum amount of reusable structure for each project. If I don’t want to use something, I can delete that page or section easily. And if I try something new that I like, I can easily edit my template to add that as an option for future projects.
My OneNote project folder template includes the following sections:
I will discuss each section in detail below.
I generally use the Project Info folder as a quick-reference section for the project overall, and at the moment I have the following reference pages as part of the template folder:
Send to OneNotefunction of Outlook to store them here as sub-pages for quick access
The next section in my folder template is for Task Lists. A lot of people will use Outlook as their day-to-day task management tool, or even a dedicated task-management program like ToDoList (highly recommended, it’s what I use most of the time), but I have found it useful to have a task list section in OneNote for the following purposes:
All of this is made easy by the fact that OneNote has pre-configured ‘tags’ for making something a generic Task (Control+1), or
To Do priority 1 or
To Do priority 2. These latter two don’t have pre-defined hot-keys, but you can add them if you wish or create other task-related tags. [NOTE: See the Using OneNote Tags blog post]
The screen shot below gives you a highly simplified example of what this might look like:
OneNote Tip: You can move one or more items up or down within a OneNote list just by using the alt+shift+up arrow or alt+shift+down arrow keys. You can so use this trick to increase or reduce indent of one or more items in a list by using the alt+shift+left arrow and alt+shift+right arrow commands. The left-right options even work if the lines aren’t next to each other, as long as they are both selected at the same time.
I use this folder to take and store meeting notes for all non-elicitation project meetings. I use the templates and functions discussed in the Using MS OneNote for Meeting Notes blog post to make this easy.
I segregate the generic project meeting notes this way from elicitation notes to make it easier to search just for things that came up during those meetings. You do this by limiting your search to
this section rather than the whole notebook. And if you use the Task tag discussed above in a meeting notes page, it’s easy to extract all of the tasks that came out of those meetings to a single page by using the ‘Tags Summary’ function. [Again, see the Using OneNote Tags blog post]
This is also something where having a shared OneNote notebook for a project is a benefit because no matter who captures meeting notes, they can be stored here for access by everyone to the notebook.
I use this folder in much the same way I use the general Meeting Notes folder discussed above, except I use it for notes from all of my elicitation sessions. As above, one of the main purposes of putting the elicitation notes in a separate folder is to make searching easier. I usually don’t create any initial structure other than the folder itself at first, although I find I tend to organize the pages in the folder by business group, date, or occasionally by topic area. Whatever seems to make the most sense given the project work I expect to do.
In general, the Elicitation Notes section is a good place to:
getting startedinfo for an elicitation session, include a copy of it here
The idea is to have all of the raw information you elicited as a separate searchable section that is distinct from the other types of information.
The Analysis Notes folder is where I like to store my
rough analysis work for a given project. This includes such ideas as:
howI am going to communicate once I have sketched out the
This folder essentially serves as a digital notepad where I can think, summarize, and generally organize the information that comes out of my analysis work. And by having a separate folder for analysis information it lets me keep
my thoughts content separate from the
their thoughts content of the elicitation folder.
The Requirements Notes section is one I don’t always use, but I have found it very useful in the past when I am working on a highly complex effort or when I am coordinating with other BA’s. It is where I put information as I am moving from ‘analysis’ to ‘definition’, and is again in a separate folder to help me search for just information in this state, or for changes made to this type of information. Basically, it is where:
staging areawhere I start putting together actual requirements information or artifacts. I will usually create a single page for each major functional area, and sub-pages for specific sub-functions. Or if you are working in a more Agile fashion you create a page for each epic, a sub-page for each theme, and then a sub-sub-page for each user story (or all stories in a theme on a single page).
Because the information is in OneNote and organized around specific functional areas, it’s usually easier for me to share information on specific questions or functions with stakeholders or other BA’s I am working with just by emailing that page (or sharing my screen, or the notebook, or other options). The main benefit being the information is separated and structured for easy sharing and editing.
As information gets finalized in this section, I am then usually creating more
final requirements artifacts in whatever form is most appropriate. But because I often end up including a bit of
extra information on the pages as I am finalizing the requirements, this section remains a great resource even after final artifacts are created if I want to go back and look for additional information, or to help identify if I left something important out.
The Requirements folder is another one where I tend to make heavy use of the Wiki Links function of OneNote in order to provide links back to content I am analyzing from elsewhere in OneNote. It is also a good place to use customized status tags such as ‘Concept’, ‘Draft’, ‘Reviewed’, and ‘Approved’ so that you can tag the requirements here before exporting them to whatever is the appropriate final location.
Note that if you are working with a more Agile process, a shared OneNote folder such as this could be your actual requirements location. You can create page templates for Use Cases or User Stories, leverage them as necessary, insert screen shots and other collateral, etc. And with OneNote’s page history functions, you can view and track changes as well.
The last section I include is a Solutions Notes folder. As with the other folders, its main purpose is to segregate information related to the solutions that were considered. This becomes especially useful if you end up doing a vendor analysis effort as part of the solution design. In general I will use this folder for storing notes on different vendors that were considered; RFI and RFP work; notes from discussions with the solutions team; putting together questions and feedback of my own on proposed solution elements; and all similar work related to the solution.
And as always, the main purpose of having a dedicated folder is for enable better searching and sharing.
That last step in this process is to actually create your folder template. Note that because OneNote doesn’t support folder template files like Word or Excel have dedicated template files, what you need to do at a high level is:
Or, for even more detail follow the instructions below:ACTION – Create a template of the basic notebook layout I use.
To do this:
You should now have an empty OneNote notebook.
ACTION – The next step will be to create default folders that will be initially present in every project notebooks. In my case this would be to add the following folders:
ACTION – Now that we have our basic folder structure, it’s a good idea to populate some of the folders with some placeholder pages where you think best.
ACTION – Once you have created the basic structure of the project notebook to your desires, you now need to save the new folder and page structure you have just created as a template. You do this by:
Now, whenever you need to create a OneNote notebook for a new project you just re-open that template notebook and “Save As” under the project name before you make any changes.
That’s everything. I hope you found it useful. As always, comments are appreciated.