Tobias Lubrano

Art & Posters

about me

Tobias Lubrano

Launcher / Product design case study

A better tool.
A reason to switch.

A better tool.
A reason to switch.

A better tool.
A reason to switch.

Turning an unfinished fundraising MVP into a tested release with real customer feedback and AI-assisted prototyping.

Turning an unfinished fundraising MVP into a tested release with real customer feedback and AI-assisted prototyping.

My contribution

UX design, research, prioritization and prototyping

UX design, research, prioritization and prototyping

AI prototyping tools

Cursor · Google AI Studio

Cursor · Google AI Studio

13

13

User interviews

User interviews

3

3

Team leaders in focused prototype tests

Team leaders in focused prototype tests

4.5/5

4.5/5

Early average CSAT

Early average CSAT

01 / The challenge

Familiar didn’t
mean usable.

Familiar didn’t
mean usable.

Fundraisers relied on the existing platform to sign up donors and review performance. For team leaders, understanding how their team was doing meant navigating a complicated statistics experience.

Fundraisers relied on the existing platform to sign up donors and review performance. For team leaders, understanding how their team was doing meant navigating a complicated statistics experience.

The replacement, Launcher, was already in progress when I joined. But its MVP was unfinished, and neither interviews nor testing had established whether it solved the right problems.

The replacement, Launcher, was already in progress when I joined. But its MVP was unfinished, and neither interviews nor testing had established whether it solved the right problems.

The challenge was to make a controlled release possible and give long-time users a compelling reason to switch.

The challenge was to make a controlled release possible and give long-time users a compelling reason to switch.

Legacy

The familiar starting point, with fragmented access to everyday tasks.

Initial MVP

A new interface, but the team-statistics need was still unresolved.

Reworked Launcher

Statistics and direct access to team members take priority.

Dashboard excerpts, cropped to compare the top-level organization.

02 / Release, learn, rework

Ship enough to learn.
Then choose what matters.

Ship enough to learn.
Then choose what matters.

I focused first on the minimum changes needed for a controlled release with one willing customer team. While they used Launcher in the field, I ran interviews and tested a high-fidelity prototype in the new design system.

I focused first on the minimum changes needed for a controlled release with one willing customer team. While they used Launcher in the field, I ran interviews and tested a high-fidelity prototype in the new design system.

01

Make it testable

Address the immediate usability issues needed for a controlled release.

Address the immediate usability issues needed for a controlled release.

02

Learn in the field

Collect feedback after one customer team uses Launcher for a week.

Collect feedback after one customer team uses Launcher for a week.

03

Research in parallel

Interview 13 fundraisers and team leaders, using a prototype to test assumptions.

Interview 13 fundraisers and team leaders, using a prototype to test assumptions.

04

Reprioritize

Combine field feedback and interviews to choose critical fixes and useful improvements.

Combine field feedback and interviews to choose critical fixes and useful improvements.

03 / The product decision

Give people a reason
to change their habits.

Give people a reason
to change their habits.

The first release had to solve a problem worth switching for.

A fresh interface alone wasn’t enough. Team leaders needed to understand individual performance to decide who needed support, how to motivate people, and where to focus their attention.

A fresh interface alone wasn’t enough. Team leaders needed to understand individual performance to decide who needed support, how to motivate people, and where to focus their attention.

Team statistics became the priority because that need remained difficult to meet in both the legacy product and the MVP.

Team statistics became the priority because that need remained difficult to meet in both the legacy product and the MVP.

Prioritize now

Critical usability issues and direct access to useful team statistics.

Critical usability issues and direct access to useful team statistics.

Sequence later

The remaining feature backlog, planned for subsequent releases over the following year.

The remaining feature backlog, planned for subsequent releases over the following year.

04 / Interaction deep dive

Make the person,
not the navigation,
the focus.

Make the person,
not the navigation,
the focus.

I used Cursor and Google AI Studio to turn different statistics interactions into prototypes quickly. That made the options tangible enough to evaluate, test, and revise.

I used Cursor and Google AI Studio to turn different statistics interactions into prototypes quickly. That made the options tangible enough to evaluate, test, and revise.

Cursor + Google AI Studio → interactive prototypes → customer feedback

Cursor + Google AI Studio → interactive prototypes → customer feedback

Explored / 01

Personal & team cards

Switch between separate statistics cards for the two contexts.

Switch between separate statistics cards for the two contexts.

Explored / 02

Team-member dropdown

Select an individual from a list to view their results.

Select an individual from a list to view their results.

Chosen / 03

Avatar switcher

Keep the people visible, with one consistent statistics panel below.

Keep the people visible, with one consistent statistics panel below.

The chosen interaction: switch people while keeping the statistics in context.

Testing changed
the emphasis.

I started with an internal reality check, then tested with three fundraising team leaders.

Earlier versions contained statistics but had no avatar switcher. The team-leader feedback pushed us to foreground statistics and make moving between people central to the experience.

We brought those changes into the version prepared for launch.

AI accelerated exploration.
User feedback shaped what shipped.

AI accelerated exploration.
User feedback shaped what shipped.

05 / Interface craft

The details had
to work together.

The details had
to work together.

The reworked dashboard brought the statistics experience into the wider Launcher interface. The same visual language extends to the achievements flow, including distinct locked and unlocked states on mobile.

The reworked dashboard brought the statistics experience into the wider Launcher interface. The same visual language extends to the achievements flow, including distinct locked and unlocked states on mobile.

Achievement overview: a consistent card system across states.

Mobile detail states: progress before and after unlocking.

06 / Early outcome

4.5/5

4.5/5

Average CSAT from early Launcher adopters

Average CSAT from early Launcher adopters

A positive first signal.
A continuing feedback loop.

A positive first signal.
A continuing feedback loop.

We added CSAT to the released Launcher to hear from customers moving to the new experience. Early responses were encouraging.

We added CSAT to the released Launcher to hear from customers moving to the new experience. Early responses were encouraging.

This measures initial satisfaction, not a demonstrated improvement in adoption or task completion. The remaining backlog gave us a direction for the following year.

Reflection

The key decision
was the sequence.

The key decision
was the sequence.

Make a controlled release possible. Learn from the field. Focus the next iteration on a problem that could make switching worthwhile.

Make a controlled release possible. Learn from the field. Focus the next iteration on a problem that could make switching worthwhile.

Rapid prototypes turned uncertainty into testable interactions. Direct feedback kept the work grounded.

Rapid prototypes turned uncertainty into testable interactions. Direct feedback kept the work grounded.

What I would measure next

Repeat use of the statistics widget, adoption of Launcher, and how easily leaders can find a team member’s results.

Repeat use of the statistics widget, adoption of Launcher, and how easily leaders can find a team member’s results.

Tobias Lubrano

UX / UI Designer & Frontend Developer

Projects

Launcher

Automotive Industry

Hello Austria

Pandora’s Box

Tobias Lubrano

UX / UI Designer & Frontend Developer

Projects

Launcher

Automotive Industry

Hello Austria

Pandora’s Box