Case Study
Connecting Platform Compatibility, Upgrade Planning, and SSO
Established an N-2 version-support policy, directed ArcGIS Enterprise upgrade planning, and led delivery of single sign-on compatibility with Azure Entra ID across Accela's GIS integration work.
Jump to a section
Delivered capability
A defined support policy and a delivered identity integration.
The work connected platform compatibility to customer upgrade decisions and delivered single sign-on support. It made the integration's support expectations and identity capabilities concrete.
My contributionI owned the product and partner coordination, support-policy work, roadmap, and customer communication. Engineering and QA implemented and tested the integration.
- Starting point
- Accela and ArcGIS evolved on separate release schedules. Customers also needed the integration to work with their organization's identity system.
- What changed
- An N-2 support policy, coordinated upgrade planning, and ArcGIS SSO compatibility with Azure Entra ID addressed those dependencies together.
Project scope
The work behind the result
Defined an N-2 version-support policy
Directed compatibility analysis and customer rollout planning
Led ArcGIS SSO compatibility with Azure Entra ID
One customer workflow, two platform roadmaps
Accela's civic platform integrates with Esri ArcGIS Enterprise. Customers experience that as one workflow, even though the products follow separate release schedules and have different support considerations.
My responsibility covered the ArcGIS and Esri relationship across Accela's integrated customer base. An upgrade decision needed to account for compatibility, customer timing, and what we were prepared to support.
Define the support decision
I directed compatibility analysis and established a research-backed N-2 support model. The policy defined the recent versions we would support, giving the upgrade program a consistent basis for planning and communication.
The product judgment was to connect support expectations to the roadmap. Compatibility information needed to guide the upgrade order and the conversation with customers, rather than remain an isolated technical finding.
Turn the policy into a rollout plan
I coordinated upgrade sequencing, tickets, technical context, and business communication. The same dependency had to be understandable to engineering, services, customer-facing teams, and the agency planning its upgrade.
Customer presentations connected the platform work to the decisions agencies needed to make. The rollout plan and communication were part of the product responsibility because a technically compatible release still needs a workable path into a customer's environment.
Deliver the identity requirement
Alongside the upgrade program, I led a development and QA team delivering ArcGIS single sign-on compatibility with Azure Entra ID. Single sign-on lets people use their organization's identity across the connected experience.
I built the roadmap and coordinated the customer and partner context for this executive-sponsored work. Engineering and QA owned implementation and testing; I kept the product requirement and sequencing connected to the wider platform relationship.
Why the work mattered
The result was a defined support model, coordinated customer upgrade planning, and delivered SSO compatibility. The identity work addressed an integration requirement in the Esri relationship, while the support policy gave the broader upgrade program a durable decision framework.
This is the kind of platform product work I enjoy: understanding a technical dependency deeply enough to make a clear product decision, then carrying that decision through delivery and customer communication.
Skills demonstrated