I make sure the data is real.
Before I use a number, I check it with whoever produces it: Data, Sales, or Operations. That way the diagnosis starts from numbers the whole team trusts.
PRODUCT & GROWTH DIAGNOSIS · SERVICE 01
Know where conversion leaks before you redesign.
A diagnosis for teams that know a metric isn't moving but aren't sure why. You walk away with a clear report on what's holding back your growth, what fixing it is worth, and what to do first.
Leandro Balbian · Growth Product Manager & Product Designer · 8 years in B2B SaaS and marketplaces
- FOR
- Heads of Product, CPOs, Growth teams, and founders
- DURATION
- 3 weeks
- FORMAT
- 3 live sessions + async work
- YOU LEAVE WITH
- A clear priority and a proposal ready to build
02 / THE PROBLEM
The symptom is visible. The cause almost never is.
The metric dropped, people abandon a flow, or a feature doesn't get adopted. The whole team sees that. What isn't clear is why, and without a shared cause, every area pitches its own fix.
- Conversion changed, and product, business, and tech each have a different explanation.
- The dashboard says one thing and the sales team sees another.
- You already redesigned something and the metric didn't move.
- There are more ideas on the roadmap than capacity to build them.
THE REAL COST
The cost isn't the analysis. It's the sprint spent solving the wrong problem.
03 / HOW I DO IT
How I figure out what to solve.
I cross-check the sources.
I compare what users do, what it costs the business, and what shows up in real sessions. One source shows the symptom; cross-checking shows the cause.
I turn the finding into a decision.
I size what fixing it is worth, check feasibility with engineering, and turn it into a concrete proposal with a metric to tell whether it worked.
04 / TOOLS
I work with the tools your team already uses.
BEHAVIOR
Google Analytics 4
Where users drop off and at which funnel step.
SESSIONS
Microsoft Clarity
Why they drop off: heatmaps and recordings of real sessions.
BUSINESS
Metabase
What it costs the business: leads, conversion, and revenue.
If your team uses other tools, I'll work with what you already have.
05 / WHAT THE 3 WEEKS LOOK LIKE
Three weeks, three live sessions, and a decision at the end.
BEFORE WE START
Access and context
WHAT I DO
I review the brief and the tracking you have.
WITH YOUR TEAM
Read access and the metric you're worried about.
WEEK 1
Discover
WHAT I DO
I validate the data and map the user journey.
WITH YOUR TEAM
Kickoff session (60 min).
WEEK 2
Diagnose
WHAT I DO
I cross-check the sources and isolate the cause.
WITH YOUR TEAM
Findings review (60 min).
WEEK 3
Decide
WHAT I DO
I size, prioritize, and put the proposal together.
WITH YOUR TEAM
Final presentation for leadership (60 min).
Recommended: a PM and someone from Data join all three sessions.
06 / WHAT YOU GET
Four deliverables, and what you can do with each one.
Problem diagnosis
FORMAT
1-page document + data appendix
WHAT YOU DO WITH IT
Present it to leadership so product, business, and tech work from the same explanation.
Validated baseline
FORMAT
Dashboard or reproducible query
WHAT YOU DO WITH IT
Measure any change against the same number, without arguing about where it comes from.
Prioritized friction map
FORMAT
Impact/effort matrix
WHAT YOU DO WITH IT
Plan next quarter's roadmap with clear criteria.
Solution proposal and measurement plan
FORMAT
Brief ready for an RFC or ticket
WHAT YOU DO WITH IT
Your team takes it into development, or we turn it into an experiment.
It can end in an experiment, an operational fix, a tracking correction, or a product initiative. Not necessarily a redesign.
07 / AFTER THE DIAGNOSIS
The diagnosis doesn't have to end in a document: I can also design the solution.
The diagnosis doesn't include final design or development. When the team decides to move forward, I continue with the same context, without re-explaining the problem from scratch.
- 01 Diagnosis (you are here)
- 02 Experiment
- 03 Product
02 · GROWTH EXPERIMENTS & ACTIVATION
Test the solution before building all of it.
I design the experiment, the flow, and the success metric so you can decide whether to scale, iterate, or kill it.
03 · COMPLEX PRODUCT DESIGN
Design the full solution.
UX/UI for SaaS, B2B platforms, and marketplaces: flows, roles, a design system, and a handoff engineering can implement.
08 / RELATED CASE STUDIES
The method, applied to real cases.
09 / NEXT STEP
Tell me which metric won't move, and I'll tell you where I'd start.
Give me a quick rundown of what's going on and I'll reply with a first take on your situation.
How much of my team's time does it take?
Three 60-minute live sessions, one a week. Outside those sessions, I just need a PM and someone from Data to answer quick questions asynchronously.
What if our analytics are broken or incomplete?
That's not a blocker. Part of the diagnosis is checking which data is reliable and which signal is missing. Where tracking falls short, I lean on business data and real sessions, and fixing the tracking can be one of the deliverables.
Can we sign an NDA?
Yes. If your company needs one, we sign it before you share any access.
When can we start?
After an initial conversation. We kick off as soon as read access and the kickoff date are set.