An effective way to approach a managed notification project is through development of a business case. (Many organizations require one.) Done right, a business case is more than a justification. It forces consideration of factors that can make or break a project. Plus, it establishes a go-forward plan. Even if not required for approval of a project, a strong business case can set the stage for success.
The business case should be a collaborative document with input from various stakeholders. Then, it should be kept alive, with updates and modifications, even after approval. A strong business case doesn't need to be long, but it should be thorough.
The business case will be the guide throughout the project. Plus, it's an excellent way for obtaining buy-in from stakeholders (including those who hold the purse strings).
Elements for a good notification program Business Case are:
Galain Solutions, Inc. has published a white paper "Building a Good Business Case", which is available upon request to firstname.lastname@example.org. Couple the Business Case document with Galain's white paper, "Notifications, Alerts, Warnings: The Next Generation" and you have a good primer on launching or enhancing a notification program that truly produces success. (The "Next Generation" white paper is also available upon request to email@example.com.)
All the best,