Pamela Bonan

Context and challenge

Grupo Sabin was creating a paperless unit without traditional queues, where technology would mediate the on-site journey. The challenge was not simply digitizing steps: patients of different ages and abilities needed to use every interface independently, often while physically and emotionally vulnerable.

As the project’s sole Product Designer, I interpreted the predefined requirements, researched references, structured the flows, and prototyped the check-in kiosk, queue display, collection-room screen, and feedback form.

Design decisions

QR scanning is the kiosk’s primary path, while manual order entry provides a fallback when the camera or code fails. Addressing patients by name confirms successful identification and makes the interaction feel less generic.

The four interfaces were designed as one connected experience. Components, language, and feedback patterns repeat across devices, while each surface responds to its context.

Outcome and retrospective

Following launch, the Digital Unit received the highest Google rating. Public reviews are qualitative signals rather than proof that design caused the outcome, but comments mentioning speed, convenience, QR Code use, and ease of service connect directly to the experience we designed.

Context and challenge

Univerz proposed digitizing the food experience at Coca-Cola Arena, a venue with capacity for more than 20,000 people. The product needed to work in a high-demand context with limited time and divided attention.

As the sole Product Designer, I turned a predefined functional scope into architecture, flows, and a high-fidelity prototype over five weeks, collaborating with the PM and client.

Product decisions

QR Code access removes the need to install an app. Pickup and seat delivery begin in the same flow, avoiding an early split. Personal information is requested only at checkout, when it is necessary for the receipt and order tracking.

Outcome and retrospective

The prototype was completed and approved within the five-week cycle, but did not move into development. The result is therefore a designed and documented solution rather than a claim of market impact.

Identifying the pattern

At Espresso Labs, many projects include admin panels. While content, permissions, and business rules changed, their interface architecture remained predictable: side navigation, tables, filters, forms, states, and dashboards.

I proposed turning the existing Figma component library into a functional foundation that represented interactions and states, reducing the need to document every variation in separate frames.

From library to functional template

I created the original layout, components, and interaction patterns in Figma, then directed the AI through successive refinement rounds. Instead of generating every page from scratch, we duplicate validated models and adapt only the required content and rules.

Do not generate from scratch when a validated pattern already exists.

Early signals and next steps

The template has been used in two projects, producing three admin panels. The process is still being validated; next steps include tracking creation time, adjustment volume, team autonomy, and reuse by Development.