← Selected impact

E-Net Production

Product ownership · 2017 — 2019

Owning a No-code Product from Backlog to Delivery

How I combined product ownership with frontend leadership for a platform used to build promotional shop-in-shop experiences.

The product

At E-Net Production I owned delivery for a no-code platform used to build and distribute promotional shop-in-shop experiences across retailer and e-commerce websites.

The role sat between client expectations, product decisions and technical delivery. A request could sound simple in a meeting but affect the editor, the generated experience and the way the team would support future campaigns.

Turning requests into a product backlog

I worked directly with client stakeholders to gather requirements and translate them into delivery tasks and milestones. The important step was deciding whether a request represented a reusable product capability or a one-off need.

That distinction shaped the backlog. A no-code tool becomes difficult to use when every exception turns into another option, but it also fails when it cannot represent the real work people need to publish.

Owning the delivery loop

I led the technical team through backlog refinement, planning, daily coordination, retrospectives and client demos. Reviews were not only status updates; they were a way to test whether the delivered behaviour matched the original need.

I balanced business priorities with technical debt and frontend-system development while remaining close to the problems engineers were solving. That helped keep product decisions connected to implementation constraints.

Two responsibilities at once

Alongside product ownership, I was Frontend Team Lead for a distributed group of more than twelve people. I conducted one-to-ones, recruitment, retrospectives and performance reviews while supporting delivery across the wider frontend team.

The overlap made prioritisation especially important. Product ownership required clarity about what the platform should become; team leadership required enough space for people, quality and technical foundations.

What the role taught me

Owning a product did not mean providing all the answers. It meant keeping the problem, trade-offs and next decision visible to the people doing the work and to the stakeholders depending on it.

All case studies →Experience →