Most products don't fail in design. They fail in execution.

I step in when execution starts to break as teams and products begin to scale. I clarify what’s failing and align systems, teams, and work so execution becomes consistent.

This usually shows up as teams move from early traction to real scale.

01 / Practice

Most teams don’t need more strategy.
They need a system that holds under real conditions.

01.01

Data & Platform Operations

Systems that work in controlled conditions start to fail under real use. This is where things start breaking as teams scale and the system can no longer keep up. Pipelines fail at scale, SLAs slip without warning, and platform teams get stretched past the point where they can keep up.

I step in when the system needs to hold and it doesn't, stabilizing pipelines, tightening operational discipline, and rebuilding what fails under real conditions.

PipelinesData architectureSLAsPlatform engineeringIncident response
01.02

Product & Company Operations

Fast-moving teams outrun their operating structure and generate coordination debt. This typically shows up as the team grows and the original ways of working stop holding. Priorities shift faster than the system can absorb, ownership blurs, and execution turns into a series of partial handoffs.

I redesign how the work runs — rebuilding operating cadence, clarifying ownership, and aligning product, data, and engineering into a system that delivers.

Product operationsCross-functional executionRoadmap deliveryOKRsTeam structure
01.03

Strategy &
Execution

Strategy holds in planning and breaks in execution. It becomes visible as the organization grows and alignment starts to drift. Priorities compete, teams fragment, and the work drifts away from what actually matters. It's the gap between where you said you're going and what's actually happening.

I work directly with leadership to identify where the plan is breaking, define what needs to change, and translate strategy into execution that produces visible, repeatable results.

Strategic planningExecution oversightOKR designOperating modelStakeholder management
02 / About

More than an advisor.
Senior enough to set direction, hands-on enough to run it.

The work starts by identifying where execution breaks and why.

I've spent 15 years running the execution layer across data infrastructure, software products, and company operations — where things needed to ship, not just be designed well.

Often this happens mid-growth, as organizations expand and start adding teams, and the way work used to get done stops holding.

The engagements where I do my best work are the ones where the gap between strategy and delivery is the problem. Where the team is capable but the system isn't holding. Where someone needs to run the work, not manage the person running it. Where the problem is clear, but the system to solve it isn't.

This work becomes useful once there's real traction to protect, not for teams still finding product-market fit.

Based
Sweden
Working
Remote · EU · US · UK
Languages
EN · ES · FR · IT
Background
COO · Data & SaaS
Format
Embedded · Fractional
03 / Engagement

How the work runs.
Structured, but not formulaic.

03.01 Diagnose I get oriented fast: in the system, in the conversations, reading the actual state of the work. No intake forms. No onboarding theater. I ask direct questions and I form a view. Week 1–3
03.02 Align I bring a clear-eyed read of what's actually broken, what needs to change, and how the system should be structured to support it. We agree on scope, milestones, and definition of done before work begins. Week 3–4
03.03 Operate I run the work. Depending on the engagement, that means leading technical delivery, owning operational processes, driving cross-functional coordination, or all three. I'm in the work, not on the sidelines. Month 1–6
03.04 Hand off Every engagement ends with a clear handover: documentation, systems, and the team in a position to run what we built. No indefinite engagements. No dependency created. Month 5–7
04 / Contact