Workshop Artifact · Developer Experience · 2hr 20min
Developer Dialogue
API Creation Journey Map
A cross-functional session mapping the reality of API development from concept to consumption — surfacing pain points, tool gaps, and quick wins across five lifecycle phases.
Journey Mapping API Governance Developer Experience C-Suite Alignment
Session Agenda
20 min
Opening: Introductions & Context
60 min
Session 1: API Journey Reality Check
10 min
Break
35 min
Session 2: Pain Point Prioritization & Solutions
15 min
Wrap-up: Next Steps & Decision Log
Pre-Session Survey Findings
12
Participants across 4 product areas
Mixed roles: API producers, consumers, architects, and product managers — intentionally diverse to surface the full lifecycle picture.
100%
REST APIs in use today
Event-driven architectures are emerging alongside REST, surfacing new requirements around security models, monitoring, and versioning strategy.
3
Common pain points pre-identified
Cross-team standardization, discoverability of internal APIs, and manual processes with significant tool gaps appeared across all respondents.
2×
Different governance approaches per team
One team ran a single unified process for internal and external APIs. Another ran completely separate workflows. Neither knew the other existed.
API Lifecycle Journey Map
Phase 01
Concept & Planning
From initial business need identification to approved API design approach
Current Reality
APIs are often an afterthought — "we need an API for this UI"
Requirements come from business; architecture is left to tech leads
Pain Points
No standard discovery tool — must rely on personal contacts
Difficult to prioritize APIs without explicit customer requirements
Quick Wins
Involve API requirements in PRDs from day one
Secure API sponsorship at product level
Phase 02
Contract Definition
From API design concept to finalized, approved API specification
Current Reality
Uneven application of process — Word docs, UML, bullets, OpenAPI all in use
No standard design tooling across the org
Pain Points
No clear approvals process — "is it just the engineers?"
Auth is often an afterthought at this stage
Quick Wins
Guidance on API-first / API-as-a-product principles
Linting and validation tooling for API specs
Phase 03
Development & Testing
From approved contract to tested, working API implementation
Current Reality
Testing tools are UI-focused; API testing via curl commands
No automation for API regression testing
Pain Points
Little to no NFR testing (performance, security)
External APIs hard to test — can't replicate prod data
Quick Wins
Standard testing tools for APIs (Postman seats)
AI tooling to validate providers against standards
Phase 04
Deployment & Operations
From working code to production-ready, accessible API
Current Reality
Documentation scattered across GitHub, SharePoint, Atrium
Every tool has docs in a different place
Pain Points
Difficult to understand best practices when deploying a new API
Least-privilege access management unclear per tool
Quick Wins
Centralized index — not all docs, just where to go
Federated approach linking GitHub, Swagger, how-to guides
Phase 05
Consumption & Iteration
From deployed API to successful adoption and ongoing improvement
Current Reality
No unified way to discover internal APIs
"Understanding who uses my API?" — no visibility
Pain Points
No communication channel for breaking changes
Lack of SSO for programmatic token retrieval
Quick Wins
Self-service API access (registration / API keys)
One-stop place for discovering and onboarding to APIs
Session Wrap-Up
What were our top 3 pain points that got the most votes?
What were our top 3 solution ideas we want to pursue?
What surprised you most today — something you didn't expect to hear?
Follow-ups are assigned during session. Each has a named owner and a clearly articulated next decision point before the group disperses.