Inigo AnguloContact
Work01How I think02Lab03Writing04
Lead: product strategy and leadership

Senior product leadership, from strategy to execution.

9+ years turning ambiguous, data heavy problems into products people trust: discovery and opportunity identification, strategy, roadmapping and prioritisation, ownership of the outcome, and the design and delivery that follow. At GetYourGuide, ING, WPP and Crowdhouse, in product teams of three to thirty. As a product lead or lead product designer in your organisation, or on an independent engagement when that is what the problem needs.

  • Product discovery
  • Opportunity identification
  • Product strategy
  • Roadmapping and prioritisation
  • Product leadership
  • Cross functional alignment
  • Product execution
  • UX and design direction
02  Product & UX

Senior product and design lead, in one person.

9+ years turning ambiguous, data-heavy problems into products people trust: checkout, onboarding, design systems, dashboards.

10 yrsproduct, design and growth across commerce and complex systems
+11%checkout conversion at GetYourGuide, ten experiments, four markets
5countries shipping from one design system at ING
17 daysfirst commit to production on Acervo, for a private client

When this makes sense

01

Founder led product has stopped scaling

You are the product manager, the CEO and the sales lead. Decisions wait for you, and the team builds what is easiest to specify instead of what moves the metric. Someone has to own the product function.

02

A roadmap full of features, no outcomes

Everything on the list is reasonable, nothing is prioritised by evidence. I bring the discipline of measuring before deciding and killing what does not pay, and I stay until the number moves.

03

A product team without a senior lead

After a reorganisation, ahead of a launch that cannot slip, or because the team has outgrown its founders. I take ownership of the product, its roadmap and its design direction, whether that is a permanent seat or a defined engagement.

How I lead product work

  1. ListenTwo weeks inside your data and your customers: analytics, sales calls, support tickets, the field. I come back with the three problems that matter and the evidence for each.
  2. FrameA roadmap with outcomes, not features. Each item has a number it should move and the cheapest experiment that proves it.
  3. ArchitectI design the system and its boundaries with your engineers: what we build, what we buy, what we do not touch.
  4. ProveExperiments with pre registered success criteria. A/B tests, prototypes with real users, or a thin slice in production.
  5. Close the loopI stay until it ships and the number moves. Decisions are written down with the reasoning, so the team can carry on without me.
A first step that fits most situations

Product opportunity assessment. Two weeks to understand the business opportunity, identify what should be built, define an initial scope, name the risks and dependencies, and recommend an execution approach. It stands on its own and it is how most engagements start, whether what follows is a build, a product lead in the team or nothing at all.

Start with the assessment →

Proof, not promises

GetYourGuide, checkout

+11% checkout conversion from the step nobody was measuring

The team was optimising the wrong step. 38% of converters left checkout and came back with no re-entry experience. Ten experiments later: +11% conversion across four EU markets.

Read the case study →
+11% checkout conversion from the step nobody was measuring

Who this is for

A good fit

  • Series A to C companies with a product team of 3 to 30
  • Founder led products that need a product function
  • E-commerce, marketplaces, fintech and B2B SaaS
  • Product organisations in Zurich, Switzerland or remote across Europe

Probably not

  • You want a deck and no involvement in delivery
  • The decision has already been made and you need a signature
  • You need someone on site five days a week in Zurich (I work hybrid)

Questions I get asked

Permanent role, contract or independent engagement?

All three, and the work is the same: I take responsibility for product outcomes. As a product lead or lead product designer in your organisation, as a contractor for a defined period, or independently on a scoped engagement through my own firm. The format follows the problem, not the other way round.

How does an engagement start?

Two weeks inside your data and your customers, and a roadmap of outcomes with the first experiments shipped. For independent work, scoped by days per week with a fixed number after a first conversation.

Do you work on site in Zurich?

Hybrid. I am based near Zurich and come on site for workshops, kickoffs and the moments where being in the room matters. The rest is remote.

Do you only do strategy, or do you execute?

Both. I run discovery and roadmap, and I stay through design and delivery. I design the flows and the interface myself, and on Acervo I shipped the software myself with AI agent teams; with your team I lead the people who do.

What is the difference between a product consultant and a product lead?

A consultant diagnoses and recommends. A product lead owns outcomes inside the team. I do the second, which includes the first, whichever contract it sits on.

Which languages do you work in?

English and Spanish, both at working level for product and stakeholder work.

Explore a product challenge.

Tell me where the product is stuck. Thirty minutes, no deck; I will tell you how I would approach it and whether I am the right person.

The same profile, other directions

Build, lead and optimize are three dimensions of one product practice, with hands-on design in all of them. The case studies show the same person doing each.