When I first came to the OneNote team, I got sent links to no less than 15 notebooks, had my monitor "upgraded" from a CRT to an LCD, was issued a Tablet PC, had the COM API dropped on me and had to make the transition from enthusiastic user to tester on the team. One of my first tasks was to give the program manager team my thoughts on initially encountering OneNote. It's pretty easy to fall into the trap of only designing for people who already use your application, but we don't want to forget about first time users either. This is especially true for OneNote, which is, in many ways, still the "new kid on the block."
My feedback went something like this:
The other thing I've noticed is that many of the problems that annoy me or anyone at Microsoft are just about exactly the same as what the computer populace as a whole point out. For instance, I'm not the only person who wants new pages at the top. Nani's tool really helps here, and it's nice to see I'm not completely off base with my thoughts on how OneNote should work. This helps validate my scenario based testing. It gives me an extra level of confidence that the tests I design for new features are an accurate method of the way in which people will use OneNote. They reflect the real world use of OneNote and are not too focused on minimal path types of work flows.
Questions, comments, concerns and criticism always welcome,