Metrics are a team decision — only track what drives impact.
1. Unify goals across teams
-
Business wants ROI → I map it to retention + AUM
-
Engineering needs clarity → I define scope + priorities
-
Data needs signals → I define events + KPIs
-
UX wants adoption → I track activation + churn
-
Stakeholders want impact → I show outcomes
2. Define metrics together
-
With business: ROI, conversion, CAC
-
With data: dashboard events, trust score
-
With engineering: latency, uptime
-
With design: drop-off rate, NPS
-
With support: tickets per user, time to resolution
3. Make impact visible
-
We’ll track onboarding time — target: <10 days”
-
If churn > 15%, we iterate UX”
-
Weekly dashboard = 1 source of truth for all”
2. Co- design solutions: define MVP together, shape the US from real use cases, align on what´s realistic and valuable from the start
How I collaborate with stakeholders — and not die trying
Conflict management with stakeholders:
I manage conflicts by listening actively, identifying the real issue, and communicating with transparency and empathy. I keep the conversation focused on the shared goal, provide visibility, document agreements, and never take things personally. If the conflict blocks the business and I’ve tried everything else, I escalate.
How I work with engineering — and not fail
1. Involve engineering early to validate: feasibility, architecture, constraints, and effort estimates before any solution is locked.
2. Co- design solutions: define MVP together, shape the US from real use cases, align on what´s realistic and valuable from the start
3. Prioritize together: always use frameworks like ICE or impact/effort matrices — always balancing business impact with technical complexity and scalability.
4. Run joint refinements: lead refinement sessions with tech and design to refine scope, clarify edge cases, and break down deliverables into actionable tickets
5. Drive sprint clarity: Every sprint has clear goals, ownership, and outcome metrics. I’m present during standups, unblock issues quickly, and maintain async alignment.
6. Measure what we build: I define KPIs together with engineering and data. Post-launch, we track performance and improve based on real metrics and tech feedback.
7. Celebrate outcomes, not just delivery: Engineering is part of success reviews. I make sure their work is visible, impactful, and tied to real business results — not just shipped features.
How I work with design — and not get lost
I collaborate closely with the UX-UI team, consistently incorporating these fundamental principles into our products and services:
1. Focus on the user: put at the customer at the center
2. Coherence: in all devices as mobile, tablet, web and even iwatch
3. Hierarchy: prepare the information in Z-shaped pattern, or F-shaped pattern or lawin mowing
4. Accessibility: I ensure inclusive experiences by addressing auditory and visual impairments in products or services
5. Usability: ease of use using empathy map to answer at this questions
-
What do users hear?
-
What do users think and feel?
-
What do users see?
-
What do users say and do?
-
What are the efforts? and outcomes?
