0:0018:08

Platform as a Product - When Developers are your customers

Shuchi Mittal 18:08 2023

Some of Fiserv's developers didn't know their platform team existed

Developers at Fiserv, it turns out, have been engineering platforms themselves without knowing an internal team already runs them. That surprise exposes the cost of project-by-project infrastructure support: bottlenecks, engineers stretched across 20 projects, burnout and a growing pile of one-offs. Shuchi Mittal, Global Head of Digital Transformation Platforms at Fiserv, traces how her organization set out to change that. What happens when platform engineers start treating developers as customers?

See the staged path from project mode to roadmaps, personas and self-service platform APIs

Watch on YouTube

In short

Shuchi Mittal, Global Head of Digital Transformation Platforms at Fiserv, explains how Fiserv's platform engineering organization moved from project-driven support to a product mindset that treats internal developers as customers. Drawing on Team Topologies, she walks through the stages of that shift: visible work tracks, product owners, roadmaps, feedback loops, user personas and an API-first, self-service platform.

“They were very surprised. So not only were they running into issues trying to use some of the platforms we have, but some development teams didn't even know we existed or we did some of the work for them.”
“So they're not seeing multiple platforms, they're seeing one platform.”

What you will learn

  • Map your organization to Team Topologies stream-aligned and platform teams to cut developers' cognitive load.
  • Spot the signs that project-based platform support has become a bottleneck: overloaded engineers, context switching and solutions trapped inside single projects.
  • Plan a staged move to a product model: a single visible work track, product owners, an idea portal, published roadmaps and quarterly planning.
  • Build feedback loops with developer customers through office hours, newsletters and a developer community.
  • Design self-service by defining user personas, mapping journeys across platforms and taking an API-first approach.

Key takeaways from the speaker

  • When Platform Engineering teams take ownership of specific parts of their platforms and create internally visible brand identities, they can articulate the benefits of their work to their customers - App Developers.
  • Explicitly define Product management responsibilities that include continuous improvement activities, such as road mapping, usage metric data-gathering, and quality monitoring. Focus on platform self-service to remove friction.

Details

Level
Intermediate
Format
Talk
Technical depth
Introductory technical
For
People manager, Senior individual contributor, Executive
Length
18:08
Published
June 2023

Questions this talk answers

Why does project-based platform engineering stop scaling?

No platform team has enough people for every project, so it becomes a bottleneck, and solutions built for one project stay invisible to the rest of the enterprise. Engineers spread across as many as 20 projects end up context switching and burning out.

How does Team Topologies help platform teams?

It separates stream-aligned teams that drive business value from platform teams that handle lower-order concerns such as VMs and monitoring, reducing cognitive load. The interaction model moves from facilitation towards offering capabilities as a service.

What practical steps moved Fiserv from project mode to product mode?

Teams first built a single work track to make all work visible, then recognized the need for product owners, collected requests in an idea portal, published roadmaps and started quarterly planning. They also tracked capacity for feature work versus firefighting and sized features in story points.

How can platform teams get better feedback from developers?

Fiserv started office hours, newsletters about what platform engineering was working on and its impact, and evangelism through a developer community of more than 2,000 people.

What comes after building individual platform products?

Recognizing that developers see one platform, Fiserv is defining user personas, mapping user journeys and pain points across platforms, and moving to an API-first, touchless model where developers wire platform APIs from a portal into their pipelines.

About this talk

“Infrastructure teams slow us down”, “It takes too many tickets to get my infrastructure”, “I have no idea what platform I can use or when” - Do these sound familiar? Your shared services organization is busy just trying to keep the lights on while the product development teams find it difficult to use those services and look for workarounds. This escalates into lots of one-offs over time and a mountain of tech debt. Fiserv Platform Engineering organization adopted a product mindset for delivering platform capabilities a few years ago, which has helped us align better with the needs of our product development teams and accelerate the value flow through the enterprise. This involved aligning teams to capabilities, embracing agile development, user research and feature analysis, creating self-service pathways, defining and measuring KPIs, setting up feedback loops and so on. Terms like "customer", "value" and "friction" have become part of our vernacular. The tide is beginning to turn to healthy collaboration and dialogue between developers and platform engineering teams, and overall better outcomes for the enterprise.

Topics

Related talks

Browse the library