Protected $5M+ Revenue with Enterprise-Ready Identity and IAM Compliance

The Client: A Maritime Technology Leader

A global engineering and maritime professional services organization operating at the intersection of compliance, risk management, and digital transformation, providing voyage optimization, navigation, and regulatory software used by large shipping companies worldwide.

The client operates globally with enterprise-scale revenue and serves some of the world’s most complex maritime organizations.

In this market, enterprise-grade identity management is not optional. SSO, MFA, and centralized user governance are baseline requirements for procurement, renewal, and compliance approval.

‍

The Mission: Interim Product Manager

The Single Sign-On initiative had been running for over two years without a dedicated Product Manager. Engineering was progressing incrementally, but there was limited strategic alignment, no clear roadmap slicing, and no strong articulation of business value.

SSO was treated as a technical enhancement rather than a revenue protection and compliance initiative.

We were brought in as the PM role had effectively been vacant. Enterprise customers were signaling that the lack of SSO was becoming a renewal blocker. Authentication friction was generating tens of thousands of support tickets annually, creating operational cost and customer dissatisfaction.

Our mandate evolved quickly.

What began as “deliver SSO” became:

• Protect multi-million enterprise revenue
• Establish an enterprise-ready identity layer
• Align fragmented product teams
• Professionalize product discovery and delivery

This was not a feature delivery mission. It was a structural platform transformation.

‍

Our Main Quest: Single Sign-On for Fragmented Product Lines

Launch: Onboarded Very Fast

Multiple development teams were contributing to identity-related work, yet no single Product Manager was driving discovery, prioritization, and alignment.

We created clarity, focus, and measurable delivery momentum by rapidly establishing structure and alignment:

• Conducted a Now–Next–Later prioritization workshop
• Reframed SSO as a revenue protection and enterprise compliance initiative
• Introduced structured agile rituals
• Centralized documentation and dependency tracking

First Deliverables and Results

1. Single Sign-On for Legacy Products

Our first major milestone was consolidating fragmented logins across legacy maritime systems and successfully launching an enterprise beta.

Legacy systems are notoriously difficult to integrate. They were built at different times, by different teams, with different identity logics and database structures. There was no shared user model and no centralized identity governance layer.

The biggest challenge we faced was unique user identification across systems:

• Maritime users do not always have corporate email addresses. Many offshore crew members operate without official company emails, especially on vessels with limited connectivity.
• Users often have multiple identities across products. The same person could have different usernames or email variations depending on the tool.
• Identifier collisions existed across systems. In some cases, User A in Product X and User B in Product Y shared the same identifier — creating data integrity and security risks.

A conventional SaaS solution — forcing a single unique email identity — would have excluded a significant portion of maritime users and created adoption resistance.

Instead, we designed a flexible identity architecture:

• Email as the primary identifier when available
• Unique username fallback for users without corporate email
• Backend reconciliation logic to prevent cross-product identity conflicts

We started with one legacy product, launched a controlled beta with enterprise customers, validated authentication flows, and then expanded incrementally to additional systems. This phased rollout reduced risk and allowed us to refine identity matching logic in real-world scenarios.

The result: a scalable identity model tailored to maritime realities — not copied from generic SaaS patterns.

2. Introducing Change Without Disruption

Maritime enterprises are highly risk-averse. Change management is particularly sensitive when a large portion of the workforce operates offshore, sometimes in the middle of the Atlantic, with limited technical support.

Forcing immediate login migration would have created friction, support overload, and potential operational risk.

We deliberately chose a soft-transition model:

• Traditional login methods remained available
• SSO was introduced as an additional, more efficient option
• Enterprises could gradually onboard users to centralized identity
• Communication emphasized improved security and convenience, not system replacement

This approach minimized resistance while modernizing the authentication infrastructure.

Instead of triggering disruption, SSO adoption grew organically — driven by usability improvements and enterprise IT alignment.

3. Enterprise-Ready Identity Foundation

Beyond user-facing login consolidation, we delivered the structural groundwork for enterprise IAM (Identity and Access Management) compliance.

This included:

• Centralized identity mapping across products
• Auditability improvements for provisioning and de-provisioning
• Architectural readiness for MFA rollout
• Compatibility with enterprise identity providers, such as Entra ID / corporate AD

