First, let me point out that Owen Braun is blogging now. He's the lead program manager on my team responsible for OneNote. He's got a great post up about how we now support multiple notebooks. And he's promising a whole feature on hyperlinks...
Recently I've had some mail from various OneNote users telling me that they are using OneNote for team work - shared sections and folders of notes which every member of the team can read and contribute to, and of course search. I've also been reading blogs like this one. I like this post because sbreck describes exactly the type of scenario we are targeting OneNote 12 at. Of course, he is trying to do it with OneNote 2003, so he has a few issues. It works, but it runs into limits. OneNote 12 has had significant work done to make it a breeze to work in small to medium groups effectively and quickly. Allow me to drone on….
How did we get here?A lot of people view OneNote as a single-user application designed for personal notes. This is a pretty narrow view of an application we have much grander ambitions for. Of course it is not as narrow as the "it only works on TabletPC" myth (grr), but it's still pretty narrow.
As we started planning OneNote 12 in the summer of 2004, for kicks we dusted off our original vision for it. Right there in black and white in the original vision doc from early 2001 there is a sentence I wrote at the urging of my dev manager to specify what we were NOT going to do in the first release as a guide to the team. It states, "Scribbler [OneNote] will be a single-user application for personal use. Although we intend to make it a multi-user application in the future, our first release will focus on the single user scenario to make sure we get it right".
Our dev team was actually very excited to design into OneNote from the very beginning the ability to treat every page and every little bit of content on a page as a node on a graph that can be modified by any number of user agents. They did not want to make any assumptions in the architecture or the code that required a single user to be doing the modifications to this graph in a particular sequence. So we had to put in a little explicit "Down Boy!" to make sure we stayed focused for the first release.
When we had a chance to do SP1 with a load of features, we enabled real-time multi-user editing of pages. We had already found OneNote a compelling way to enhance meetings - it would be even better if we could all use it together - including people attending by phone. We hooked ourselves up to a convenient peer-to-peer sharing technology that was in every version of Windows we supported: DirectPlay. This is used for multi-player games on LANs, but it also works for note taking apps that work using the same principle of passing changes to the other members in the "game'. I wrote more about this here.
The upshot was that we had a non-trivial multi-user editing surface which could be used in real-time. Multi-user editing of a document is one of those hard problems in computer science. It's been done for simple documents such as text files or pixel-drawing whiteboards, but to do it for something tricky and complex like a OneNote page was novel. I am not aware of any non-research application out there that does this to the degree we do (where any user can edit at once in an unstructured way). There were a few limitations to this approach - namely it was really focused on synchronous multi-user editing (i.e. you are all working together in real-time), so it was not a good candidate for collaboration that lasted more than a few hours.
Another thing we added in SP1 was the ability to open a folder on a file share. We had some customers early on (even before we shipped the final code for the original release) who immediately saw that OneNote was a great place to keep the notes for a team (of, say, lawyers and paralegals) for one or more projects. They had a problem today where only one person could read and access notes and documents at one time with their existing tools, and they needed to move faster. They were quite motivated to make it so each user could see and add to or annotate a shared set of information, such as the case file for a client. It's sort of interesting to have a PDF file in a shared location such as a file share or document management system. More interesting is if you can see the other lawyers' opinions of the various clauses in that contract or brief - written in ink or typed beside the pages, or highlighted passages.
OK, still with me? Here's where OneNote 12 comes in.OneNote 12 allows something we are tentatively calling "shared notebooks". Other working titles include "Nirvana and you", or "Happiness on a stick". [:)]
With a shared notebook:
Shared notebooks may sound fancy but really they are just the most obvious thing. I can work on page as I would with my private notes. So can you. You can see what I wrote, and vice versa. So can Hans, Reza, Mary and Yuriko. We can continue this way for months if necessary. It's the most natural way to work together. It's like sitting around a big desk with your team and having a space in the middle where there are post-its, documents, notes etc. and you can see what others are doing or have done while you stepped out. There's no barrier to grabbing a doc and commenting on it while some one else writes the conclusion. Or add comments to a post-it note already on the desk while someone else is reading it.
Best of all you can go on a trip and take the whole desk with you for reference, make changes, then when you come back through the magic of software your modifications are just merged in with the work that has been going on. (Ok, you can see that the physical metaphor sort of runs out of gas because this is something you really can’t do without software.) In software there's no bumping into each other and holding a paper at an awkward angle while someone else tries to see it. Its also trivial to search and locate anything in the massive archive you can build up - very unlike paper.
Today when a team works together they have a file share or a SharePoint site where they put files. You can browse to that place and see what files are there. You can't see what's in the files without opening them. You can't see what others think about each file. You can’t access these files offline unless you take them offline manually and lock others from editing them to avoid nasty conflicts when you go to put your changes back. All those barriers go away with OneNote 12.
When I try to describe this in words I usually get a few questions:
Ok, that's fine, but what use is this?There are lots of uses as I've mentioned above. An example for us was when we were trying to get our plans firmed up for the last milestone of development. Usually that process entails putting specification documents on a server and having devs read those docs and make private comments in a non-shared place. We usually try to have at least two separate devs estimate the work to develop the proposed capability to cross check and make sure nothing is missed. The downsides of this process are that no one can see if the devs have started reading the specs or making comments. No one can see the comments. Devs have to ask questions via email or physically locating the PM, and no one else can see those questions.
For our last milestone we used OneNote 12 and created a shared notebook, using several sections but one especially held a page for every proposed feature. We put a table at the top of each page, and embedded the spec document in question. The table also had a place to list the devs, testers, comments, unanswered questions (marked with note flags), etc. Everyone on the team could see the notebook at any time, even on the bus ride home. You could see which devs had started making comments on which spec. Two devs could comment on the same spec at the same time. We could query the whole notebook to see how many unanswered questions there were and what they were.
There were some neat side effects too. For example, previously we used to put these specs out and dev would say they would estimate them. Now we could actually see that they didn’t start estimating them until the following week (with an integrated development team it is gold to know what is really happening, not just what is supposed to be happening). Some PMs took advantage of that knowledge to put up an updated spec that had more detail - something we had been asked not to do in the past as devs had often started estimating the spec unbeknownst to us.
The most amazing thing was that we were done with the whole exercise and had higher faith in its being well executed in a matter of a week - usually it takes a month. This underlines one of the selling points of this approach - it makes your organization more agile. I was talking to a law firm the other day which is interested in OneNote. I asked them why a firm that charges by the hour is interested in time-saving productivity tools? The answer: law firms that engage in litigation are more interested in winning the case than in hourly fees. Anything that allows them to put a case together and move faster than the competition increases their chance of winning. The CIO told me that he learned something from a General when he served with the military: winning is all about not waiting your turn.