Product is not a role. It's a moment.

In 2026 I took back ownership of product at Buser. Not as a fallback — as a deliberate choice. For that sentence to make sense, I need to be honest about what happened before.

2022–2023: building under constraint

When I took on product at Buser in 2022, the equation was simple to state and brutally hard to execute: cut cost and grow revenue at the same time. The pandemic had shaken the bus travel sector, margins were thin, and every product decision needed a clear economic hypothesis before it became a line of code.

That period taught me something no growth cycle ever could: product, at its core, is making decisions under constraint. When the budget is unlimited, it's easy to confuse activity with results — you experiment with everything, learn a little about everything, and rarely discover what actually moves the business. When the budget tightens, that confusion disappears. You find out fast what matters, because the cost of being wrong is immediate and visible.

Two and a half years building product with real criteria. Not glamorous. Extremely useful.

2024: raising my hand

In 2024, Buser entered a different phase: growth. More users, more routes, more pressure to scale operations and product simultaneously.

And I raised my hand.

I said openly that I wasn't the right person to lead product in that moment. I had never done a scaleup — that specific cycle of scaling a product that already works, multiplying what's gaining traction, managing larger teams in a context of accelerated expansion. I wasn't going to learn that repertoire at the speed the company needed, and pretending I knew would have been a risk I wasn't willing to put on the business.

Ben Horowitz writes about this in The Hard Thing About Hard Things: one of the hardest decisions a leader can make is recognizing that the profile that got the company here may not be the profile that takes it to the next stage. He talks about "management debt" — the debt that accumulates when you delay difficult decisions. Keeping the wrong person in the wrong role for the wrong reason (ego, misplaced loyalty, fear of admitting limitation) is the most expensive kind of management debt there is.

He also makes a distinction that stuck with me: there is a real difference between the leader who builds something big and the leader who manages something big. Different skills, different temperaments, different contexts. Neither is universally superior — there's only the right profile for the right moment.

Handing over the role wasn't weakness. It was the most rational move I could make — for myself and for the company. Most people don't do it because ego is more expensive to manage than any technical mistake.

2026: returning when the moment is yours

Now the context has shifted again. Buser needs the numbers to work — efficiency at scale, economic discipline, product that moves margin without sacrificing growth. This is not a crisis. It's maturity. Those are radically different things.

And this is exactly the repertoire I have. I've run this cycle before. I know how it works. I know where the traps are. I don't need to learn at the company's pace — I can execute at the pace the company needs.

That's why I came back. And that's why it makes sense.

The framework I use to think product in this moment: DHM

Gibson Biddle, former VP of Product at Netflix, defines product strategy with a direct question:

"How will your product delight customers in hard-to-copy, margin-enhancing ways?"

That question is the DHM framework — Delight, Hard to copy, Margin. Simple in form, brutal in application.

Delight: enchantment with purpose

Most conversations about user experience stop at "make the customer happy." DHM goes further: the enchantment that matters is one that also improves the business economics. These aren't opposing forces — they're things that need to overlap.

Biddle's classic example: Netflix customers would say the most "delightful" product would be charging them half the price. But that doesn't sustain enough margin to keep improving the product. So the right delight isn't what customers ask for — it's what they value and what the company can deliver in an economically sustainable way.

In practice, this completely changes how you prioritize. Features users request but don't move retention fall back. Features that seem invisible but reduce churn or increase usage frequency move up the backlog. The product starts being prioritized by impact hypothesis, not by volume of requests.

Hard to copy: what takes years to replicate

This dimension is about defensible advantage — not feature, not polished design, but something structural that a competitor would take years to replicate. Biddle uses Hamilton Helmer's 7 Powers as a reference: scale economies, network effects, accumulated data, brand, switching costs, proprietary process, scarce resource.

At Netflix, the most powerful example is personalization. In 2005, recommendations were clicked in 2% of cases. After two decades of accumulating behavioral data from hundreds of millions of users, that number reached 80%. That's not a feature — it's data infrastructure that no competitor can quickly replicate, regardless of how much money they invest.

The question I ask for every product initiative: if a competitor copied this tomorrow, how long would it take them to reach the same level? If the answer is "a few months," it's not real competitive advantage — it's just execution. Execution matters, but it's not a moat.

Margin: the component product ignores (and shouldn't)

Here's the heart of DHM — and where most product teams fail silently.

"Product isn't finance." That phrase exists in many tech companies, explicit or implicit in the culture, and it's one of the most expensive beliefs an organization can hold. Product that doesn't think about economics isn't mature product — it's product that outsources to another team the responsibility of making the business work.

Margin in DHM doesn't mean "cut costs." It means every product decision needs a clear hypothesis for how it improves the business economics. The levers are many:

• Retention: users who stay longer have their CAC amortized across more cycles — acquisition cost dilutes, margin rises
• Usage frequency: more touchpoints = more revenue opportunity, more data, better personalization
• Self-service: reduces support cost without reducing experience quality — often improves it
• Natural upsell: features that create organic progression within the product, without depending on a sales team
• Price for perceived value: product that delights supports better pricing — delight and margin aren't opposites, they're levers that reinforce each other

What can't happen is product decisions being made without that hypothesis. Not because "product should serve finance" — but because product that ignores economics is product that eventually runs out of budget to exist.

How I run DHM in my current moment

In the context of 2026 at Buser — efficiency at scale, making the numbers work — I deliberately run DHM backwards.

Most teams start with Delight: "what enchants the user?" and then try to fit competitive advantage and margin on top. This works well in growth moments, when there's capital and tolerance to experiment.

In my moment, I start with Margin: what needs to be true economically? What's the size of impact this initiative can have on unit economics? Then I ask: how do we deliver this in a way that also delights — not just that works? And finally: what in this solution is hard to copy, what builds long-term advantage?

This inversion completely changes what ends up on the roadmap. You stop building product "for users" in the abstract and start building product that solves real business problems through a better experience. The difference sounds subtle. In practice, the projects that survive this filter are completely different from what would have entered without it.

Biddle documents this in the Netflix cases: half the strategies they explored failed. The ones that won almost always hit two or three DHM objectives simultaneously — they delighted, created advantage, and improved margin at the same time. Strategies that only delighted without moving margin rarely survived long-term.

What scaleup and discipline have in common

One thing: consistent execution.

I'm not a different person in each phase. What changes is the prioritization criterion. In growth, you bet on breadth — test more, expand the possibility space, take calculated risk with available capital. In discipline, you bet on depth and efficiency — better understand what's already working, remove what moves no metric, improve precisely what matters.

The muscles are the same. The training is different.

Knowing which phase you're in — and having enough honesty to recognize when you're not the right profile for it — is real competitive advantage. Both for the company and for you as a leader.

Product is not a role. It's a moment!