I turn complex information, business needs and real workflows into systems that help people understand, decide and work better. Some projects allow me to show the full journey; others belong to professional contexts where evidence needs to be presented more carefully.
Two projects allow me to show the problem, the decisions and the architecture in enough depth to serve as public evidence of how I work.
A prototype built around a concrete operational need: structuring information, prioritizing relevant variables and turning fragmented records into a clearer, more usable follow-up surface.
A system for organizing complex information over time, connecting previously separate documents and making accumulated knowledge queryable with context and traceability.
I do not organize my work around a particular tool. I organize it around the type of problem that needs to be solved.
I transform business questions into clear, reusable analytical structures designed to understand business evolution and support decisions.
Distributed information, inconsistent metrics, and reporting that explains the number but not always the reason.
Analytical models, KPIs, dashboards, automation and executive reporting.
Business analysis, metric design, data quality and the bridge between business and technology.
More structured and reusable analysis systems designed to explain what is happening behind the metric.
Power BI · DAX · Power Query · SQL · Databricks · Delta Lake · Excel · Power Automate
I design query and knowledge-retrieval systems for documentation that is complex, sensitive, and hard to work with manually.
Scattered documents, unstructured information, and the need to query without losing privacy or control.
Anonymization by design, a controlled document corpus, semantic search and applied AI layers with traceability.
Product Owner & Data/AI Lead: functional architecture, data model, document pipeline and progressive AI integration.
A private platform able to organize, version and query complex information while controlling what content the AI layer is allowed to use.
Supabase · PostgreSQL · RLS · Netlify · Semantic Search · AI indexing · Serverless workflows
I apply data and product thinking to real healthcare processes, prioritizing clear workflows and the experience of the people who use the information every day.
Fragmented clinical and operational information, difficult shift handoffs, and systems that do not always reflect the real workflow.
Longitudinal follow-up systems, knowledge structures, trend visualization and multi-device operational prototypes.
Discovery, information architecture, product thinking, functional UX and iterative development with real users.
Turn fragmented information into systems that can be read, navigated and evolved without confusing the tool with the problem it needs to solve.
A concept-validation prototype exploring follow-up, trends and shift handoffs in a clinical setting.
Research is not about accumulating information. It is about building a structure that shows what we know, where it comes from and how it connects.
Information fragmented across sources, disciplines and time, with relationships that are difficult to follow and conclusions that need context.
Knowledge architectures that connect sources, evidence and relationships without losing provenance, evolution or degree of certainty.
Analysis and methodological design: frame the question, structure evidence, model relationships and turn complexity into a reviewable system.
A knowledge system where information can be reviewed, connected and evolved without losing traceability or turning a possibility into a conclusion.
Evidence Mapping · Knowledge Architecture · Longitudinal Analysis · Traceability · Semantic Retrieval · Hypothesis Management
Understand which problem is worth solving. Define who it is for. Structure the information. Design the flow. Build a first version. Observe how it is used. Iterate again. For me, product appears when data, business and technology start working around a real need.
What is happening, what information exists, who needs to use it and what decision the system should help make. That criterion runs through both the projects I can show and the professional contexts in which I have worked.
How I work →Public projects show how I build. My professional trajectory adds the context where many of these capabilities were developed and continue to be applied.
Analysis, business monitoring, information models and Business Intelligence focused on turning data into understandable and usable decisions.
Connecting operational needs, forecasting, analysis and information solutions while keeping the business problem tied to its implementation.
Pricing, margins, profitability, KPIs and reporting to understand business evolution and support commercial decisions.
A specific volunteer collaboration that brought analysis into a different context and reinforced the value of clear, traceable and useful information.
The Deep Dives show the process in greater detail. If you would like to continue the conversation around data, AI, product or HealthTech, you can do so through Contact.
