CMS Hybrid Cloud

Clarifying onboarding, governance, and operational relationships across a complex federal cloud ecosystem.

The ecosystem had evolved across multiple teams, workflows, governance structures, and lifecycle stages. The work focused on making those relationships operationally visible so the organization could align, coordinate, and evolve more intentionally.

Focus

Operational Visibility, Service Blueprinting, Customer Readiness, Continuous Improvement

Role

Lead Service Designer

The ecosystem extended across interconnected operational domains distributed throughout the service lifecycle.

Lifecycle & Operations

onboarding operations

lifecycle coordination

operational readiness

Governance & Support

governance pathways

compliance requirements

customer support workflows

Shared Infrastructure & Operations

infrastructure operations

shared service teams

Intersections

Customer-facing experiences were shaped by operational dependencies, governance sequencing, and backstage coordination occurring throughout the lifecycle.

Where Operational Complexity Created Friction

While operational knowledge existed across teams, the organization lacked a shared understanding of how onboarding, governance, operational support, and optimization connected across the full lifecycle.

Operational execution relied heavily on tribal knowledge

Feedback mechanisms existed but lacked coordinated orchestration

Workflow sequencing across systems lacked clarity

Customer readiness expectations varied across lifecycle stages

Governance appeared disconnected from operational workflows

Translating Fragmented Operations Into Shared Understanding

The work focused on converting fragmented operational knowledge into a clearer understanding of how onboarding, governance, support operations, and lifecycle management connected across the ecosystem.

Operational Focus Areas

lifecycle orchestration

governance alignment

onboarding visibility

backstage operational mapping

readiness modeling

feedback ecosystem analysis

Organizational Deliverables

end-to-end lifecycle blueprints

operational findings synthesis

governance recommendations

ecosystem alignment frameworks

continuous improvement backlog

Key Findings & System Observations

Existing Feedback Loops Were Present but Fragmented

The organization already had multiple feedback mechanisms in place, but they operated independently rather than as a coordinated system tied to lifecycle stages.

It lacked system coordination across feedback cadence, operational loops, improvement systems, and prioritization structures.

Why: Teams built feedback into their workflows, but without visibility into how those loops connected to other stages or informed broader optimization.

Governance Was Embedded but Not Operationally Visible

Security alignment existed throughout onboarding workflows, but documentation and mental models framed it as a standalone step, creating confusion around ownership and sequencing.

How to apply:Reframe governance as interwoven across lifecycle stages rather than isolated checkpoints.

Operational Readiness Lacked Shared Definition

Teams lacked a unified understanding of customer readiness, contributing to inconsistent onboarding expectations and operational handoffs.

Why:Different teams defined "readiness" through their own operational lens, creating misalignment at transition points.

Shifting Toward Operational Visibility

Operational Alignment

Established foundations for system-level service management

Improved operational coordination visibility

Reduced dependency on tribal operational knowledge

Governance Integration

Structured lifecycle-aligned governance pathways

Introduced framework for friction identification and prioritization

Continuous Improvement

Created foundation for continuous improvement operations

Improved visibility across onboarding and operational workflows

Operational Outcomes & Organizational Impact

Created clearer operational visibility across onboarding workflows, governance touchpoints, and support operations

Established foundations for more coordinated operational prioritization and continuous service improvement

Established a shared operational foundation for lifecycle-based service management

Reduced dependency on fragmented tribal knowledge across onboarding and operational workflows

Improved coordination across Customer Support, shared service teams, and operational stakeholders

Enabled more intentional alignment between governance structures and day-to-day operational execution

Reflection

Once teams gained clearer visibility into how the ecosystem operated as a whole, more intentional conversations around governance, prioritization, and operational improvement became possible.

Explore More Work

View All Case Studies