This was a critical shift from fragmented authentication to centralized governance — directly addressing renewal blockers raised by enterprise customers.

‍

From Feature Delivery to Platform Thinking

Initiative 1: Streamlining Product Ops

Problem:

• Discovery insights, technical decisions, and business assumptions were fragmented across teams.
• There was no single source of truth connecting enterprise risk, revenue impact, and user stories.
• Engineering was progressing, but without a clearly articulated mission narrative or structured roadmap slicing.

What has been done:

• We structured a centralized Confluence space covering the full mission: business case, identity architecture, phased rollout, and functional breakdown of SSO.
• We connected enterprise risk — churn and compliance exposure — directly to roadmap priorities, ensuring technical delivery was anchored in business value.
• We introduced a phased Now–Next–Later roadmap, enabling incremental legacy integration instead of overwhelming “big bang” releases.
• We implemented visible dependency tracking across teams, increasing transparency and predictability.

Value delivered: a structured, outcome-driven platform initiative with clear business relevance, instead of a loosely scoped backend project.

Initiative 2: Establishing a Structured Product Strategy Process

Problem:

• The SSO initiative lacked a clearly defined product strategy; decisions were primarily driven by technical feasibility rather than strategic positioning.
• There was no structured approach to defining the user space, problem space, and long-term value proposition.
• Leadership discussions were tactical and reactive, with limited alignment on how SSO supported enterprise revenue protection and platform growth.
• The absence of a shared strategic framework made prioritization inconsistent and slowed decision-making.

What has been done:

• We introduced a structured strategy development process, beginning with clearly defining the user segments — enterprise IT admins, compliance officers, and maritime crew — and their distinct identity challenges.
• We mapped the problem space, connecting fragmented authentication, governance gaps, and compliance exposure to measurable business risk.
• We facilitated focused strategy workshops to articulate a clear value proposition and long-term vision for centralized identity across the product ecosystem.
• We translated this vision into strategic pillars: enterprise readiness, IAM compliance, ecosystem unification, and renewal protection.
• We aligned stakeholders around these pillars, creating a shared decision-making framework for future identity-related investments.

Value delivered: higher leadership alignment, faster prioritization decisions, and delivery anchored in long-term platform objectives rather than short-term technical fixes.

This structured approach transformed strategy from an abstract discussion into an actionable framework.

Initiative 3: Establishing Cross-Team Ownership & Accountability

Problem:

• SSO required collaboration across multiple product teams with historically independent roadmaps.
• Ownership boundaries were unclear, creating delays and dependency friction.
• Platform initiatives lacked structured escalation and alignment mechanisms.

What has been done:

• We introduced recurring cross-team alignment forums focused specifically on identity dependencies.
• We created a shared dependency tracker updated weekly to surface blockers early.
• We clarified domain ownership across legacy systems and defined accountability paths.
• We established structured escalation channels for enterprise-critical risks.

Value delivered: a cohesive platform program with shared responsibility and faster delivery momentum.

This shifted SSO from distributed backend coordination to a coordinated, cross-team identity program.

‍

Discovery Mini-Missions: Our Side Quests

In parallel to leading SSO, we supported adjacent initiatives:

• Rollout and communication strategy for renewal-sensitive enterprise customers
• Executive-level refinement of the business case for continued identity investment
• Cross-functional collaboration between product, engineering, and security

These efforts strengthened organizational maturity beyond the SSO scope.

‍

Mission Achievements: Delivered Outcomes

💡 Revenue Protection — Protected $5M+ in company revenue by addressing enterprise churn risk linked to missing IAM compliance capabilities.

💡 Operational Efficiency — Projected 70–80% reduction in authentication-related support tickets, unlocking significant annual cost savings and reducing customer IT burden.

💡 Platform Foundation for Growth — Established the centralized identity layer enabling MFA rollout, auditability, ecosystem stickiness, and cross-product expansion.

‍

Mission Extensions

The mission was extended multiple times since its initial start date:

• Original Mission Period: October 2024 – April 2025 (6 months)
• First Extension: Extended through June 2025 (additional 2 months)
• Second Extension: Extended through February 2026 (additional 8 months)

Total mission duration: October 2024 – February 2026 (approximately 16 months).

These extensions reflect continued value delivered and sustained enterprise need for product management support as the identity initiative evolved from initial delivery to platform expansion and continued development phases.