Welcome back to our “craft your program strategy” series! In the first blog entry of this series, we explored why a long-running program mindset outperforms short-term, one-off projects when it comes to identity security. This time around, we’ll focus on two cornerstone documents that bring that program mindset to life:
These two planning assets work in tandem to define, guide, and communicate the purpose and value of your identity security program—both to key stakeholders and to the broader business. We’ll show how they help you keep teams on the same page, streamline decision-making, and highlight your program’s strategic value from day one.
If you joined us for our 'why “program vs. project” matters for identity security' blog post, you already know that programs and projects look similar on paper but have fundamentally different aims. Projects focus on discrete deliverables—like onboarding a new department or automating a single provisioning workflow. In contrast, a program is an ongoing framework. It adapts to new systems, regulatory changes, and shifting business realities, all while driving continuous improvement. To scale your identity security effectively, you need both:
This is where your charter and roadmap truly shine.
As highlighted by our 'The importance of an identity security program charter' article, every successful identity security program needs a solid foundation. The charter sets that foundation by spelling out why the program exists and how it will operate. Think of it as a formal contract—though not necessarily laden with legal jargon—that aligns all stakeholders on scope, goals, and decision-making structures.
Typically, a charter includes:
To help you jumpstart the process, SailPoint offers an identity security program charter template that you can tailor to your organization’s specifics. This can save significant time—rather than starting from scratch, you’ll adapt an existing blueprint complete with recommended sections, example metrics, and governance structures.
Similarly, referencing our 'Developing an identity security program roadmap' article, where the charter answers “why?” and “who?”, the roadmap covers “what?” and “when?” It transforms the charter’s vision and objectives into a phased-approach—what you’ll implement first, which capabilities come next, and how different phases build on each other.
If you’d rather not build a roadmap from scratch, we’ve curated two helpful templates:
Customize them to reflect your priorities—whether that’s faster provisioning, enhanced monitoring, or addressing compliance hot spots like SOX or GDPR.
Imagine your charter as the strategic “mission statement” and your roadmap as the “tactical schedule.” Both are living documents that inform each other:
By revisiting these two documents together each quarter or at key milestones, you keep your identity security efforts tightly aligned with organizational changes—and make sure you’re communicating that alignment clearly to leadership.
Let’s say an organization’s executive sponsor defines ambitious goals in their program charter: “Establish consistent user provisioning across 100% of mission-critical apps within 12 months, reduce time-to-provision by 40%, and cut audit findings in half.” That same sponsor works with their program manager to create a phased roadmap that schedules which apps get onboarded in which quarter, when key automation scripts roll out, and how policy modeling can strengthen audits.
After Phase 1, the team sees the new self-service capabilities saving each helpdesk associate 10 hours per week—well ahead of schedule. They update the charter’s success metrics to capture that time savings, and re-prioritize a second phase to bring more high-risk apps in sooner. This ongoing feedback loop ensures no team is stuck re-inventing the wheel, and that leadership sees a direct link between documented goals and tangible progress.
A solid program charter and a well-structured roadmap are two sides of the same coin—defining your identity security program’s purpose and plotting the journey to realize that purpose. They keep everyone in sync, from your executive sponsor to your system administrators, and they ensure that incremental wins pave the way for lasting gains.
Ready to put this into action? Here’s how to get started:
And of course, if you missed it, be sure to circle back to our Craft your program strategy article and the first blog in this series on why “program vs. project” matters for identity security. With a clearly documented charter and roadmap, you’ll be well on your way to building (and sustaining) a successful identity security program that keeps pace with your organization’s evolving needs!