Tip Sheets


Blackbaud K12 Tip Sheets

Issue link: https://k12hub.blackbaud.com/i/595050

Contents of this Issue


Page 1 of 2

800.443.9441 | solutions@blackbaud.com | www.blackbaud.com December 2018 2 3 2 1 Discover Once you've identified your team and agreed on the pain points that you'll be solving with new software, you can begin looking for solutions. Online Research A great way to start your research is by checking out what other private schools are doing. You can do this by catching up on blogs and white papers that are available online, often for free. In-Person Research Another great source of research is available through your peers. Reach out to peer private schools and find out what they are using and what they like or dislike about it. Also, don't forget to ask your internal teams what they want to be able to accomplish with a new tool. Requirements Outline Based on your online research and feedback from your peers and team members, start compiling a list of items that the software must have and items you want to have. Use this list to help guide your decisions. haven't clearly articulated what problems you're trying to solve at the beginning, then you run the risk of purchasing the wrong software for the wrong reasons. The mission of the project should be to help accomplish a high-priority organizational goal. Note: It's important that during the early stages of selecting your software you have executive buy-in. Make sure this person is on board and kept up to date during the entire process. Evaluate Based on the features you decide your private school needs and wants, begin narrowing your vendor list to two or three vendors that you would like to learn more about based on what they offer. At this point in the sales process, your project manager should reach out to a few of the key vendors to set up a software demonstration. Be sure to: • Include your entire project team on the demonstration • Create a standardized software score card that ensures that everyone is evaluating your "must-haves" and "want-to-haves" during the demonstration • Expect to walk through the software at a high level

Articles in this issue

Links on this page

Archives of this issue

view archives of Tip Sheets - EvaluatingNewSoftware_R2