Product Design Manager · Bezeroo

Defining a configurable platform to control the complete waste journey.

2025 · Present · Management platform · Transport application

Bezeroo operates across regulation, finance, operations, logistics and multiple professional roles. I joined while the product and operating model were still taking shape, established the design function and defined the shared product model connecting the management platform and transport application.

Aerial view of an industrial waste and energy facility at sunset, with tall chimneys rising over a vast grid of processing basins.
RoleProduct Design Manager
FocusProduct leadership · Product direction · Product modelling · Strategic design · Design leadership
StageProduct development
Period2025 · Present
PlatformManagement platform · Transport application

Product challenge

One product had to support different organisations without becoming a different product for each one.

Regulated waste management connects declarations, documentation, billing, collections, transport, treatment, reporting and compliance. Each organisation can apply different rules, permissions and operating structures.

The central product challenge was to separate configurable organisational rules from the shared logic needed to maintain control, traceability and consistency across the complete waste journey.

Different organisations

The platform must adapt to different regulated entities without creating separate products.

Different professional roles

Administrators, producers, waste managers, transport operators and drivers act on different parts of the same system.

Connected operations

Declarations, billing, operations, transport and compliance depend on shared information and coordinated states.

Diagram of the configurable Bezeroo product system at the centre, surrounded by product domains (declarations and documentation, billing and financial logic, waste operations, transport and logistics, reporting and compliance, dashboard and configuration) and the two product surfaces (manager platform, transport app), supported by a shared foundation of actors, roles, states, permissions, documents, rules and traceability.

Product direction

The shared product model and the priorities behind it.

Decision 01

I defined the shared product model behind the platform.

I translated regulatory, operational and technical requirements into a common model of roles, states, permissions, workflows and dependencies. This foundation could then be applied across declarations, billing, waste operations, reporting and transport.

Trade offReusable patterns allow the platform to adapt without losing consistency.

Interior view of an industrial waste facility with conveyor belts, sorting machinery and concrete structures under cool lighting.
Decision 02

I shaped priorities around regulation, operational risk and technical feasibility.

I shaped roadmap priorities across the management platform and transport application, balancing regulatory deadlines, operational dependencies, customer needs and engineering capacity.

The work required deciding which capabilities needed to exist first, which exceptions had to be resolved and how each module would connect to the wider product.

Trade offProduct decisions had to reflect engineering capacity and system dependencies.

A man in a denim jacket checks a smartphone and holds a tablet, with the cab of a truck visible in the background.
Decision 03

One product model connects management and field operations.

The management platform and transport application are connected surfaces of the same system. Planning, execution, evidence, incidents and completion remain linked to the organisations, records and states managed across the product.

Trade offField activity stays connected to the organisations, records and states managed within the wider product.

A man in a denim jacket checks a smartphone and holds a tablet, with the cab of a truck visible in the background.

What I led

I established the design function while the product itself was being defined.

My responsibility extended beyond individual journeys. I established ways of working, structured product decisions and aligned Product, Engineering, business and regulatory specialists around a shared understanding of the system.

I owned
  • Product modelling
  • Product direction
  • Strategic design
  • Design leadership
  • Organisational alignment
  • Experience consistency
I worked with
  • Product leadership
  • Engineering
  • Business stakeholders
  • Operational specialists
  • Regulatory specialists
  • Client facing teams

Connected product surfaces

The management platform connects the complete regulated operation.

The management platform connects declarations, documentation, billing, waste operations, reporting, compliance and configuration through one shared structure. The transport application extends the same model into field operations.

Declarations

Structured progress from initial completion through review, submission, validation and closure.

Manager platform view of a collection request with assigned manager or transporter, status timeline, operational detail, related documents and reception and closure.

Waste operations

Connected requests, collections, reception, storage, treatment and completion within one operational model.

Transport app view showing routes in queue, route in progress, stop details, document access, evidence capture, incident reporting and completion at destination.

Transport application

Connects drivers, vehicles, routes, stops, collections, documents, photographs, signatures, incidents and completion at destination.


Success criteria

Success had to be understood across the complete operation.

Workflow completion

Can regulated and operational processes reach completion without lost progress or context?

Operational control

Can each organisation understand what is pending, blocked, completed or at risk?

Data quality

Does information remain complete and consistent across operations, billing and reporting?

Role adoption

Can each professional role identify and complete its responsibilities without relying on external explanations?

Validation

Because Bezeroo is a connected operational system, success could not be assessed through one isolated journey. I defined measurement priorities around completion, control, data quality and role adoption.

A configurable operating model for regulated waste management.

Bezeroo connects management, operations and transport through one shared product model. Current priorities strengthen configurability, operational control, reporting and consistency across modules.

Configurability · Operational control · Connected workflows · Reporting · Product consistency


Next case

Mapping the kitchen journey to a connected customer experience.

At Leroy Merlin, the challenge shifted from regulated operations to a high consideration retail journey connecting digital tools, specialist advice and physical stores.

Explore Leroy Merlin
Two people annotating a large kitchen journey mapping sheet with sticky notes and printed research artefacts on a warmly lit wooden table.