• SHIPPED
Unification of projects, versions, designs and libraries. All in one.
Central Launcher
Platform
One place for projects, versions and libraries. Unified by design.
Eliminated version chaos across 100+ users, cut support overhead by 50%, and shipped in 4 months. Here's what worked, what didn't, and what's next.
-
Product design
Stakeholder management
Interactive prototyping
User research & testing -
Desktop
-
Design Lead
-
4 months (MVP)
-
100+ daily users
-
1 Designer, 3 engineers
Problem
Clearing up version inconsistencies
Developed software solutions were available in different versions on the systems of individual people. This led to problems in obtaining and distributing current project statuses, which in turn caused frustration both with customers and between employees.
Recognizing this, we saw this as an opportunity to help users experience a smooth, brand-aligned, and user-friendly workflow while getting everyone on the same page.
Research
In the early stages of the project, we interviewed and surveyed over 25 participants to understand their use-cases and struggles.
Common Pain Points
Version Fragmentation
The absence of version control allowed multiple conflicting versions to coexist, fragmenting the entire software landscape.
————————————————————————————————————————-
Distribution Inefficiency
Version misalignment across teams caused compatibility breakdowns and unclear feature expectations, disrupting distribution flows.
————————————————————————————————————————-
Productivity Loss
Mismatched software versions forced teams to constantly troubleshoot compatibility issues, draining time and focus.
————————————————————————————————————————
Solution
One coherent
software platform
The goal of the central launcher platform is to give users an optimized & user-friendly way of software distribution. Products, versions and services are presented in a correct, professional, appealing way ready to be shared any time.
Key features of the central launcher platform include:
The same software version for everyone
————————————————————————————————————————
Easy software procurement and sharing
————————————————————————————————————————
Overview of the entire software catalog————————————————————————————————————————
Brand-consistent presentation / identity preservation
————————————————————————————————————————
Unifying software versions.
The central launcher platform gives users a user-friendly and optimized way of software distribution. Now products, versions and services are presented in a correct, professional, appealing way ready to be shared any time.
One coherent
software platform
100%
Version Consistency
All users on current versions within 30 days of launch
RESULT
The Real Win
Beyond the numbers, we fundamentally changed how people thought about software updates. Updates went from "that thing I avoid" to something that just happens. Customer confidence in our tools increased measurably and complaints about "using the wrong version" dropped to near zero.
IMPACT
Business Impact
The centralized platform reduced IT overhead significantly, allowing the team to focus on strategic initiatives rather than firefighting version issues. Customer satisfaction scores improved markedly, with specific praise for the professional, reliable software experience.
Within 3 months of rolling out these updates:
90%
Distribution Time Saved
Manual deployment changed from 4 hours to 20 minutes
50%
Support Tickets Down
Version-related issues dropped from 120 to 60 monthly
Impact
JUST ENOUGH PROCESS
How We Got Here
Fast iteration, constant validation, minimal documentation debt.
WEEK 1 - 2
Research Sprint
Interviewed 25 users (employees + customers), analyzed 6 months of support tickets, and mapped current workflows. Key insight: people didn't hate updates, they hated uncertainty. They never knew if they were on the right version or if an update would break their workflow.
WEEK 1 - 2
Research Sprint
Interviewed 15 users (employees + customers), analyzed 6 months of support tickets, and mapped current workflows. Key insight: people didn't hate updates, they hated uncertainty. They never knew if they were on the right version or if an update would break their workflow.
WEEK 1 - 2
Research Sprint
Interviewed 15 users (employees + customers), analyzed 6 months of support tickets, and mapped current workflows. Key insight: people didn't hate updates, they hated uncertainty. They never knew if they were on the right version or if an update would break their workflow.
WEEK 1 - 2
Research Sprint
Interviewed 15 users (employees + customers), analyzed 6 months of support tickets, and mapped current workflows. Key insight: people didn't hate updates, they hated uncertainty. They never knew if they were on the right version or if an update would break their workflow.
