Launchpad Release Management
A release management portal built from scratch to scale the customer experience.
Product overview
Launchpad is a customer-facing release management portal that helps enterprise users access technical documentation, track product updates, and manage integration versions.
Before Launchpad, the release-delivery process ran without a dedicated product: information was passed along manually, documentation was spread across different sources, and customers struggled to track changes.
The task was to build a scalable product from scratch — a single space where customers can find what they need on their own and stay in control of the update process.
Process
I worked across the full product cycle — from research and definition through to final UI and delivery.
I researched users, their roles, goals, and work scenarios, analyzed the business context and constraints, and used that to shape the key UX scenarios, the information architecture, and the MVP structure.
From there I built the interfaces from concepts to final UI, worked through states and interactions, supported development, adapted solutions to implementation constraints, and ran design QA.
Problem
The existing release-delivery process didn’t scale with the product and created a gap in the customer experience.
The main difficulties:
- Fragmented information. There was no single source of truth for releases and documentation, which made finding and accessing materials hard.
- Opaque releases. There was no transparent history of versions and changes, so release updates were opaque to customers.
- Manual information handoff. Information was passed along manually and wasn’t systematized, which limited scaling the process.
- Experience mismatch. The customer experience didn’t match the maturity of the product.
7 screens
Strategy — coming soon
Personas — coming soon
UX artifacts — coming soon
Collaboration
- Product Manager: defined goals and priorities together, translating business requirements into clear user scenarios; joined planning, prepared solution presentations and took part in user-testing sessions.
- Technical Writer: shaped interface copy and content structure, designing the information flow across both the product and the documentation — and we applied the HEART framework together to measure and improve the experience.
- Developers: walked the team through user flows and interactions, discussed technical constraints and opportunities, adjusted designs accordingly and verified the build against the intended design.
- QA: worked with QA engineers through testing to keep the final product true to the design and user scenarios, refining interface details along the way.
Results
The portal became a single customer-facing interface for the product, providing a cohesive context for interacting with it.
Key results:
- Information architecture. Simplified access to documentation and release information through a reworked information architecture.
- Release information (self-serve). Self-serve release tracking with version history and integration updates made the process transparent — without contacting support.
- Onboarding & navigation. Faster onboarding for new teams thanks to a clear structure and predictable navigation.
- Scalability. Scalable structure and design that let the portal grow without losing consistency.
- Product perception. Improved perception of the product as a mature customer solution.
Next project
Artifact box