Product Design

My approach from research and design, to  launch and beyond

PREVIOUS
NEXT

Foundation

Systems Thinking

Focusing on connections, change over time, emerging patterns.
'Zooming out' to the bigger picture while analytical thinking helps me 'zoom in' again.

Accessibility

I design and build for and with people with bodies, not just roles. Whatever I create must respect the physical, mental and contextual limitations of my audience.

Open Source

Design and building knowhow and ethic are to be shared and not guard-railed as proxies to power.

‍

Research and engagement

My goal when doing user research is to gather insights that can minimise uncertainty and increase understanding both about who we are designing for and about who are designing with. It all starts with research strategy. A way to describe what we want to learn, from whom, how and why. This formulation is usually the result of a workshop with product stakeholders. As a principle, I aim for method triangulation: using diverse methods and perspectives to research the same topic.

Data visualisation of field study insights and their relations with design requirements
For Carmeuse, we combined insights from expert reviews, interviews and field observations to generate requirements which then we classified into different design concerns.

The preparation and facilitation of workshops is another cornerstone of my research practice. It is based on coming up with collaborative exercises, preparing supporting material and guiding the participants to complete them.

Three side-by-side office and library scenes with colorful sticky notes showing workshop results on company communication and content themes.
For Stanley/Stella, I organised a workshop to gather user requirements for their intranet. Using the metaphor of a building and its different rooms, I asked participants first to combine different rooms and then ideate about what information they expect in each. The rooms symbolise different purpose specific sections of the Intranet.

Throughout the research phase I always aim for traceability from initial request and evidence that supports it, to research questions it raised, to methods employed to answer the questions, evidence gathered, requirements generated and design decisions triggered. Their implementation and measurement closes the traceability loop I can ideally monitor throughout product development.

Traceability loop in product design.

Cases:

Information Architecture

While with research and engagement I take a deep dive in the social aspect of the product, with information architecture I take a look at the world from within the product and shape its reflection. I use mind maps, JSON schemas, domain models, OOUX and other means to both understand and evolve the data and content layer of the product. The multi-method approach enables both to look at the data from different perspectives and open it to diverse audiences.

Object models from Console.

Console

PARANOISE RADIO - Independent contributor

Wireframes

Once the information architecture was stable enough to design against, I used it to identify user flows. 

The flows follow the radio journey established during research. Programming, scheduling, production, sharing, and publishing become both the primary navigation of Console and the organising logic for its modules. Modules are assigned to different members, according to their current responsibilities.

Identified user flows

For each flow I create detailed blueprints that capture user actions and system responses.

Example of user flow. Submitting a prerecorded show episode. Click to enlarge

Interface design

The interface extends the visual principles of paranoiseradio.com, drawing additional influence from music production software and hardware. The aim is to make Console feel part of Paranoise while giving operational information the clarity and density needed for repeated use.

Production module: submitting a prerecorded show episode.

Design decisions:

  • On login, Console opens the Production module with the resident’s next slot selected and the slot menu collapsed. Users can expand it to choose another slot.
  • The initial screen is an upload surface accepting artwork, an MP3, or both, allowing residents to begin with whichever asset is ready.
  • The interface adapts to the uploaded assets: an image editor appears for artwork, an audio player for an MP3, and the complete submission form if both are present.
  • Before submitting, residents can review the selected slot, metadata, artwork, and audio.
  • Validation identifies missing or unsupported material without discarding successfully uploaded work.
  • Submitting creates an EPISODE, links it to the selected SLOT, and triggers the server upload, playlist assignment, and scheduling workflows.
  • Console reports each workflow outcome independently, preserves completed steps, and escalates failures to Ops for manual resolution.
  • Once processing is complete, the resident receives a confirmation email with the generated visuals attached.

Outcome and next steps

Console has already changed episode submission from a sequence of disconnected operational tasks into a coordinated workflow. The live product has demonstrated measurable value while giving me the evidence needed to identify where its first architecture no longer supports the organisation.

Next steps include:

  • Migration to the designed data model.
  • Prioritisation and roadmapping of user flows to be developed with Paranoise members.
  • Setting up a design system.
  • Incremental implementation of user flows.

Reflection

This project reflects how I approach AI-assisted product development. Building V0 quickly was useful: it put a real tool in front of residents, reduced work, and exposed constraints that a speculative design process might have missed. But I traded off speed with scalability.

The lasting lesson is to use rapid implementation with intent. A narrow first release can validate value, but the product must eventually be reconciled with the domain it serves. In Console, that means moving from automating a submission to building a web radio operations platform.

I shipped a focused tool that delivered measurable value, used real adoption to discover the limits of its architecture, and redesigned the system around the way Paranoise actually operates.

PREVIOUS
NEXT