Moves Management

I've uploaded the 2 documents to my profile.  If you search for me in the directory and click on my profile, then look in the red side bar on the right side and find the "My Files" section you will find them both there.  I believe you will have to download them from there.

Our biggest lessons learned were:

1.) There is a lot of flexibility in how plans can be set-up, therefore it is important for the entire Development Department to be involved in the initial planning process, discussing possible scenarios for how different fundraisers/campaigns would like to utilize the functionality so that it works for the entire department and there is consistency of use - is very important for reporting.

2.) Set clear goals/intentions for the functionality so you know what you are trying to accomplish when setting it up - ex: we new we had 3 primary goals with regards to plans; track and provide metrics on our fundraising activities  to leadership staff and our board (ability to show them the larger picture of fundraising and the work that goes into closing gifts); create a process that is helpful for fundraising staff and is being used consistently; and allow better understanding of individual fundraisers portfolios and better manage crossover - so we are organized with complex donors who may be getting asks for multiple campaigns or being asked to increase.

3.) Think about how you want/need to report out (on an individual fundraiser level, department level, and organization level) and what is most important.  In my opinion, It's great to have a place to enter information for historical purposes, and that's important, but at some point, if you can't get it back out easily or use the information to define lists, extractions, etc. you start to use some of the real power the database can have.

4.) Document!  I'm a huge fan of creating standard operating procedures (thank you David Crowther for showing me the importance of this).  Provides a resource for the on-boarding period while staff i still getting used to the new procedure, makes it easier to explain/teach the procedure to new staff members, and serves as a reminder of why certain decisions were made.

5.) It's better to have too much flexibility and not use it than not enough and have to change it all.  Take this with a grain of salt - I'm not an advocate of creating data points you don't need, but if there is the possibility of repeated use but not necessarily often, I'd say go for it.  BUT be sure you document and the purpose is understood otherwise you may end up with data points you don't feel you can rely on.