hola — I'm Mary.

A high-energy product leader — always learning, always up for the next challenge.

Mary Lozada — portrait
product leader · founder (exited) · board member

Four convictions I operate by — each one earned, not borrowed.

01 Product management

Strategy that compounds — features that add up, and growth the product drives itself.

  1. Empathy. The customer defines the problem; the job is to truly understand it.
  2. Business case. The unit economics behind it decide which problems are worth solving.
  3. North Star. One target and a few key metrics, with every bet traced back to them.
  4. Continuous discovery. Constant learning, systematised, so every conversation feeds every team's work.
  5. Roadmap. A living plan worked backwards from the North Star, sequenced so each release unlocks the next.
  6. Translation. Turning customer, business and engineering into one shared language.

The outcome is growth: acquisition, activation, retention and revenue.

02 Cross-functional leadership

The generalist's edge: align the whole org, not just the team.

Founded and exited a specialty-foods group — owned marketing, P&L, compliance & ops; seven years on a hospital board.

03 AI at work

Faster, deeper, surer — or it's just bloat.

Built my own agentic operating system — protocols for every mode of work, session workflows that close with lessons learned, and a compounding skills library. I use it end to end: prototyping, aggregating research, decision support, monitoring builds and stakeholder updates.

04 Refined ambition

Sharpened by constraint, not shrunk by it.

Two kids later: more efficient, more deliberate, more empathetic — with the ambition fully intact.

☆ based in Vienna 🇦🇹

A systems thinker who sees the connections others miss — and a strategist who refuses to stay in the deck. I work the messy middle where business, technology, and real customers collide, because that's where products are actually won.

Beyond the CV

My core working values.

How I manage resources, teams, and my own career — the operating principles under the CV.

Everything has a so what.

Every feature, every deck, every hire, every hour — it either ties back to the bigger picture or it doesn't happen. This is how I manage resources, teams, and my own career: I only move pieces when I'm confident they compound into a greater strategy. Motion is cheap. Compounding is the game.

01

The big picture first — always.

Strategy before tactics. Context before action.

02

The 'so what' second.

Every insight needs a direction. Data without a decision is decoration.

03

Enabling execution third.

Especially across teams — alignment prevents dilution and duplication.

The rest, in seven lines

Strategise away — but without solid execution you might as well be an intern at a Big 4.

Vision without delivery is just a deck.

Your energy is contagious. Like hiccups.

Bring the right kind.

Represent your customers — but always within business context.

Advocacy without commercial sense isn't product thinking.

Burnout isn't from working too much.

It happens when work doesn't feel meaningful or acknowledged.

Don't fall in love with features, products, or ideas. Ever.

Stay attached to the problem. Never the solution.

Include everyone — happy engineers ship faster and with fewer bugs.

Celebrate every win. Big and small.

Own your mistakes. Retros are gold mines.

Acknowledge, learn, improve. That's the loop.

The operating loop
Strategise→ Discover→ Define→ Build→ Ship↺

Adding Strategise at the top isn't a step — it's a lens. It changes why you discover, what you validate, and how you build.

Principles are easy. Arguing them in public is the work.

The talks and essays where I make these arguments live under the pillars. If you want me on a stage, a podcast, or a problem — say hola.

01 · About

Engineer by training, founder by fire, product leader by trade.

Engineering gave me the analysis, the founder years the range, the hospital board the stakes, SaaS the craft — and each chapter built something the next one needed.

The journey so far

Civil engineering at the University of Toronto — graduated with honors — a scholarship exchange at ETH Zürich, then a master's with distinction at UCL. Engineering is where my analytical thinking was forged: decomposing a problem into its forces and load paths. That instinct is the seed of how I operate now — a systems thinker who reads where the weight actually goes, and what's just ornament.

Off the clock

Parent to two small children, DIY and property flipper, a love for specialty foods, Latin dancing, and a conviction that work should have sabor.

Native · EnglishNative · SpanishFluent · FrenchFluent · ItalianLearning · German
Venezuela→Toronto→Zürich→London→Santander→Vienna

See the pillars I write & speak about ⇒

02 · Pillars

What I talk (and write) about.

Four things I think about out loud — on a stage, in an essay, and here as I write them.

✦ Open to speaking & writing — talks, podcasts, workshops
01 · Pillar

Product management

The craft of strategic product — building things that compound, and growth the product leads.

Most roadmaps are motion, not compounding.

Even a single feature needs foresight: build for the reuse you can already see coming.

Talk · Essay

Past, present, future: the three tenses of a good PRD and epic.

Mine your retros, name the problem, design for what's down the roadmap.

Talk · Essay

The problem statement is bigger than you think.

Defining a problem has structure: understanding the ask, why it matters and the context around it, then tying it back to the business case. The problem space is smaller than the solution space, but the extra time spent there is what produces the most distinctive solutions.

Talk · Workshop
02 · Pillar

Cross-functional leadership

The generalist's edge — systems thinking and stakeholder alignment across the whole org.

The context layer everyone's missing.

Some context every department needs: the customer profile, the segments and personas within it, the brand, the business case and management's goals. OKRs are more than a kick-off meeting — when everyone rallies behind the objectives with that shared context, the work adds up.

Talk · Essay

A survival kit for the messy middle.

When many initiatives run at once, someone has to keep reminding everyone what they add up to. That means reading the room, knowing how other departments work and what's on their roadmaps, respecting their timelines and effort, and communicating in a standard way.

Talk · Essay
03 · Pillar

AI at work

How to actually use AI — to get faster, deeper, and more sure.

AI has three jobs: speed, depth, confidence.

If a workflow isn't moving one of those needles, it's bloat. So I pointed product management at myself: protocols for every mode of work, sessions that close with lessons learned, and AI across the loop — prototyping, research synthesis, decision support, build monitoring and stakeholder updates.

Talk · Essay

Building is commoditized. Judgment isn't.

Data for its own sake is bloat: be deliberate about why you run each experiment, and act fast on what it tells you. You can ship features faster, but you can also experiment faster — so make room for experiments on the roadmap, accept what works and what doesn't, and ship what's actually useful.

Talk · Workshop
04 · Pillar

Refined ambition

Ambition sharpened by constraint — an operator and a mother.

The refined ambition of working parents.

More efficient, more deliberate, more empathetic — and what the corporate world still gets wrong about ambitious parents.

Talk · Essay

The essays are coming.

This page grows into writing as I publish it. Until then — if you want me on a stage, a podcast, or a hard problem, say hola.

03 · Work

Proof, not promises.

Four projects, each popping out to its own case study: the competitive analysis, refer-a-friend, the agentic workflow, and the skills repertoire.